In order to successfully deploy the Microsoft Surface Pro 3 with SmartDeploy, you'll need to use SmartDeploy version 1.1.5010 or later.
Additionally, this UEFI Class 3 device automatically adds a BCD firmware entry for any present bootable USB media on each boot. This means that even with the UEFI "Alternate System Boot Order" set to "SSD Only", the machine will still boot to a bootable USB device on each boot.
Therefore when deploying the machine via offline USB media, the machine wou
If you are using VMware virtualization products to build reference computers with SmartDeploy, and you want to create a Windows 8.1 or Windows Server 2012 R2 image, you'll need to follow these instructions.
Through testing, we have noticed inconsistent shut down results from within VMware products. When using the Capture Wizard to subsequently capture an image of that machine, the resultant image file does not contain full metadata. If you then attempt to deploy this image, it will result in th
Microsoft is doing some pretty cool things within Windows 8 to allow you to Refresh and reset your PC to a known good starting point. This should be a much cleaner WinRE implementation than the PC Manufacture's implementations with Windows 7. It also appears to have given us USMT Hard-Link Migration for the masses.
In this related article, talking about improvements in Windows Setup, and more specifically about the new web based purchase/download/upgrade process... they mention the following:
Here is a list of some of the changes and enhancements in the SmartDeploy 1.1.1920 release.
1803: Ensured all Deploy Wizard, Advanced Options, System Properties work properly.
1812: Allow for multiple Domain's & OU's in answer files
1813: Fixed crash when selecting an image file for deployment that was being copied to
1819: Added messaging if attempting to capture Virtual Box with guest additions installed
1849: Fixed post image task pointing to a missing file
SmartDeploy stores the device drivers for Windows PE in the platform pack for a given model, where necessary. This is to help easily facilitate creating boot or deployment media that supports the network and mass storage for that device.
SmartDeploy versions prior to 1.1.1910:
---Windows PE 2.1
We only add Windows PE drivers if necessary for a given model. This is because many models are covered for both
For years people have struggled with the best way to capture and share dialog boxes or other objects they see on their computer screen.
The old tried and true method: PrtScn & Alt+PrtScn
The PrtScn button by default captures the entire desktop, and using Alt+PrtScn captures only the active window on the desktop. This is a good start to get what you want captured. You can then open the Microsoft Paint application (mspaint) and paste in what you have captured. The trick here is to ma
In a follow-on to my previous “Windows 7, BitLocker and Recovery” blog, I was wondering what would happen if you installed Windows 7 to an existing partition so that you ended up with a single partition instead of two, and then ran the BitLocker wizard. Or, if you made a 300MB active partition in the beginning of the disk and then told Windows setup to install to the free space.
In the “Hardware requirements for BitLocker Drive Encryption” section of the Windows 7 Help and Support, it state
Windows 7 has greatly improved and simplified the process of setting up BitLocker and the Windows Recovery Environment. In fact both the separate partition structure required for BitLocker, and the automatic failover to the Windows Recovery Environment are setup by default in Windows 7. With Windows Vista neither of these were setup up by default. With Windows Vista the guidance from Microsoft was to create a 1.5GB system partition for BitLocker, and this is exactly what the BitLocker Drive Prep