Still looking for feedback on whether you examined the .mst file with the viewer to see whether it contains the correct .prf file and the right registry values to deploy it.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
On Mar 21, 12:32 pm, "Sue Mosher [MVP-Outlook]"
The other option I have is to setup outlook to apply a PRF file on
first run by making a reg setting change at login (Which I have tested
fine) but this does nothing with removing old versions and giving the
user the latest version of Outlook 2003 which is what we want to
acheive.
If you deploy a profile using the .mst file, it uses exactly the same mechanism. You can check this for yourself using the MST viewer. Maybe something is wrong with the .mst file.
I ran the PRF file manually and this works no problem. Some users will
already have a profile which needs to be kept. Even though they don't
use exchange yet they use outlook for contacts and tasks etc and just
have a local PST file.
So the PRF is set up to always modify the default profile?
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
I ran the PRF file manually and this works no problem. Some users will
already have a profile which needs to be kept. Even though they don't
use exchange yet they use outlook for contacts and tasks etc and just
have a local PST file.
Here is what I have:
A local installation of Office 2003 which I beleive is SP1 buy maybe
RTM, this was installed from an admin share (Installation point)
I have created another admin share in a seperate directory and patched
the RTM version of Office with SP2.
When I run setup using the following syntax
SETUP.EXE TRANSFORMS=X:\MICROSOFT\OFFICE2003PROSP2\OUTLOOk.MST /qb-
The local install of office is updated to SP2, but the profile is not
applied to Outlook. I have also configured the MST file to remove
older versions of Outlook.
I must be doing something wrong but for the life of me I can't figure
it out!
Thanks for your help
AJ- Hide quoted text -
- Show quoted text -
On doing some more investigation into this, I can see that the MST
file is working as I changed the org name for the office install and
when I looked in Outlook the org name matched. It looks as though it's
just the profile which is not getting updated but when I run the PRF
manually all works. I have done a few more tests and some work and
some dont and I am using the same machine, it is so not consistent and
very frustrating!!!!!
Im clean out of ideas..................
AJ- Hide quoted text -
- Show quoted text -
Ok I will gather this information, but FYI the deployment works if
Office is not installed on the local machine. Outlook is deployed
together with the correct profile no problems. The problem arises when
I have a machine that already has office installed (2003). The office
applications get upgraded to SP2 but Outlook does not get the profile.
This is using the same command line.
THanks
AJ- Hide quoted text -
Ok on looking at the MST file using the MST Viewer I see the following
that are probably most relevant
CREATED - OCW_Strings Name (s64*) Value (s128)
+ CustomizeOutlook 3
+ Msi_ProductVersion 11.0.7969.0
+ Msi_UpgradeCode {01110000-6000-11D3-8CFE-0050048383C9}
+ NewPrfName ADP Test Exchange
+ OCW_Added_Outlook_File_1 [INSTALLLOCATION]\custom11.prf
+ OutExchangeConfigure 1
+ OutExchangeConfigureMailbox 1
+ OutExchangeExchangeAccount Microsoft Exchange Server
+ OutExchangeExchangeServerName pp-dsi-exvs1
+ OutExchangeExchangeUserName %UserName%
+ OutExchangeFullItemsOnly 1
+ OutExchangeHeadersOnlySlow 1
+ OutExchangeLocalCopy 1
+ OutExchangeOABPath %USERPROFILE%\local settings\application data
\microsoft\outlook\
+ OutExchangeOSTPath %USERPROFILE%\local settings\application data
\microsoft\outlook\outlook.ost
+ OutExchangeSlowHttpFirst
And
DATA CHANGE - Registry Registry Root Key Name Value Component_
+ OCW_Added_Content_OutFirstRunNoDash 1 Software\Microsoft\Office
\11.0\Outlook\Setup FirstRun #x0000000000000000 OCW_Added_Content_UP
+ OCW_Added_Content_OutFirstRunWithDash 1 Software\Microsoft\Office
\11.0\Outlook\Setup First-Run #x0000000000000000 OCW_Added_Content_UP
+ OCW_Added_Content_OutImportPrf 1 Software\Microsoft\Office
\11.0\Outlook\Setup ImportPRF [INSTALLLOCATION]custom11.prf
OCW_Added_Content_UP
+ OCW_Added_Content_UP 1 Software\Microsoft\OfficeCustomizeWizard
\11.0\RegKeyPaths\{91110409-6000-11D3-8CFE-0150048383C9}
OCWAddedContentWritten_PerUser_Permanent #1 OCW_Added_Content_UP
+ OCW_Added_Content_UP_GUID2NAME 1 Software\Microsoft
\OfficeCustomizeWizard\11.0\RegKeyPaths
\{91110409-6000-11D3-8CFE-0150048383C9} Microsoft Office Professional
Edition 2003 v11.0.7969.0 OCW_Added_Content_UP
+ OCW_Added_Content_UP_NAME2GUID 1 Software\Microsoft
\OfficeCustomizeWizard\11.0\RegKeyPaths Microsoft Office Professional
Edition 2003 v11.0.7969.0 {91110409-6000-11D3-8CFE-0150048383C9}
OCW_Added_Content_UP
+ OCW_Outlook_Added_Content 2 Software\Microsoft
\OfficeCustomizeWizard\11.0\RegKeyPaths
\{91110409-6000-11D3-8CFE-0150048383C9} OCWAddedOutlookContentWritten
#1 OCW_Outlook_Added_Content
DATA CHANGE - RegLocator Signature_ Root Key Name Type
+ OCW_AC_RegLocator_UP 1 Software\Microsoft\OfficeCustomizeWizard
\11.0\RegKeyPaths\{91110409-6000-11D3-8CFE-0150048383C9}
OCWAddedContentWritten_PerUser_Permanent 2
DATA CHANGE - ReserveCost ReserveKey Component_ ReserveFolder
ReserveLocal ReserveSource
+ OCW_Added_Outlook_File_1 OCW_Outlook_Added_Content
[INSTALLLOCATION]\custom11.prf 6788 0
Im not sure where it is getting custom11.prf from????? Hmm OK I just
searched for this file and I can see this PRF on the local machine.
Thanks
AJ- Hide quoted text -
- Show quoted text -
