SMS 2003 clients not assigned?

[dave2korg]

All,

I am new to SMS 2003, and have recently switched over from HP Openview CCM. Before you read, the accounts used for SMS have been tested with openview and have full domain administrative priveledges. As well, AD has been extended and information has been published inside the system management folder.

I have installed SMS 2003 in AD and configured all the search agents with appropriate settings, as well as the network discovery with the appropriate subnet and domain for my 50 machine network.

I can see the systems come up under collections, but all appear to be unassigned.

I recently uninstalled openview from the server, and decided to shift to SMS since it will support licensing queries. I noticed the client executible comes up with the same exe name as openview; so to attempt to avoid this i (attempted to) push the advanced client with the option of 'always repair or upgrade'. With no success to a test machine, i am left to ask questions.

 

[tbrennans]

You need to configure the boundaries (whether AD or IP subnets) in sms to let the client know what sms site server it belongs to.

 

[dave2korg]

Site boundaries have been configured with both the subnet and domain site.

 

[tbrennans]

Well...

If they are not showing as assigned then they probably arent :-D

Open the admin console then right click on the "XXX - Site name" container and choose properties.

Select the "Site Boundaries" tab and see what's in there.

By default only the subnet that the site server exists in is input for you automatically.

You cant put a class b subnet in if its really a class c

so if you were to put in 10.0.0.0 and the subnet was really 10.10.10.0 it wouldnt work. You have to put in what is really the actual subnet.

 

[dave2korg]

i removed the subnet all together after making this post. so just the AD site is there.

our ip subnet is 10.10.2.x and 255.255.255.0
that subnet was in there
machines that i want to administrate with SMS are in that subnet. our webservers and db servers are in a different subnet.

 

[tbrennans]

Make sure the AD site that you have doesnt include the subnets you dont want sms to manage, when that is good, go to your all systems collection right click and go to all tasks, select update collection membership then refresh the collection. See if that updates everything so that is assigned

 

[dave2korg]

i right clicked one of the machines, and it had listed as the site name Default-First-Site-Name

so when i added that to site boundaries (my domain was there as well) and updated, all of my workstations became assigned.

where do i go to change from 'default-first-site-name' to my domain's name?

 

[tbrennans]

hmmm Well this is getting into AD setup, something I prefer not to give advice on!

What I would recommend, is that if you arent comfy in the AD setup that you stop, and remove the AD site name from SMS and go with the IP subnet ranges. The main benefit you will get from using AD sites is that you will be able to globally roam from SMS site to SMS site.

If you have 50 clients, this surely wont be an issue.

After you change that back to the subnets, once again go in and update and refresh the collection and you should be in business.

 

[ncotton]

In the Sites and Services Tab, make sure the SMS Server box (machine) is placed in the SMS site that you created, as a server can only be a member of one site. If it is reporting DFSN, then the server is in DFSN branch of the site tree.

Neil J Cotton
njc Information Systems
Systems Consultant
HND, BSc HONS, CCNA, BCS, IETF, DMTF

 

[dave2korg]

Neil

I changed that to reflect my company's name. Thanks

 

[ncotton]

No problem.

As Tim said...there is no opperational difference between working with oclet'ed subnets or AD Sites as far as the boundaries are concerned. It is just easier to manage, cause you have your site definned at one central management location. If you want to include a new subnet, you just add it to your AD Site in ADS&S, rather than going through any references to it in SMS, and any other sytems that work with subnets and ADSites.

I recommend AD Sites, but again, makes no difference to performance.

Neil J Cotton
njc Information Systems
Systems Consultant
HND, BSc HONS, CCNA, BCS, IETF, DMTF