My Microsoft.Windows.Client.Computer is empty (no instances)

Microsoft.Windows.Server.Computer is not empty

Microsoft.Windows.Computer is not empty and showing all windows clients.

Why is my Microsoft.Windows.Client.Computer empty ? Can I fix this somehow.

Thanx for help

are you importing any clients through connectors? what would you be expecting here?

I use the sccm connector to import clients

I expect to see all windows workstations

as I see all the Windows servers in Microsoft.Windows.Server.Computer 

I extended the hardware inventory of clients in the same way I extended inventory for the servers

I found out I have scom client on servers and not on workstation. And I have tested the scom ci connector. Could that be the reason why windows.computer.server is working ?

• Edited by FrankCoast Friday, September 12, 2014 6:48 PM

I use the sccm connector to import clients

I expect to see all windows workstations

as I see all the Windows servers in Microsoft.Windows.Server.Computer 

I extended the hardware inventory of clients in the same way I extended inventory for the servers

I found out I have scom client on servers and not on workstation. And I have tested the scom ci connector. Could that be the reason why windows.computer.server is working ?

• Edited by FrankCoast Friday, September 12, 2014 6:48 PM

I use the sccm connector to import clients

I expect to see all windows workstations

as I see all the Windows servers in Microsoft.Windows.Server.Computer 

I extended the hardware inventory of clients in the same way I extended inventory for the servers

I found out I have scom client on servers and not on workstation. And I have tested the scom ci connector. Could that be the reason why windows.computer.server is working ?

• Edited by FrankCoast Friday, September 12, 2014 6:48 PM

I use the sccm connector to import clients

I expect to see all windows workstations

as I see all the Windows servers in Microsoft.Windows.Server.Computer 

I extended the hardware inventory of clients in the same way I extended inventory for the servers

I found out I have scom client on servers and not on workstation. And I have tested the scom ci connector. Could that be the reason why windows.computer.server is working ?

• Edited by FrankCoast Friday, September 12, 2014 6:48 PM

I just have seen the same issue.

If the computer is not "discovered" by the SCOM or the AD connectors, the Windows.Computer CI is not created. But a few weeks ago it was created by the SCCM connector!

The only change we did was to upgrade SCSM 2012R2 to UR3.

FrankCoast, what version do you have?

SCSM 2012R2

I have microsoft.windows.computers because of SCCM connector

Microsoft.Windows.Server.Computer is comming from SCOM Connector. Servers have SCOM agent.

But my clients do not have SCOM client.

How can I fill up the Microsoft.Windows.Client.Computer with the data from microsoft.windows.computers ?

Create a orchestrator ?

Any suggestions welcome

No suggestions ?

I know that you got an answer to this on Network Steve so I am just adding it here in case anyone has a similar question in the future. 

http://www.networksteve.com/forum/topic.php/Copy_Instances_from_Microsoft.Windows.Computer_to_Microsoft.Wind/?TopicId=45436&Posts=2