Skip navigation
5684 Views 7 Replies Latest reply: Feb 25, 2010 3:08 PM by jradziszewski RSS
jjaeger Apprentice 74 posts since
Sep 20, 2008

Has received 1 of 9 achievements.
Currently Being Moderated

Sep 16, 2009 9:22 AM

Rollup two Cores on different Domains with no trust

I have two core servers that are on different domains. The doamins do not have any trust between them. I need to open induvidual ports in the firewalls on both ends in oreder to roll up the second core. The first core is on the same domain as the second core, and has already been rolled up. Does anyone have any idea what ports need to be open so I can acomplish the second core rollup?

When the rollup server connects to the core when you add a new core, it reads the database information from the remote registry. What account does it use to do this, and is this a one time thing, or does it do it everytime that it rolls up the data?

  • Johann Apprentice 105 posts since
    Jan 25, 2008

    Has received 1 of 9 achievements.

    James,

     

    I have a similar issue in our enviroment.

    Two Core Server, one Rollup Core. First Core (in same domain as Rollup Core) did the rollup well. Second Core in another domain with not trust didn't succeed. Error message something like "NT authority failed...coulnd't access remote registry..."

    Our solution was logging in on the Rollup and creating a mapping to the c-drive of the Core Server in the different domain. Mapping went well with credentials from the other domain. After that I tried to add the second server to the Rollup Core again and was asked for credentials from the other domain. Entered them and it worked fine.

     

    Hope this helps you.

     

    Johann

  • MarXtar SSMMVPGroup 2,056 posts since
    Jul 2, 2008

    Has received 8 of 9 achievements.
    Currently Being Moderated
    2. Oct 10, 2009 8:31 AM (in response to jjaeger)
    Re: Rollup two Cores on different Domains with no trust

    The advice above is good. As a note, the connection to read settings is a one time thing so you will be fine after the first time.

     

    Mark Star - MarXtar LANDesk Enhancements

    Home of Power State Notifier & Wake-On-WAN for LANDesk

    New Updated Power State Notifier Pro!

  • jradziszewski SupportEmployee 32 posts since
    Jun 2, 2009

    Has received 1 of 9 achievements.
    Currently Being Moderated
    4. Feb 24, 2010 12:12 PM (in response to jjaeger)
    Re: Rollup two Cores on different Domains with no trust

    Try issuing a "NET USE * \\[remoteserver]\c$" in a command prompt window before adding the source (remote) core in the rollup tool.

  • jradziszewski SupportEmployee 32 posts since
    Jun 2, 2009

    Has received 1 of 9 achievements.
    Currently Being Moderated
    5. Feb 24, 2010 12:14 PM (in response to jjaeger)
    Re: Rollup two Cores on different Domains with no trust

    Also try opening the regsitry editor on the rollup core, and remotley connecting to the source / child core (File > Connect Network Registry) and reading HKLM\SOFTWARE\LANDesk\ManagementSuite\Core\Connections\Local.

  • jradziszewski SupportEmployee 32 posts since
    Jun 2, 2009

    Has received 1 of 9 achievements.
    Currently Being Moderated
    7. Feb 25, 2010 3:08 PM (in response to jjaeger)
    Re: Rollup two Cores on different Domains with no trust

    If you run the NET USE command (e.g NET USE * \\server\c$) from a command prompt window (CMD.EXE) you should see the following message in the command prompt window.

     

    Drive X: is now connected to \\server\c$.

     

    The command completed successfully.

     

    If you are prompted for credentials, enter those and you should see the same message.

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 20 points
  • Helpful Answers - 10 points
LANDESK Community powered by Jive SBS® 4.5.7.1  |  Legal Notices  |  Privacy Policy  |  Icon 

TweeterOn Twitter  |  Icon FacebookOn Facebook © 2007 LANDESK Software