Integrating hotfixes into Windows 2003 unattend

[eger]

There is not much info about slipstreaming and unattended installation for windows 2003. I have managed to create a CD with most fixes and some tools on the CD and have it semi-unattended. Though it is not fully unattended because lots of windows 2003 updates don't do quiet installing or don't do it correctly (prompts me lots of times).

I was wondering if anyone knew how to integrate the hotfixes into windows 2003 other than the svcpack method and any other helpful information on slipstreaming windows 2003.

I can't be the only one out there building tons of identical servers daily =)

[Alanoll]

what updates aren't silent? perhaps you're using the wrong switch for the wrong hotfix type?

[eger]

what updates aren't silent? perhaps you're using the wrong switch for the wrong hotfix type?

Q832483 is the one i'm having trouble with. When run with /? it says /Q is the quiet mode.

In my svcpack.inf I have: Q832483.EXE /Q

But it always prompts to install.

I install other updates with the same switches just fine (KB870669.exe /Q)

Any ideas? Other ways to slipstream this update?

I am trying to find a way to integrate the updates so I don't waste valuable CD space with all the update installers (since I need the space for external applications).

[Alanoll]

use

"Q32483.exe /C:""dahotfix.exe /q /n"" /q:a"

in SVCPACK.INF

Knew it was switch related...

as for actually integrating them, it'll get REALLY tricky. RaveRod had a post awhile back, that MAY be of help to youfor that. RyanVM does something similar with his hotfix pack, so checking out his site may be of use ( http://www.ryanvm.net )

[eger]

use

"Q32483.exe /C:""dahotfix.exe /q /n"" /q:a"

in SVCPACK.INF

Knew it was switch related...

as for actually integrating them, it'll get REALLY tricky. RaveRod had a post awhile back, that MAY be of help to youfor that. RyanVM does something similar with his hotfix pack, so checking out his site may be of use ( http://www.ryanvm.net )

How did you know that switch? And what is dahotfix.exe? How is it you are finding that custom command line and file to use on it?

[Alanoll]

http://www.msfn.org/board/index.php?showtopic=31886

Though the file versions are different, the KB #s are the same...

The problem with the MDAC fixes have been around for awhile. The hotfix package themselves aren't typical installers. They extract into a temp folder, and then call dahotfix (included in the file) to actually install.

/C: is a commandline option for IEXPRESS package to override the line it executes upon extraction. /q:a is to be quiet.

Then the inside switches come from dahotfix.exe themselves.

I'm not sure, but the MS site might also have information on these switches as well.

EDIT: http://support.microsoft.com/default.aspx?...kb;en-us;326573

Down near the bottom it describes the siwtches. Rule of thumb, is that MDAC fixes usually use dahotfix, and XML hotfixes usually use something similar.

[eger]

http://www.msfn.org/board/index.php?showtopic=31886

Though the file versions are different, the KB #s are the same...

The problem with the MDAC fixes have been around for awhile. The hotfix package themselves aren't typical installers. They extract into a temp folder, and then call dahotfix (included in the file) to actually install.

/C: is a commandline option for IEXPRESS package to override the line it executes upon extraction. /q:a is to be quiet.

Then the inside switches come from dahotfix.exe themselves.

I'm not sure, but the MS site might also have information on these switches as well.

EDIT: http://support.microsoft.com/default.aspx?...kb;en-us;326573

Down near the bottom it describes the siwtches. Rule of thumb, is that MDAC fixes usually use dahotfix, and XML hotfixes usually use something similar.

Well geez... That makes life so much easier now doesn't it... =p