OS Deployment - How to clone, move and/or update your OSD managers

Version 10
    Share This:

    Since 12.1 it's possible to setup tftp servers and image repositories on distant sites and/or different subnets than the subnet of the OSD manager. Before that you either had to set one OSD manager on each location or use osd proxies which would only allow you to make the tftp server available on the distant site but it would not allow image caching which means you the images had to be downloaded from the same distant share for all deployments.

     

    This would have made OSD proxies useful to deploy images through VLANs but less efficient to deploy images through WAN, which often led to setup an OSD manager by location.

     

    Another reason to setup several OSD managers is having isolated LANs, as an example.

     

    The downside of having to set several OSD managers is that you'll probably want to setup the same projects on all of them, which can be time costing and could lead to errors when you'll copy the project settings.

     

    Warning: this procedure only work as is if the path to ../data/osdeployment is the same on the devices your are cloning, if not there will be some paths to update as Paolo states in the comments (thanks for the hint )

     

     

    1- Clone your OSD manager:

     

    You will have to set WAIK or  ADK and install an agent for every new OSD manager but there are some tricks that'll ease your job for the first installs:

     

    - copy your images to their new location (on your new osd manager or on another server, depending on what you have chosen to do)

     

    - set the new OSD manager exactly like the original OSD manager (same paths etc) and check that it runs the same agent version. Update it if it isn't the case.

     

    - unload the OS Deployment module from both the old and the new server (or simply stop their agent's service):

    unload_mod.png

     

    - save the folder /data/OSDeployment on the new OSD manager

     

    - copy the folder /data/OSDeployment from the original OSD manager to the new one

     

    - once the new folder /data/OSDeployment is copied onto the new OSD manager:

    - go to the new OSD manager's /data/OSDeployment folder

    - move everything that's in the PXETFTP folder (default is C:/PXETFTP) to a backup folder

    - delete /data/OSDeployment/OSD_amd64.wim and /data/OSDeployment/OSD_x86.wim

    - delete the folders  /data/OSDeployment/template-amd64 and /data/OSDeployment/template-x86

    This will make the OSD manager regenerate the winpe wims after the service's restart.

     

    - start the service on both osd managers. Check the folders /data/OSDeployment and C:/PXETFTP (if the default) and wait until all the files you have deleted in the previous step are regenerated (it might take a moment for the wims).

     

    - edit the OSD manager module configuration on the new OSD manager to set the new tftp ip etc:

    osd_conf.png

     

    - rebuild the project

     

     

     

    2- Update the new OSD manager with new projects:

     

    You'll probably create new projects after cloning your OSD managers. If you don't want to recreate these new projects manually on your other OSD managers, you can simply:

     

    - copy the new image to the new location (on your new osd manager or on another server, depending on what you have chosen to do)

     

    - export the new project from the reference osd manager, then import it to the new osd manager

     

    - edit the image location in the project you've just imported on your new OSD manager:

    img_conf.png

    Click on "Check Image" to make sure it's ok.

     

    - rebuild the project

     

     

     

    Note: This probably applies to 12.1 and following but I haven't tested it yet.