Possible Causes for Windows Distribution and Deployment Failure

Provisioning a Windows distribution to a managed server can fail for several reasons:

• The Windows operating system might not be compatible with the managed server. For a list of qualified servers, see Manageable Server Requirements in Sun N1 System Manager 1.3 Site Preparation Guide.

• The SSH entries for that managed server on the management server known_hosts file might be stale or obsolete. Determine the management server name and IP address, and then remove the entry for that managed server from the known_hosts as described in To Update the ssh_known_hosts File.

• The product key is unique to each release of the Windows OS. To ensure that the correct product key applies, either modify the OS profile to include the correct product key or use the productkey attribute on the load server command.

• If you encounter a TFTP error when loading the OS profile, the GUID is likely incorrect. To find the GUID of a system, use the Pre-Boot eXecution Environment (PXE) to boot the system.

• If the Linux OS was installed previously on the managed server, Windows will ask about partitions the first time that you try to install Windows on the system. To resolve this issue, delete the partitions on the managed server's disk.

• The operating system name has to be exactly the name given when using the risetup.exe command. For example, D:\RemoteInstall\Setup\English\Images\OS-name where OS-name is the name of the OS.

  The OS architecture type must be specified correctly. For example, a 64–bit OS image should be stored in the RIS server directory D:\RemoteInstall\Setup\English\Images\OS-name\amd64.

• You created the directory C:\N1SM already exists on the RIS server before running n1smconfig, and n1smconfig displays the error INFO : Error when trying to configure RIS server. To resolve this issue, log in to the RIS server and delete the C:\N1SM directory, then run n1smconfig again. The C:\N1SM directory is created on the RIS server by n1smconfig.

• You have upgraded from N1 System Manager 1.3 to N1 System Manager 1.3.1. Delete and re-add the RIS server as described in Windows Deployment Fails after Upgrade from N1 System Manager 1.3 to 1.3.1.