Anonymous_User Absent Member.
Absent Member.
189 views

AD Driver Patch OS Architecture


I have member server in my domain running a remote loader. This member
server is running a 32-bit OS version. The DC's in the domain are all
64-bit OS version. When applying the AD driver patch, what architecture
should I go with? The one that matches the member server or the one that
matches the domain controllers? Or maybe a combination of both? This
thought just came to my mind when I realized that the pwfilter.dll file
included in the patch is supposed to be installed in the DC's. Isn't
that correct?


--
celsolima
------------------------------------------------------------------------
celsolima's Profile: https://forums.netiq.com/member.php?userid=260
View this thread: https://forums.netiq.com/showthread.php?t=47079

Labels (1)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: AD Driver Patch OS Architecture

On 3/13/2013 12:24 PM, celsolima wrote:
>
> I have member server in my domain running a remote loader. This member
> server is running a 32-bit OS version. The DC's in the domain are all
> 64-bit OS version. When applying the AD driver patch, what architecture
> should I go with? The one that matches the member server or the one that
> matches the domain controllers? Or maybe a combination of both? This
> thought just came to my mind when I realized that the pwfilter.dll file
> included in the patch is supposed to be installed in the DC's. Isn't
> that correct?


The later RL's include both architectures, and the patches include
patches for both.

So that teh CPL can have both versions on hand, for whatever type of DC
it encounters.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD Driver Patch OS Architecture

On 13.03.2013 17:24, celsolima wrote:
>
> I have member server in my domain running a remote loader. This member
> server is running a 32-bit OS version. The DC's in the domain are all
> 64-bit OS version. When applying the AD driver patch, what architecture
> should I go with? The one that matches the member server or the one that
> matches the domain controllers? Or maybe a combination of both? This
> thought just came to my mind when I realized that the pwfilter.dll file
> included in the patch is supposed to be installed in the DC's. Isn't
> that correct?


The patch instructions are pretty clear on this.

You are pretty much correct in that you need to apply the 32 bit
specific files locally on your member server and the 64 bit password
filter DLLs on your DCs

However, there is a twist regarding the Password Sync control panel
which you run on the server that hosts the remote loader.

Within the Password Sync control panel you can remotely install/update
the pwfilter.dll on each DC. The control panel looks in the
c:\Novell\IDM_PassSync\w32 and c:\Novell\IDM_PassSync\w64 directories
for the correct pwfilter.dll file to copy to the DC - so you should make
sure to update *both* 32 bit and 64 bit binaries locally under
c:\Novell\IDM_PassSync

--
----------------------------------------------------------------------
Alex McHugh
NetIQ Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support is provided via email.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD Driver Patch OS Architecture


I am not sure about the installation instructions being pretty clear
unless you are looking at a different documentation than I am. You are
providing information in your reply that I cannot find anywhere in the
patch installation instructions. If those instructions about the
IDM_PassSync fodler are somewhere else, could you point me to the source
for my future reference?


--
celsolima
------------------------------------------------------------------------
celsolima's Profile: https://forums.netiq.com/member.php?userid=260
View this thread: https://forums.netiq.com/showthread.php?t=47079

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD Driver Patch OS Architecture

On 13.03.2013 18:54, celsolima wrote:
>
> I am not sure about the installation instructions being pretty clear
> unless you are looking at a different documentation than I am. You are
> providing information in your reply that I cannot find anywhere in the
> patch installation instructions. If those instructions about the
> IDM_PassSync fodler are somewhere else, could you point me to the source
> for my future reference?
>
>


I was referring to the instructions (readme_5094830.html) from "IDM
4.0.1-3.6.1-3.5.1 Active Directory driver version 3.5.14 Patch 8" - the
latest patch.

Under the section: Password Filter Update:

3. On only the server with the Remote Loader, copy the patched
pwfilter.dll to the following locations:
Use the pwfilter.dll from the \32-bit directory and copy to
the\Novell\IDM_PassSync\w32.
Use the pwfilter.dll from the \64-bit directory and copy to
the\Novell\IDM_PassSync\w64.

These are the files that IDM uses when it copies the filter to a new
domain controller

--
----------------------------------------------------------------------
Alex McHugh
NetIQ Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support is provided via email.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: AD Driver Patch OS Architecture

On Wed, 13 Mar 2013 16:24:01 +0000, celsolima wrote:

> I have member server in my domain running a remote loader. This member
> server is running a 32-bit OS version. The DC's in the domain are all
> 64-bit OS version. When applying the AD driver patch, what architecture
> should I go with?


The actual binary for the shim (addriver.dll) is running on the member
server, so you need the 32-bit version of that.


> thought just came to my mind when I realized that the pwfilter.dll file
> included in the patch is supposed to be installed in the DC's. Isn't
> that correct?


Yes.


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

Please post questions in the forums. No support provided via email.

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.