MSCE 2010 - Pending Management
We have a new installation of MSCE 2010. We've set aside an OU of computers for testing this and have added one Windows 7 computer. MSCE will discover the computer and deploy the agent, but the computer remains under Pending Management with the
"Management State: Installation in Progress". The internal logs say "If the computer remains in this state for an extended period, Reject the computer and try again". And that's it. Rigorous Google searching has only turned up mildly relevant
results.
Why is this computer stuck in Pending Management with Installation in Progress? I look in the task manager of the computer and see the HealthService.exe process/service running, so what is the deal?
Here are the 2 relevant events I am seeing on the MSCE server:
Log Name: Operations Manager
Source: Health Service Modules
Date: 12/21/2011 9:02:24 AM
Event ID: 11771
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: MSCE-01.ourdomain.contoso.com
Description:
Error getting state of service
Error: 0x8007007b
Details: The filename, directory name, or volume label syntax is incorrect.
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor
Instance name: ESSENTIALS
Instance ID: {E9C46C56-69C5-FF89-C4EF-5290ACEAD818}
Management group: MSCE-01_MG
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Health Service Modules" />
<EventID Qualifiers="49152">11771</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-12-21T16:02:24.000000000Z" />
<EventRecordID>14071</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>MSCE-01.ourdomain.contoso.com</Computer>
<Security />
</System>
<EventData>
<Data>MSCE-01_MG</Data>
<Data>Microsoft.SQLServer.2008.DBEngine.FullTextSearchServiceMonitor</Data>
<Data>ESSENTIALS</Data>
<Data>{E9C46C56-69C5-FF89-C4EF-5290ACEAD818}</Data>
<Data>0x8007007b</Data>
<Data>The filename, directory name, or volume label syntax is incorrect.
</Data>
</EventData>
</Event>
Log Name: Operations Manager
Source: Health Service Script
Date: 12/21/2011 9:11:41 AM
Event ID: 4000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MSCE-01.ourdomain.contoso.com
Description:
GetSQL2008DBSpace.js : 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Health Service Script" />
<EventID Qualifiers="0">4000</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-12-21T16:11:41.000000000Z" />
<EventRecordID>14073</EventRecordID>
<Channel>Operations Manager</Channel>
<Computer>MSCE-01.ourdomain.contoso.com</Computer>
<Security />
</System>
<EventData>
<Data>GetSQL2008DBSpace.js</Data>
<Data>0</Data>
</EventData>
</Event>
I don't know if this is a Group Policy issue in our domain; I don't know if this is a SQL issue and if so, why since the MSCE installer installed its own SQL server?; I am really not sure what to try next. Any input is much appreciated!
December 21st, 2011 2:49pm
Hi, first I will move this to the system center essentials forum for you as this seems to be a CSE question.
Second it looks like the erros you post here are related to the sql maangement pack not being able to do something and that is something tyo check later, but not related to your current issue. You might have a look at the SQL management pack guide and check
the runas profiles and such and see if that helps you further with that one.
nornmally if you push agents they should go to pending mgmt during install and after the agents reports back as installed succesfully it should move itself to agent managed. It does happen sometimes that it will stay in this transit state (same for full
scom) and than a reject and a re-deploy should work out. If you can have that agent machine restarted first thast could also already solve the issue and/or make the sercond attempt more likely to succeed. It could be that some other msi installer is stuck
somewhere and this msi cant get its taksk finished (that is why a reboot might help from that agent machine). So not needed for the scom agent, but it could be needed for other updates and such.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient
Free Windows Admin Tool Kit Click here and download it now
December 21st, 2011 3:33pm
Hi, first I will move this to the system center essentials forum for you as this seems to be a CSE question.
Second it looks like the erros you post here are related to the sql maangement pack not being able to do something and that is something tyo check later, but not related to your current issue. You might have a look at the SQL management pack guide and check
the runas profiles and such and see if that helps you further with that one.
nornmally if you push agents they should go to pending mgmt during install and after the agents reports back as installed succesfully it should move itself to agent managed. It does happen sometimes that it will stay in this transit state (same for full
scom) and than a reject and a re-deploy should work out. If you can have that agent machine restarted first thast could also already solve the issue and/or make the sercond attempt more likely to succeed. It could be that some other msi installer is stuck
somewhere and this msi cant get its taksk finished (that is why a reboot might help from that agent machine). So not needed for the scom agent, but it could be needed for other updates and such.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient
December 21st, 2011 3:33pm
Hi, first I will move this to the system center essentials forum for you as this seems to be a CSE question.
Second it looks like the erros you post here are related to the sql maangement pack not being able to do something and that is something tyo check later, but not related to your current issue. You might have a look at the SQL management pack guide and check
the runas profiles and such and see if that helps you further with that one.
nornmally if you push agents they should go to pending mgmt during install and after the agents reports back as installed succesfully it should move itself to agent managed. It does happen sometimes that it will stay in this transit state (same for full
scom) and than a reject and a re-deploy should work out. If you can have that agent machine restarted first thast could also already solve the issue and/or make the sercond attempt more likely to succeed. It could be that some other msi installer is stuck
somewhere and this msi cant get its taksk finished (that is why a reboot might help from that agent machine). So not needed for the scom agent, but it could be needed for other updates and such.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient
Free Windows Admin Tool Kit Click here and download it now
December 21st, 2011 3:33pm
Thanks Bob!
The agent machine that is stuck in Pending Management is a Windows 7 computer. The OU that computer is located in is blocking all Group Policy Inheritance, and then I linked both GPO's that MSCE installer created to that OU. In addition to that
Windows 7 computer is the MSCE server itself. After trying to get this to work for the last 2 weeks, I have just today added a Windows XP machine to that OU, ran "gpupdate /force" on it and rebooted. Instead of being stuck in Pending Management
with "Installation in Progress" like the Windows 7 computer, it just fails with the following event:
An agent push install or repair was attempted and failed. The task was run from the management server MSCE-01.ourdomain.contoso.com against the computer sy-test.ourdomain.contoso.com.
Additional details:
Task Start Time: 12/21/2011 5:32:34 PM UTC
Task End Time: 12/21/2011 5:33:41 PM UTC
Full Event Description: The Agent Management Operation Agent Install failed for remote computer sy-test.ourdomain.contoso.com.
Install account: OURDOMAIN\Administrator
Error Code: 80070659
Error Description: This installation is forbidden by system policy. Contact your system administrator.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Essentials\AgentManagement\AgentLogs\SY-TESTAgentInstall.LOG
C:\Program Files\System Center Essentials\AgentManagement\AgentLogs\SY-TESTMOMAgentMgmt.log" on the Management Server.
Again, the only GPO's on the OU are the GPO's the MSCE installer created. All other inheritance has been blocked, gpupdate /force was ran, and then the computers have been rebooted. Mystifying, isn't it?
December 21st, 2011 4:39pm
Thanks Bob!
The agent machine that is stuck in Pending Management is a Windows 7 computer. The OU that computer is located in is blocking all Group Policy Inheritance, and then I linked both GPO's that MSCE installer created to that OU. In addition to that
Windows 7 computer is the MSCE server itself. After trying to get this to work for the last 2 weeks, I have just today added a Windows XP machine to that OU, ran "gpupdate /force" on it and rebooted. Instead of being stuck in Pending Management
with "Installation in Progress" like the Windows 7 computer, it just fails with the following event:
An agent push install or repair was attempted and failed. The task was run from the management server MSCE-01.ourdomain.contoso.com against the computer sy-test.ourdomain.contoso.com.
Additional details:
Task Start Time: 12/21/2011 5:32:34 PM UTC
Task End Time: 12/21/2011 5:33:41 PM UTC
Full Event Description: The Agent Management Operation Agent Install failed for remote computer sy-test.ourdomain.contoso.com.
Install account: OURDOMAIN\Administrator
Error Code: 80070659
Error Description: This installation is forbidden by system policy. Contact your system administrator.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Essentials\AgentManagement\AgentLogs\SY-TESTAgentInstall.LOG
C:\Program Files\System Center Essentials\AgentManagement\AgentLogs\SY-TESTMOMAgentMgmt.log" on the Management Server.
Again, the only GPO's on the OU are the GPO's the MSCE installer created. All other inheritance has been blocked, gpupdate /force was ran, and then the computers have been rebooted. Mystifying, isn't it?
Free Windows Admin Tool Kit Click here and download it now
December 21st, 2011 4:39pm
Thanks Bob!
The agent machine that is stuck in Pending Management is a Windows 7 computer. The OU that computer is located in is blocking all Group Policy Inheritance, and then I linked both GPO's that MSCE installer created to that OU. In addition to that
Windows 7 computer is the MSCE server itself. After trying to get this to work for the last 2 weeks, I have just today added a Windows XP machine to that OU, ran "gpupdate /force" on it and rebooted. Instead of being stuck in Pending Management
with "Installation in Progress" like the Windows 7 computer, it just fails with the following event:
An agent push install or repair was attempted and failed. The task was run from the management server MSCE-01.ourdomain.contoso.com against the computer sy-test.ourdomain.contoso.com.
Additional details:
Task Start Time: 12/21/2011 5:32:34 PM UTC
Task End Time: 12/21/2011 5:33:41 PM UTC
Full Event Description: The Agent Management Operation Agent Install failed for remote computer sy-test.ourdomain.contoso.com.
Install account: OURDOMAIN\Administrator
Error Code: 80070659
Error Description: This installation is forbidden by system policy. Contact your system administrator.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Essentials\AgentManagement\AgentLogs\SY-TESTAgentInstall.LOG
C:\Program Files\System Center Essentials\AgentManagement\AgentLogs\SY-TESTMOMAgentMgmt.log" on the Management Server.
Again, the only GPO's on the OU are the GPO's the MSCE installer created. All other inheritance has been blocked, gpupdate /force was ran, and then the computers have been rebooted. Mystifying, isn't it?
December 21st, 2011 4:39pm
Small Progress: The windows XP VM that was failing the installation because of system policy has been resolved. It only took about 13 gpupdates, 10 shutdowns, and 1 re-ordering of the network connections in advanced settings, and FINALLY the rsop came back
with the correct policies applied.
But it's still stuck in the same state as the Windows 7 machine. Pending Managenement and Installation in Progress.
I think I've actually reached the dead-end. Here it is.
This is an event from the Windows XP machine I finally got to not outright fail the agent installation:
The OpsMgr Connector could not connect to MSCE-01.OURDOMAIN.contoso.com:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected
host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I did as the event said I should. I verified network connectivity, the server is running and registered its listening port (lol event log used the wrong "it's"), and the firewalls are definitely not blocking anything.
Here is the results C:'WINDOWS>netstat -an |find /i "listening" command I ran on the MSCE server:
C:\Users\Administrator.OURDOMAIN>netstat -an |find /i "listening"
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5723 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5724 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8530 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8531 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49170 0.0.0.0:0 LISTENING
TCP 0.0.0.0:50001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:51906 0.0.0.0:0 LISTENING
TCP 0.0.0.0:57016 0.0.0.0:0 LISTENING
TCP 0.0.0.0:64040 0.0.0.0:0 LISTENING
TCP 192.168.1.185:139 0.0.0.0:0 LISTENING
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:5723 [::]:0 LISTENING
TCP [::]:5724 [::]:0 LISTENING
TCP [::]:8100 [::]:0 LISTENING
TCP [::]:8530 [::]:0 LISTENING
TCP [::]:8531 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49170 [::]:0 LISTENING
TCP [::]:50001 [::]:0 LISTENING
TCP [::]:51906 [::]:0 LISTENING
TCP [::]:57016 [::]:0 LISTENING
TCP [::]:64040 [::]:0 LISTENING
C:\Users\Administrator.OURDOMAIN>
I also found information about which ports need to be added as Windows Firewall exceptions for MSCE. I added these exceptions to both the XP machine and the MSCE server, and then disabled the firewalls entirely on both.
The XP machine is still producing the Error Event ID 21006.
I am on the cusp, I just KNOW IT! >.<
----------- WTE Systems -----------
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2011 2:45pm
Small Progress: The windows XP VM that was failing the installation because of system policy has been resolved. It only took about 13 gpupdates, 10 shutdowns, and 1 re-ordering of the network connections in advanced settings, and FINALLY the rsop came back
with the correct policies applied.
But it's still stuck in the same state as the Windows 7 machine. Pending Managenement and Installation in Progress.
I think I've actually reached the dead-end. Here it is.
This is an event from the Windows XP machine I finally got to not outright fail the agent installation:
The OpsMgr Connector could not connect to MSCE-01.OURDOMAIN.contoso.com:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected
host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I did as the event said I should. I verified network connectivity, the server is running and registered its listening port (lol event log used the wrong "it's"), and the firewalls are definitely not blocking anything.
Here is the results C:'WINDOWS>netstat -an |find /i "listening" command I ran on the MSCE server:
C:\Users\Administrator.OURDOMAIN>netstat -an |find /i "listening"
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5723 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5724 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8530 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8531 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49170 0.0.0.0:0 LISTENING
TCP 0.0.0.0:50001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:51906 0.0.0.0:0 LISTENING
TCP 0.0.0.0:57016 0.0.0.0:0 LISTENING
TCP 0.0.0.0:64040 0.0.0.0:0 LISTENING
TCP 192.168.1.185:139 0.0.0.0:0 LISTENING
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:5723 [::]:0 LISTENING
TCP [::]:5724 [::]:0 LISTENING
TCP [::]:8100 [::]:0 LISTENING
TCP [::]:8530 [::]:0 LISTENING
TCP [::]:8531 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49170 [::]:0 LISTENING
TCP [::]:50001 [::]:0 LISTENING
TCP [::]:51906 [::]:0 LISTENING
TCP [::]:57016 [::]:0 LISTENING
TCP [::]:64040 [::]:0 LISTENING
C:\Users\Administrator.OURDOMAIN>
I also found information about which ports need to be added as Windows Firewall exceptions for MSCE. I added these exceptions to both the XP machine and the MSCE server, and then disabled the firewalls entirely on both.
The XP machine is still producing the Error Event ID 21006.
I am on the cusp, I just KNOW IT! >.<
----------- WTE Systems -----------
December 22nd, 2011 2:45pm
Small Progress: The windows XP VM that was failing the installation because of system policy has been resolved. It only took about 13 gpupdates, 10 shutdowns, and 1 re-ordering of the network connections in advanced settings, and FINALLY the rsop came back
with the correct policies applied.
But it's still stuck in the same state as the Windows 7 machine. Pending Managenement and Installation in Progress.
I think I've actually reached the dead-end. Here it is.
This is an event from the Windows XP machine I finally got to not outright fail the agent installation:
The OpsMgr Connector could not connect to MSCE-01.OURDOMAIN.contoso.com:5723. The error code is 10060L(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected
host has failed to respond.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I did as the event said I should. I verified network connectivity, the server is running and registered its listening port (lol event log used the wrong "it's"), and the firewalls are definitely not blocking anything.
Here is the results C:'WINDOWS>netstat -an |find /i "listening" command I ran on the MSCE server:
C:\Users\Administrator.OURDOMAIN>netstat -an |find /i "listening"
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5723 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5724 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8530 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8531 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49170 0.0.0.0:0 LISTENING
TCP 0.0.0.0:50001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:51906 0.0.0.0:0 LISTENING
TCP 0.0.0.0:57016 0.0.0.0:0 LISTENING
TCP 0.0.0.0:64040 0.0.0.0:0 LISTENING
TCP 192.168.1.185:139 0.0.0.0:0 LISTENING
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:5723 [::]:0 LISTENING
TCP [::]:5724 [::]:0 LISTENING
TCP [::]:8100 [::]:0 LISTENING
TCP [::]:8530 [::]:0 LISTENING
TCP [::]:8531 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49170 [::]:0 LISTENING
TCP [::]:50001 [::]:0 LISTENING
TCP [::]:51906 [::]:0 LISTENING
TCP [::]:57016 [::]:0 LISTENING
TCP [::]:64040 [::]:0 LISTENING
C:\Users\Administrator.OURDOMAIN>
I also found information about which ports need to be added as Windows Firewall exceptions for MSCE. I added these exceptions to both the XP machine and the MSCE server, and then disabled the firewalls entirely on both.
The XP machine is still producing the Error Event ID 21006.
I am on the cusp, I just KNOW IT! >.<
----------- WTE Systems -----------
Free Windows Admin Tool Kit Click here and download it now
December 22nd, 2011 2:45pm
Eureka!
When I created the server, I did not give it a static IP address because this was merely going to be a test so I skipped the ritual of allocating one of our static IP's and just let it run as-is. Behold, DNS problems!
The client machines were resolving msce-01 to an IP address that belonged to a different host, so OF COURSE the agents aren't going to connect...
Thankfully, it's the holidays and I can hide my DUNCE hat with a giant red santa clause hat! :D----------- WTE Systems -----------
December 22nd, 2011 5:30pm