When performing a centrally initiated deployment, the 'Conflict' page of the deployment wizard will display information about the required user intervention. There are many reasons why user input may be required. Below is a complete list of items that can be displayed on the 'Conflicts' page, what the message means, and steps that can be taken to resolve the conflict.
Sysprep Errors
Sysprep name errors
These errors can occur when the 'Sysprep answer file' option is selected, and 'Computer Name' is enabled. These errors can be resolved by editing the name that has been specified for the endpoint(s).
| Conflict Error Message |
|---|
A computer name must have a minimum length of 1 character |
A computer name can not be longer than 15 characters |
A computer name can not be only numbers |
A computer name can not start with a . character |
A computer name can not contain any of the following characters \\ / : ? " < > or spaces |
The current input is a reserved Windows name and can not be used |
Sysprep admin account or local admin account
These errors can occur when the 'Sysprep answer file' option is selected, and 'Create Computer Account' is enabled. These errors can be resolved by editing the credentials that have been specified for the computer account:
| Conflict Error Message |
|---|
| No username has been provided for new administrator account |
| No password has been provided for new administrator account |
| An invalid username has been provided for new administrator account |
Sysprep domain errors
These errors can occur when the 'Sysprep answer file' option is selected, and 'Join Computer to a Domain' is enabled. These errors can be resolved by checking the name of the domain that has been specified, and the credentials that have been provided to join the specified domain.
| Conflict Error Message |
|---|
| No domain name has been provided |
| No domain username has been provided |
| No domain password has been provided |
| An invalid domain name has been provided |
| An invalid domain username has been provided |
General Server Errors
Golden image errors
These errors will reset the 'Deployment' wizard to page 2, this indicates that the golden image that was selected needs to be changed.
| Conflict Error Message | Recommended Troubleshooting |
|---|---|
| Selected golden image file could not be found | Ensure that the golden image store is online and that the selected golden image is available. A different golden image may need to be selected. |
| Selected golden image store could not be located | Ensure that the golden image store is online and that SiteDeploy is able to access the share. This can be done by editing the golden image store on the 'Golden Image Stores' page of SiteDeploy. |
Drive Selection
These errors occur when a destination drive needs to be specified if multiple disks exist on the target endpoint, or if the target disk is unsuitable for the deployment.
| Conflict Error Message | Recommended Troubleshooting |
|---|---|
| Select a drive | If the endpoint has multiple drives connected this message will be displayed, select the drive that will be used as the destination for this deployment. |
| Target drive too small | Ensure that the computer has a drive with sufficient storage for the golden image that will be deployed to it. |
| Target drive not found | |
| Golden Image is a dynamic volume and the agent doesn't contain a dynamic volume to copy to | Deploying a golden image that contains a dynamic volume requires an existing dynamic volume on the target drive. Ensure that the destination drive has a dynamic volume structure that matches the dynamic volumes in the golden image. Partitions can be created in the deployment media by launching Reflect and then using the command line utility with the Diskpart commands. For more information on using Diskpart, see this article. |
Other
| Conflict Error Message | Recommended Troubleshooting |
|---|---|
| Agent no longer available | |
| Agent architecture does not match golden image | This indicates that the target computer's CPU architecture does not match the operating system contained in the golden image. For example, attempting to restore an image that contains a 64-bit operating system to an endpoint that has a 32-bit processor. A different golden image should be selected that matches the architecture of the endpoint. |
| Agent has a different recovery environment to image | This indicates that the endpoint PE |
Agent/Endpoint errors
| Conflict Error Message | Recommended Troubleshooting |
|---|---|
| This computer is no longer in Recovery Environment | The endpoint is no longer in the recovery environment. Boot the endpoint again using the deployment media. |
| The following agents are no longer in the Recovery Environment | Multiple endpoints are no longer in the recovery environment. Boot the endpoints again using the deployment media. |
| This computer is still initializing into the Recovery Environment | |
| This computer is performing another activity | |
| This computer is not connected to Site Manager | |
| Select a computer to proceed | |
| Reflect is being manually used while this computer is in the Recovery Environment | |
| This computer is performing an automatic restore from the Recovery Environment | |
| There is a connection error with this computer in the Recovery Environment | |
| This computer is performing a directed restore from the Recovery Environment | |
| This computer is performing a directed deployment from the Recovery Environment |