/build/static/layout/Breadcrumb_cap_w.png

2003 Server SP2 R2 in one shot

Hi all,

I'm building an unattended inst of Windows Server 2003 Standard R2 SP2.
Unfortunately R2 remains it's own install, even with the current set of SP2 R2 CDs.
Also, R2 contains long file names and I'm tied to DOS for the initial copy.
So I created an SFX archive of the R2 folder with 7-zip. I unpack the folder in the cmdlines (the $OEM$ stuff at t-12 minutes) with "R2.exe -y -oCMPNENTS" Works fine so far, but when I then try to install calling "CMPNENTS\R2\setup2.exe /q /a /p:key /sr" nothing happens.
I now tried a workaround by calling the same line as Command0 in [GuiRunOnce] of the unattend.txt, but I'd like it better to run inside the cmdlines.

Anybody gotten this to work with w2k3 server sp2?

Cheers,
Konstantin

0 Comments   [ + ] Show comments

Answers (4)

Posted by: Tone 17 years ago
Second Degree Blue Belt
0
You need to copy the R2 disc to root of CD1, more info on http://www.msfn.org
Posted by: KPrinz 17 years ago
Fourth Degree Green Belt
0
don't I get a UI then? This is what I read from the posts at msfn.
Posted by: Tone 17 years ago
Second Degree Blue Belt
0
from what I can remember there is a one dialiog box you cant bet rid off..
Posted by: KPrinz 17 years ago
Fourth Degree Green Belt
0
For some reason it doesn't work from inside cmdlines. However calling the setup later (first thing after setup and not from Command0 but from a batch in Command0) with cmd /c im front works like a charm.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ