Re: Converting an Unmanaged Office 2003 SP1 to a Managed Office 2003 S



Hi Rich,

>From your basic scenario, I'm not following your Standard to Pro 'upgrade' scenario. There isn't an 'upgrade' path for Office
within the same (2003) product series and the Office Service packs are series (2000, XP/2002, 2003) specific but they aren't
'edition' (package) specific.

This information may be helpful
http://support.microsoft.com/default.aspx?scid=kb;en-us;307803&sd=tech

========
<<"Rich" <Rich@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:AF50EF31-FA41-4994-9320-2C5FA6A8823C@xxxxxxxxxxxxxxxx
Hello,

Can someone please help me? I am trying to convert an unmanaged Office 2003
SP1 Standard to a Managed Office 2003 SP2 Professional through Group Policy.
I have created an MST File with the required settings. I created a package
in Group Policy to include the MST. The deployment was successful, however
an exisiting user does not grab the new settings that were applied on the MST
File. If a new user logs in, that user will grab the new settings.

Here are the steps that I took:

1. Deployed Office 2003 Standard SP2 via group policy with the MST File.
(Existing user did not grab settings from MST File). I have to deploy
standard first before upgrading to Pro. If I don't do this, then I would
have Standard and Pro at the same time.
2. Deployed Office 2003 Professional SP2 via group policy with the MST
File. I specified in the package to upgrade from the Office 2003 Standard
SP2 package. Existing user did not grab settings from MST File.
3.

I have tried different settings in Step 9 in the Custom Installation Wizard
file by selecting and deselecting "Mirgrate User Settings." Also tried using
a .ops file with no luck. Also I've even tried converting from unmanaged
Office 2003 SP1 Standard to a managed Office 2003 Standard SP1.

Am I missing a step here? Or is it even possible to have existing users
grab the new settings from the MST File?

Note: It works fine when upgrading from Legacy Office apps (Office
97/2000/XP).

Thanks. >>
--
Let us know if this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx



.



Relevant Pages

  • Re: Ideas of making C64 emulation easier
    ... in one file with the settings and all disc images you need for the game ... Such a standard would make things much easier, ... The bundle itself could simply be a zip file. ... run the emulator instead of a zip program. ...
    (comp.emulators.cbm)
  • Re: Standard vs. Student/Teacher
    ... Upgrade edition is not free, and it's actually more expensive than a regular ... the Mac version should come out later that year, ... for S&T and Standard vs. $399 + $239for Standard and Upgrade). ... *not* lose your installs. ...
    (microsoft.public.mac.office.word)
  • Re: OK to install SBS 2003 R2 Premium over SBS 2003 Standard?
    ... "Premium technologies". ... the switch from SBS Standard to Premium during the upgrade is supported. ...
    (microsoft.public.windows.server.sbs)
  • Re: Need Advise - Upgrading Windows 2000 Server to 2003.
    ... To upgrade/migrate IIS with load balancing better choose IIS newsgroup: ... I would try an inplace upgrade in a test lab first. ... mixture of Web Servers and 3rd party application servers. ... migrating the settings over. ...
    (microsoft.public.windows.server.setup)
  • Re: Standard vs. Student/Teacher
    ... If I purchase the full price Standard Edition of Office 2004, ... the S&T version may not be eligible for an upgrade to Office 12, but yes, ... There are a couple of differences between the Standard and the S&T editions: ... *not* lose your installs. ...
    (microsoft.public.mac.office.word)