The title “Richard Got NAPd” was born back 2005 when I first joined Microsoft and participated in Microsoft’s 1st deployment rollout of System Center Configuration Managers 2007 Network Access Protection (NAP) which was a 3 year project. As a member of MSIT during this deployment, it gave me allot of insight into network intrusion protection and security compliance. So the title implies I that was intrigued by the integrated technology of Network Access Protection and systems management and compliance monitoring which consumed the first 3 years of my time at Microsoft.
I posting a Workaround for a issue I found and notice that other people running into. So far I not seen or found a root cause or a fix. But this work around is the best I have discovered and better than rebooting the Hyper V host to resolve the issue.
Link to the Article on Tech Net:
URL: http://social.technet.microsoft.com/forums/en-US/virtualmachinemanager/thread/ac48fd59-3de9-4191-8466-25bedee3f5b1
Workaround:
Though I have not found the root cause, but I did find something of a workaround that quickly brings the Hyper V host back to a functional state.
When I see the error of :
Error (2912)
An internal error has occurred trying to contact an agent on the servername.domain.com server.
(No more threads can be created in the system (0x800700A4))
Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
I go to Services and Restart the "Windows Management Instrumentation" Service. Restarting this services also restarts the following services: (if they are on your server)
- Hyper V Virtual Machine Management
- Virtual Machine Manager Agent
- Hyper-V Image Management Service
- Hyper-V Networking Management Service
- IP Helper
- EMC PowerPath Service 5.1.2
- SMS Agent Host
Due to the type of services that are also restarted when doing this, and if the Hyper V host is in production. I would suggest doing this with caution and sending a user awareness notification for the temporary outage. Though the outage is small depending on how long it takes for certain services to start.
Because the Hyper-V Image Management Service is restarted. Users will not be able remote control a virtual machine or may be kicked off the VM remote control session. And if you are doing this while TS into the Hyper V host server, you may lose TS connectivity momentarily.
About Richard Dixon
I’ve worked in the field of Systems Management since 1990, performing integration and automation through the use of Microsoft technologies such as System Center Configuration Manager 2007, Operations Manager, Service Manager, SQL Server 2008 & Reporting Services, Visual Studio, and SharePoint with InfoPath Integration. I am proficient on SCCM, Microsoft's Hyper V Virtualization technology, and Failover Clustering & Network Load Balancer Services. I have also worked extensively with SCCM Network Access Protection and enjoy learning new technologies. I am also a Microsoft Partner. I started work at Microsoft in 2005 in the SMS/SCCM team of MSIT, which later became the Management Platforms & Services Delivery group in the Management Services division. In MPSD I managed our Lab, Preproduction & Production environments using Microsoft's Hyper V technology. These environments support several SCCM infrastructures which include the management of 200,000 managed desktops across Microsoft. Prior to working at Microsoft I worked for Warner Bros/AOL Time Warner, NBC Studios, AT&T WorldNet Service, 24 Hour Fitness, State of California Health Department, Northrop Grumman, NOS Communications, GE Capital, KLA Tencor, Wells Fargo Mortgage Bank, Dudeworks, TeleTech, and TekSystems.
Specialties:System Center Configuration Manager 2007, Service Manager, Virtual Machine Manager 2007 R2, Operations Manager 2007 R2, Hyper V, SQL Server, Scripting, Visual Studio, SharePoint Services and InfoPath Integrations and Systems Center Essentials.