for me, i fixed this by adding "everyone - read" permissions in IIS on the default website for the section "CCM_CLIENT".
I figured this out by specifying a fallback status point using FSP=<server> in the command line. The FSP can be your MP. The FSP log was telling me that the client could get the ccmsetup.cab due to permissions issues.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.