MDT images and Endpoint and Azure

At work, we'll be heading into using Endpoint and Azure in a more in depth way in the next few months to manage our systems and have the computers register. The department head is more clued up about wanting this implemented and I'm a bit lost on some of the features and what's happening with our MDT images. We have 2 MDT images in use at the moment one for general office setup and one for home use. The home one is set to force updates to be installed when finishing the MDT image and on the desktop for the first time and name itself in a specific way and register on Endpoint. The office one we can control more with policies and when it gets updates, join the domain etc. We've just found that when we've got some of the home ones back in and tried to clone them for office use that after applying the image and go to desktop for the first time, it seems to have named itself back to the name it had at home and is running through some of the setup as if at home, i.e. trying to apply updates there and then on the desktop when finishing applying the image.

Does that make sense to anyone? Don't assume anything on my part. Is there anything to check? A colleague thinks we need to retire the home computer name off Endpoint before we clone with the office image, but I've tried that correctly (I think), the computer sees it has been retired but cloning it again still tries to run update when finishing applying the image. Could anyone give me simple steps as what to check or what might be the issue? Is the MDT image set up incorrectly?

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ