sccm 2007 client not updating OU location, last logged on user etc.

[peanican]

I'm really struggling here. I have redone my SCCM server and I'm installing clients with the client push method. The clients are taking down the new client but in the admin console I'm missing some information. The clients say they have the advanced client installed which is good, they have some information like IP address, netbios name etc. But are missing critical fields like what OU they belong to or last signed on user. What logs do you need to see? Please HELP.

[peanican]

I'm really struggling here. I have redone my SCCM server and I'm installing clients with the client push method. The clients are taking down the new client but in the admin console I'm missing some information. The clients say they have the advanced client installed which is good, they have some information like IP address, netbios name etc. But are missing critical fields like what OU they belong to or last signed on user. What logs do you need to see? Please HELP.

 

 

What component actually queries the username / Domain, InventoryAgent?

[anyweb]

what discovery methods have you configured ?

[Eswar Koneti]

When a computer sends its DDR to SCCM server ,it contaians the follwoing information.

SMS unique identifier (GUID) ,NetBIOS name,IP addresses,IP subnets,Operating system name and version,Domain or workgroup,Last logon user name,Agent name (the discovery method that generated the DDR),Active Directory container,Active Directory group.

 

For generating OU information,you should have enabled Active Directory System group Discovery ? Did you enabled this ?

[peanican]

When a computer sends its DDR to SCCM server ,it contaians the follwoing information.

SMS unique identifier (GUID) ,NetBIOS name,IP addresses,IP subnets,Operating system name and version,Domain or workgroup,Last logon user name,Agent name (the discovery method that generated the DDR),Active Directory container,Active Directory group.

 

For generating OU information,you should have enabled Active Directory System group Discovery ? Did you enabled this ?

 

 

Update. I rebooted my server and went to bed. The next morning all the OU information is showing up! I do have a couple things showing <null> like AD Domain Name and CPU type. The funny thing is I can't remeber on my last server if those showed up fo me then. Should the client be pulling this information? Is there a log that will show the failed queries?

 

On a side note. This forum is the best, I've been using it for a year now and this is the first time I have not found the info in a previous post.

[Eswar Koneti]

Update. I rebooted my server and went to bed. The next morning all the OU information is showing up! I do have a couple things showing <null> like AD Domain Name and CPU type. The funny thing is I can't remeber on my last server if those showed up fo me then. Should the client be pulling this information? Is there a log that will show the failed queries?

 

On a side note. This forum is the best, I've been using it for a year now and this is the first time I have not found the info in a previous post.

 

Hey,I was out of office last week,couldnt' reply. Are you looking at default collection,computer properties ?

If so,then you will see this(CPU Type) as NULL since this value is not part of sms_r_system.the default collection is querying the information from sms_r_system.CPU Tyoe informaiton will be present in SMS_G_System_PROCESSOR table.

 

right on computer,go to resource explorer,click on hardware---_processor.You will see CPU type value 3 which means "This is a PowerPC computer".

 

This should give some idea http://technet.micro...y/cc180445.aspx

 

Look at Bottom Note:

 

In some unusual cases, SMS might report values for properties, such as CPU type, that are not accurate. In most cases, SMS obtains the values from WMI. So in the case of CPU type, this might be due to the fact that the CPU type is newer than the version of WMI that you are running. Updating WMI (by updating the operating system, possibly with a service pack) might correct the inaccuracy. When first developing a report or other feature that depends on inventory data, you should review the data closely to ensure that no such issues apply to the data you are using.