OK scratch that – it of course does work interactively. I was just being thrown off by the fact one has to (re)config/specify the local Admin instance each time. Later on in the interactive it asks for the remote
hosts. Silly me.
-Kirk
From: Kirk MacDonald [mailto:Kirk.MacDonald@xxxxxxxxxxxxxxxx]
Sent: Thursday, August 24, 2017 1:36 PM
To: Mark Reynolds <mareynol@xxxxxxxxxx>; General discussion list for the 389 Directory server project. <389-users@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: [389-users] Re: Registering remote 389-DS instances in Console
Thanks for the reply. I am struggling with the script because it only seems to see local instances, when running the script interactively.
Sent:
Thursday, August 24, 2017 1:30 PM
To:
General discussion list for the 389 Directory server project.; Kirk MacDonald
Subject:
Re: [389-users] Registering remote 389-DS instances in Console
|
On 08/24/2017 11:30 AM, Kirk MacDonald wrote:
I have built 3 new 389-DS instances (389-Directory/1.3.5.10 B2017.145.2037) on different services. Each has local Admin console. They are all in the same Administrative Domain.
Perfect...
Are you planning on using one central Admin/Config server? If so, you just need to registers the other 3 remote servers with your local one. Done.
If want to goto any admin server and see all the other servers then you have to do the same thing on each host: Goto Server A, and register B, C, D, goto Server B - register A, C, D, etc, etc.
Or, is there a more “simplistic” approach that can be done via each Admin console UI?
Using the script is the easiest. There is no way to do it via the console ui.
Regards,
Mark
Thanks,
Kirk MacDonald
Eastlink
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
|
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
