Sharing of thoughts and information is what blogging is all about. This way we can learn from each other. Post A Comment!These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Anthony Bartolo Twitter | LinkedIn
Pierre Roman Twitter | LinkedIn
Many manufactures are now creating ultra light and thin laptops and tablets to appease the masses in terms of desirable computing products. In order to achieve this however, the once valued DVD/CD-ROM and to be left out. There are many alternatives to installing Windows 8.1. Deployment can occur anywhere from network drives to USB enabled DVD/CD-ROMs. So why create a Step-By-Step to deploy an OS from a USB? Many smaller companies are strapped for resources. IT administrators for these organizations require ingenuity to create solutions to adhere to their requirements of the company employees they support. Couple this Step-By-Step post with that with the relatively inexpensive cost of today's USB keys and you've got a viable solution to deploy Windows 8.1
Step 1: Install Windows ADK for Windows 8.1
Step 2: Install Microsoft Deployment Toolkit 2013
Step 3: Creating a Deployment Share
Step 4: Import the Windows 8.1 OS
Step 5: Importing Necessary Applications
One of the advantages of utilizing MDT 2013 to create the image for the USB key is the ability to include drivers and / or applications that are specific to your organization's needs. In this example, Microsoft's Calculator Plus, will be added to this image. Feel free to customize it as you see fit.
Repeat this process as many time as required to include all the pertinent applications required.
Step 6: Create and Configure a Task Sequence
Step 7: Create the Microsoft Deployment Toolkit 2013 Media
Once the steps above are completed, an IT professional can now utilize the newly created USB Key to deploy Windows 8.1. While the drivers included with Windows 8.1 should suffice, additional drivers can be added to the USB key should the hardware being deployed to not be supported by default. Driver inclusion can be configured via MDT 2013 and will be included on a future post. As mentioned earlier, there are a great deal of ways Windows 8.1 can be deployed. Learn more at Microsoft Virtual Academy.
Good Article in more detail ...
Just make sure they don't fully automate and add "SkipBDDWelcome=Yes" otherwise you could have a pure OTI which is COOL for IT, but if the key gets left about and some poor hapless user/CIO picks it up and plugs it in....
Sean - IT will have to be mindful of where they leave the key. Or, as you suggested, do not add the "SkipBDDWelcome=Yes" amidst the script.