MDT 2013 Advice

[jertsy]

Hi all

 

After wasting the last 3 weeks trying to get WDS working, its broken on 2012R2 with update 1 according to MS via our support company. I have been playing with MDT, basically time is against me so can anyone see any problems occurring with the following process.

1. Install windows 7

2. Install Office 2013

3. Install windows updates from MS

3. Install any curriculum software

4. Capture with MDT

5. Deploy with MDT

Our Gpo's set the PC's to look at our WSUS server for update's so the PC's should use that in future?

I know MDT can do a lot more with task sequences and without fat images, but to get me away would this process work? I then plan to learn MDT better over the coming year and perhaps rebuild all PC's again next summer.

 

Any advice gratefully received.

Jertsy

[themightymrp]

As far as I am aware, MDT still requires WDS in the background in order to be able to PXE boot machines....

[jertsy]

As far as I am aware, MDT still requires WDS in the background in order to be able to PXE boot machines....

 

No I have booted off a winPE disk and it then runs the task sequence from that, I did think that myself at first.

I have successfully captured and deployed now.

 

But to PXE, yes I think you do need WDS.

[computer_expert]

As far as I am aware, MDT still requires WDS in the background in order to be able to PXE boot machines....

 

For PXE, yes, you still need WDS.

 

In the deployment share properties you can tell MDT to create an ISO image that you can either burn to a CD/DVD or extract to a bootable memory stick (you'll need to run bootsect.exe to install the bootloader to the USB stick though) to use on the odd machine that won't pxe boot.