This section provides instructions for resolving issues with device imaging.
Clicking on the Device Imaging node of the Configuration Manager will refresh the summary information for all device imaging requests, regardless of the time set in the Schedule Home Page Summarization. There is no workaround for this issue at this time.
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.|
If a device has ever been a member of a collection that is selected for device imaging, the device is considered to still be a member of the collection. For example, if a thin client device is changed to another type of device, it is included when the All Thin Client Devices collection is selected for device imaging. Also, the number of devices listed on the Device Imaging home page does not decrease when a device is removed from a collection.
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:
- For systems running a 64-bit operating system: “HKLM\Software\
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.