robr

I'm having a problem a hotfix - 832894. All my hotfixes are installed during WinPE via cmdlines.txt. This appears to run and install fine, but if I go to Windows Update, I'm told I still need to install this. From CMDLINES.TXT q832894.exe /Q:A /R:N Any thoughts? This is on Windows Server 2003 Standard

Thanks, here's MS' response which is the same as yours, I'll give this a shot Include them in the OEMRunOnce section of the winbom.ini, so they are installed on the first boot to the Windows Desktop. Example: [OEMRunOnce] "Example Hot Fix","""\\OPKSERVER\OPKTools\Apps\msxml4qfe.exe"" /Q /C:""msiexec /l msxml.msi /qn"" "

i havent integrated an MSI into an unattended install before, but i had thought that the msiexec installer wasnt available during windows setup.

Microsoft in their infinite wisdom has apparently decided to release the hotfixes for Microsoft Storage Server in .MSI format. Has anyone dealt with these before and what's the best way to incorporate them into an unattended install? Directory of C:\OPKTools\Hotfixes 04/28/2004 12:00 PM 222,720 WindowsStorageServer2003FeaturePack-KB838 985.msi 04/28/2004 12:11 PM 167,424 Windows_Storage_Server_2003-KB825191.MSI 04/28/2004 12:11 PM 316,928 Windows_Storage_Server_2003-KB828214.msi 04/28/2004 12:11 PM 523,264 Windows_Storage_Server_2003-KB828878.msi 04/28/2004 12:12 PM 425,984 Windows_Storage_Server_2003-KB835152.msi 04/28/2004 12:18 PM 425,472 Windows_Storage_Server_2003-KB838238.msi

I ended up using sysprep.inf [GuiRunOnce] "C:\Windows\SYSTEM32\CMD.EXE /c RD c:\stage /s /q"

I have some directories I'd like to be deleted upon enduser mini-setup. I figured I could use cmdlines.txt to do this, but if I add an entry like this: [Commands] "rmdir /s /q c:\stage" or like this: [Commands] "%windir%\SYSTEM32\CMD.EXE /c RMDIR c:\stage /s /q" I'm told RMDIR can't be found. I realize I could put all the files in the sysprep directory which is deleted automatically, but I'm already committed to where the current directory structures live. Any suggestions?

depends what you mean by using winbom to install software. i use winbom.ini to point to the WinPE configuration on the network, the WinPE software installs are located in the config set. No idea if you mean something else by using winbom.ini.

hmmm, i havent looked at the IEAK at all, i wouldnt want to do it for this small thing, but thanks for making me think in that direction in case i come across something else it would be suitable for. i havent run the msi directly with the switches, the preinstall guide for storage server says to use msiexec to call it and use those switches.

for anyone else that gets stuck on this, the batch file did work, the carats did not. i'd like to figure out how to properly do this without a CMD file, because a "dos box" pops up to run the CMD file. I'd prefer to see nothing, but this will do for the moment.

ok i found a couple of solutions here http://www.mail-archive.com/unattended-inf...t/msg00285.html the first says create a .cmd file with the command i need to run and call it from [guirunonce], that way theres no nested quotes. ugly but it will work. the second i dont know if it will work but it said to use a carat like this [guirunonce] "blah.exe ^"option1, option2^" /abc"

ok this is odd, i checked the docs, the docs show quotes in the examples [GuiRunOnce] "command 1" "command 2" . . however i did a google search on guirunonce and see examples without the quotes. before i drive 45 minutes into the office to test this and continue with my project, can you confirm quotes aren't needed? this is one of my few remaining big hurdles. thanks again for all the help, i really appreciate it. The last time I touched this stuff was NT 4.0 and there were no internet resources for unattended installs back then, I'm really glad to see there are several resources available now.

oh! you're right.... i dont have the docs in front of me, but now that you mentioned that, i remember reading that. as i recall though it still needs to be enclosed in quotes doesnt it?

even the webboard software here is converting one of my quotation marks to read &QUOTE . Wherever you see &QUOTE on my post, it's just supposed to bea quotation mark

the command line entry requires quotes. if i type msiexec /i c:\stage\sasetup30.msi ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,UsersAndGroups,NetworkSetup,Logs,SystemB ackup,AlertEmail,Shutdown,RemoteDesktop,SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,Fo ldersAndShares,Services,DisksAndVols" /qn at the command prompt, it works. the documentation for [guirunonce] says you need to enclose the command in quotes as well. So now you have quotes within quotes and I thought there was a special syntax for that. Maybe not, I don't think I've tried it like below, but without the syntax, I'm pretty sure that the second set of quotes will act like a closing quote. [GuiRunOnce] "StorageServer","msiexec /i c:\stage\sasetup30.msi ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,UsersAndGroups,NetworkSetup,Logs,SystemB ackup,AlertEmail,Shutdown,RemoteDesktop,SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,Fo ldersAndShares,Services,DisksAndVols" /qn"

im not trying to appear special, i could care less about who has what. im just upset that an avenue of support for such a niche product with poor preinstall documentation was closed down to me by someone at microsoft. im working for a vendor that sells big storage arrays, so i guess the product was made available to companies in that line of business.

well with guirunonce, the install failed with an error saying unattend.txt is invalid or has an error. im thinking its just the syntax but im not sure.

after some thought, this is probably to early in the process to install this, perhaps it belongs in [GuiRunOnce]

Hmmm........ it saw the command, it just failed... from winbom.log: Found Preinstall Section '"msiexec /i c:\stage\sasetup30.msi ADDLOCAL=BackEndFramework' for application 'StorageServer' ERROR: An invalid Install Technology was provided for 'StorageServer'. Can not continue with current application Preinstallation. Factory state "Installing applications" took 1.266 seconds to complete.

no, thats the command to do an unattended install of the microsoft storage server 2.0 software from a command prompt. unfortunately my plan of throwing it in the winbom.ini didn't work for some reason

actually i need to get it to run during preinstall, so i guess it need to go into winbom.ini under [OemRunOnce] I was just creating an INF file and running it to test the syntax before going through the whole preinstall process.

Whats the proper syntax for the quotes here? (wrapped for readability). Gracias! [DefaultInstall] "StorageServer","""msiexec /i c:\stage\sasetup30.msi ADDLOCAL="BackEndFramework,WebUI,NAS,SetDateAndTime,Set_Language,UsersAndGroups,NetworkSetup,Logs,SystemB ackup,AlertEmail,Shutdown,RemoteDesktop,SysInfo,ScheduledDefragmentation,ShadowCopyManagement,UPS,Fo ldersAndShares,Services,DisksAndVols" /qn"""

ok thanks for letting me know, i have a few other OPK related problems i'm working on before i get back to this one.

Thanks, I did post there and got a somewhat helpful response... it pointed me in the right direction anyway . Though the MS individual that responded asked me not to post about that product because it's apparently not generally available to OEMs and asked me in the future to go through my Microsoft rep. Not a particularly useful solution since that rarely results in getting anything done in a timely fashion, but hopefully I'll make it over this hurdle and move on to something else to get messed up on .

good catch on the signature, i never would have figured that one out. I keep thinking of 2003 Server as XP server, but I need to use Signature=$CHICAGO$ I'll try that as soon as my current preinstall attempt at Storage Server fails... er... works! The reason I'm switching back and forth from 2003 Server to PE is because its an OPK install of 2003 Server using the Windows PE methodology.

This is for Windows 2003 Server I've created the SVCPACK.INF from the instructions given for unattended install of hotfixes, however this doesn't run during GUI mode setup. Reading through the instructions again for creating this file, I don't see anything that explains how to make this file execute. Is it supposed to happen automagically? This is from a WinPE CD and the files reside here: Directory of C:\OPKTools\cfgsets\storage server msi test\$OEM$\$$ 03/26/2004 01:52 PM <DIR> . 03/26/2004 01:52 PM <DIR> .. 03/26/2004 10:54 AM 1,088 svcpack.inf 03/26/2004 12:02 PM <DIR> system32 03/26/2004 01:52 PM <DIR> Update The update directory contains all the files renamed to 8.3 format For the hell of it, after Windows is installed, I right click on the INF file and select install but nothing happens. Also of note, there is no other SVCPACK.* on the WinPE CD, but after installation, there is a .IN_ in the C:\i386 directory on the target machine. There is also a SVCPACK.INF in the C:\WINDOWS\INF directory. My .INF file ends up in C:\WINDOWS when the install is complete. Here's the INF file: [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [setupData] CatalogSubDir="\i386\Update" [ProductCatalogsToInstall] [setupHotfixesToRun] q282010.exe /Q /O /N /Z Q321884.exe /Q:A /R:N Q323255.exe /Q /O /N /Z Q328310.exe /Q /O /N /Z Q329048.exe /Q /O /N /Z Q329115.exe /Q /O /N /Z Q329170.exe /Q /O /N /Z Q329390.exe /Q /O /N /Z q329441.exe /Q /O /N /Z Q329834.exe /Q /O /N /Z q330994.exe /Q:A /R:N Q331953.exe /Q /O /N /Z Q810565.exe /Q /O /N /Z Q810577.exe /Q /O /N /Z Q810833.exe /Q /O /N /Z Q811493.exe /Q /O /N /Z Q811630.exe /Q /O /N /Z Q814033.exe /Q /O /N /Z Q815021.exe /Q /O /N /Z Q817287.exe /Q /O /N /Z Q817606.exe /Q /O /N /Z q817787.exe /Q:A /R:N q819639.exe /Q /O /N /Z Q819696.exe /Q /O /N /Z q821557.exe /Q /O /N /Z q822925.exe /Q:A /R:N q823182.exe /Q /O /N /Z q823559.exe /Q /O /N /Z q823980.exe /Q /O /N /Z q824141.exe /Q /O /N /Z q824146.EXE /Q /O /N /Z q825119.exe /Q /O /N /Z q828035.exe /Q /O /N /Z q828750.exe /Q /O /N /Z Q832483.EXE /Q:A /R:N winscrpt.exe /Q:A /R:N qchain.exe