?
Solved

Deployment Problem

Posted on 2013-11-08
7
Medium Priority
?
222 Views
Last Modified: 2013-11-26
I have a Windows 2008 r2 server running ADDS and WDS.  I am trying to setup a deployment server to deploy windows 7 enterprise using unattend files to automate the installation of windows.  As the actual deployment will happen in a company with a hundred computers, I have no time to manually specify the language and hard drive options for each PC.  

So far I am stuck in getting these unattend files to work.  My deployment server functions perfectly, but the unattend files don't seem to be used by the server.  If I image a machine, I am still asked for language, drive options etc., which shouldn't be happening if I have unattend files.  I have pointed the deployment server to the windows PE unattend file in my Remote Install directory, and I have allowed for my image to be installed using an unattend file, which I also specified the location. I have also tried unsuccessfully putting the unattend file on a USB stick.

What am I missing?
0
Comment
Question by:LostInWindows
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
7 Comments
 
LVL 24

Expert Comment

by:Nagendra Pratap Singh
ID: 39635538
At least try to use MDT.
0
 
LVL 17

Accepted Solution

by:
James Haywood earned 2000 total points
ID: 39635968
This article shows what files you need and where to place them
http://technet.microsoft.com/en-us/library/dd637990(WS.10).aspx
0
 
LVL 1

Author Comment

by:LostInWindows
ID: 39642108
I am using MDT and I used system information manager built into Windows AIK to build the unattend files.

I also followed the steps that hhaywood000 posted and placed the PXE pass unattend file in the ..\RemoteInstall\WDSClientUnattend directory; Yet when PXE booting a machine, I am still prompted for language, drive options and user name, when this should not be happenning with my unattend file.  The other image specific unattend file is not working either, as it should specify a volume license key for Windows 7, but a freshly imaged machine will claim to be unactivated and have no product key entered.

What else could I be missing?
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
LVL 24

Expert Comment

by:Nagendra Pratap Singh
ID: 39643634
You need to enter those in bootstrap.ini. Password etc may be misspelled there.
0
 
LVL 1

Author Comment

by:LostInWindows
ID: 39666914
We have been trying the suggestions listed here.
We are using MDT. We have a WIM image that we want to use for our deployment.
We have built unattend.xml files for the deployment.

When we PXE boot the new workstation machine it installs Windows 7, but it isn't reading the unattend files at all. None of the configurations that we have in the unattend files are added and all we have is a base install.

We are wondering about sharing permissions as we have a non-domain computer/ non-domain account and it needs to read the share, but we can't tell if that is the issue or not.

My client is small and cannot afford SCCM. Also, I don't know SCCM so acquiring that software won't be a benefit.

Do I need special sharing on the unattend file? What share permission(s) do I need? Obviously either the problem isn't sharing or everyone full control isn't correct/enough.

Help! I'm lost. Any suggestions would be appreciated.
0
 
LVL 17

Assisted Solution

by:James Haywood
James Haywood earned 2000 total points
ID: 39667420
If you are using MDT rather than WDS then you won't need to place the answer files in WDS. MDT just uses the WDS pxe boot mechanism then takes over with regard to OS deployment. This book is easily the best (and simplest) guide to setting up and configuring MDT. This website is an excellent resource

http://scriptimus.wordpress.com/

A good place to start troubleshooting is looking at the deployment logs on the Windows 7 box
%WINDIR%\TEMP\DeploymentLogs
0
 
LVL 1

Author Closing Comment

by:LostInWindows
ID: 39677685
It is amazing how many little things have to be setup in MDT. WE now have it about 95% working. But the big news for us is that the answer file (unattend.xml) is being utilized.
Thank you very much for your help.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
This Micro Tutorial will give you a introduction in two parts how to utilize Windows Live Movie Maker to its maximum capability. This will be demonstrated using Windows Live Movie Maker on Windows 7 operating system.
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

718 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question