Windows 7 deployments

Aug 23, 2000
15,509
1
81
Does anyone have experience using MDT 2010 and AIK to build a Windows 7 image and set it up to deploy to various computers?
All the documentation I find from M$ is either incorrect, out of date, or poiting to tools that the downloads don't have what they say they are.

I'm hoping someone has put together a guide on how to do this as I haven't found a M$ guide that is complete or 100% correct.

I run into one problem and search and find a fix only to run into another issue in the next step. I'm getting sick and tired of having 10 windows open trying to dig thorugh countless posts.
 

WinOutreach

Junior Member
Sep 13, 2010
4
0
0
The TechNet article <a href=”http://technet.microsoft.com/en-us/library/dd919185(WS.10).aspx”>Chosing a Deployment Strategy</a> links to several step by step guides to varying deployment scenarios.

Hopefully the guides and further resources linked to from this article provide more complete information on the use of MDT and AIK.

Brandon
Windows Outreach Team- IT Pro
 

Chapbass

Diamond Member
May 31, 2004
3,147
96
91
I use MDT 2010 with windows 7 all day at work here. I've done pretty significant research on it (I was the one that created ours here)...whats up?
 
Aug 23, 2000
15,509
1
81
The TechNet article <a href=”http://technet.microsoft.com/en-us/library/dd919185(WS.10).aspx”>Chosing a Deployment Strategy</a> links to several step by step guides to varying deployment scenarios.

Hopefully the guides and further resources linked to from this article provide more complete information on the use of MDT and AIK.

Brandon
Windows Outreach Team- IT Pro

I appreciate the link but the problem is most of the microsoft articles I've been reading either reference the previous version of MDT or AIK, or are missing steps in the process.

So far I've managed to install MDT and AIK, after hunting for valid downloads on MS site due to the AIK downloads not working correctly and linking to the add on pack. That was maddening.

Bascially I'm to the point that I have my Win 7 imported, I have my apps imported, and I've finally got a WinPE disk that boots (thanks ms for screwing up those directions). I need to test to make sure it all works, (Monday probably) but what I need to know and from what I've seen it isn't clear,
Do I just have my machine with the MDT 2010 and AIK (server) running on the network and boot to the PE disk on the client and it will know to look for the "server" Or do I need to do more?

Basically, what I want to do i have 1 image with Windows, Office and some other standard apps that I can deploy to any machine in the environment.
We are still running WinXP on our computers, and It looks like I can use the MS solution to deploy Win7 and also during that process it can P2V the existing machine or transfer data.

I've taken a break from this for a few days just to get everything straight in my head as bouncing between threads and finding fixes to MS mistakes had me so turned around I didn't know where the hell I was.
I'm just hoping there is a more concise step by step guide for this that isn't missing steps or doesn't link me to 10 other pages.
 

Chapbass

Diamond Member
May 31, 2004
3,147
96
91
First off:

http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part1.html

That guide is awesome.

2nd: What method of deployment are you using to get the initial winpe image out to the machines? I use WDS and its pretty much flawless. Unless the environment you're in can't handle large amounts of network traffic (which you could use multicasting to help mitigate), I would do it this way.

Which issues in MDT were you having? The only major issue I was having with deployment is where if you go to deploy on a machine wher MDT was used previously, it failed out. I solved this by editing the litetouch.vbs script, right in the beginning, have it delete the c:\_SMSTaskSequence and C:\MININT directories. This will get it to do a clean install.

Other than that, therres really two ways of doing this: You can have a standard image, with everything on it already, and use that to deploy, OR you can have just a stock image (or close to stock, more on this in a minute), and use the application deployment to install apps, updates, etc, all from a stock image.

On our MDT, we have two basic types of installs. I work for a 3rd party IT company that has a few different parts of our business. As we do a lot of hosting in our in-house datacenter, we deploy servers on a daily basis. Because all of these need completely different software, configuration, etc, the only thing I do with the server images is once every 6 months or so, run a task sequence that deploys the image, updates it fully, and recaptures it. No software, no configuration. This allows us to deploy images much faster when we actually have work that needs to be done. I also do this with consumer OSes, only to a lesser extent.

The other part of our business deals with an internally developed piece of software. We sell the software to our clients, and the software comes with a laptop and some various peripherals. Because the laptop is always the same model (or very close), we've created an image that already has all of the software installed (including things like SQL Server, Office, etc), and when we onboard a new company, its as simple as opening up the boxes and plugging in a network jack.


The portion that I haven't looked at yet, but am planning on doing so in the next week or so, is getting the SQL Database hooked up to MDT. This would allow us to install a certain image based on say, the make or model of the computer that is connecting to MDT, or by the username. Thats the next step, and its a pretty big one :p

Anyway, I'm rambling. Any of this make any sense?