Setting the FSP & SLP registry values.

Nov 17, 2011 at 1:42 PM

Here is another quick one...

Possiblely as a client health check option overwrite/populate the FSP & SLP registry values so as to assist with the client assignment and reporting process. I know personally some clients have required the SLP server name to be set before successeful client assignment would occur. Without doing this the only other option is those cases is an agent reinstall. The choosing the correct values could maybe taken from the defined agent install switches. Maybe the remote health check process would only overwrite an existing value if the coresponding agent install switches have been defined within the HTA.... just thinking aloud late at night here in Aus.

Cheers

Ben

Nov 17, 2011 at 1:48 PM

I just recently wrote a PowerShell script that I used to [remotely] migrate ConfigMgr 2007 SP2 R3 clients from one primary site to another. As part of this process, I set the FSP and SMSSLP registry values. If interested, feel free to e-mail me @ pcgeek86@gmail.com.

Cheers,
Trevor Sullivan
http://trevorsullivan.net 
http://twitter.com/pcgeek86 

Nov 17, 2011 at 9:02 PM

Thanks guys! This seems like a useful feature and I'll add it to issue tracker.

After some research it seems these are the registry values on client that should be modified remotely:

SLP Server: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\SMSSlp
FSP Server: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\FSP\HostName

 

Nov 17, 2011 at 10:26 PM

Sorry I didn't state the registry keys, it was late at night and I couldn't recite them from memory... :)