Hi, I am facing some problem with our MOM 2005 server that, about 845 machines out of 1446 are showing in pending status . this is one of the machine status.... We are using MOM 2005, sql 2005,windows 2003 server 32 bit Regards, TusharTushar

Hello Tushar, Please check if any error or warning events was logged on the problematic machines. And you can refer to this simialr thread: MOM 2005 Agent Deployment Questions http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/375ce367-c38b-4daf-8cf3-728a76abb783 Thanks,Yog Li TechNet Community Support

Hi Tushar, Kindly have a look at technet below http://technet.microsoft.com/en-us/library/cc180826.aspx~Cheers, Rohit Kochher

Hello Tushar, Please check if any error or warning events was logged on the problematic machines. And you can refer to this simialr thread: MOM 2005 Agent Deployment Questions http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/375ce367-c38b-4daf-8cf3-728a76abb783 Thanks,Yog Li TechNet Community Support

Hello Tushar, Please check if any error or warning events was logged on the problematic machines. And you can refer to this simialr thread: MOM 2005 Agent Deployment Questions http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/375ce367-c38b-4daf-8cf3-728a76abb783 Thanks,Yog Li TechNet Community Support

you need to check in the mom 2005 admin console in the discovery rules, to make sure there are still discovery rules for those machines. If there are not discovery rules for those machines you will need to make new ones so they will continue to be managed. I'm assuming that they at one point were managed and reporting to mom 2005. if this is the case this is probably the cause. hope this helps!Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you! my new blog om2012.wordpress.com

Hi, Thanks for your solution ... I am doing it as per your suggest ... but i am not clear about "I'm assuming that they at one point were managed and reporting to mom 2005. if this is the case this is probably the cause."Tushar

you need to check in the mom 2005 admin console in the discovery rules, to make sure there are still discovery rules for those machines. If there are not discovery rules for those machines you will need to make new ones so they will continue to be managed. I'm assuming that they at one point were managed and reporting to mom 2005. if this is the case this is probably the cause. hope this helps!Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you! my new blog om2012.wordpress.com

you need to check in the mom 2005 admin console in the discovery rules, to make sure there are still discovery rules for those machines. If there are not discovery rules for those machines you will need to make new ones so they will continue to be managed. I'm assuming that they at one point were managed and reporting to mom 2005. if this is the case this is probably the cause. hope this helps!Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you! my new blog om2012.wordpress.com

Hi Tushar, 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, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,Yog Li TechNet Community Support

Hi Tushar, 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, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,Yog Li TechNet Community Support

Hi, Problem is not resolved yet, but thnks to ScottMoss , as per his answered , I have tried to create a one discovery rule for one machine which machine is shown in Pending action before . And Yes now it'll not shown in pending action its in Agent managed mode . But this is not possible for 845 machines(which is my main question). Is there any way to resolve .....Tushar

you could dump the names of the computers that you need to manage into the manualmc.txt file I think is what its called. http://technet.microsoft.com/en-us/library/cc180815.aspx for more details see below for usage. To use the ManualMC.txt file to specify computers for discovery On the Management Server, create a text file named ManualMC.txt in the directory where you installed MOM 2005. The default installation directory is \%SystemRoot%\Program Files\Microsoft Operations Manager 2005. Add the computer names to the ManualMC.txt file. Save the file as an ANSI (default), Unicode, or UTF-8 encoded file. Top Of Page Guidelines for Adding Computer Names to the ManualMC.txt File When you add computer names to the ManualMC.txt file, use the following guidelines: Enter one computer name per line. Do not leave blank lines between computer names. Add the computer names by using any of the following conventions: Fully Qualified Domain Name (FQDN) name - only if the computer is joined to an Active Directory domain. NetBIOS name. (The character limit for NetBIOS computer names is 15 characters.) Domain\ComputerName. Workgroup Name\ Computer Name. You can remove agents from any computer in a ManualMC.txt file by simply removing the computers entry in the file and making sure that there are no other rules that include the computer. The agent will be removed during the next scheduled discovery, or you can do this immediately by right-clicking a Management Server and then clicking Run Computer Discovery Now. Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you! my new blog om2012.wordpress.com

you could dump the names of the computers that you need to manage into the manualmc.txt file I think is what its called. http://technet.microsoft.com/en-us/library/cc180815.aspx for more details see below for usage. To use the ManualMC.txt file to specify computers for discovery On the Management Server, create a text file named ManualMC.txt in the directory where you installed MOM 2005. The default installation directory is \%SystemRoot%\Program Files\Microsoft Operations Manager 2005. Add the computer names to the ManualMC.txt file. Save the file as an ANSI (default), Unicode, or UTF-8 encoded file. Top Of Page Guidelines for Adding Computer Names to the ManualMC.txt File When you add computer names to the ManualMC.txt file, use the following guidelines: Enter one computer name per line. Do not leave blank lines between computer names. Add the computer names by using any of the following conventions: Fully Qualified Domain Name (FQDN) name - only if the computer is joined to an Active Directory domain. NetBIOS name. (The character limit for NetBIOS computer names is 15 characters.) Domain\ComputerName. Workgroup Name\ Computer Name. You can remove agents from any computer in a ManualMC.txt file by simply removing the computers entry in the file and making sure that there are no other rules that include the computer. The agent will be removed during the next scheduled discovery, or you can do this immediately by right-clicking a Management Server and then clicking Run Computer Discovery Now. Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you! my new blog om2012.wordpress.com

you could dump the names of the computers that you need to manage into the manualmc.txt file I think is what its called. http://technet.microsoft.com/en-us/library/cc180815.aspx for more details see below for usage. To use the ManualMC.txt file to specify computers for discovery On the Management Server, create a text file named ManualMC.txt in the directory where you installed MOM 2005. The default installation directory is \%SystemRoot%\Program Files\Microsoft Operations Manager 2005. Add the computer names to the ManualMC.txt file. Save the file as an ANSI (default), Unicode, or UTF-8 encoded file. Top Of Page Guidelines for Adding Computer Names to the ManualMC.txt File When you add computer names to the ManualMC.txt file, use the following guidelines: Enter one computer name per line. Do not leave blank lines between computer names. Add the computer names by using any of the following conventions: Fully Qualified Domain Name (FQDN) name - only if the computer is joined to an Active Directory domain. NetBIOS name. (The character limit for NetBIOS computer names is 15 characters.) Domain\ComputerName. Workgroup Name\ Computer Name. You can remove agents from any computer in a ManualMC.txt file by simply removing the computers entry in the file and making sure that there are no other rules that include the computer. The agent will be removed during the next scheduled discovery, or you can do this immediately by right-clicking a Management Server and then clicking Run Computer Discovery Now. Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you! my new blog om2012.wordpress.com