XP/WDS Deployment


G

Guest

Hi,



My objective is to deploy XP over the network using Windows Server 2003. I
just wanted to clear up some confusion I've had will the different tools as
some other questions.



1) So did MDT 2008 replace all old versions of BDD?

2) Does light touch mean that it needs user input? And if so does the
Zero touch need SMS?

3) Are BDD/MDT just tools to help interface with WDS which is
ultimately how its handed down to the client?

4) Whats the latest version/release/download of WAIK? Does it include
a boot.wim that I can use for my deployment?

5) Can I capture a Windows XP box to a WIM file (thick image w/o
involving MDT) to be deployed using ImageX?

6) If Yes, will it lay down a sector based image or are WIM images
generally not sector based and so wont be HW specific?

7) Can I then use the Unattended.xml with WDS for the XP image?

8) Can I in general use WSIM (Windows System Image Manager) to build
answer files for XP or do I need to use Deply.cab to automate the minisetup?

9) Will all the WDS options (Client Naming Policy, which OU to place
the machine etc etc) work with the XP image deployment?

10) Can I use the Vista Boon.wim to push down an XP image?



Thanks, that's it for now.
 
Ad

Advertisements

R

Robinson Zhang [MSFT]

Hi,

Thank you for posting here.

Here are my answers for your questions:

1) Yes, Microsoft changed the software name BDD to MDT.

2) Normally, Lite Touch needs user input. Technically, you can use
unattended files (custom.ini, ect ) to avoid user input, but the steps are
complex. Zero touch needs SMS. For more information, you can refer to this
article: Zero Touch Windows Deployment With SMS
(http://207.46.16.252/en-us/magazine/2006.03.zerotouch.aspx)

3) BDD/MDT also can customize Windows PE and has other functions. For more
information, please visit this website: Microsoft Deployment Toolkit Team
Blog (http://blogs.technet.com/msdeployment/)

4) The latest version is Windows Automated Installation Kit (AIK) for
Windows 7 RC, Please download from
(http://www.microsoft.com/downloads/details.aspx?FamilyID=60a07e71-0acb-453a
-8035-d30ead27ef72&displaylang=en). It includes boot.wim.

5) The answer is yes. Detail information: Capture an Image
(http://technet.microsoft.com/en-us/library/cc749003(WS.10).aspx)

6) The WIM image are file-based.

7) You need Image unattend file. For more information: Automating Setup
(http://technet.microsoft.com/en-us/library/cc730695(WS.10).aspx)

8) We can only use WSIM to generate Windows Vista or Windows Server 2008
unattend files. And it can only open install.wim files. This is why you
cannot use WSIM to generate a Windows XP unattend file or a boot.wim file.
To generate a Windows XP unattend file, you can use Setup Manager
(setupmgr.exe).

9) Yes.

10) Yes.

If there is anything we can do for you here in this thread, please feel
free to post back here.

Hope it helps.

Best regards,
Robinson Zhang
 
G

Guest

Hello Rob,

Thanks for your time and help, I really appreciate it!

I do have some additional questions.

4)Does it matter which version of WAIK I use in relevance to which image
(xp/vsta) I plan to capture, or is it just a matter of where I plan to
install the tools (aka "Technician computer")? does it matter where I get
the Boot.wim from for my XP Deploy, can i use either WAIK or any Vista CD?

7)So I guess I can use WdsClientUnattend.xml for the XP image (or any image
really) to automate the first phase (partition drive etc) and then I would
use sysprep.inf to automate the mini-setup. I can place the sysprep.inf on
the WDS server under the $oem$ folder structure for the XP image, I will not
even have to put the sysprep.inf on the machine im imaging. am I correct so
far? in fact I don't even have to keep the c:\sysprep folder on the machine
im imaging (besides sysprep to reseal), I can place all the tools in the
same ($oem$) folder on the WDS server? Which means I can modify the
sysprep.inf on the fly and will be read/used the next time the next time WDS
lays down the XP image, correct??

9)What do I need to put in the sysprep.inf to ensure that it takes the
"Machine name" and OU settings from the WDS server?

11)Can I at any point mount the XP image (with imagex) to add drivers
(NIC/Video) and then modify sysprep.inf on the WDS to read those folders?

"Robinson Zhang [MSFT]" said:
Hi,

Thank you for posting here.

Here are my answers for your questions:

1) Yes, Microsoft changed the software name BDD to MDT.

2) Normally, Lite Touch needs user input. Technically, you can use
unattended files (custom.ini, ect ) to avoid user input, but the steps are
complex. Zero touch needs SMS. For more information, you can refer to this
article: Zero Touch Windows Deployment With SMS
(http://207.46.16.252/en-us/magazine/2006.03.zerotouch.aspx)

3) BDD/MDT also can customize Windows PE and has other functions. For more
information, please visit this website: Microsoft Deployment Toolkit Team
Blog (http://blogs.technet.com/msdeployment/)

4) The latest version is Windows Automated Installation Kit (AIK) for
Windows 7 RC, Please download from
(http://www.microsoft.com/downloads/details.aspx?FamilyID=60a07e71-0acb-453a
-8035-d30ead27ef72&displaylang=en). It includes boot.wim.

5) The answer is yes. Detail information: Capture an Image
(http://technet.microsoft.com/en-us/library/cc749003(WS.10).aspx)

6) The WIM image are file-based.

7) You need Image unattend file. For more information: Automating Setup
(http://technet.microsoft.com/en-us/library/cc730695(WS.10).aspx)

8) We can only use WSIM to generate Windows Vista or Windows Server 2008
unattend files. And it can only open install.wim files. This is why you
cannot use WSIM to generate a Windows XP unattend file or a boot.wim file.
To generate a Windows XP unattend file, you can use Setup Manager
(setupmgr.exe).

9) Yes.

10) Yes.

If there is anything we can do for you here in this thread, please feel
free to post back here.

Hope it helps.

Best regards,
Robinson Zhang
 
G

Guest

Hi again Rob,

So I went ahead and set this up with WDS (in a test environment) and it
worked like a charm, except for 2 issue during the mini-setup. Also if you
can please be so kind and answer me questions 4-7-9-11 in my previous post,
it would greatly appreciated.

a)It didn't use the name policy from WADS to name the machine, it just used
some random machine name.

b)It failed to Join the domain, i got the following message..
"The user you have specified is not permitted to join the machine to the
domain, would you like to proceed for now and try joining later"
Here is a copy of my sysprep.inf file...
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS

[GuiUnattended]
AdminPassword=810883f795c7171ff3bd49edf32eb4a42c52cd34adaa37617edda01b81d0db38
EncryptedAdminPassword=Yes
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
ProductKey=KDKF2-882FW-VFR8H-W3FXP-MW928
FullName="Just testing"
OrgName="Image Test"
ComputerName=*

[TapiLocation]
CountryCode=1
AreaCode=718

[Identification]
JoinDomain=idcomp.local
DomainAdmin=administrator
DomainAdminPassword= xxxxxxxxxxxxx (i do have a long password with
symble chractors)

[Networking]
InstallDefaultComponents=Yes

[Branding]
BrandIEUsingUnattended=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0

Thanks!!!


"Robinson Zhang [MSFT]" said:
Hi,

Thank you for posting here.

Here are my answers for your questions:

1) Yes, Microsoft changed the software name BDD to MDT.

2) Normally, Lite Touch needs user input. Technically, you can use
unattended files (custom.ini, ect ) to avoid user input, but the steps are
complex. Zero touch needs SMS. For more information, you can refer to this
article: Zero Touch Windows Deployment With SMS
(http://207.46.16.252/en-us/magazine/2006.03.zerotouch.aspx)

3) BDD/MDT also can customize Windows PE and has other functions. For more
information, please visit this website: Microsoft Deployment Toolkit Team
Blog (http://blogs.technet.com/msdeployment/)

4) The latest version is Windows Automated Installation Kit (AIK) for
Windows 7 RC, Please download from
(http://www.microsoft.com/downloads/details.aspx?FamilyID=60a07e71-0acb-453a
-8035-d30ead27ef72&displaylang=en). It includes boot.wim.

5) The answer is yes. Detail information: Capture an Image
(http://technet.microsoft.com/en-us/library/cc749003(WS.10).aspx)

6) The WIM image are file-based.

7) You need Image unattend file. For more information: Automating Setup
(http://technet.microsoft.com/en-us/library/cc730695(WS.10).aspx)

8) We can only use WSIM to generate Windows Vista or Windows Server 2008
unattend files. And it can only open install.wim files. This is why you
cannot use WSIM to generate a Windows XP unattend file or a boot.wim file.
To generate a Windows XP unattend file, you can use Setup Manager
(setupmgr.exe).

9) Yes.

10) Yes.

If there is anything we can do for you here in this thread, please feel
free to post back here.

Hope it helps.

Best regards,
Robinson Zhang
 
G

Guest

typo...
"(i do have a long password with symbol characters)"

Geez

Hi again Rob,

So I went ahead and set this up with WDS (in a test environment) and it
worked like a charm, except for 2 issue during the mini-setup. Also if you
can please be so kind and answer me questions 4-7-9-11 in my previous
post, it would greatly appreciated.

a)It didn't use the name policy from WADS to name the machine, it just
used some random machine name.

b)It failed to Join the domain, i got the following message..
"The user you have specified is not permitted to join the machine to the
domain, would you like to proceed for now and try joining later"
Here is a copy of my sysprep.inf file...
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\sysprep\i386
TargetPath=\WINDOWS

[GuiUnattended]

AdminPassword=810883f795c7171ff3bd49edf32eb4a42c52cd34adaa37617edda01b81d0db38
EncryptedAdminPassword=Yes
OEMSkipRegional=1
TimeZone=35
OemSkipWelcome=1

[UserData]
ProductKey=KDKF2-882FW-VFR8H-W3FXP-MW928
FullName="Just testing"
OrgName="Image Test"
ComputerName=*

[TapiLocation]
CountryCode=1
AreaCode=718

[Identification]
JoinDomain=idcomp.local
DomainAdmin=administrator
DomainAdminPassword= xxxxxxxxxxxxx (i do have a long password with
symble chractors)

[Networking]
InstallDefaultComponents=Yes

[Branding]
BrandIEUsingUnattended=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=0

Thanks!!!


"Robinson Zhang [MSFT]" said:
Hi,

Thank you for posting here.

Here are my answers for your questions:

1) Yes, Microsoft changed the software name BDD to MDT.

2) Normally, Lite Touch needs user input. Technically, you can use
unattended files (custom.ini, ect ) to avoid user input, but the steps
are
complex. Zero touch needs SMS. For more information, you can refer to
this
article: Zero Touch Windows Deployment With SMS
(http://207.46.16.252/en-us/magazine/2006.03.zerotouch.aspx)

3) BDD/MDT also can customize Windows PE and has other functions. For
more
information, please visit this website: Microsoft Deployment Toolkit Team
Blog (http://blogs.technet.com/msdeployment/)

4) The latest version is Windows Automated Installation Kit (AIK) for
Windows 7 RC, Please download from
(http://www.microsoft.com/downloads/details.aspx?FamilyID=60a07e71-0acb-453a
-8035-d30ead27ef72&displaylang=en). It includes boot.wim.

5) The answer is yes. Detail information: Capture an Image
(http://technet.microsoft.com/en-us/library/cc749003(WS.10).aspx)

6) The WIM image are file-based.

7) You need Image unattend file. For more information: Automating Setup
(http://technet.microsoft.com/en-us/library/cc730695(WS.10).aspx)

8) We can only use WSIM to generate Windows Vista or Windows Server 2008
unattend files. And it can only open install.wim files. This is why you
cannot use WSIM to generate a Windows XP unattend file or a boot.wim
file.
To generate a Windows XP unattend file, you can use Setup Manager
(setupmgr.exe).

9) Yes.

10) Yes.

If there is anything we can do for you here in this thread, please feel
free to post back here.

Hope it helps.

Best regards,
Robinson Zhang
 
Ad

Advertisements

T

Tim Quan [MSFT]

Hi,

"It didn't use the name policy from WADS to name the machine, it just used
some random machine name."

Did you deploy Windows XP using WDS with MDT/BDD? If so, I am afraid that
the WDS naming policy will not work. The naming policy only works without
MDT/BDD.

Set the Computer Naming Policy
http://technet.microsoft.com/en-us/library/cc771624(WS.10).aspx

Hope it helps.

Tim Quan - MSFT
 
G

Guest

Hello Tim,

I used WDS and not BDD, but I actually resovled this by removing "Computer
Name" from the sysprep.inf, w/o that line it picked up the machine name
perfectly fine from WDS.
 
T

Tim Quan [MSFT]

Hi,

Thank you for the reply.

4) I suggest installing the latest version of WAIK:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=94bb
6e34-d890-4932-81a5-5b50c657de08

You should use the boot.wim file from a Windows Vista or Windows Server
2008 disk. I recommend using the boot.wim file from a Windows Server 2008
32bit disk. We can use it to deploy all operating systems (except Windows
7) and it supports multicast.

7) You understanding is correct.

11) I think the answer is Yes if Windows XP is captured as a .wim file.

Tim Quan - MSFT
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top