Resources for IT Professionals >
System Center Configuration Manager Forums
>
Configuration Manager Operating System Deployment
>
Why is SCCM client installed when already in image?
Why is SCCM client installed when already in image?
- I may have asked this before so apologies if so
I'm just testing Win 7 deployment using standard SCCM created TS via the wizard. When you capture the package the SCCM client is included
When deploying the client, it appears, is reinstalled from scratch - Just that it adds another 5 minutes to the overall build
Was just wondering why its necessary to install client when it has already been installed via the capture TS
Whilst on the subject of speed I recall there's a pause of 90 seconds I think between package installs. Is that still the case in SP2?
Thanks
Ian Burnell, London (UK)
All Replies
- Not sure if this applies to win 7, so forgive me if I'm wrong. My environment is XP SP3 and SCCM 2007 R2. When we build an OS image for deployment, one thing that needs to happen is the correct preparation of the SCCM client, so as to avoid duplicate entries in SCCM. This includes stopping the agent and removal of certificates. http://technet.microsoft.com/en-us/library/bb694095.aspx
This may why it is installed in the TS post installation. If you aren't correctly preparing the client as part of your capture TS, you should look at above link.- Marked As Answer byEric Zhang - MSFTMSFT, ModeratorWednesday, December 02, 2009 9:51 AM
- Unmarked As Answer byIan Burnell Wednesday, December 02, 2009 11:16 AM
- Hi Ian,
Before capturing image on the Mater computer which installed with SCCM client, you need to perform some preparation work, see the steps in the technet article that Rob provided. - Interesting - so you're saying that the standard wizard created capture task to install the client is not enough i.e. you must add some vbscript or other code into the TS to further strip the SCCM client before it can be considered "ready" for the image
So that being the case before I reinvent the wheel is there any code or anything out there I can use as a template - in my testing I'm using mixed mode so unsure if there are any computer specific templates
Ian Burnell, London (UK) - Doesn't the Microsoft Deployemnt Toolkit do this?
And on your other question, SP2 includes the hotfix in the client to cure the 90 seconds delay between packages. - Thanks Neil - I don't suppose you'd know what action or better still VBscript you're referring to in MDT?
Ian Burnell, London (UK) - This is not answered
I investigated this and my understanding is the SCCM task sequence "Prepare Configmgr Client" does what is in the KB article listed i.e. removes site code stops service etc. Therefore the client in the image should be "sid neutral" for want of a better word
Therefore same question. When doing a deployment using this captured image the TS to setup windows and configmgr REINSTALLS the client - ccmsetup.log states that the client is present and is the same version but still does a reinstall - which takes at least 5 mins and then the client initialises which takes another 2-3 minutes i.e. about 8 minutes lost - which I can't understand given the client is prepared and in the image
Ian Burnell, London (UK) - Is there anyone from Microsoft who could answer this ?
When running the TS item "Prepare Configmgr Client" as part of the capture it runs osdpreparesmsclient.exe
Here is part of the smsts.log from the capture
Stopped the service 'ccmexec' successfully PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Successfully stopped the client agent service. PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
UnAssigning the SMSClient succeeded PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Removing SitePolicy succeeded. PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Successfully opened client certificate store. PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Deleted 2 SMS certificates PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Deleting Client properties from file C:\Windows\SMSCFG.INI succeeded. PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Reseting the Trusted Root Key successful PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Deleting instance of 'CCM_Client' successful PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Successfully reset Registration status flag to "not registered" PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Successfully disabled provisioning mode. PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Deleted 18 instances PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Policy cleanup done PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Setting startup type for 'smstsmgr' service to manual.. PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
'smstsmgr' service is configured to be manual PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Execute method succeeded PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
SMS Client has been successfully prepared for OS capture PrepareSMSClient 11/11/2009 09:26:40 292 (0x0124)
Process completed with exit code 0 TSManager 11/11/2009 09:26:40 1756 (0x06DC)
!--------------------------------------------------------------------------------------------! TSManager 11/11/2009 09:26:40 1756 (0x06DC)
Successfully complete the action (Prepare ConfigMgr Client) with the exit win32 code 0 TSManager 11/11/2009 09:26:40 1756 (0x06DC)
If you look in there unless I'm mistaken it does all the things required in the documentation i.e. stops execmgr service, remove certificates and removes the assigned site code
Therefore back to the original question, why does it need to reinstall the client completely during the setup windows and configmgr task ?
I estimate this to take 5-8 mins (extra) during each build - if a manager is standing behind you waiting for his/her pc its a bit difficult to explain :)
Ian Burnell, London (UK) - I think the answer is, you don't really need to, but...
As far as I can tell, the client in the image should be in a state where it can easily be enabled using some vbscript actions (assigning a site code for one).
Unfortunately, taksequences execute the modification of the unattend file (replacing variables with ts variables, and settings in the ts) and the installation of the configmgr client in one task sequence step (Setup windows & configmgr).
Given some time, I think you could separate them and build your own (setup windows) step, which customizes the unattend file, and a setup configmgr step which would set the client's sitecode
"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
