Forum Discussion
Deployment best practices
This is a tough one.
Ideally, you would try to minimize the payload on every machine by only deploying what is needed. You could look into something like Software Center in Config Manager to enable a self service install of apps that are needed only for certain users.
If you have a large set of machines that need many apps, building a reference image and deploying that would most likely turn out to be faster than installing all the apps after the deployment of the actual OS. You will end up with a very large reference image though.
One other thing you may want to consider is in-place upgrade since that would carry forward all of your installed apps.
So in this case would you use MDT/SCCM to use task sequences to install everything on a single computer to setup a computer and then capture that image again with SCCM/MDT?
Also, in regard to in place upgrades, do you have a link that walks you through that process? This is a very new resource for imaging.
- Heather_Poulsen
Community Manager
Here is information on in-place upgrades:
We also have a virtual lab that will guide you step-by-step through the process:
That's right, here is some info on how to create a reference image with MDT: https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image
You can then deploy the refence image with MDT or ConfigMgr.
Here is some info about in place upgrade
with MDT: https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-to-windows-10-with-the-microsoft-deployment-toolkit
with ConfigMgr: https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-to-windows-10-with-system-center-configuraton-manager
Marc-Andrea,
the first link, for creating reference image, links to a 404. Thank you
Can you try https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/create-a-windows-10-reference-image? It looks like the community software does not like long links.
the first link (ref image) is broken (404) :-(
