DGantz

Cadet 3rd Class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-04-05
19:25
303 views
Active Directory multiple remote loaders on same server?
Hi
I have 2 Active Directory drivers pointing to same Active Directory. The one driver is doing provisioning into Active Directory and synchronizing passwords. The second one is just pulling a subset of accounts from Active Directory to eDirectory and not synchronizing any passwords. Can I have the remote loaders for both of these drivers running on the same Windows server?
Thanks
Deb Gantz
I have 2 Active Directory drivers pointing to same Active Directory. The one driver is doing provisioning into Active Directory and synchronizing passwords. The second one is just pulling a subset of accounts from Active Directory to eDirectory and not synchronizing any passwords. Can I have the remote loaders for both of these drivers running on the same Windows server?
Thanks
Deb Gantz
3 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-04-05
19:46
On 4/5/2019 2:26 PM, gantzda wrote:
>
> Hi
>
> I have 2 Active Directory drivers pointing to same Active Directory. The
> one driver is doing provisioning into Active Directory and synchronizing
> passwords. The second one is just pulling a subset of accounts from
> Active Directory to eDirectory and not synchronizing any passwords. Can
> I have the remote loaders for both of these drivers running on the same
> Windows server?
Yes, but.
Big but. (Does this Remote Loader make my butt look bigger? Says the
Windows server...)
The first one to run, will register to do passwords. The second one
will NOT. And you cannot easily designate this one to do passwords,
that one not to, it is just simply order of loading.
So make the services dependant on each other, and load the second
instance after the first.
>
> Hi
>
> I have 2 Active Directory drivers pointing to same Active Directory. The
> one driver is doing provisioning into Active Directory and synchronizing
> passwords. The second one is just pulling a subset of accounts from
> Active Directory to eDirectory and not synchronizing any passwords. Can
> I have the remote loaders for both of these drivers running on the same
> Windows server?
Yes, but.
Big but. (Does this Remote Loader make my butt look bigger? Says the
Windows server...)
The first one to run, will register to do passwords. The second one
will NOT. And you cannot easily designate this one to do passwords,
that one not to, it is just simply order of loading.
So make the services dependant on each other, and load the second
instance after the first.
DGantz

Cadet 3rd Class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-04-08
15:38
Well that is a very big but :). I am thinking it might be best to keep them on separate servers, we seem to have to restart these remote loaders when they stop processing for various reasons and I am not sure making the services dependent on each other would help in that situation.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2019-04-08
18:09
On 4/8/2019 10:44 AM, gantzda wrote:
>
> Well that is a very big but :). I am thinking it might be best to keep
Woo, woo there man! No personal attacks. Calling my butt big. For shame
sir, for shame. 🙂
> them on separate servers, we seem to have to restart these remote
> loaders when they stop processing for various reasons and I am not sure
> making the services dependent on each other would help in that
> situation.
It is easier on separate servers. I worked with a site that had 4 AD
Drivers as remote loaders on one server, and it worked, just had to keep
this important but in mind.
>
> Well that is a very big but :). I am thinking it might be best to keep
Woo, woo there man! No personal attacks. Calling my butt big. For shame
sir, for shame. 🙂
> them on separate servers, we seem to have to restart these remote
> loaders when they stop processing for various reasons and I am not sure
> making the services dependent on each other would help in that
> situation.
It is easier on separate servers. I worked with a site that had 4 AD
Drivers as remote loaders on one server, and it worked, just had to keep
this important but in mind.