Add Outlook in Office 2007
We deployed MS Office 2007 to all our workstations without Outlook. Now we wish to deploy Outlook. I made the change to our office .msp file so that Outlook is now included and populated the required fields for our exchange server and to create a new profile. For new installs this works perfectly.
For existing installs that don't have outlook, from what I have read, I should be able to just apply this new .msp to the workstation and Outlook should get installed. It works sort of. Outlook does get installed but the icon in the start menu is without a graphic and when you launch outlook it is launching a new profile wizard and asking for user and server info. Am I missing something to this OCT patch thing?
For existing installs that don't have outlook, from what I have read, I should be able to just apply this new .msp to the workstation and Outlook should get installed. It works sort of. Outlook does get installed but the icon in the start menu is without a graphic and when you launch outlook it is launching a new profile wizard and asking for user and server info. Am I missing something to this OCT patch thing?
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
From my reading, you can't use an MSP to update an existing installation. You must use a version of CONFIG.XML. Check out the links provided to the various MS KBs in the Office 'Package KB' here on AppDeploy.
Posted by:
aogilmor
13 years ago
my reading of the msi says you could probably use ADDLOCAL="OUTLOOKFiles" to add the Outlook product to an existing installation
Posted by:
anonymous_9363
13 years ago
...which you can do via the XML file. I can't exactly recall what the problem was with using transforms with the Office 2007 (and later) MSIs, plus I'm no longer working for that client so can't check but we tried all sorts of shenanigins but in the end came back to running Setup.EXE against an edited XML file.
EDIT:
Merry Christmas, Owen! :-)
EDIT:
Merry Christmas, Owen! :-)
Posted by:
aogilmor
13 years ago
...if you're restricted to using setup.exe ADDLOCAL might not work so your only option might be the xml file.
BUT you should be able to do msiexec /i {guid} ADDLOCAL="OUTLOOKFiles"
don't have time to try it with o2k7...trying to get out early for Christmas Eve.
Thanks Ian! Merry Christmas to you too!
BUT you should be able to do msiexec /i {guid} ADDLOCAL="OUTLOOKFiles"
don't have time to try it with o2k7...trying to get out early for Christmas Eve.
Thanks Ian! Merry Christmas to you too!
Posted by:
joedown
13 years ago
Just to follow up with this in case anyone else has this issue. I finally gave up and called MS. Apparently there is a known bug in the office installation, no really, where the shortcut icon does not get created correctly. MS also stated that the best way to update office is to use the OCT and create a new patch with just the changes you want to do to office instead of just updating the existing patch. Under the add files option you need to add a shortcut to the exe. The shortcut under the Configure Shortcuts section does not work.
Posted by:
zlatan24
13 years ago
ORIGINAL: joedown
We deployed MS Office 2007 to all our workstations without Outlook. Now we wish to deploy Outlook. I made the change to our office .msp file so that Outlook is now included and populated the required fields for our exchange server and to create a new profile. For new installs this works perfectly.
For existing installs that don't have outlook, from what I have read, I should be able to just apply this new .msp to the workstation and Outlook should get installed. It works sort of. Outlook does get installed but the icon in the start menu is without a graphic and when you launch outlook it is launching a new profile wizard and asking for user and server info. Am I missing something to this OCT patch thing?
Yesterday my friend asked me to help him with one problem. As it turned out ms outlook problem. I advised him some programs, but it didn't assist him. Only today morning I have found tool which might relieve in this trouble. Fortunately it was quite effective and would be the same helpful in any other situation - [url=http://www.recoverytoolbox.com/damaged_pst_file.html]large .pst file damaged[/url].
Posted by:
anonymous_9363
13 years ago
Hey, Timmster. What was it about the fact that each of the poster's response has included a link to that vendor's web site that led you to that conclusion?
Cynic...LOL
Cynic...LOL
Posted by:
timmsie
13 years ago
There does seem to be pattern developing! could just be an amazing coincidence of course....
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.