Troubleshooting

Article:HOWTO63370  |  Created: 2011-12-15  |  Updated: 2011-12-15  |  Article URL http://www.symantec.com/docs/HOWTO63370
Article Type
How To

Subject


Troubleshooting

Table: Troubleshooting

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.

Device in the Device Manager shows an exclamation mark after DA-SOI

When DA-SOI for Non critical drivers is executed,all the DeployAnywhere and scripted OS installations are performed. However when the operating system is up, the devices in the device manager appear with an exclamation mark and cannot be used. When the same drivers are applied to the device manually , the following warning/error message occurs:

driver failed in windows logo test

If the unsigned drivers show an exclamation mark for the devices, use the following tag entry in the unattended answer file:

DriverSigningPolicy

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 WHOAMI

does not get overwritten and PXE listens on the IP addresses that it picks up at startup.

PXE is not binding to the given IP address when the Symantec Boot Services server has two NIC cards installed on it.

This workaround is based on the following conditions:

  • Symantec boot services server is running on win2k8R2.

  • Symantec boot services server has two active NICs.

  • DHCP server and Symantec boot services server are bound on the same NIC.

Assuming that the two NICs are A and B, perform the following to make the Symantec boot services server operational:

  • If you want to use the NIC B for SBS, you need to check the binding preference of this card. Perform the following steps on 2k8 R2 computer:

    Go to Network > Properties> Change Adapter SettingsBoth A and B NICs are present here.

  • On this window (network connections), press Alt (keyboard option).Then the file menu options are visible. Select the Advanced menu and click Advanced Settings . Change the connections order so that NIC B is set to the first row in the list. Click Ok to save the changes.

    You have changed the binding order of the NIC on your computer.

  • Now check the binding of the DHCP server and clicking the DHCP server by Start > Run > dhcpmgmt.msc.

    Click on the + option in the left pane so that the ipv4 and ipv6 options are visible. Then, right-click on the host name and click on the Add/Remove bindings menu. You can see the server Bindings properties window.

    Click on NIC B so that the binding can be set to IP of NIC B only. Then, click Ok to save the changes.

During Installation for Plug-in, a package is rolled out before the maintenance window starts on the client computer when Run once ASAP in maintenance window only is checked in

You cannot install the Deployment Solution plug-in in a maintenance window by using the Run once ASAP in maintenance window only option.

You are required to create a schedule using the Add Schedule option.

PXE-E77 error is received when the client computer is booted to a PXE image

If PXE images were created when SBS services were not running, you receive an error when you boot the client computer to that PXE image. The error that is received is PXE-E77.

Verify that all SBS services are running. If any of the following four services is not running, then start it manually:

  • Symantec netBoot interface

  • Symantec netBoot mtftp

  • Symantec netBoot NSiSignal

  • Symantec netBoot Server

When the services are started, on the Deployment Solution console, click Settings > Deployment > Create Preboot Configurations. Select all the PXE images that were created when the SBS services were not running and click Recreate Preboot environment to recreate them.

To prevent this issue from occurring, ensure that the PXE services are started and set to automatic before you create any preboot configurations.

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 DeployImage 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.

The computer does not connect to the domain when Join Domain option is used from the OS install page

The computer does not connect to the DeployAnywhere domain when Join Domain option is used from the operating system install page.

Join Domain task can be performed using Apply system configuration task.

The Create Image task fails on Linux preos

computer if the image name contains space

The Create Image on HTTP server fails if the image name contains space.

The image name must not contain any space.


Legacy ID



v50308546_v61911175


Article URL http://www.symantec.com/docs/HOWTO63370


Terms of use for this information are found in Legal Notices