Workshare 5.2 MSI
Hi all,
I haver a new app with a new problem...
Some background - AD deployment, - packaging in WISE, - Problem app Workshare 5.2
So .Net 3.0 is a pre req for this app - iv packaged it and installs a treat, along with some other pre reqs - XML 6.0 parser, RGBRAST [see: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=303334]
Windows Communication Foundation, Windows Workflow Foundation and Woprkshare PDF converter.
Within the same GPO I have set Workshare 5.2 to install, this comprises of the follwing MSI's in install order:
Workshare Protect Engine,
Workshare Protect Client,
Workshare Professional,
The Engine installs as it should, but when it comes to the 'client' there is no trace it is being applied or installed.
The machine rsop has no reference to the client install nor does a gpresult or appwiz. instead the install jumps straight to the 'Workshare Professional' install but fails as the Client isnt present...
When i run a manual install of the Client with its MST it runs sucessfully, then when i give the machine a reboot the 'Workshare Professional' installs.
Any ideas???
I haver a new app with a new problem...
Some background - AD deployment, - packaging in WISE, - Problem app Workshare 5.2
So .Net 3.0 is a pre req for this app - iv packaged it and installs a treat, along with some other pre reqs - XML 6.0 parser, RGBRAST [see: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=303334]
Windows Communication Foundation, Windows Workflow Foundation and Woprkshare PDF converter.
Within the same GPO I have set Workshare 5.2 to install, this comprises of the follwing MSI's in install order:
Workshare Protect Engine,
Workshare Protect Client,
Workshare Professional,
The Engine installs as it should, but when it comes to the 'client' there is no trace it is being applied or installed.
The machine rsop has no reference to the client install nor does a gpresult or appwiz. instead the install jumps straight to the 'Workshare Professional' install but fails as the Client isnt present...
When i run a manual install of the Client with its MST it runs sucessfully, then when i give the machine a reboot the 'Workshare Professional' installs.
Any ideas???
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
Enable the MSI logging policy (in verbose mode). The resulting log, which gets written in %SystemRoot%\TEMP (i.e., NOT the user's temp folder...) will tell you what went wrong.
Posted by:
MightyMin
15 years ago
%SystemRoot%\TEMP
Hi Ian,
Just gave this a try and there doesnt seem to be a log for this component!
I have one for the Engine, extract: [and all of the previous]
[MSI (c) (70:F4) [15:21:30:453]: Executing op: DialogInfo(Type=1,Argument=Workshare Protect Engine)]
And then after that log nothing relating to this deployment...
I have made sure it isnt a corrupt GPO etc by creating a new GPO and applying just this MSI but still no joy :(
Puzzling as it works manually when i do a msiexec.exe /I /qb
Posted by:
turbokitty
15 years ago
Did you transform that MSI? I think it has a little tick box on the last dialog asking if you want to install the client.
That one is a nightmare. I can send you what I have if you're interested.. send me an email.
That one is a nightmare. I can send you what I have if you're interested.. send me an email.
Posted by:
turbokitty
15 years ago
I figured I should probably share.
"default MSI" means REBOOT=ReallySuppress, ALLUSERS=1
Things must install in this order:
DOTNET_KB908002_2
Use default msi
OFF03_KB907417
office2003-kb907417.exe /quiet
OFF07_KB935514
office07-kb935514.exe /quiet
Microsoft Visual C++ 2005 Redist
Use default MSI
DotNET 3
dotnetfx3.exe /q /norestart
Microsoft Report Viewer
reportviewer.exe /q:u /c:"install /q /l"
Interop assemblies (o2007pia.msi)
Use default msi
workshare protect engine (protectengine.msi)
msiexec /i "REINSTALL=ALL REINSTALLMODE=vomus INSTALLSERVICE=1 SKIP_UPGRADE_WARNING=1"
workshare protect enterprise client (protectenterpriseclient.msi)
use default msi
Workshare PDF converter
Use default MSI
Workshare.msi
I transformed this one.
Msiexec /i "REINSTALL=ALL REINSTALLMODE=vomus ALLUSERS=1 SKIP_UPGRADE_WARNING=1"
WORKSHAREPROTECTCR00100210.MSI
Use default msi
I then laid down a custom MSI that installed the office plugins I think.. anyway check to see if the office plugins got installed.
"default MSI" means REBOOT=ReallySuppress, ALLUSERS=1
Things must install in this order:
DOTNET_KB908002_2
Use default msi
OFF03_KB907417
office2003-kb907417.exe /quiet
OFF07_KB935514
office07-kb935514.exe /quiet
Microsoft Visual C++ 2005 Redist
Use default MSI
DotNET 3
dotnetfx3.exe /q /norestart
Microsoft Report Viewer
reportviewer.exe /q:u /c:"install /q /l"
Interop assemblies (o2007pia.msi)
Use default msi
workshare protect engine (protectengine.msi)
msiexec /i "REINSTALL=ALL REINSTALLMODE=vomus INSTALLSERVICE=1 SKIP_UPGRADE_WARNING=1"
workshare protect enterprise client (protectenterpriseclient.msi)
use default msi
Workshare PDF converter
Use default MSI
Workshare.msi
I transformed this one.
Msiexec /i "REINSTALL=ALL REINSTALLMODE=vomus ALLUSERS=1 SKIP_UPGRADE_WARNING=1"
WORKSHAREPROTECTCR00100210.MSI
Use default msi
I then laid down a custom MSI that installed the office plugins I think.. anyway check to see if the office plugins got installed.
Posted by:
MightyMin
15 years ago
Thanks Nathan, Ill give it a try...
I did want to say as im deploying via GPO the .NET3.0 vs_setup.msi doesnt install WCF, WPF, WF, RGBRAST so I have an install order which looks like this:
Workshare 5.2
1.1 Office XP SP3 + Updates *pre-installed
1.2 Lockback Registry Key [Shared Add-in Support Update for Microsoft .NET Framework 2.0 (KB908002)]
1.3 MS ReportViewer 2005
1.4 VisualC++ 2005 Re-distributable
1.5 MS XML 6.0
1.6 MS .Net 3.0
1.6.1 RGB9Rast Installation Database*
1.6.2 Windows Communication Foundation
1.6.3 Windows Workflow Foundation
1.6.4 Windows Presentation Foundation
1.7 Workshare Protect Engine
1.8 Workshare Enterprise Client
1.9 Then the final Workshare.MSI
*The RGBRAST cant be deployed by GPO[1] so I took the DLL from the package and created a new package that just copied the DLL over - maybe it should be registered too?
[1]http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=303334
Very much appreciated.
I did want to say as im deploying via GPO the .NET3.0 vs_setup.msi doesnt install WCF, WPF, WF, RGBRAST so I have an install order which looks like this:
Workshare 5.2
1.1 Office XP SP3 + Updates *pre-installed
1.2 Lockback Registry Key [Shared Add-in Support Update for Microsoft .NET Framework 2.0 (KB908002)]
1.3 MS ReportViewer 2005
1.4 VisualC++ 2005 Re-distributable
1.5 MS XML 6.0
1.6 MS .Net 3.0
1.6.1 RGB9Rast Installation Database*
1.6.2 Windows Communication Foundation
1.6.3 Windows Workflow Foundation
1.6.4 Windows Presentation Foundation
1.7 Workshare Protect Engine
1.8 Workshare Enterprise Client
1.9 Then the final Workshare.MSI
*The RGBRAST cant be deployed by GPO[1] so I took the DLL from the package and created a new package that just copied the DLL over - maybe it should be registered too?
[1]http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=303334
Very much appreciated.
Posted by:
turbokitty
15 years ago
Tearing this apart and deploying each piece individually is playing with fire as it is. Once you start manually copying and registering files, you tread into a quagmire. I read here that you can deploy that piece via WSUS if you have it.
The install order and all its command lines can be found in the setup's ini file.
The install order and all its command lines can be found in the setup's ini file.
Posted by:
aaron.henson@gmail.c
15 years ago
turbokitty,
I see all the commands you made there, and I can do that all from a batch file, but how are you putting it all into one MSI?
I see all the commands you made there, and I can do that all from a batch file, but how are you putting it all into one MSI?
Posted by:
turbokitty
15 years ago
Oh, I'm not. I'm using my deployment tool to chain them all together.
Posted by:
anonymous_9363
15 years ago
I'm using my deployment tool to chain them all together....which, of course, you can do with GP as well.
Posted by:
aaron.henson@gmail.c
15 years ago
ORIGINAL: VBScab
I'm using my deployment tool to chain them all together....which, of course, you can do with GP as well.
How can you "order" your installations via GPO? Also, how can you get GPO to handle the command line switches turbokitty has in the post?
Other than Basic and Maximum user interface, how can you get a msi, for example, to "msiexec /i "REINSTALL=ALL REINSTALLMODE=vomus INSTALLSERVICE=1 SKIP_UPGRADE_WARNING=1"?
Posted by:
AngelD
15 years ago
Any commandline property you handle by a transform.
The installation order is either handle in the order you add them to the GPO; first added = first installed OR you re-order them by using ASSM (Assigned Software Sequence Manager).
The installation order is either handle in the order you add them to the GPO; first added = first installed OR you re-order them by using ASSM (Assigned Software Sequence Manager).
Posted by:
anonymous_9363
15 years ago
Any commandline property you handle by a transform....which, again, you add to the GPO, using the 'Modifications' tab. Note that, if you have multiple transforms, you have to add them all at the same time [Bizarrely, the Ui provides a means to change the order of the MSTs!] . If you click 'OK' to close out the addition, you can't go back and add another MST, you have to start the WHOLE process again.
Posted by:
davidkevanian
15 years ago
Hi Mighty Min,
I've packaged and deployed Workshare Professional 5.2 and had to overcome the same problem you are facing now - "ProtectEnterpriseClient.msi" did not deploy via GPO. The problem was resolved by going to the "Advanced Deployment Tab" of the GPO and checking the box that says "Ignore language when deploying this package." Please post to the board and let me know if this was successful. Good luck!
I've packaged and deployed Workshare Professional 5.2 and had to overcome the same problem you are facing now - "ProtectEnterpriseClient.msi" did not deploy via GPO. The problem was resolved by going to the "Advanced Deployment Tab" of the GPO and checking the box that says "Ignore language when deploying this package." Please post to the board and let me know if this was successful. Good luck!
Posted by:
MightyMin
15 years ago
Ok so I have it installing now... finally!
Setting the GPO to ignore the language helped - thanks for that :)
When I logon to the machine the first time and fire up Word the plugin shows and everything looks good,
But if I close word and re-open its gone? this happens on a clean machine too... :(
TurboKitty; what did you includein this custiom MSI you mention?- "I then laid down a custom MSI that installed the office plugins I think.. anyway check to see if the office plugins got installed. "
Setting the GPO to ignore the language helped - thanks for that :)
When I logon to the machine the first time and fire up Word the plugin shows and everything looks good,
But if I close word and re-open its gone? this happens on a clean machine too... :(
TurboKitty; what did you includein this custiom MSI you mention?- "I then laid down a custom MSI that installed the office plugins I think.. anyway check to see if the office plugins got installed. "
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.