jrobins Posted January 16, 2014 Report post Posted January 16, 2014 We are having an issue with some laptops and machines that are turned off overnight not downloading necessary items for the SCCM 2012 client install. We are going through the upgrade from 2007 to 2012 and are manually installing the client through the SCCM console. Now that we have gotten the majority of our clients up to the 2012 version, we are planning to push the client going forward through WSUS. Unfortunately, BITS is not allowing the update to come down in the time that some machines are on the network. After some digging, we have concerns that the Group Policy setting for the command line properties are being ignored. We have the Group policy set as follows: /mp:oursccmserver.domain.com / service / forceinstall / BITSPriority:FOREGROUND SMSSITECODE=PRISITE FSP=OURFSP.domain.com However, the command line entry in the ccmsetup.log file on machines that have received the client as well as those not installing is showing the following: - Ccmsetup command line: "C\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf - Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. Can someone tell me why it is not picking up the settings in the registry? we have verified the settings are hitting the machines from GP, just does not seem to be using them which is why we thing it is allowing BITS to throttle the download of the pre-reqs. Thanks in advance for any suggesstions/help. Quote Share this post Link to post Share on other sites More sharing options...
