I have Office 2K installed on target machines along with MS Project 2003.
Now, when I run Office 2003 Package over it, Office gets upgraded. However, when I launch MS Project 2003, I am prompted to input the licensing details of MS Project 2003. Any idea, how can I avoid this?
Can I get any help by using Resource kit for modifying the Office 2003 Package?
Thanks
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
Using AppDeploy's 'Search' facility is always instructive. http://itninja.com/question/blackberry-3.6-must-run-setup.exe865&mpage=1&key=visio&#31865

Although we got no response from the OP as to whether the issue was fixed, it was only a few days ago. Or, would you by the slimmest of slim chances, be the OP?
Answered 02/15/2008 by: VBScab
Red Belt

Please log in to comment
0
You are Genius....Yes, I m the one who posted the earlier topic. Lost the login info, had to create new one.
Still not clear as to what to look for in office mst file. Thanks for your quick response.
Answered 02/15/2008 by: MSIRepackager
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: MSIRepackager
Still not clear as to what to look for in office mst file.
Eh? Your posts don't mention an MST...
The issue, as far as I can see, is that your Office installation is clearing the license entries for Project and/or Visio. As I suggested, run ProcMon in parallel with Project/Visio (afer the Office install has run) and it will show you what registry and file activity is taking place. From there, you should be able to work out how to stop the Office installation from clearing the license info, if indeed that's what's happening.

Remember that any changes you make should be applied via a transform. Office is a special animal as regards transforms and you should use the Office Resource Kit's customisation tool to create it in the first instance. You can then use your normal MSI-authoring tool to edit the transform. Make sure you set the original MSI read-only first, as some tools may add tables to the MSI, which Office is, to say the least, not keen on!
Answered 02/15/2008 by: VBScab
Red Belt

Please log in to comment
0
As you said it correctly, I have a GUID-formatted key for Project 2003 - at HKLM\SOFTWARE\Microsoft\Office\11.0\Registration; which gets deleted after the installation of Office 2003.
Where can I find this GUID in the Office MST and how can I avoid clearing the license info of Project 2003.

Thanks for your your responses.
Answered 02/18/2008 by: MSIRepackager
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: MSIRepackager
As you said it correctly, I have a GUID-formatted key for Project 2003 - at HKLM\SOFTWARE\Microsoft\Office\11.0\Registration; which gets deleted after the installation of Office 2003.
Where can I find this GUID in the Office MST and how can I avoid clearing the license info of Project 2003.
Open the MST in your authoring tool and search for it. You may want to set a property using AppSearch and then condition the component containing the registry key so that, if the property is populated, the offending entry is skipped.
Search your authoring tool's Help file or MSI.CHM (which will have been installed by the tool) for details on using AppSearch.
Answered 02/18/2008 by: VBScab
Red Belt

Please log in to comment
0
I did exactly as you said. I tried searching the GUID in Office.mst using Wise Package Studio. However, I couldn't locate the specific GUID anywhere inside it.
As an alternative approach, I imported the Project 2003 registry key GUID value that is being erased with Office Installation........and applied this registry set on target machine after Office installation. Used Wise script to do so. It worked and the issue is resolved........atleast on test machine. Please, let me know if this is a correct way to rectify the issue?
Answered 02/19/2008 by: MSIRepackager
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: MSIRepackager
Please, let me know if this is a correct way to rectify the issue?
Well, it's *A* solution that works for you. If you cannot locate the GUID in the MST, my suspicion would be that a Custom Action is resetting the registry entry. If it were me, I'd run the MSI/MST through my authoring tool's debugger (or use DebugView) to determine which action is causing the change. However, you may be happy to continue with the 'solution' you have. Sometimes, expediency wins over correct procedure, we all uderstand that. :)
Answered 02/19/2008 by: VBScab
Red Belt

Please log in to comment
0
Yes, very true. I'm grateful for your help.
Answered 02/19/2008 by: MSIRepackager
Senior Yellow Belt

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