Back to Contents Page

Appendix B — Troubleshooting: Dell OpenManage™ Remote Install User's Guide

bullet.gif (1107 bytes) Recovering Remote Install Images From a Corrupted Image Server Database bullet.gif (1107 bytes) Managing Images
bullet.gif (1107 bytes) Configuration Change Issues bullet.gif (1107 bytes) Managing Logs
bullet.gif (1107 bytes) Installation Issues bullet.gif (1107 bytes) Managing DHCP
bullet.gif (1107 bytes) Operation Issues bullet.gif (1107 bytes) Image Capture
bullet.gif (1107 bytes) Managing Storage bullet.gif (1107 bytes) Deployment and Configuration Issues
NOTE: See "Technical Notes" for additional information about storage, system compatibility, and capture.

Recovering Remote Install Images From a Corrupted Image Server Database

If the Remote Install database becomes lost or corrupted, previously stored images that were not exported as backup images become inaccessible through Remote Install. It may be possible to recover such an image by manually zipping the directory that holds the image and then importing the image back to the image server using the manually zipped archive. This zip utility is located on the image server at:

InstallDrive:\dell\openmanage\netstart\utilities\ImageZip.bat

where InstallDrive is the drive letter of the Remote Install installation drive. 

To attempt to recover an image using this method, perform the following steps: 

  1. Navigate to the Remote Install storage directory that contains the image files.

  2. Find the directory that holds the image to be recovered. If the image was captured, its directory is under the \image\ subdirectory of the storage directory; if the image was imported, its directory is immediately under the storage directory. 

  3. All image directories have randomly-generated names. To assist you in finding the correct directory, use Notepad to open the package.conf file in each image directory and browse for the following strings:

imageName=name  

comment=comment  

where name is the name of the image and comment is the image description.  

  1. Navigate to the directory in which ImageZip.bat resides and use the recovery utility to generate the Zip file. 

The syntax for the utility is: 

ImageZip.bat myRecovery.zip ImageFolder InstallDrive  

where myRecovery.zip is the output zip file which is ready to be imported by Remote Install, ImageFolder is the directory of the orphan image to be recovered, and InstallDrive is the drive letter without the colon (for example, C or D,) under which Remote Install was installed. 

Example syntax: 

ImageZip.bat C:\orphan1.zip C:\storage\jib2XkpsjA4lx1_y C 
ImageZip.bat C:\orphan2.zip C:\storage\image\image.as2elfuKQjd983a1 C 

The zip file is ready for image import.

  1. Use the Remote Install browser-based GUI to import this image.

Configuration Change Issues

Changing the Configuration of a Target System

If you change the IP address of a target system or other network configurations, you must delete the target system from Remote Install's list of discovered systems, reinstall the services on the target system so that the image server can correctly communicate with it, and then allow Remote Install to redetect the target system through DHCP/PXE from the image server. 

Changing the Configuration of the Image Server

If you change the network configuration or settings for the image server, you must perform one of the following steps:


Installation Issues

Problem Symptom Diagnostics/Solution
The intended image server does not meet the requirement of Remote Install. For example, the image server is running Microsoft Windows 2000 Professional operating system or the image server is a Dell™ OptiPlex™ system. Installation failure. Check system requirements and use proper systems.
The user does not have Administrator privilege during the installation. Installation failure. Log in as a user who has Administrator privilege to install the software.
Sufficient space is not available in the image server to install Remote Install. Installation failure. Check system requirements and prepare enough storage for the image server.
Ports used by other applications conflict with the ports used by Remote Install. Strange and inconsistent communication behavior when using Remote Install. For example, Remote Install uses port 1311 as default port for its Web server. If for any reason some applications are running on the ports, close them to avoid conflict.
Other DHCP servers are running on the management network. Strange DHCP behavior when using Remote Install. Remote Install carries its own DHCP. Do not run other DHCP servers on the management network. Stop running other DHCP servers on the management subnet.

Operation Issues

Accessing and logging in to Remote Install.

Problem Symptom Diagnostics/Solution
The image server is not running properly. The Remote Install home page returns a blank or error page. The IP address of the image server has been changed. Restart the image server or restart Remote Install. Ensure that the OpForce and Secure Port Server services are running using the Services shortcut under the Admin Tools icon in the Windows control panel.
The admin console is not running properly. The Remote Install home page returns a blank or error page. If you have many large capacity storage locations, the admin console's responses may be delayed while the system calculates storage space. Close your browser and reopen it to retry the operation.
Incorrect Web address including port number. The Remote Install home page returns a blank or error page. Type in the correct Web address. The default port number is 1311. However, this port number is configurable.
The browser has SSL turned off. Cannot access Web page as required by Remote Install. Turn on SSL option for the browser.
The image server is not running. The Remote Install homepage returns an blank or error page. Restart the image server or restart Remote Install services.
Invalid user name and password. Invalid domain and application selection. Cannot log in to Remote Install. Ensure that the log in information is correct.
User does not have administrator privilege. Can log in to Remote Install, but cannot use Remote Install. Give the user Administrator privileges.

Managing Storage

Problem Symptom Diagnostics/Solution
Cannot add a storage to the image server. Enter parameters and click Add; an error message is returned.

The storage server is not running.

The IP address provided in the UI is not the IP address of the storage server.

The storage server is not connected to the image server.

The share directory name for the storage is not correct.

The user name and password to log on to the storage server is not correct.

The storage directory is not shared.

Storage does not show up in the storage list. Storage that was added before does not show up in the storage list.

The storage server is not connected to the image server.

The IP address of the storage server has been changed.

The share directory name of the storage location has been changed.

The share directory of the storage has been set to no-share on the storage server.

Cannot delete storage. Try to delete a storage from the user interface; an error message is returned. The storage has some images stored.

The storage has some update packages stored.

Remove images and RAID packages from a storage location before deleting the storage.

Managing Images

Problem Symptom Diagnostics/Solution
Cannot import image. When submitting the import request, an error message is returned. The intended import file does not exist.

The specified image name already exists.

The storage location is already full.

The image file is not valid.

Cannot export image. When submitting the export request, an error message is returned. The intended export file name is not valid.

The system on which the exported image file is going to reside does not have enough space.

Cannot delete image. When submitting the delete request, an error message returned. The image to be deleted is in use; Remote Install may be deploying it.
The size of the image showing up on the image table is not correct. When listing the image, the size field of the image is not correct. The image is still in the import process.

The image is corrupted.

The operating system field for the image is blank. When listing the image, the operating system field of the image is blank. The image is still not fully imported.

The image is corrupted.

Image import failure. During the image import process, the importing hangs. The storage might be full.

The import file might be corrupted.

The import file was deleted before the import process was finished.

Need to delete the unfinished import image and restart import.

Managing Logs

Problem Symptom Diagnostics/Solution
Cannot show activities. Select time range and maximum number of activities. Click Refresh. The activity table is blank. Wrong time range. The start time is after the end time.
Wrong exported log file. Select time range and maximum number of activities. Click Export. The export file has more items than specified in the max number of activities. The maximum number of activities input is for the activity table on the browser only. The export file will contain all files specified in the time range.
Some activities does not show up in the activity table. Select time range and max number of activities. Click Refresh. Some activities that have happened do not show up. Increase the maximum number of activities to show.

Managing DHCP

Problem Symptom Diagnostics/Solution
Cannot add DHCP scope. Add DHCP scope. Click Add but an error message is returned. The DHCP server is not running. Restart the Secure Port Server service and retry.
Cannot delete DHCP scope. Select a DHCP scope to delete; an error message is returned. The scope entered is not valid.

DHCP scope is in use.

Cannot List DHCP scope. Listing the DHCP scopes displays a blank page. The DHCP server is not running. Restart the Secure Port Server service.

Image Capture

Problem Symptom Diagnostics/Solution
The system to be image-captured is not listed. The system that the user tries to capture is not listed. Remote Install can only capture systems in certain states or status. A system has to be in the Up or Admin state to be captured.
Cannot shut down the target system for image capture. Select and input parameters for the capture. The capture process does not start. Bad connection with the target system.

Malfunctioning of agents.

Image capture stops after the system was shut down for image capture. Submit an image capture request; the target system shuts down, but the capture does not start. Problem with Sysprep or Windows.

The imaging agent fails to detect the target system.

The imaging agent cannot write to the storage.

The target system cannot communicate with the image server.

The storage is full.

System status displays capture failure. Submit an image capture request; the capture does not start and the activities log records I/O errors. Storage is full. Check the amount of free space in the storage. Delete unwanted images from storage to make room for the capture. Retry the image capture.

Check for other connection or storage configuration problems and
then retry the image capture operation.

NOTE: Retrying the image capture operation from the "Capture
Failure" state does not allow you to choose to capture for backup
or capture for deployment; the original capture option is
maintained. 

If the previous measures do not work, delete the system from the
image server and reboot the target system manually.

Image capture stops before the progress bar reaches 100 percent. Image capture initially started successfully. The capture process stops before completion. The storage becomes full during the capture process. Other I/O errors occurred.

The target system lost communication with the image server.

Deployment and Configuration Issues

Problem Symptom Diagnostics/Solution
Target system is not autodiscovered by the image server. Power up a target system in the network. The new target system is not listed in the system list. If Spanning Tree is enabled on a switch port that PXE is attempting to use, the inherent delay before the port starts forwarding packets can cause DHCP to time out. You must either disable Spanning Tree on that switch or turn on a feature that allows the port to begin forwarding packets immediately. An example of such a feature is "port fast learning" on Cisco switches.

The image DHCP server is down.

The target system is not connected to the management network.

The target system does not have PXE support.

The target system is not set to boot to PXE first. See "Configuring Boot Order."

Cannot start deploying to a bare metal system. Power up a bare metal system, select the Deploy tab, cannot see the system.
  1. Ensure that the system is a true bare metal system, meaning that the disk is empty or lacks a partition table. You may need to reformat the disk.

  2. A NONE image might have been assigned to the bare metal system.
Cannot deploy to a bare metal system. Turn on a bare metal system and assign an image and a configuration to the system. Submit the job. The system reboots but goes to Deployment Failure. The image does not match the target system configurations. Possible problems include the disk size of the target system being too small or a mismatched RAID type.
Cannot bring a Dell preinstalled operating system to the Up state. Assign a configuration to the system, power up the system. The system does not go completely to the Up state. Agents are not installed on the target system.

The configuration supplied to the target system is not a valid configuration.

Agent failed to configure the target system.

Agent was able to configure the system. However, the agent could not communicate back with the image server.

Cannot redeploy an image to a system with a running operating system. Select the Deploy tab; the system does not show up on the list. A system cannot be redeployed when it is in the Up state. It has to be brought to the Admin state to be redeployed. See "How do I Change a System's State to Admin?"
Cannot redeploy an image to a system in Admin state. Select the Deploy tab; assign an image and a configuration to the system. Submit the job and nothing happens. The agent on the target system was corrupted.

A bad network connection exists between the image server and the target system.

The Dell OpenManage KickStart utility running on the image server conflicts with the KickStart utility running on the target system. Image server displays Unmanaged status for a system in the Wait For Configuration state. The image server should not be running the KickStart utility.
Target system waiting to be rebooted. Image server displays Wait for Reboot state for the target system. Verify that the network is connected correctly, then reboot the target system.
Target system displays Unknown error state. Image server displays Unknown state for the target system. Delete the target system from the image server, add it back, and then reattempt the operation that generated the error. If the error persists, contact technical support.

Back to Contents Page