Partially upgrading the OSD architecture to version 12.1 and later

If your architecture doesn't permit you to use only one OSD Manager, but there are still some areas of your network where you can consolidate the system, here's a procedure how to partially move to the new OSD architecture.


Make sure you have read the upgrade considerations before you start this process.

  1. Uninstall the Windows AIK and install the Windows ADK on all devices that remain OSD Managers in your new architecture.
  2. After the Windows ADK installation, select the Configuration node of the OSD Manager.
  3. Click Properties .
  4. In the Properties window verify that the Windows ADK Path is correct.
  5. (Optional) If this is not the case, click Select next to the text box. A pop-up menu appears with the directory structure of the device where you can directly select the installation directory. Click OK to confirm and close the window.
  6. Click Test next to the Windows ADK Status box, to test if the Windows ADK is correctly installed.
    If the OSD agent can find the Windows ADK in the indicated directory and it is fully functional the status is updated to Windows ADK installed. For any other status value, review your installation and installation directory and repeat the test until the Windows ADK installed status is displayed.
  7. Click Check Environment to verify that all your OSD Manager parameters are still properly set and working.
  8. Repeat the following procedure on all obsolete OSD Managers that are going to be removed:
    1. Select the projects you want to move to the new parent OSD Managers under the respective Projects node.
    2. Click Edit > Export .
    3. In the Export the Current Node dialog box enter the file path for the export directly into the File Path box or click the button next to it to call a list of all available drives and directories of your client.

      The path entered here must be a full path, it cannot be a relative path. Besides, you must enter a name for your export file with an extension.

    4. Click OK .

      If the content of your exported objects are not in a location accessible by the new OSD Manager, you must also copy all the object content, that is the drivers, the image, and so on, to a location accessible by the new OSD Manager. The directory structure as it is defined in the object must be exactly the same on the target as it was on the source, otherwise the project build on the new OSD Manager will fail.

  9. On the new parent OSD Manager go to the Projects node.
  10. Click Edit > Import .
  11. In the Import a Node dialog box select the file containing the data to import.
  12. Click OK.
  13. When the import is completed, go to the object properties and make sure everything still works, that is, if you are importing a project, click the test buttons and rebuild it.
    Go to the Storage tab to follow as the newly build projects come online again and are synchronized with the OSD Manager's image repository and thus become available to all children.


    If a project appears in the list, but the connected image is not added, an error occurred during the build.

  14. Select the OS Deployment node.
  15. Select all obsolete OSD Mangers, from which you have recovered all still needed objects in the right window pane.
  16. Click Remove OSD Manager .
    All obsolete OSD Managers are removed from the list.
  17. Select your new parent OSD Manager in the left tree and select its Members tab in the right pane.
  18. Click Add Image Repository/Network Boot Listener .
  19. Select the obsolete OSD Manager devices from under this new parent in the Add an Image Repository or a Network Boot Listener window.
  20. Check the Image Repository box.
  21. (Optional) If the agent is not to be a network boot listener, clear the Network Boot Listener box.
  22. Click OK.
    Your obsolete OSD Managers are now all added as image repositories directly under the new parent OSD Manager.
  23. Select the Storage tab of your OSD Manager.
  24. Select the objects that you moved from your obsolete OSD Manager to the new one in the right window pane.
  25. Click Edit > Synchronize button.
  26. In the appearing Select Image Repositories window select your obsolete OSD Manager, that is now an image repository.

    This operation transfers the selected OSD objects from the OSD Manager's image repository to your obsolete OSD Managers and makes them available to the targets.

  27. Click OK .
    The Operation Status window appears, displaying the list of all image repositories and the synchronization status of the objects on each.


    Be aware, that this status only shows, if the synchronization order was sent to the respective target, it does not indicate that the target received the order or that the objects were synchronized on it.

The order to synchronize the objects on the image repositories is launched. To verify if the image repositories are synchronized, you must check the Storage tab of each target.

Once the synchronization is completed your situation should be as it was before the upgrade, but with the new architecture.


This upgrade procedure purged most OSD folders of generated data on the former OSD Managers. The driver cache folder must be manually removed as well as the Windows AIK, which is no longer required on these devices.

Was this page helpful? Yes No Submitting... Thank you