Home > SCCM, SCCM Operating System Deployment (OSD), Windows XPE > Generate a new GUID for the SCCM Client

Generate a new GUID for the SCCM Client

It was not until I started working on getting our HP Thin Clients to work with SCCM imaging that I had to worry about generating a new GUID for the SCCM client without doing a repair or reinstallation.  You see the HP t5720 is really the thorn in my side.  The HP t5720 devices we have are 80% of our thin client population and only have 512MB of flash disk and 512MB of RAM.  In order to get the SCCM client to really work well with Windows XP Embedded 2002 it is ideal to have Service Pack 3 (SP3) for the OS.  What really hurts with that is there is not much free space left – even after removing the HP preload utilities that we do not use.  In fact there is not enough space to install the SCCM client.
Keep in mind that we are not joining these devices to the domain, patching them, or doing much more than a few configuration changes and enabling reporting and remote tools.  We use the HP Enhanced Write Filter (EWF) to lock the devices down and purge unwanted changes.
So, I hijacked a 1GB flash drive from a HP t5730 and set down the path to create my image (I will have another entry on the steps to having an image for these devices work with SCCM OSD soon).  Specific to the SCCM client I had to make sure I accomplished the following:
  • Not to have a repair or reinstallation occur post image
  • Be 100% certain that the “SMS Agent Host” is running and the client is fully functional
  • Ensure that the SCCM client has a unique GUID

To accomplish this I had to break out the SMS 2003 Toolkit (I needed “ccmdelcert.exe” and “tranguid.exe”).  I wrote a VBScript that did the following and was part of the larger process that, as I mentioned, I will post later (timing between these items will be detailed in that post as well).

  • Delete SMSCFG.INI (located in C:Windows)
  • Stopped the “SMS Agent Host” service (need to restarted the SCCM client to generate a new SMSCFG.INI file)
  • Started the “SMS Agent Host” service
  • Ran TRANGUID.EXE (this is what will regenerate the GUID and force the SCCM client to talk to the server)

In the end I have an image that can drop down to a HP t5720 with a 512MB flash drive that generates a unique GUID for SCCM and all of the client functionality exists.  To this point we have not found any issues.

  1. Fernando
    May 26, 2011 at 1:54 am

    Todo ok.
    Muchas gracias Josh.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: