DS7.1: An Imaging "job" will all run correctly until it fails on the Ghost task with 'file not found'.
|Article:TECH127631|||||Created: 2010-05-24|||||Updated: 2010-10-26|||||Article URL http://www.symantec.com/docs/TECH127631|
We have created an image of a system, but on deployment of the image, though the rest of the job runs correctly, the actual imaging task with Ghost fails because the image file can not be found.
There are several possible causes, but the common ones follow:
- The Task Server to which you are connected is a down-line Notification Server in a hierarchy and is not a package server.
- The image has been restricted from replication to all package servers and you are attempting to get it from one that doesn't have it.
- The Package Server services have not been installed on the Task Server to which the client is connected during imaging.
- The image was captured on a Site Server but the client connects to the NS for the image (the NS isn't a package server).
- Package replication has failed to the package server / task server the client is connected to.
- The package/image source location has become damaged or removed.
NOTE: DS 7.1 is designed to pull images from the Task Server to which a client connects on the assumption that the Task Server will have Package and DS Site services installed. This is how the product is currently designed and how your NS installation should be managed to properly use DS 7.1. With that in mind, please read the following comments:
- The best resolution for this is to restrict users from using the NS as a Task Server.
- The NS could also be made a Package Server, but this isn't recommended. Hierarchy replication uses Package Server replication, and it is not recommended that the NS be a package server. Therefore, packages from top-tiers never make it to the NS itself, just to outlying package servers.
- A change request has been made to change the behavior of the task to automatically find a package server with the image.
- Change the replication of the image package. By default, all DS images are set to replicate to all package servers. If you have restricted this manually and a client connects to a task server on that package server, it will fail by design.
- Install Package Services on the Task Server, or restrict imaging clients from connecting to the task server. Please review the "note" above.
- Same as #1 above - restrict the clients from connecting to the NS for Task Services. Images are always replicated using Package replication, even within a site, and therefore don't get BACK to the NS. Images are only on the NS if captured there.
- We have seen instances of packages failing to replicate. This could be caused by IIS llimitations, environmental, or others. There is also a known issue where HTTP package replication will fail on files 2G or larger sometimes - the default image file size. You may need to either shrink the file size of the images (try 1.5G instead) or restrict package server replication to UNC instead of using both HTTP and UNC.
- If the package source location is deleted, the image is generally removed from all target locations. More on this can be found in HOWTO21731. In short, packages are designed to keep up-to-date, so if you make changes in the source, those changes are replicated out to the destinations. Deleting an image constitutes a change, and generally, that deletion is then replicated out, thus wiping out all images. You'll have to find either a backup of the image or re-capture to resolve this.
Article URL http://www.symantec.com/docs/TECH127631