Software Deployment

- Install the MSI as an administrative install to an administrative install point
- Apply the patches to the administrative install point
- Use the patched MSI from the administrative install point as the source for deployment

Hi,

Thanks for your answer.
But I have never done it before so I dont know how to do the administrative install, and apply the patches to the install point etc...
For sure it probably easy but as I sad I have never done it before.

Could you or some one else describe it with a little more detaile?

Thanks!

You have 'Super Member' status and you've NEVER done an admin install or applied a patch?!? Man....

Anyway, did you, by some slim chance, read my signature? Use this search term, including the quotes:

. "windows installer" +administrative +install +point

Once you've feasted on the glory that is Google, you can then use it again:


. "windows installer" +patch +install +point

Allthough patching is often used I don't think you will be able to remove an applied patch on an AIP after installed. Can't remember if I've ever tried that.

So depending on your requirements you could also have a look at "Patching Initial Installations"
http://msdn.microsoft.com/en-us/library/aa370581(VS.85).aspx

ORIGINAL: AngelD
Allthough patching is often used I don't think you will be able to remove an applied patch on an AIP after installed.That's true. One of my previous clients kept separate folders for each iteration (including Service Packs, also) to cater for that eventuality. That's a client call, rather than a specific packaging issue, of course.

VBScab:
Well many thanks for your help and kindness.
I guess that I am a Super Member because of my number of posts here. As you can see I have 0 on the Scoreboard!
Maby I have alot of posts and no scores because I dont have that much experience of MSI packaging... Or what do you think?

[:'(][:'(][:'(][:'(]

But dont worry I will not bother you again...

ORIGINAL: AngelD

Allthough patching is often used I don't think you will be able to remove an applied patch on an AIP after installed. Can't remember if I've ever tried that.

So depending on your requirements you could also have a look at "Patching Initial Installations"
http://msdn.microsoft.com/en-us/library/aa370581(VS.85).aspx



Thanks AngelD! Looks helpfull. Will try it now.

When I try this commandline:
msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb

I only get the Windows Installer info screen. Like if I write "msiexec /?"

ORIGINAL: aXz
When I try this commandline:
msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb

I only get the Windows Installer info screen. Like if I write "msiexec /?"Look again at the command lines shown in the articles. First:

. msiexec /a Example.msi
to install an admin version of the package. You will be prompted for a network location, but any will do. The place where you "install" this image is what is known as the 'administrative insall point' and is the point from which your workstations will install. Thus, it makes sense to use a globally-available network share. Then, patch the admin install point:

. msiexec /a Example.msi /p msipatch.msp;msipatch2.msp

ORIGINAL: aXz
I guess that I am a Super Member because of my number of posts here. As you can see I have 0 on the Scoreboard!
Maby I have alot of posts and no scores because I dont have that much experience of MSI packaging... Or what do you think?With the greatest respect, perhaps a little less posting and a little more reading might help? As far as I can recall, almost every one of your posts could have been answered by either using AppDeploy's search function or a search engine like Google. To my mind, it's pure laziness to post questions about how to patch a Windows Installer package. Then, when you get response, you skim through the pages you were directed to and cobble together an incorrect command line. Surely you must realise when the WI engine prompts you with a message box detailing the command line switches that you entered something incorrectly?

ORIGINAL: VBScab

ORIGINAL: aXz
When I try this commandline:
msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb

I only get the Windows Installer info screen. Like if I write "msiexec /?"Look again at the command lines shown in the articles. First:

. msiexec /a Example.msi
to install an admin version of the package. You will be prompted for a network location, but any will do. The place where you "install" this image is what is known as the 'administrative insall point' and is the point from which your workstations will install. Thus, it makes sense to use a globally-available network share. Then, patch the admin install point:

. msiexec /a Example.msi /p msipatch.msp;msipatch2.msp



Ok.. Thanks I will try this.


Surely you must realise when the WI engine prompts you with a message box detailing the command line switches that you entered something incorrectly?

Of course I understand that. But is it wrong to ask what I am doing wrong? Thats what I think is a good forum. A forum where you as a newbee dont have to be worried if you ask anything stupid. Maby I was wrong....
Anyway lets leave that discussion.

When I use this commandline
msiexec /a package.msi /p patch.msp

The Msi installer starts and the installation beginne.

But I have 3 patches so I use this commandline
msiexec /a package.msi /p patch.msp;patch2.msp;patch3.msp

But that dosent work. I have read the articles and I dont understand why it dosent work.
I have done the administrative install before I try to add my 3 patches (msiexec /a package.msi)

Try pathing them one by one.
ex.
msiexec /p <path to patch.msp> /a <path to AIP\package.msi>
msiexec /p <path to patch2.msp> /a <path to AIP\package.msi>
msiexec /p <path to patch3.msp> /a <path to AIP\package.msi>

Have you tried adding explicit paths to the MSI and patches, i.e.

. msiexec /a [path_to_MSI]Example.msi /p [path_to_MSP]msipatch.msp;[path_to_MSP]msipatch2.msp

ORIGINAL: AngelD

Try pathing them one by one.
ex.
msiexec /p <path to patch.msp> /a <path to AIP\package.msi>
msiexec /p <path to patch2.msp> /a <path to AIP\package.msi>
msiexec /p <path to patch3.msp> /a <path to AIP\package.msi>




I guess I will have to do it that way. Its only 3 patches so I can live with that.


ORIGINAL: VBScab

Have you tried adding explicit paths to the MSI and patches, i.e.

. msiexec /a [path_to_MSI]Example.msi /p [path_to_MSP]msipatch.msp;[path_to_MSP]msipatch2.msp



I have always used explicit paths to the MSI and MSP files.