The SmartDeploy Media Wizard enables you to quickly build boot media that includes a custom answer file. When you create boot media with an answer file it is stored at the root of your SmartPE media (CD or USB) as SmartDeploy.xml. This answer file has several important items that you may want to modify on the fly including:
.WIM file being deployed
Platform Pack (.ppk) being selected
Windows Deployment Services (WDS) compatible image files are a good companion for a custom answer
SmartDeploy now fully supports OS image capture for deployment using Microsoft's Windows Deployment Services (WDS). Devon's blog does an excellent job of over-viewing the process to capture a WDS compatible SmatDeploy image file. The process is wizard-driven and truly extends the capability of the product.
In a large computer lab settings, it is very desirable for you to be able to automate the deployment wizard using an answer file. For example, some of the large labs I support include up
One feature that I have started to utilize in SmartDeploy Enterprise is differencing images. This technology is currently available for you to reduce your image development time, decrease the amount of space required for OS image storage, and improve the change management process of 'certifying' OS images in your IT organization. A simple way to think about differencing images is that they represent only the changes (delta) between image ‘A’ and image ‘B.’ Most IT shops have at least a dozen
We all need some time saving tips. I want to share a couple of time saving tips that I have developed while working with Smart Deployment Enterprise. The tips alone are not revolutionary, but they are valuable and will help new SDE adopters get even more out of an already valuable imaging suite.
Part of being super efficient in image development is to use a virtual reference computer for gathering your base image (see my earlier post and Devon's post on creating a reference VM). I have a
For years, IT departments have been searching for a method to maintain a perfected Operating System image which can be quickly and easily deployed to the majority of the computer models supported throughout the organization. This 'golden image' should contain all the necessary OEM drivers for the hardware to work without any secondary steps to manipulate the device manager or otherwise update drivers after the initial image deployment. I have personally experienced high levels of frustration
In almost ten years of Windows Operation System image deployment experience, I have been chasing an easier way to manage the OS image development process or OS image life cycle. Most of us in the industry have grown tired of the antiquated process of building a reference Operating System image on driver specific hardware only to have the dreaded Blue Screen of Death (BSOD) appear when the manufacturer changes chipsets or other components on common corporate-class models. Many organizations hav