[MDT] MDT2010 Deploying Win XP

[Chuckster]

How can I set it up so that it already knows what keyboard layout to use, what the timezone is, which network it's going on etc?

For example, do you use '85' for TimeZone? If so, this doesn't work for me.

Any suggestions?

[plexer]

You can edit the unattend and sysprep that it uses.

Ben

[Chuckster]

You can edit the unattend and sysprep that it uses.

Ben

I'll try that and see what happens.

I have another problem. Before sysprepping the maching using MDT 2010, I had all the latest updates and patches installed on it. Now that I've reintalled the OS via MDT 2010, it's reverted back to just SP3 with IE6 and what have you.

How can I ensure that all patches and updates remain when imaged onto other workstations?

[plexer]

Installing the o/s using an MDT Task Sequence would do a fresh install and then capture the machine.

The is an option to run windows updates in the task sequence, otherwsie you can set your machine up how you want, don't choose to image it and there is a seperate task sequence that I've seen mentioned which then syspreps and images the machine.

You then import the freshly captured wim image as an o/s install in MDT and you can create a new task sequence to deploy this.

Ben

[Chuckster]

Would that be "Standard Client Replace Task Sequence"?

Can I have a look at an example Sysprep/Unattend file, if you have one?

[Chuckster]

Is there a way where you can get Win XP to connect to the domain and set up a computer account in AD like RIS?

I can enter the computer name and type in what domain it is and what the OU is, but this doesn't work. It just assigns the domain name as a workgroup

[eean]

This could be caused by a bug in Windows. I couldn't understand why Sysprep and WDS was not joining the domain. In the end I found applying a KB patch that didn't really relate to the problem fixed it!
I'm on holiday now until Tuesday, if you want me to find which KB it was, send me an PM on Wednesday and I'll take a look.

[Chuckster]

This could be caused by a bug in Windows. I couldn't understand why Sysprep and WDS was not joining the domain. In the end I found applying a KB patch that didn't really relate to the problem fixed it!
I'm on holiday now until Tuesday, if you want me to find which KB it was, send me an PM on Wednesday and I'll take a look.

Thanks. I would definitely much appreciate that.

I just find MDT 2010 so irritating and it's so bloody cumbersome to say the least.

I can't believe how M$ can get it wrong time and time again.

[DrCheese]

They haven't got it wrong at all, it's just that it's really designed for Vista and 7, not XP which was made way before it.
If your deploying XP you are far better off sticking with an ordinary RIS server or WDS in mixed mode.

[eean]

I've never heard of MDT - what is it and how is it better/different to what WDS and Group Policy does anyway?
The KB fix I found fixed a problem with Windows XP running sysprep, post image setup from WDS on Server 2008. I think 2008 was the problem - something about requiring enhanced security.

Sorry, I assumed that MDT was an add-on for WDS. So this fix might not apply to your problem.

I wish I'd found out about MDT before I spent ages getting WDS to work - bloody Microsoft - RIS in legacy mode was so easy, why did the have to take it out of Server 2008?