Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering the Microsoft Deployment Toolkit

You're reading from   Mastering the Microsoft Deployment Toolkit Take a deep dive into the world of Windows desktop deployment using the Microsoft Deployment Toolkit

Arrow left icon
Product type Paperback
Published in May 2016
Publisher
ISBN-13 9781782172499
Length 330 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Jeff Stokes Jeff Stokes
Author Profile Icon Jeff Stokes
Jeff Stokes
Manuel Singer Manuel Singer
Author Profile Icon Manuel Singer
Manuel Singer
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Imaging Concepts and Theory FREE CHAPTER 2. Setting Up Your Environment 3. Creating Reference Images 4. Default User Profile Customization 5. CustomSettings.ini and Task Sequence 6. Drivers 7. Image Deployment 8. USMT – The User State Migration Tool 9. Troubleshooting Deployment Logs 10. Validating the Image 11. Database, UserExit Scripts, and Web Services A. Additional Enterprise Configuration Items

Deployment share


The deployment share is quite similar to our reference share. Most of the content of the CustomSettings.ini and Bootstrap.ini will be the same. The OSes of the deployment share are simply the WIM files, which we just captured, the product of our reference share task sequences. The applications will be complex drivers for specific hardware devices or applications applied post-OS deployment. However, our base images are somewhat set in stone at this point. The WIM files from our reference share form the base operating system of our deployment task sequences.

Again, creation of the deployment share follows the reference share, with some naming differences:

Name the directory DeploymentShare to keep our naming standards correct. We absolutely want to keep the reference share and deployment share work separate. This gives us the flexibility of experimenting in the reference share space, building baseline images, tweaking task sequences, and so on, without impacting deployment...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image