Anonymous_User Absent Member.
Absent Member.
239 views

AD drover 4.0.2.2 PowerShell


Hi,

Working with the new AD driver and the PowerShell part.
Is it only oneliners we can do?

Was going to create Home Directories and that seems to be
straightforward until we come to the rights issue, adding the correct
rights seems to need a script.

Found this rather good article: http://tinyurl.com/poqvg73

So, Ideally the File management suite would be the tool.

Other option I can think of is the sneaky cat driver written by Alex,
the scripting driver or the text driver together with a scheduled
script.

Has anyone done this with only the AD driver? or do you handle the Home
Directories afterwards somehow?


--
joakim_ganse
------------------------------------------------------------------------
joakim_ganse's Profile: https://forums.netiq.com/member.php?userid=159
View this thread: https://forums.netiq.com/showthread.php?t=49140

Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: AD drover 4.0.2.2 PowerShell

joakim ganse <joakim_ganse@no-mx.forums.netiq.com> wrote:
> Hi,
>
> Working with the new AD driver and the PowerShell part.
> Is it only oneliners we can do?


I can't see why you can't use a oneline invoke-expression cmdlet to call a
script.

The big negative of ad driver powershell is only success/error can be
returned.

> Was going to create Home Directories and that seems to be
> straightforward until we come to the rights issue, adding the correct
> rights seems to need a script.
>
> Found this rather good article: http://tinyurl.com/poqvg73
>


The rights part is by far the hardest part. I don't entirely like the way
the various windows scripting languages have chosen to expose sacl/ace
management. They all have different nasty gotchas. I've found shelling out
to setacl.exe is often far easier and more reliable.

> Other option I can think of is the sneaky cat driver written by Alex,
> the scripting driver or the text driver together with a scheduled
> script.
>
> Has anyone done this with only the AD driver? or do you handle the Home
> Directories afterwards somehow?


I've only done this with the scripting driver, both in vbscript and
powershell.

--
If you find this post helpful and are logged into the web interface, show
your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD drover 4.0.2.2 PowerShell


Thanks,

the Invoke-Expression was what I was looking for.

Agree with that this is far from the best method of doing it, but I
think it works for the task of just adding the starting point of the
Home Directory.


--
joakim_ganse
------------------------------------------------------------------------
joakim_ganse's Profile: https://forums.netiq.com/member.php?userid=159
View this thread: https://forums.netiq.com/showthread.php?t=49140

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD drover 4.0.2.2 PowerShell

On Tue, 05 Nov 2013 14:45:41 +0000, joakim ganse wrote:

> Has anyone done this with only the AD driver? or do you handle the Home
> Directories afterwards somehow?


We do Home Directory management using Novell Storage Manager. Works great
for OES and Windows servers.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.
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.