Using ghost 3.1 to build winpe enviroment

Using ghost 3.1 to build winpe enviroment drivers#
Using ghost 3.1 to build winpe enviroment update#
Using ghost 3.1 to build winpe enviroment windows 10#

Most machines finish the process in 30-45 minutes and we have a machine that is literally ready to hand to an employee.

We don't put applications in our image, instead we deploy a vanilla image and the last step of our MDT task sequence calls PDQ Deploy to push out the correct application package for that machine. Net3.5, compresses the wim, and pushes it to MDT. When we're ready to deploy the latest major Win10 version (aka Fall Creators update), we just dump the vanilla ISO and any rollup into a share and the same script grabs it, extracts the wim, removes appx packages we know we don't want, adds.

Using ghost 3.1 to build winpe enviroment update#

When were ready to use the latest Win10 rollup, we just copy the update into a share on the server and that same scheduled script injects it into the image and pushes the image to MDT.

Using ghost 3.1 to build winpe enviroment drivers#

We dump new drivers in a share on the server and a scheduled script imports them into MDT and rebuilds the WDS PXE image if necessary. All we have to do is run a single powershell command (to pre-stage the pc) and then PXE boot the machine(s).Д®ven our image creation is mostly automated. Now our deployment process is pretty much completely automated and whether we're deploying 2 or 10 machines, they are literally ready to hand to employees after 30-45 minutes. We invested the time to setup MDT, WDS, PDQ (for software), and some custom powershell. Why not shorten your deployment time to 45 min or less, whether your deploying to 1 or 50 machines? Instead of messing with USB media, why don't you take the few extra steps and setup PXE via WDS (or something else) and automate your image deployment process. I've been updating this one to inject drivers to it every time I find a machine that has some unsupported hardware, and it's now 100% on every system I've tested it against (NVME ssd's gave me a little trouble, but that works now too). I'm not able to find a clear answer about it anywhere, so perhaps not. Is there a quick and easy way to export all of my drivers/customization's to apply to the new winpe environment?

Using ghost 3.1 to build winpe enviroment windows 10#

So I've built myself a pretty slick little WinPE imaging/capturing environment, but with the release of Windows 10 1703/1709, I'd like to update it to allow the use of larger USB media with multiple partitions (one for winpe, one for wim files).

The original question of updating a PE environment has NOT been answered however, so I cannot choose a 'best answer' at this time.** I am extremely grateful to all who have assisted in clarifying the licensing. There has been a lot of great information here that has been extremely helpful to me, and has prevented some potentially expensive troubles. **EDIT: This post has become a discussion on OEM deployments and licensing requirements.