Searching...
Filters
SmallMediumLarge
Home Print Show Topic URL Previous Next
IT Management Suite
Client Management Suite
Server Management Suite
Deployment Solution
Asset Management Suite
ServiceDesk

Troubleshooting Tip: Imaging and Install OS task

Deployment Solution

The troubleshooting tips related to the imaging and install OS tasks of Deployment Solution are as follows:

Table: Imaging and Install OS task

Issue

Description

Workaround

The following error message occurs when you create an image over HTTP with the -ID switch:

Not enough space on destination drive. Spanning is not supported on this drive.

When you create a sector- by- sector image over HTTP, where HTTP is configured on Windows 2003 32-bit, IIS 6.0 displays the error message:

Not enough space on destination drive. Spanning supported on this drive.

  • Use -split switch when you create image, where -split size is less than 2GB.

  • Configure HTTP on 64-Bit Windows.

An error occurs when you join a Vista computer to a domain

You clone a Vista computer using an image that you prepared with Sysprep.

Apply configuration changes. When you try to join the computer to a domain, the following error occurs:

Windows can't complete the installation

Join the computer to a domain using a different task after the Clone task.

Preserved files on Vista computers have incorrect names

Windows Explorer (Vista) may not show the correct name for a folder that is preserved and renamed after a clone task. This problem occurs if the renamed folder contains a copy of desktop.ini.

Find and delete the hidden file named desktop.ini inside the affected folders. Windows Explorer should then correctly display the folder name.

CRC files created by Symantec Ghost return a false result

By default, Symantec Ghost informs the operating system about the disk layout after a clone.

However, that might cause the CRC files created by Symantec Ghost to return a false result. The false result could be that disks are not identical when they are identical.

For example, after an image-to-disk restore, a CRC32 verify that operation might return an inaccurate CRC result because under WinPE, the source disk remains mounted by Windows

Therefore, a CRC create on the source disk and then a verification on the destination disk may return an inaccurate CRC result because WinPE can change the source drive.

The -noOs switch prevents ghost from updating the operating system with the destination disk changes. The source is mounted by Windows and therefore the CRC value may change due to system file changes by Windows and therefore the CRC value may change due to system file changes by Windows

If the source image and destination disk have similar partition layouts, then be sure the system from mounting a file system driver once the clone is complete. This can happen on similarly partitioned disks even when you use the -nooslayout switch.

In IE8 native mode, the credentials on the Deploy Image task disappear when you type the credentials on the Deploy Image task and click Advanced.

In IE8 native mode, if a user types the credentials on Deploy image task, and clicks on Advanced tab, the credentials on Deploy image task does not appear

Use the IE7 compatibility view in an IE8 web browser. The credentials appear even after you click Advanced.

The Deploy Image task gets error during the XP GHO image import when the Windows XP operating system boots with DeployAnywhere

When you execute the Deploy Image task with the DeployAnywhere option enabled on a Windows XP computer, you encounter a non-functioning of the keyboard and mouse when booting the operating system. This problem does not recur frequently

You are required to connect to a different USB keyboard to continue with the installation.

Any of the following errors are displayed during execution of Install Linux/ESX OS task:

  • 'DISK NOT FOUND' with error code 101 when computer is in the automation

  • 'Error 15 : File not found' when computer boots into production

This issue occurs if the Linux OS's Linux kernel version is older than version 2.6.27 and you use IDE disks. For example, this issue can occur in RHEL 5 and on versions earlier than SUSE 10.2.

You can perform either of the following to successfully install the Linux OS:

  • Replace %DISK% token by actual device name in the configuration or answer file.

    The Linux configuration file is located in, <instaldir>\Program Files\Altiris\Notification Server\NSCap\bin\UNIX\Deployment\Linux\x86\SOI\AnswerFile path.

  • Remove %DISK% token from the answer file.

Deploy Image task fails on unknown client computers when configured in an Initial Deployment job

If Deploy Image task is configured in the Initial Deployment job, then it fails for some client computers.

You must add the following command in the Command-line options field of the Command -line tab of the Advanced option of the Deploy Image task:

-mp -clients=3 -threshold=2 -connectimeout=10

Windows 8 client computer fail to join the domain that is specified in the Deploy Image task.

After you execute the Deploy Image task on a Windows 8 client computer, the computer is not able to join the domain that is specified in the Deploy Image task.

You must execute the Apply System Configuration task on the Windows 8 client computer after executing the Deploy Image task to join the domain.

The Deploy Image task fails to deploy an image of Windows 12 BIOS type client computer on a UEFI enabled client computer.

This issue occurs when you deploy an image of Windows 12 BIOS type client computer on a UEFI enabled client computer.

You must add the following command in the Command-line options field of the Command -line tab of the Advanced option of the Deploy Image task:

-cesp

The Create Image task fails when you create an image of a client computer

The Create Image task fails for a package server that is configured with IIS, as the Deployment folder is missing from the following path in the IIS:

Sites\Default Web Site\Altiris\PS\

This issue occurs if you install the Deployment Solution package server component and then enable the Network Boot Service (NBS) on the site server that is configured with both package server component and the NBS.

You must execute the Create_DeploymentDir.bat command that is placed in the following location:

<install_dir>/Altiris/Altiris Agent/Package Delivery/76D113DE-16D4-4A31-826F- A4DACCEAC8AB}/cache/

An error is displayed when you execute the Install Windows OS task that is accessed from the console and is launched from a computer other than the Notification Server computer

When you execute the Install Windows OS task with a custom answer file that is accessed from the console and is launched from a computer other than the Notification Server computer

Unattended upgrades using setup /unattend with no answer file are not supported when running Windows PE

You must install the Java SE Runtime Environment 7u25 on the Notification Server computer.

The Prepare For Image Capture task fails for Windows 8 client computer

The Prepare For Image Capture task fails for Windows 8 client computer that is not restarted after installing a Windows update.

You must restart the Windows 8 client computer after installing the Windows updates.

A client computer does not join the domain after the Deploy Image task is performed.

A client computer does not join the domain after the Deploy Image task is performed if the image deployed on the client computer is not prepared using the Sysprep utility.

You must deploy an image that is prepared using the Sysprep utility.