Cannot automatically join Windows domain via SYSPREP after installing UNC name filter

  • 7002511
  • 30-Jan-2009
  • 27-Apr-2012


Novell Client 4.91 SP5 for Windows 2000/XP
Novell Client 4.90 for Windows NT/2000/XP
Novell Client 4.83 SP2 for Windows NT/2000/XP
Microsoft Windows  XP Professional


Cannot automatically join Windows domain via SYSPREP after installing UNC name filter
This issue was originally reported on the 4.83 and 4.90 versions of the client and fixed in 4.90 SP2
It has reappeared on the 4.91 SP5 version of the client and a new defect has been entered against that version
this TID will be updated if and when the bug with 4.91 SP5 is fixed.
Microsoft SYSPREP reports domain name is invalid.
Issue may vary depending on speed of machine.  Customer reports suggested that slower workstations did not appear to exhibit the issue.


One workaround is to disable the NWFILTER service until after SYSPREP has completed the domain joining portion of the setup process.  This can be accomplished by renaming NWFILTER.SYS and then setting up post-SYSPREP actions to rename NWFILTER.SYS back to its original name.  Or, remove the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NwFilter] key from the image SYSPREP is being run against and then re-import a saved copy of this key after SYSPREP completes.

Fixed in Novell Client 4.9 SP2 NWFILTER.SYS dated January 10, 2005.

Additional Information

If the NWFILTER.SYS driver is disabled prior to running SYSPREP, the problem does not occur.
Note that in the Novell Client 4.90 for Windows NT/2000/XP, NWFILTER.SYS is refered to as the "UNC Path Filter" and is listed in the "Advanced Settings" tab of the Novell client properties.  The NWFILTER service can still be disabled & re-enabled in the same methods described above, and on 4.90 and later it is also possible to disable the service using this "UNC Path Filter" option under the Novell client's "Advanced Settings".

Formerly known as TID# 10086130