Answered Cross Domain SCOM Monitoring

  • Friday, February 15, 2013 5:17 AM
     
     

    Hi All,

    I have a SCOM 2007 R2  setup in the child domain ,which has a two way trust with its parent domain.

    I have a requirement to monitor the servers in the parent domain.however when i attempt to discover SCOM discovers the servers but fails to install the agent.

    The error is :

    Note1: The account used for installation is a domain admin account in the child domain.

    Note2: All the systems in the child /local domain are discovered and there is no issue in agent installation and monitoring.

    Since it is a two way trust I was hoping it was enough,but looks like i am missing something .Could anyone please tell me what additional configurations are required to get through this and get the servers under monitoring from the parent domain.

All Replies

  • Friday, February 15, 2013 5:48 AM
    Moderator
     
     

    Hi,

    > child domain ,which has a two way trust with its parent domain.

    If I understood this correct both domains are in the same forest, right?

    > Note1: The account used for installation is a domain admin account in the child domain.

    > requirement to monitor the servers in the parent domain

    This account has to be a local admin on the server where you installing an agent. By default domain admins are not members of the local Administrators group on machines in another domains (parent domain in your case). Please check permissions for account you're using. 


    http://OpsMgr.ru/

  • Friday, February 15, 2013 6:12 AM
     
     

    Hi

    08007005 indicate a permission error. As Alex suggested deploy the agents to the child Domain using a Domain Admin account from the child domain. If you don't have a Domain Admin account you need at least an account which has local Administrator permission on each server. For Domain Controllers you probably would need the child Domain Administrator to give you Administrators permission or he would need to provide appropriate credentials.

    Cheers,

    Stefan


    Blog: http://blog.scomfaq.ch

  • Tuesday, February 19, 2013 5:34 AM
     
     

    Thank you All,

    It worked on a couple of machines in the parent domain and a couple it failed.

    I guess this is machine and port specific now. As I am able to install agents in the parent domain on a few and not on others. I shall take it up from here ....

    Many thanks again to All :-)

  • Tuesday, February 19, 2013 7:49 AM
    Moderator
     
     Answered


    Hi,

    I would like to suggest the following:

    1. If the computer has antivirus software installed, please temporarily disable it and try again.

    2. Try to install the agent manually and see if it works:

    Install Agent Using the MOMAgent.msi Setup Wizard
    http://technet.microsoft.com/en-us/library/hh212915.aspx

    If the issue persists, please also check it with Process Monitor:

    Process Monitor
    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

    Thanks.


    Nicholas Li
    TechNet Community Support

  • Thursday, February 21, 2013 6:38 PM
     
     Answered

    Hello Himanshu, 

    As Nicholas stated, install the agent Manaually. 

    You can copy the agent from the SCOM installation Media under the agent folder and select the agent based on the OS Architecture.

    Also in the Administration Tab in SCOM, click on the security option and select the "Review Manually Installed Agents" option. 

    Once you install the agent manually, also make sure to update the host file on the managed node so that it contains the IP address netbios Name and FQDN of the Management Server the agent is pointing to. 

    Lastly, in the administration tab, under pending management right click and approve the agent.

    Hope this helps!

    Regards,


    Abdul Karim. (http://sites.google.com/site/scomblogs Twitter:@Abdul_SCOM)