Tuesday, October 19, 2004 2:21 PM
philipnet
Assignment and network discovery
It seems that site assignment and network discovery go hand in hand.
Or at least that's what some rough tests show.
In my bid to re-setup our (new) SMS server on a site which already has the SMS client in most existing PCs and on every new or re-setup PC (as it's on our image) I've had the luxury of some knowledge and a little bit of time. Conversely when I/we/us setup up our test SMS server before we hardly new anything, but had loads of time to get it right
.
First of all I setup the site boundaries. I thought that if I just limited it to Active Directory and just did an Active Directory discovery then everything would be sorted and SMS wouldn't do it's impression of DoS-ing the network
. I was wrong. I had to have IP address ranges included in the boundary or else the SMS server wouldn't include itself in the site.
Secondly I had to turn on network discovery in order for SMS to assign site codes to all our machines (and we only have one site).
That was yesterday and now about 60% of the machines have been assigned to a site. The remainder were most likely turned off last night when the network discovery was run.
So I'm off now to configure our SMS server to DoS the network once a week.
It's not as if people are complaining that our network's slow enough already
.