Improving User Experience During Deployments
When it comes down to your deployment, the user at the end waiting for their BAU rebuild or their new machine from the refresh scenario doesn’t care about the technology behind the installation. What does the user care about?
All that is certain is they don’t care you just built a ZTI deployment with SCCM 2012. All they care about is getting their machine in the same state it was in when they left it with you (or last working state). What if your deployments are done at the desk or even initiated by the user?
It’s an interesting theory. Why would you as an administrator want your users involved in the deployment of the desktop. Take this scenario. A recent experience where the customer wanted to deploy Windows 7 on a pilot if the user wanted it. ZTI was already performed via SCCM 2007 with all their applications all packaged and delivered in SCCM.
It was time to break out UDI. By customizing the UDI wizard we enable the user to have limited control over the deployment such as which applications they require. The task here was running the preflight check for application discovery and restoring those applications along with their user state at the end of the Windows 7 deployment which was a format of the drive. State was stored on the server to prevent it from been lost and the user had the chance you untick or add additional applications to their installation.
All ended well when the user was given a choice of system knowing that their state and applications would be restored when the deployment is completed.
If you are in a similar situation then you should seriously look at this for your deployments. It comes with MDT 2010 Update 1 and lots of information can be found in the MDT Documentation Library either with the download or on TechNet for the latest version.