Windows 10: Windows Server 2022MDTUpdate Deployment Share

Windows10MDTMDTUpdate Deployment Share=== Making sure the deployment share has the latest x86 tools ====== Processing LiteTouchPE x86 boot image ===Building requested boot image profile.System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM&

:)

 

Moving MDT deployment share to a new server

Hello,

I'm in the process of building a new VM of Server 2022 and would like some advice on moving our deployment share (MDT) to the new server. I'd like to move the deployment share that resides on a separate partition on the old server and reattach to the new Windows Server 2022. The old server has both MDT and WDS installed with the DeploymentShare and the RemoteInstall folder on the same partition. Looking for some advice before diving in and ending up loosing data.

Would the approach be as follows:

1. Attach the partition containing the DeploymentShare and Reminst folder to the new Server 2022

2. Install WDS on the new server and point the installation to the existing E:\RemoteInstall folder

3. Install MDT and attach the existing DeploymentShare.

or is it best to take the following approach with a less likely chance of overwriting data.

1. Create a new partition with the same share name on the new server.

2. Install WDS pointing the Reminst folder to the new partiton

3. Install MDT to the new partition.

4. Copy the data from the \OldServer\Reminst folder to \NewServer\Reminst folder.

5. Copy the data from the \OldServer\DeploymentShare folder to \NewServer\Deploymentshare folder.

 

Need Help in BitLocker deployment Step by Step

Dear All,

We are planning to deploy to deploy Windows 10 BitLocker in our organization. Could you please anyone help me with step by step deployment from the scratch.

1. What are the requirement?
2. How to setup BitLocker management server?
3. What are the per-cautions and best practices?

Thanks in well advance for brief guide.

Best Regards

Faisal

 

Customised Windows 10 deployment on multiple desktops and laptops.

OK, after giving this a thought and thinking how I would do it, here's my suggestion. Please notice that, as I said, this is how I would do it. Other geeks might disagree with parts or all of it.

I tested this scenario using one Hyper-V VM as technician machine (the one to build image) and three virtual machines to test simultaneous deployment in two scenarios:

• Capturing install.wim from technician machine and using DISM to apply / deploy image from a network share
• Capturing install.wim from technician machine, making ISO from it, deploying by clean installing from ISO burned to Flash drive

Based on the fact that ISO method is clearly faster and simpler, it is what I suggest to you. I estimate you would need an hour and half to two hours to customize install image, capture it and make an ISO, then assuming you would make 5 Flash drives for install / deployment you would need about half an hour per five machines, in other words you would deploy to those 25 new machines in less than three hours, almost a full working day to deploy those 50 existing ones.

Two working days, day 1 to make the image and deploy to new machines, day 2 to deploy to old ones.

Chronological workflow based on my suggestion:

Phase 1, Image customization tutorial, parts One through Six:

• Install Windows 10 on a technician machine (I recommend Hyper-V VM but any capable PC is OK)
• Boot to Audit Mode
• Update Windows, install software, customize & personalize Windows
• Sysprep

Phase 2:

• Capture the install.wim from technician machine as told in this tutorial, Part Four steps 4.1 through 4.5 (physical PC as technician machine) or Part Four steps 4.6 through 4.13 (Hyper-V VM as technician machine)
• Create ISO as told in same tutorial, Part Five
• Burn / write ISO to as many Flash drives as you want to / need to for simultaneous installs
• Boot production machines from Flash drive, install Windows 10

The above is how I would do this. If you choose the DISM method instead, applying install.wim from a network share, see this Microsoft support article: https://technet.microsoft.com/en-us/.../hh824910.aspx

For more advanced deployment using MDT see this article: https://technet.microsoft.com/en-us/.../dn475741.aspx