Deploying Windows XP SP 3 via SCCM: EXE vs MSI
Hi all,
I am new to packaging/distribution, so please forgive the newbie-type question.
I have a project to upgrade all of the PCs in my workplace from Windows XP SP2 to SP3 using SCCM 2007. I have downloaded and extracted the SP3 files to a folder on the network, and I have set up a package for distribution. I used the following command line for executing the program: msiexec /i Update.msi /qb-!
The package downloads to the target client PC, but the program fails during the install. When I went on the Internet to research the reason for this I noticed most administrators seem to be using Update.exe rather than Update.msi when deploying SP3 from SCCM. There must be a reason for this, but I do not know.
Any ideas?
M
I am new to packaging/distribution, so please forgive the newbie-type question.
I have a project to upgrade all of the PCs in my workplace from Windows XP SP2 to SP3 using SCCM 2007. I have downloaded and extracted the SP3 files to a folder on the network, and I have set up a package for distribution. I used the following command line for executing the program: msiexec /i Update.msi /qb-!
The package downloads to the target client PC, but the program fails during the install. When I went on the Internet to research the reason for this I noticed most administrators seem to be using Update.exe rather than Update.msi when deploying SP3 from SCCM. There must be a reason for this, but I do not know.
Any ideas?
M
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
dvdzonenz
14 years ago
MSI is not a suitable thing to install IE and service packs. This has been discussed elsewhere.
You may try WSUS etc. Or update the entire image to SP3
You may try WSUS etc. Or update the entire image to SP3
Posted by:
DeployTech
14 years ago
Marmot,
if you run the install of SP3 using the "<fullfile>.EXE" /passive /norestart, that will work fine for you, I have done it a number of times with SP1\2 and 3 for XP from SMS and SCCM. If you try to run the SP3 upgrade from the MSI manually, I don't even think that it works (I remember trying it once and I'm sure it failed).
As for IE7, if you use the IEAK, that will create an MSI for you that will deploy fine from SMS\SCCM\GPO.
if you run the install of SP3 using the "<fullfile>.EXE" /passive /norestart, that will work fine for you, I have done it a number of times with SP1\2 and 3 for XP from SMS and SCCM. If you try to run the SP3 upgrade from the MSI manually, I don't even think that it works (I remember trying it once and I'm sure it failed).
As for IE7, if you use the IEAK, that will create an MSI for you that will deploy fine from SMS\SCCM\GPO.
Posted by:
Marmot
14 years ago
Thank you for your prompt replies.
So, deploying the EXE is the recommended/best practice way to go with SCCM... Then the reason for including an MSI in the install package is for GP deployments?
So, deploying the EXE is the recommended/best practice way to go with SCCM... Then the reason for including an MSI in the install package is for GP deployments?
Posted by:
DeployTech
14 years ago
You'd use WSUS to deploy in a non-managed environment (if your organisation are big enough for GPO, you are big enough for WSUS), and slipstream it into your Windows Source for rebuilds.
Posted by:
Marmot
14 years ago
Do you deploy the full package (WindowsXP-KB936929-SP3-x86-ENU), or do you extract the package and deploy Update.exe?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.