camilorg Posted May 27, 2011 Share Posted May 27, 2011 I have created a WinXP PRO unattended installation DVD that works great, with Windows Updates embedded, thanks to the great help from MSFN articles and comments on topics created in the forum.Now I have to add the .NET Framework to the installation DVD.So far I have run this installation filehttp://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exeFrom the RunOnceEx file. It runs fine and the .NET Framework installation has no issues.But when I use my DVD now I end up with a gazillion updates for the .NET Framework.Can you please tell me how can I add these .NET Framework updates to the unattended installation DVD? Thanks in advance, your help will be greatly appreciated. Link to comment Share on other sites More sharing options...
Sp0iLedBrAt Posted May 28, 2011 Share Posted May 28, 2011 You can also add them from RunOnceEx. Start any update from Command Prompt with the /? switch and it will tell you which switches to use to make it silent or passive (i.e. unattended in any way). You can also extract the .msp files from the updates themselves and run them through Windows Installer, i.e. Install Options </package | /i> <Product.msi> Installs or configures a product /a <Product.msi> Administrative install - Installs a product on the network /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>] Advertises a product - m to all users, u to current user </uninstall | /x> <Product.msi | ProductCode> Uninstalls the productDisplay Options /quiet Quiet mode, no user interaction /passive Unattended mode - progress bar only /q[n|b|r|f] Sets user interface level n - No UI b - Basic UI r - Reduced UI f - Full UI (default) /help Help informationRestart Options /norestart Do not restart after the installation is complete /promptrestart Prompts the user for restart if necessary /forcerestart Always restart the computer after installationLogging Options /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile> i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file ! - Flush each line to the log * - Log all information, except for v and x options /log <LogFile> Equivalent of /l* <LogFile>Update Options /update <Update1.msp>[;Update2.msp] Applies update(s) /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode> Remove update(s) for a productRepair Options /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode> Repairs a product p - only if file is missing o - if file is missing or an older version is installed (default) e - if file is missing or an equal or older version is installed d - if file is missing or a different version is installed c - if file is missing or checksum does not match the calculated value a - forces all files to be reinstalled u - all required user-specific registry entries (default) m - all required computer-specific registry entries (default) s - all existing shortcuts (default) v - runs from source and recaches local packageSetting Public Properties [PROPERTY=PropertyValue] You need the switches in bold for the .msp files.Cheers Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now