endless543

For anyone that is stuck with a similiar situation; apparantly Microsoft is aware of the issue and suggested the following fix: http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2012/02/03/kb2509007-does-not-install-correctly-when-installed-at-the-same-time-as-kb977203-or-kb977384.aspx 3 days of sleepless nights. Glad it wasn't something I was doing wrong.

Hi Guys, First off, let me say thanks to all the contributors of this forum. The guides I have found in here has helped me greatly in getting SCCM 2007 SP2 R3 configured and in production. Our environment is a single central primary site with ~350 clients. My OSD task sequence for Setup ConfigMgr has been working fine with a single PATCH (KB977384) addition to the installation properties. The Properties look like this: SMSSLP=SCCMServer FSP=SCCMServer SMSCACHESIZE=8000 PATCH="%_SMSTSMDataPath%\OSD\SVL00012\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp" Note: Package ID has been verfied to be the Configuration Client Manager The problem arose when I tried to apply my deployment task sequence for new Window 7 laptops with Software Updates packages that were advertised to my "Unknown Collection" during PXE boot. The TS detected 40+ available updates but got stuck at the progress "Downloading Updates (0%)". Searching on the web yeilded another hotfix KB2509007 that needed to be applied with the client. My new Setup ConfigMgr property now looks like this: SMSSLP=SCCMServer FSP=SCCMServer SMSCACHESIZE=8000 PATCH="%_SMSTSMDataPath%\OSD\SVL00012\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp";"%_SMSTSMDataPath%\OSD\SVL00012\i386\hotfix\KB2509007\sccm2007-SP2-KB2509007-ENU.msp" I have shared my root Site share with Domain Computer access as well as read security access to the Client folder. When I initiate my TS from PXE >>> WinPE to setup a new laptop; it fails during Setup ConfigMgr and errors out to full Windows without completing the rest of the TS. Let me know if you would like to see SMSTS.log, CCMSetup.log, or Client.MSI.log... Please help! Going bald soon and have been waking up in the middle of the night thinking about this... Update: The logs are giving me an error 1635 which leads me to permissions; but I can't what can be wrong. I might end up recreating the package and updating the Distribution Point. Attached are my logs: ccmsetup.log client.msi.log last.error.client.msi.log

Hi Guys, First off, let me say thanks to all the contributors of this forum. The guides I have found in here has helped me greatly in getting SCCM 2007 SP2 R3 configured and in production. Our environment is a single central primary site with ~350 clients. My OSD task sequence for Setup ConfigMgr has been working fine with a single PATCH (KB977384) addition to the installation properties. The Properties look like this: SMSSLP=SCCMServer FSP=SCCMServer SMSCACHESIZE=8000 PATCH="%_SMSTSMDataPath%\OSD\SVL00012\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp" Note: Package ID has been verfied to be the Configuration Client Manager The problem arose when I tried to apply my deployment task sequence for new Window 7 laptops with Software Updates packages that were advertised to my "Unknown Collection" during PXE boot. The TS detected 40+ available updates but got stuck at the progress "Downloading Updates (0%)". Searching on the web yeilded another hotfix KB2509007 that needed to be applied with the client. My new Setup ConfigMgr property now looks like this: SMSSLP=SCCMServer FSP=SCCMServer SMSCACHESIZE=8000 PATCH="%_SMSTSMDataPath%\OSD\SVL00012\i386\hotfix\KB977384\sccm2007ac-sp2-kb977384-x86-enu.msp";"%_SMSTSMDataPath%\OSD\SVL00012\i386\hotfix\KB2509007\sccm2007-SP2-KB2509007-ENU.msp" I have shared my root Site share with Domain Computer access as well as read security access to the Client folder. When I initiate my TS from PXE >>> WinPE to setup a new laptop; it fails during Setup ConfigMgr and errors out to full Windows without completing the rest of the TS. Let me know if you would like to see SMSTS.log, CCMSetup.log, or Client.MSI.log... Please help! Going bald soon and have been waking up in the middle of the night thinking about this...