"Unable to Add Image to the Image Server" Error Message When You Try to Remotely Add an Automated Deployment Services Image

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
When you try to add an image to the Image Distribution Service (IDS) component and both of the following conditions are true
  • IDS is located on a different computer from the Automated Deployment Services (ADS) Controller.

  • The ADS console is run remotely on the IDS server.
you may experience any of the following symptoms:
  • The Browse button is not available (appears dimmed).
  • When you type the drive letter and the share location to add an image, you receive the following error message:
    Unable to add image to the image server. Cannot find the path specified.
  • When you type the Universal Naming Convention (UNC) path of the image file, you receive the following error message:
    Unable to add image to the image server. Unable to complete the operation. Try running the tool from the controller or using an image path local to the controller.
This issue occurs because the ADS code assumes that the image path that you type in the Add image dialog box is a local path on the ADS Controller. For example, this issue occurs in the following scenario:
  1. The ADS image share is located at \\server name\Adsimages$ on the IDS server.
  2. The F:\Images network share maps to the ADS image share that is described in step 1.
  3. The image file that you try to add is located in the F:\Images folder on the IDS server.
  4. You run the ADS console remotely from the ADS Controller, and then you type F:\images\image name.img in the Add image dialog box.
This operation is unsuccessful because the user credentials are lost during the sequence of network router hops to the Controller and back to the IDS server. The Distributed Component Object Model (DCOM) protocol with NTLM authorization does not pass more than three networks hops--for example, from the IDS server to the ADS Controller and then back to the IDS server.

Even though the physical path location is local to the IDS server, the ADS snap-in expects the image path to be local to the remote ADS Controller. Because the image path is not found on the ADS Controller, you receive the error message that is described in the "Symptoms" section.

Additionally, if the ADS snap-in detects that it is running on a different computer than the ADS Controller, the Browse button is not available.
To add an image to the IDS server when the IDS server is not on the same computer as the ADS Controller, you must use the ADS console from the ADS Controller.
This behavior is by design.
greyed greyed-out grayed grayed-out disabled turned off

Article ID: 822056 - Last Review: 01/05/2015 13:36:49 - Revision: 1.3

  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • kbnosurvey kbarchive kbadsv1 kbsysadmin kbmisctools kbprb kbnofix KB822056