OperatingSystemNameandVersion is Null

[fostergr]

Can anyone explain to me why the client property OperatingSystemNameandVersion would remain null? I have about 500 clients that are all installed and assigned. About 200 have this field as null, hence I can't query for OS version successfully. The other 300 are fine. The 200 in question are all on the same subnets as those that have reported the property. Some are NT and some 2000.

I am running SMS 2.0 SP4.

Any ideas?

 

[RodTrent]

Is the RestrictAnonymous key set?

http://www.myitforum.com/articles/15/view.asp?id=978

Rod Trent
Microsoft.MVP.SMS
=======================================
Main site:

http://www.myITforum.com

=======================================

 

[fostergr]

I kind of thought that might be the culprit. However, when looking at some of the machines most are set to 1 and some are set to 0. I am running a change in my login script to modify the key to 0 for all workstations and we'll see what happens. I guess the security trade-off will be worth it. Thanks for your help.

 

[snyderj]

Possibly the WMI repository is corrupted and needs to be rebuilt.

Stop WMI service ("Windows Management Instrumentation" in services), delete files in C:\WINNT\system32\wbem\Repository, then restart PC. After the repository is rebuilt (takes a few minutes after restart) then you can wait for the SMS hardware inventory to be performed (within a few days) or force it through the Systems Management icon in Control Panel (start hwinv component), or use cliutils. It will take a few minutes to run the inventory, then a few more more minutes for the SMS database to get updated.