Dangers of using SYSPREP after NICI has been installed
This document (3057160) is provided subject to the disclaimer at the end of this document.
Error -1460 and -1418 changing passwords with NMAS authentication enabled
Preparing an image for deployment
Internal error 0xFFFFFA27 reported when logging into NDS with NMAS enabled
Error -1497: CCS_E_AUTHENTICATION_FAILURE (0xFFFFFA27) FFFFFA27
Dangers of running SYSPREP after NICI has been installed
If you are going to image a workstation and run SYSPREP, it
would be best to NOT install the Novell Client
(which installs NICI) until after SYSPREP has been run and the
image has been restored to the workstation.
Per Microsoft's web site onHow to use Sysprep- Microsoft warns of
using SYSPREP, under "General notes about sysprep"
"You cannot run Sysprep on a computer that has been configured as a Cluster Service server, a Certificate Services server, or a domain controller. You can run Sysprep on a standalone server. If you run Sysprep on an NTFS file system partition that contains encrypted files or folders, the data in those folders become completely unreadable and unrecoverable."
With that said, NICI is part of this Certificate Services and
running SYSPREP will cause problems with NICI.
2. Reboot the workstation into Safe Mode. Make the Administrator the owner, with full rights, of the C:\WINNT\system32\Novell\nici directory and all child directories and files.
3. Delete the entire nici directory structure where you just set the rights. Example: Delete the nici directory in C:\WINNT\system32\Novell\
4. Boot back into Windows 2000 normal mode and re-install nici.
Formerly known as TID# 10091539
Formerly known as TID# NOVL95769
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3057160
- Creation Date:05-FEB-07
- Modified Date:14-FEB-17
Did this document solve your problem? Provide Feedback