Device Imaging Troubleshooting
This section provides instructions for resolving issues with device imaging.
Device imaging deployments created using previous versions of Device Manager 2011 that do not have an expiration time set will continue to re-image indefinitely and can cause data inconsistency. Terminate all such deployments and upgrade to the latest version of Device Manager 2011.
Device imaging deployments created using Device Manager 2011 SP1 with the default status message deletion date of 180 days after the expiration date and that are later changed to a status message deletion date of less than 180 days while deployments are outstanding may result in re-imaging or incorrect reports. For example, if you change the status message deletion date to 30 days, suspend or otherwise change the state of the deployment, and then try to restart the deployment after the status message deletion date, the deployment will continue to re-image indefinitely and can cause data inconsistency, such as incorrect reports. Make sure outstanding deployments are completed before changing the status message deletion date.
Device imaging deployments should target collections that contain only the devices that need to be re-imaged, and that will exclude those devices after they are re-imaged. Otherwise, devices will re-image indefinitely. For this reason, you should not target deployments that do not change the device type of re-imaged devices at the predefined device collections. To avoid having devices re-image indefinitely, create a collection query for an inventory property value that is changed after devices are re-imaged. For example: if you are updating the OEM firmware version of a set of devices with your deployment, create a collection query that looks for the outdated OEM firmware version. This way, each device is excluded from that query after the device is re-imaged.
The device imaging reports filter by device name and only report the status state a device is in when the report is created. The Device Imaging home page reports all of the states that all of the devices go through during device imaging. If a device had more than one state during device imaging, a duplicate record for that device is listed on the Device Imaging home page.
Check the Application Event log to see whether the device imaging deployments store (Osdjobs.xml) is corrupted. The Osdjobx.xml file stores deployments as serialized XML nodes. If the Application Event Log states that the Osdjob.xml file is corrupted, an external event has caused this corruption. Stop the Device Imaging service and repair the Osdjobs.xml file.
|For more information about the Application Event Log, see How to Check the Application Event Log for Errors in Configuration Manager Help.|
To stop the Device Imaging service, open a Command Prompt window and enter the following Services Snap-in command:
net stop “EDM Device Imaging Service”
Note: For more information about how to use the Services Snap-in commands, see Start, stop, pause, resume, or restart a service on TechNet.
Browse to %programdata%\Microsoft\EDM\LocalStore\OSD and locate Osdjobs.xml_old.
Make a copy of the Osdjobs.xml_old file and store it at a different location.
Open the Osdjobs.xml_old file. Repair any XML tags that are not well formatted and any other errors.
Save the file with the name Osdjobs.xml and store the new file in %programdata%\Microsoft\EDM\LocalStore\OSD.
To start the Device Imaging service, open a Command Prompt window and enter the following command:
net start “EDM Device Imaging Service”
Information and device imaging deployments present before the corruption occurred should now be restored and visible. Recreate the deployment that failed.
View the Device Imaging home page and make sure that the deployment is completed successfully.
|If the problem continues with that deployment, run a deployment that has completed successfully in the past. Browse to %programdata%\Microsoft\EDM\LocalStore\OSD and compare the successful deployment’s Osdjobs.xml file to the Osdjobs.xml_old file.|
The following two registry keys can affect the behavior of the collections installed with Device Manager 2011:
For systems running a 32-bit operating system: “HKLM\Software\Microsoft\EDM\OSD”
For systems running a 64-bit operating system: “HKLM\Software\ Wow6432Node\Microsoft\EDM\OSD”
If collections seem to behave incorrectly or there are issues with memory usage after device imaging, check the following two values of the above registry keys:
ServiceDelayMinutes: If this value is present, the scheduler that checks the membership of Device Manager 2011 collections runs after the number of minutes set in this value; if this value is not present, the scheduler runs once each hour.
CacheExpirationMinutes: If this value is present, it sets the number of minutes the cache of status information about devices in a device collection for a particular device imaging deployment is kept in memory by the Device Imaging service. If the device imaging component does not query or set the status of any device for a particular deployment, then the corresponding device cache is deleted from memory.
After updating the system registry, you must restart the Device Imaging service before the new settings will take effect. For more information about registry keys, see the Embedded Device Manager 2011 SDK on MSDN.