Space banner

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Upgrading OSD to v12.1 and later by consolidating to one OSD Manager

This upgrade process is only for implementations that use the same projects and images throughout their entire infrastructure.

Upgrading to the new architecture with only one OSD Manager involves several steps.

Note:

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

  1. Go to the OS Deployment node.
  2. Define which of your many OSD Managers is going to be your unique OSD Manager.
  3. Select all other OSD Mangers in the right window pane.
  4. Click Remove OSD Manager .
    All spare OSD Managers are removed from the list, only the future OSD Manager remains.
  5. Select your OSD Manager in the left tree and select its Members tab in the right pane.
  6. Click Add Image Repository/Network Boot Listener .
  7. Select the former OSD Manager devices in the Add an Image Repository or a Network Boot Listener window.
  8. Check the Image Repository box.
  9. (Optional) If the agent is not to be a network boot listener, clear the Network Boot Listener box.
  10. Click OK .
    Your former OSD Managers were now all added as image repositories directly under the remaining OSD Manager.
  11. Install the Windows ADK on the OSD Manager device.
  12. After the Windows ADK installation, select the Configuration node of the OSD Manager.
  13. Click Properties .
  14. In the Properties window verify that the Windows ADK Path is correct.
  15. (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.
  16. 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.
  17. Click Check Environment to verify that all your OSD Manager parameters are still properly set and working.
  18. Select the Storage tab of your OSD Manager.
  19. Click the Synchronize button in the top panel of the Storage tab.
  20. In the appearing Select Image Repositories window select all image repositories.

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

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

    Note:

    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.

Note:

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

Comments