Testing SLP Availability
Hi all,
A quick one from me. Ever had site discovery issues on your client machine?
You can stick one of the following into your web browser to confirm that the Server Locator Point is up and running:
If you use AD Sites for boundaries
https://<slp>/sms_slp/slp.dll?site&ad=<AD Site Name>
If you use IP Subnets for boundaries
https://<slp>/sms_slp/slp.dll?site&ip=<Client Subnet ID>
If you use IP ranges
https://<slp>/sms_slp/slp.dll?site&ir=<Client IP Address>
Or if you use a combination you can concatenate the parameters
https://<slp>/sms_slp/slp.dll?site&ip=<Client Subnet ID>&ad=<AD Site Name>&ir=<Client IP Address>
So in my test environment if I run the following:
https://svr-cen/sms_slp/slp.dll?site&ip=192.168.10.0&ad=Default-First-Site-Name&ir=192.168.10.10
I get this response:
If I make my SLP unavailable, in this case disabling authentication:
Entering an invalid / undefined boundary
This post was contributed by Rob York, a Premier Field Engineer with Microsoft Premier Field Engineering, UK.
Comments
Anonymous
January 01, 2003
This article, that was published today on Microsoft’s Manageability blog, got me thinking:- http://blogsAnonymous
January 01, 2003
This article, that was published today on Microsoft’s Manageability blog, got me thinking:- http://blogsAnonymous
June 30, 2011
Good work Rob. It would be worth noting that if a customer is using System Center Operations Manager then even if they are not using the Configuration Manager Management Packs then this would be a good synthetic transaction to setup in Ops Manager.Anonymous
September 19, 2013
Note that this does NOT work in SCCM 2012. If anyone finds a link that serves the same purpose in SCCM 2012, say something.Anonymous
October 28, 2013
This shows my management point in SCCM 2012: http://sms2/sms_mp/.sms_aut?MPLOCATION&ir=10.0.0.0&ip=10.0.0.123 the ad=Default-First-Site-Name part does not seem to work