Montag, 13. Februar 2012 16:10
I have an odd issue within SCE 2010. We have 3 computers and 3 Servers that are only showing in the All Windows Computers group.
It seems they are not getting assigned automatically to the correct groups, i.e All Windows Clients or All Windows Servers.
Anyone have any ideas on this?
- Bearbeitet JCrescenzo Montag, 13. Februar 2012 16:14
Mittwoch, 15. Februar 2012 08:56Moderator
With my experience, the most likely cause of this issue is that some managed computers are sharing the same SUSClientID.
The WSUS technology in Essentials uses the SUSClientID to uniquely identify each managed computer that contacts the Essentials server. If more than one computer is using the same duplicate SUSClientID, only the first computer that reports to the Essentials server will be fully managed.
If this is the case in your environment, check out these articles for cleaning up this issue, and also fix your image so that you do not have to deal with this issue in the future.
A Windows 2000-based, Windows Server 2003-based, or Windows XP-based computer that was set up by using a Windows 2000, Windows Server 2003, or Windows XP image does not appear in the WSUS console
Resolving the duplicate SUSClientID issue, or “Why don’t all my clients show up in the WSUS console?”
If the above steps didn't work, please check the following:
1. Run SCE console, navigate to “Administration" space, choose "agent Managed" and make sure all clients are in the list.
2. Run WSUS console on your SCE server, and check whether these clients are in the "All computers" group.
3. Run ADUC on your DC, make sure all clients are in the "SCE Managed Computers" group.
TechNet Community Support
Mittwoch, 15. Februar 2012 16:30
Thank you for the reply.
Unfortunately this did not work. I knew about the dub Sus issue, and have attempted this first.
All the computers do show up within Agent Managed within SCE as well as "All Windows Computers" within WSUS and SCE.
They are all listed within the SCE Managed Computers group too.
This is very odd, I know.
Freitag, 17. Februar 2012 09:59Moderator
I agree that it is an odd issue. I had seen this issue before and it has been resolved by SCE Server automatically in several days:
Windows 2008 Servers in client group?!
And I hope the information in the thread below can also help you:
Missing computers from group
TechNet Community Support
Freitag, 17. Februar 2012 16:02
I am attempting the database solution:
Select TopLevelHostEntityId from basemanagedentity where Path like ‘%ComputerName%’
Select TopLevelHostEntityId from basemanagedentity where Name like ‘%ComputerName%'
Do I need to be in a specific database or table to run this or can I just query it from the SQL Server level?
Mittwoch, 14. März 2012 17:32
I believe that before getting to that level, we can cover a couple of other things from a SCE standpoint. Based on what you mention here, it looks like the computers are having problems in SCE trying to be added to groups, or those groups are not having those computers as members.
a couple of things that I would check are:
- are the computers getting consistent config changes? restart the health service on an affected computer and check that you get an event id 1210 on the event log. Also check that the OpsMgrConnector.Config.xml file (located in C:\Program Files\System Center Operations Manager 2007\Health Service State\Connector Configuration Cache) is updated
- also, I would check that creating any new custom group with those same windows computers work as expected. I dont remember for SCE but for SCOM we log event id 31410 every time that group calculation works. Can you check that? can you see if there are 31410s logged in the sce server?
Mittwoch, 14. März 2012 17:47
Thank you for the reply.
After reseting the health service, we do get a 1210 event, for a new configuration becoming active.
No 31410 logged on the SCE server it self though.
After the 1210 on the affected i noticed 10401 errors, stating
Module was unable to connect to namespace
This has happened 1 times since this instance was loaded.
HRESULT: 0x8004100e Details: Invalid namespace
This shows a handful of times, each stating different workflows one of them being
Wonder if that has anything to do with it
Mittwoch, 14. März 2012 18:06
The event 1210 means that the local store activated whatever config is there, however does not show if new changes are populated. Did you check the timestamp on the xml file? That is the best way to check that config works. Also, you need to check the group membership and see if new computer groups reflect changes. If the problem still persists, I may need to repro that, but let's make sure we covered the basics before moving forward.
Mittwoch, 14. März 2012 19:33
The xml file's modify date did not change after restarting however it does have the time from this morning, so it must be updating.
Not sure if I understand the computer group part you were talking about, however we have new computers that have been added to the same group and the are working fine.
Donnerstag, 12. April 2012 13:14
Sorry for the delay getting back to you. When I mentioned the XML file, I am talking about making changes in the management group and making sure those changes are basically picked up by the SCE server. You also mentioned that the xml file is updated over time which is what I was looking for..basically we update config and that config is pushed.
However, going back to your original question "It seems they are not getting assigned automatically to the correct groups, i.e All Windows Clients or All Windows Servers." I would like to understand which specific group are you supposed to see those agents populated. I dont have a SCE lab to review this but I have an opsmgr 2007 lab and I see "all windows computers", "windows server computer group", "windows server 2003 computer group", etc...
which os is the one from the affected computers? if you filter under groups for "windows" do you see the group and the members of that group? Let's focus on that part first, then we'll take it from there.
Mittwoch, 18. April 2012 15:43
Hi Jose, Thanks for the reply.
We currently have 4 groups:
All Windows Clients
All Windows Computers
All Windows Laptops
All Windows Servers
The All Windows Laptops we added, and the others were created by SCE.
The odd thing is, there are 2 clients and 4 servers not showing in their groups. They are lists in the All Windows Computers group but not their respected groups.
The 2 Clients are Windows XP Pro Desktops and the 2 of the Servers are Windows 2003 serving as File Servers and the other 2 are Windows server 2000 also serving as File Servers.
3 of the 4 servers are getting retired soon, so I am not to worried any more, however would still like to know.
Let me know what you think and if we should keep looking into it.
Mittwoch, 2. Mai 2012 04:52
Hi JCrescenzo,so just to clarify, can you share with us where are we on the status of the servers?
I understand that you are adding/removing servers, but it will be better if you are able to explain how are changes being "added" or "removed" from groups. This should happen automatically. Per your comment on xml updates, database changes are processed by the SCE server.
so when you have a chance, you need to confirm
- which views from the Windows MP are not populating info correctly
- when you mention that you added computers, do you mean that the agent was installed, or you mean that the agent was added to a custom group?
- Als Antwort markiert Yog LiMicrosoft Contingent Staff, Moderator Freitag, 25. Mai 2012 02:49
Freitag, 25. Mai 2012 03:25Moderator
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.
In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
TechNet Community Support