So, I've read the post from Psyrax in the Knowledgebase http://itninja.com/link/online-resource-kit-for-office-2007
He's suggesting using an "MSI Wrapper" to deploy Project 2007 Pro (We're using the Enterprise Edition, but I believe the deployment is the same)

Creating the MSP is the easy part, after placing the MSP in de Update directory the setup.exe runs silently. Just the way I want it.

But, via our Deployment Tool "Brainforce Deployment Center" we can only use MSI's (And only with the /qb switch [:@], under the credentials of the temporally elevated user)
So let's create the MSI wrapper....and here I'm stuck.

What is exactly an "MSI Wrapper" is it just an MSI which calls another setup?

We're using Wise Package Studio (7.0 sp1) to create and repackage setups.
Of course I can create an MSI which calls the setup.exe, but will it work?
We're using an OTAP environment so the source location of the project setup.exe is different in each environment.

Or should I just repackage the whole Project Installation (With all future administration problems)

So what are your thoughts about this?

Off-topic; and why is Microsoft making the Office 2007 Systems so damn complicated to deploy. What happened to the good old “MSI + CAB” installs, they were working great for me…
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Your correct in thinking that the MSI Wrapper is just and MSI which calls another setup. You're basically going to create the MSiIand have a custom action which launches the setup.exe. Depending on the custom action that you choose, it should run without a problem seeing that the source location is different in each location.

I wouldn't repackage the Microsoft Project installation as you're likely to get into a whole world of hurt with it. Stick to the OCT and your wrapper.
Answered 10/21/2008 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
Thanx Michael! I will try to create a wrapper.
Isn't there something like a wsi or msi template for this Office MSI Wrapper?
Or could someone post it?

If I have a good working template myself, I will see if it's post worthy [:D]
Answered 10/21/2008 by: subsense
Purple Belt

Please log in to comment
0
O.K. got a "working" MSI wrapper, but I have two more questions.

1:
When the wrapper is invoked by our deployment tool, de user gets elevated and can install software.
But the Custom Actions which kicks off the project setup.exe needs to be on "async, no wait".
So de wrapper.msi kicks in, the user gets elevated, wrapper.msi is done user gets unelevated. The project setup starts a bit later and will nog work because the user isn't elevated anymore.
So the wrapper.msi needs to be "open" until the project setup is ready, then the wrapper.msi can be closed.
How can I do that (have allready tried the different Custom Action properties).

2:
The source location is in each environment different, but the wrapper.msi is allways in de same directory as the setup.exe from project. Can I just us a "." to specify the "Current Directory"
Like in the example below?

-In Execute Immediate
After Register Product
if NOT REMOVE~="ALL"
Set Property InstalProcess to [SOURCEDIR](SetLocation)
---------------------------
Custom Action Name: SetLocation
Property: InstallProcess
Property Value: [.]
---------------------------
end if
Answered 10/22/2008 by: subsense
Purple Belt

Please log in to comment
0
1. In order for your MSI to remain open whilst setup.exe is running, you will need to change the Processing=Synchronous (or 'Syncronous, Ignore Exit code' - depending on your preference) under the properties of your custom action.

2. For you to run your setup.exe from various different directories your almost there.

Set Property InstallProcess to [CURRENTDIRECTORY]\setup.exe
------------------------------
Custom Action Type: Execute Program from Path
Custom Action Name: Whatever you want to call it, say LAUNCHSETUPEXE
Property: InstallProcess
Command Line: (Blank)
-----------------------------

That should do it for you.
Answered 10/22/2008 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
Hé Thanx Michael!
I will try your suggestions. I'll post my progress here
Answered 10/23/2008 by: subsense
Purple Belt

Please log in to comment
0
So, do you guys know this tool.:
http://www.vinsvision.com/Articles/tabid/66/EntryID/15/Default.aspx
It's doing exactly what I want. Well...allmost.
I'm walking into the issue that I cannot start a setup.exe which invokes another MSI installation in the wrapper.

Is there allready a solution or workaround for this?

Found the followin article, but it doesn't "work". I've set the custom action which installs the setup.exe to Type 23
http://msdn.microsoft.com/en-us/library/aa368010.aspx
Answered 10/24/2008 by: subsense
Purple Belt

Please log in to comment
0
No one has encountered this problem and has found a solution or workaround?
Answered 10/30/2008 by: subsense
Purple Belt

Please log in to comment
0
michaelnowell

hi michaelnowell,

I still didn't get success to create msi wrapper for project 2007. I will highly appreciate if you can help me in writing these custom action....

please help[&:]
Answered 11/26/2008 by: djain3
Second Degree Blue Belt

Please log in to comment
0
Michael's posts above make it nice and clear what needs to be done.I really can't see what else could be added to make it any clearer.
Answered 11/26/2008 by: VBScab
Red Belt

Please log in to comment
0
When I created the custom action as suggested and installed the msi i get one message as shown below:

"Please go to control panel to install and configure system components"

and no project is installed :(

i will appreciate your help
Answered 11/26/2008 by: djain3
Second Degree Blue Belt

Please log in to comment
0
I've left the Wrapper idea.
Have contacted Microsoft, they are currently investigating how I can install Project 2007 with the usage of only the MSI's. It's not as easy at it seems. MS has spend a lot of hours allready.
As soos as I (or MS) find a solution, I'll post it here.

I can't get the wrapper to install an other MSI (or several!!)......

With Windows Installer 4.5 these things will be a lot easier (So says MS)
Answered 11/26/2008 by: subsense
Purple Belt

Please log in to comment
0
So, recieved an official statement from Microsoft Premier Support;
True MSI installation of Project 2007 (and other Office system 2007 apps) is NOT supported!
They've spend some 20 Hrs on this issue.

Totally suprised by this statement of MS!!

Now I'll install project during logon, as Local Admin.
Not a nice solution....
Answered 12/06/2008 by: subsense
Purple Belt

Please log in to comment
0
ORIGINAL: djain3

When I created the custom action as suggested and installed the msi i get one message as shown below:

"Please go to control panel to install and configure system components"

and no project is installed :(

i will appreciate your help


That sounds like you do not have an explicit path specified to setup.exe in your custom action, in which case it will instead find and try to use the Windows OS setup.exe from the %windir% folder. Hence the message.

Regards,

Spartacus
Answered 12/08/2008 by: spartacus
Black Belt

Please log in to comment
0
Hi

I ran across this issue when trying to deploy Project 2007, I actually need to create log files as well.

What I did was on a clean machine, I installed Project 2007 and then found the Uninstall reg key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\} for project Pro 2007. The uninstall was launched with MSIEXEC /X {xxxxxxxxx}.

So I took that same uninstall line but changed it to
"MSIEXEC /I {xxxxxxxxxxxx} /L*v c:\Windows\Debug\Mylog.log /qn"

This installed Project 2007 with MSI command line switches.

I hope this helps as well as the other great comments
Answered 03/18/2009 by: trunks0408
Yellow Belt

Please log in to comment
0
This installed Project 2007 with MSI command line switches.No, it didn't. If it did anything, it RE-INSTALLED Project 2007. More likely, it simply repaired it.

A product can't be installed from scratch by specifying a Product Code, since that code is contained in the MSI. To install a product from scratch, one needs to specify the path to and name of the MSI.

Sorry if that seems picky but there you are...
Answered 03/18/2009 by: VBScab
Red Belt

Please log in to comment
0
Argh...

Your are correct Sir, I just tried..

you are not picky [:D], I find everything here of GREAT help, thanks to the great posts,

I will do more homework next time :-)

Trunks
Answered 03/18/2009 by: trunks0408
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity