windows 2012 deployment services server questions

hello experts I have about 100 desktop computers to deploy and would like to try out a deployment server. We have a very complex forrest set up here and I dont want get involved with the data center guys, so I'd like to create a stand alone server on an isolated network. How will that work in an existing domain environment? What would be the fastest, least complicated way to image all these PC's and deploy them on the domain? Would I have to image them, and then join the domain on site ?
thanks in advance!
WAMSINCAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Look at MDT. It'll help in both building master images and in deployment. It can use WDS, but isn't locked to it and you nay find other deployment options more suitable to your goals here.
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
MDT is very powerful... though I'm still generally using WDS.  As for imaging, you need to keep in mind licensing requirements and proper procedures.  For 100 machines, I'd probably say it's worth spending a week or two learning this and getting things configured properly... but understand, the process of learning a complex system of image preparation, capture, and deployment is NOT quick if you want to do it right - and if you want to do it wrong, you're unwise at best.

Some things you need to know:
1. Creating the image requires you build it from a Volume License installation of Windows (Retail and OEM are not allowed to be captured and imaged).
2. You should create an answer file using The Windows Automated Installation Kit (WAIK/Windows AIK).  This includes many presets for your configuration, including, potentially domain information, partitioning, product keys, etc.
3. Then you build your image in Audit mode.
4. Then you MUST, ABSOLUTELY MUST, close the image with Sysprep.
5. Then you CAPTURE the image
6. Then you deploy the image.  

Probably best to do most if not all of this in a VM.

Finally, don't go nuts installing all your apps and support programs like Acrobat, Java, etc, into the image.  They are outdated before you can deploy them.  The idea for a properly created and deployed image is to reduce or eliminate the need for user intervention - and it's a HUGE waste of time if you have to keep updating the image every 2 weeks.  Honestly, I KNOW I'm not doing things the most efficient way, but my method for various reasons is to use an extensive script that calls other scripts to configure the system.  It also calls a program called "NINITE" that can install all those third party support apps so I ALWAYS deploy a machine with the latest Java, Acrobat, etc.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WAMSINCAuthor Commented:
thanks these were great help guys forgot to close this question
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.