MSP files and GPO
Drew
.NET frame work 1.1 using Group Policy. It is an assigned package, deployed
under Computer Configuration, applied to Domain Computers.
I would like to now update each machine with .NET Framework 1.1 service pack
1. However, after figuring out how to extract all the files from the service
pack, I only have a MSP patch file to work with. I have tried to add this to
the "Modifications" and "Upgrade" tab of the package, but it will only accept
MSI file.
Anyone know what the limitations of MSP files and Group Policy is?
Is there a way to incorporate the MSP file into my GPO so I can update the
machines?
Why doesn't Microsft include an MSI file for all its software?
matty....@gmail.com
You have the below options for install if you look at S867460.msp /?
...or you could look at WSUS for future patch installs...
http://www.wsuswiki.com/WSUSFAQ
Cheers,
Matty
------
Windows ® Installer. V 3.01.4000.1823
msiexec /Option <Required Parameter> [Optional Parameter]
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 product
Display 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 information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging 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 product
Repair 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 package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on
the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the
Independent JPEG Group.
------
Drew
I was hoping to deploy it using the Software Installation section of Group
Policy like I did with the initial .NET Framework package
unless you see some other way
"matty....@gmail.com" wrote:
>
> You have the below options for install if you look at S867460.msp /?
>
> ....or you could look at WSUS for future patch installs...
Darren Mar-Elia
that you would have to have created an administrative install point for the
original package on your servers. Then, you use MSIExec to apply the .msp
file to the administrative install point package, using the following
syntax:
msiexec /a Admin Path\Data1.msi /p Source Path\data1.msp
Then you perform a Redeploy on the GP-based package. The re-deploy will be
picked up by all clients at their next foreground processing cycle and they
should essentially re-install the package with the new patched version.
Darren
--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
Check out http://www.gpoguy.com -- The Windows Group Policy Information Hub:
FAQs, Whitepapers and Utilities for all things Group Policy-related
Just Released! The new Windows Group Policy Guide from Microsoft Press!!!
Check it out at http://www.microsoft.com/mspress/books/8763.asp
"Drew" <Dr...@discussions.microsoft.com> wrote in message
news:F0ADF40E-2208-43C2...@microsoft.com...
Drew
When I attempted this, I got the following error,
"This patch package could not be opened. Contact the application vendor to
verify that this is a valid Windows Installer patch package."
Service pack 1 for Framework 1.1 is downloaded with a file name of
"NDP1.1sp1-KB867460-X86.exe. When I extract the files, I get 3 files
1. Microsoft.WindowsInstaller.dll
2. Microsoft.WindowsInstaller.Package.dll
3. PatchExec.exe
If I then extract from PatchExec.exe, I get 1 file
1. Patch.msp
When I double click on the Patch.msp I get the same error as stated above.
Has anyone deployed Framework 1.1 Service pack 1 using group policy yet
Can anyone outline for me the steps that were taken.
Thanks