indranil2121 Absent Member.
Absent Member.
317 views

User management to the target windows system

Hi All,
As we all know the features of a FanOut driver. The Fan-Out driver provisions users, groups, and password to multiple databases with minimal effort. Therefore we may provision user and push the password of eDirector to the target system. Only problem of FanOut driver is that it's not supported in Windows server.
Is there any solution For provisioning users with password to a target windows server in NetIQ? We can use scripting driver for this case to manage target windows system, but the problem is if we have 400 windows server to manage for user provision, de-provision we require 400 scripting driver for that case. It's very difficult to manage and support. Your expertise will help us to give a fantastic solution.
Labels (1)
0 Likes
1 Reply
Micro Focus Contributor
Micro Focus Contributor

Re: User management to the target windows system

On 03.12.18 07:04, indranil2121 wrote:
>
> Hi All,
> As we all know the features of a FanOut driver. The Fan-Out driver
> provisions users, groups, and password to multiple databases with
> minimal effort. Therefore we may provision user and push the password of
> eDirector to the target system. Only problem of FanOut driver is that
> it's not supported in Windows server.
> Is there any solution For provisioning users with password to a target
> windows server in NetIQ? We can use scripting driver for this case to
> manage target windows system, but the problem is if we have 400 windows
> server to manage for user provision, de-provision we require 400
> scripting driver for that case. It's very difficult to manage and
> support. Your expertise will help us to give a fantastic solution.
>
>


You're not the only one.

Novell/NetIQ Consulting Germany build a driver for this, some years
back, but it still works - you can try to ask them.

Or you can build your own driver using the Scripting driver as base. In
general you need to have two things;

a) a way to set the destination-dn which could be the fqdn server name,
or something similar.

b) a set of modified scripts which does what you want using powershell.

The can be a problem, if you do not have all the servers in the same
domain, then you will have to login for each operation, which will take
time - lots of it. And then you're back at the only solution being the
Fanout driver.

I have looked at building something like this, and it is not overly
complicated.

You should also look at using the Scripting Driver Service which will
make it faster.


Casper
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.