|
| | | Forum Newbie
Group: Forum Members
Last Login: 8/22/2007 3:01:31 AM
Posts: 3, Visits: 10 |
| | When making the package with Office 2003 I get errors when users start word, they get the "Installing office" message that always displays when running word for the first time. Then They get the "You must be an administrator to install Office" message, after clicking abort a couple of times they get Word running, this happens every time. |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 8/8/2008 12:14:02 PM
Posts: 657, Visits: 793 |
| Here is a link to our KB article containing "best practices" for creating a package of Office: http://www.nbtnet.newboundary.com/supportkb/Article.aspx?id=10044 It sounds as if the package is incomplete in some way, or it wasn't built on a "clean" machine. We recommend that you create a new package following the recommendations in the article. The Application Event Log on the systems where this error happens will probably have some hints about what is causing the problem. Look for "MsiInstaller" as the source of errors in that log. Feel free to email support@newboundary.com with information about the errors.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 8/22/2007 3:01:31 AM
Posts: 3, Visits: 10 |
| | I read the article, made an administrative installation to a network share as suggested. Then moved to another "clean" computer and started the baseline. (All using wmware) I run the command: \\CMOPUTER\SHARE\Office2003pro\SETUPPRO NOUSERNAME=True ENTERPRISE_IMAGE=True I made a full install with everything installed to the computer. After the installation was complete I did not open Word. Then I looked for changes. Tried the packade on another clean computer but still gets a message when opening word for the first time. Roughly translated to english: "You must be an administrator or have permission from an administrator to install Office. Contact the systemadministrator if you want more information" // Magnus |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 8/8/2008 12:14:02 PM
Posts: 657, Visits: 793 |
| Are you sure that you have a volume licensed edition of Office? Retail copies of Office cannot be used to create packages for distribution.
As a test, you may want to try actually launching Word before doing the find changes step. That way whatever final changes Office seems to want to make will already be included in the package. That being said, a digital license might be created, thus making the package undistributable (as noted in the article). If you go this route, avoid activating Office if possible.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 8/22/2007 3:01:31 AM
Posts: 3, Visits: 10 |
| | Yes, we have an enterprise cd with an enterprise cd-key. Office installs just fine, it is just the Outlook applikation that gives us problems. If I open up Outlook once before crating the packade, it installs fine but all the users gets error-messages bout paths pointing to my own profile. |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 8/8/2008 12:14:02 PM
Posts: 657, Visits: 793 |
| Just to verify Word, Excel, and PowerPoint are working fine on the PC you've delivered the Package too, however Outlook is not, and indicates and error related to your profile? With that information it sounds as if you must use Exchange and are applying the Office 2003 Pro package to machines that (assumably) had Office 2000 Pro installed. One "portion" of the Office upgrades Prism Suite admittedly struggles with is the modifying of individual profiles for Outlook Profiles that "bind" with an existing Exchange profile. The reason your end users are seeing this "error" is your Exchange Profile was captured. We don't have a good solution for how to create variables for this with Office 2003. You may wish to read the following Technote, and look at the Office 2003 Resource kit as an option for building a Transform File using the utility that MS has, and delivering a command line setup that also includes the "Transform File" (MST or MSP) file. This is an "answer" file to how MS should upgrade itself, and part of the process can "correctly" upgrade Outlook Profiles connected to Exchange. http://www.nbtnet.newboundary.com/supportkb/article.aspx?id=10266 If you have any questions or want to talk about this further please email us at support@newboundary.com or call us at 612-379-1851, we might have other suggestions we can offer.
New Boundary Technologies Support
support@newboundary.com |
| |
|
|