AutoArchive dilemma not good for Corporate Deployments

  • Thread starter Thread starter Glenn
  • Start date Start date
G

Glenn

Hello,

The dilemma can't easily convert Office 97-2002
archive.pst to Office 2003 archive.pst. We have kept
mailbox size under 400 MB and many of our users are from
the Outlook 97 daze.

Breaking known corporate behavior in a major corporation
escalates support costs and confusion.

Why isn't there an automated deployment tool to convert
old pst files to unicode?

Glenn
 
Glenn said:
Hello,

The dilemma can't easily convert Office 97-2002
archive.pst to Office 2003 archive.pst. We have kept
mailbox size under 400 MB and many of our users are from
the Outlook 97 daze.

Breaking known corporate behavior in a major corporation
escalates support costs and confusion.

Why isn't there an automated deployment tool to convert
old pst files to unicode?

Glenn
Click to expand...

Hmm
Interesting. I thought all things for Outlook has already been done tens times over.
If you really want something custom written I might be able to help.
Also for excellent central Outlook Client management check out
Outlook Profiler
http://goff.nu/products/windows/profiler/index.html
 
You know something I don't? If not then:
Why isn't there a utility to convert the 97-2002
archive.pst to unicode? As it sits now there are several
choices none good.
1.) Rename the old 97-2002 archive.pst and use the new
unicode archieve.pst. This creates confusion with users
and they will have to be trained ($) to open the renamed
old archieve.pst to access the old messages. Even
spending money on training there are uses in big corps
who will forget or not attend the training whereas they
call(Many of our users are dial-in from around the world
($)) the corporate help desk ($) on howto. If your just a
small office it isn't a big deal for a major corporation
it is a quantum task.
2.) Per one google group post the individual opened the
old 97-2002 archive.pst and moved it into the new unicode
archive.pst. If this works Alright for a small office but
when you have 15,000 users a slow ($) process one-by-one.

Glenn
 
You left out #3: Continue using the existing archive.pst file. This meets
your goal of not breaking known behavior.

Neither #1 nor #2 is that hard to explain to users. How many of them are
heavy archive users anyway?
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
This must be an Exchange server setting then?
-----Original Message-----
Yes, there is. Outlook 2003 can use both the Unicode- compatible PST files
and legacy PST files.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers






.
Click to expand...
 
Yes, there is. Outlook 2003 can use both the Unicode-compatible PST files
and legacy PST files.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
I see this is possibly via CIW. OK so a pst can be both
Legacy and Unicode. But why am I having a configuration
issue with AutoArchive if the pst setting is left at
default?
 
A PST cannot be both legacy and Unicode. It's either one or the other. Both
work in OL2003. Only legacy (otherwise known as ANSI) works in earlier
versions.

What is your configuration issue?
 
Saw your article on pst(s), it's very good.

We have been using Outlook since Outlook 97 so the users
have legacy pst(s). We are going to migrate the users
from Office 9 and 10. Have the Office 2003 Resource Kit
and have been testing configurations made up from CIW and
a Default OPS created by Profile Wizard with just Outlook
chosen that is imported into the MST.

In testing when I try to manually activate AutoArchive
and setup the location to the legacy pst get !
message. "Microsoft Office Outlook is running in Unicode
mode against Microsoft Exchange server and cannot archive
items to non-Unicode Outlook 97-2002 Personal Folders
archive file. Please select or create a new Personal
Folders file that supports Unicode."

Since I am a Desktop Engineer and don't setup the Exhange
server is this a configuration issue with the Server or
can this be corrected in CIW "?" Ultimately, if in the
case of new users we would like to have them make the
unicode pst so I would like to keep the CIW default
settings in CIW if possible?

What we would ultimately like to do is have AutoArchiving
preconfigured and greyed out. In otherwords we have a
predetermined spot...a user's home drive that has an
existing Exchange folder with their existing pst. Still
have not been successful with this since the field Move
old items to: is defaulted (by MS) to users local
profile\local source\... on machine

Thank You,

Glenn
 
Interesting scenario. I may have missed a reference to Exchange 2003 in the
message that started this thread, so it's good to keep the discussion going.

One approach might be to run a one-time script to rename the old archive
..pst file. Outlook should automatically create a new one. You can then
distribute instructions to the users as to how to access their old archive,
either to open it directly or to import it into the new .pst file.

I've also just learned that you can set the default AutoArchive file as part
of a .prf file. Here's the information from Microsoft:

You must change the AutoArchive through profile generation by using the
Outlook.prf file with the Modprof.exe file or the Newprof.exe file. The
following is a sample of the changes that you must make in the Outlook.prf
file:

[Service1]
;----Outlook AutoArchive------
;True=On and False=Off
DoAutoArchive=True
;specify the full path to the archive pst file
AutoArchiveFileName = "M:\temp\archive.pst"


Along those same lines, you could potentially use the .prf file to put the
users' old archive file in the profile, so they don't have to go looking for
it.
 
Sue,

After talking with my Project Manager I find they are now
interested in converting the legacy pst to unicode. Doing
some hunting I see there is a VBA method AddStore which
connects to an existing pst and creates a new pst. I
don't know if it will do the conversion it would be nice.
What do you know on this?

Thanks!

Glenn
-----Original Message-----
Interesting scenario. I may have missed a reference to Exchange 2003 in the
message that started this thread, so it's good to keep the discussion going.

One approach might be to run a one-time script to rename the old archive
..pst file. Outlook should automatically create a new one. You can then
distribute instructions to the users as to how to access their old archive,
either to open it directly or to import it into the new .pst file.

I've also just learned that you can set the default AutoArchive file as part
of a .prf file. Here's the information from Microsoft:

You must change the AutoArchive through profile generation by using the
Outlook.prf file with the Modprof.exe file or the Newprof.exe file. The
following is a sample of the changes that you must make in the Outlook.prf
file:

[Service1]
;----Outlook AutoArchive------
;True=On and False=Off
DoAutoArchive=True
;specify the full path to the archive pst file
AutoArchiveFileName = "M:\temp\archive.pst"


Along those same lines, you could potentially use the .prf file to put the
users' old archive file in the profile, so they don't have to go looking for
it.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers


Saw your article on pst(s), it's very good.

We have been using Outlook since Outlook 97 so the users
have legacy pst(s). We are going to migrate the users
from Office 9 and 10. Have the Office 2003 Resource Kit
and have been testing configurations made up from CIW and
a Default OPS created by Profile Wizard with just Outlook
chosen that is imported into the MST.

In testing when I try to manually activate AutoArchive
and setup the location to the legacy pst get !
message. "Microsoft Office Outlook is running in Unicode
mode against Microsoft Exchange server and cannot archive
items to non-Unicode Outlook 97-2002 Personal Folders
archive file. Please select or create a new Personal
Folders file that supports Unicode."

Since I am a Desktop Engineer and don't setup the Exhange
server is this a configuration issue with the Server or
can this be corrected in CIW "?" Ultimately, if in the
case of new users we would like to have them make the
unicode pst so I would like to keep the CIW default
settings in CIW if possible?

What we would ultimately like to do is have AutoArchiving
preconfigured and greyed out. In otherwords we have a
predetermined spot...a user's home drive that has an
existing Exchange folder with their existing pst. Still
have not been successful with this since the field Move
old items to: is defaulted (by MS) to users local
profile\local source\... on machine

Thank You,

Glenn one
or the other. Both
Click to expand...


.
Click to expand...
 
AddStore creates a new .pst file or exposes an existing .pst file to the
current Outlook session. It does not convert from one type to another. To
convert, you'd have to create the new store, then copy or move all the
folders and items from the old store.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Glenn said:
Sue,

After talking with my Project Manager I find they are now
interested in converting the legacy pst to unicode. Doing
some hunting I see there is a VBA method AddStore which
connects to an existing pst and creates a new pst. I
don't know if it will do the conversion it would be nice.
What do you know on this?

Thanks!

Glenn
-----Original Message-----
Interesting scenario. I may have missed a reference to Exchange 2003 in the
message that started this thread, so it's good to keep the discussion going.

One approach might be to run a one-time script to rename the old archive
..pst file. Outlook should automatically create a new one. You can then
distribute instructions to the users as to how to access their old archive,
either to open it directly or to import it into the new .pst file.

I've also just learned that you can set the default AutoArchive file as part
of a .prf file. Here's the information from Microsoft:

You must change the AutoArchive through profile generation by using the
Outlook.prf file with the Modprof.exe file or the Newprof.exe file. The
following is a sample of the changes that you must make in the Outlook.prf
file:

[Service1]
;----Outlook AutoArchive------
;True=On and False=Off
DoAutoArchive=True
;specify the full path to the archive pst file
AutoArchiveFileName = "M:\temp\archive.pst"


Along those same lines, you could potentially use the .prf file to put the
users' old archive file in the profile, so they don't have to go looking for
it.
Click to expand...
Click to expand...
 
If they elect to go this route. Will have to configure
the Office Deployment to allow any type of PST. We would
have to open Outlook in users profile and per KB article:
830336. drag and drop for each client to a new Unicode
PST. Yuck! Microsoft doesn't have utility for ANSI to
Unicode PST conversion. It would be nice if Microsoft
would update the resource Kit to include such a utility
and have it be automated as part of the upgrade for
Corporations.

Thanks!

Glenn
-----Original Message-----
AddStore creates a new .pst file or exposes an existing .pst file to the
current Outlook session. It does not convert from one type to another. To
convert, you'd have to create the new store, then copy or move all the
folders and items from the old store.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Sue,

After talking with my Project Manager I find they are now
interested in converting the legacy pst to unicode. Doing
some hunting I see there is a VBA method AddStore which
connects to an existing pst and creates a new pst. I
don't know if it will do the conversion it would be nice.
What do you know on this?

Thanks!

Glenn
-----Original Message-----
Interesting scenario. I may have missed a reference to Exchange 2003 in the
message that started this thread, so it's good to keep the discussion going.

One approach might be to run a one-time script to
Click to expand...
rename
the old archive
..pst file. Outlook should automatically create a new one. You can then
distribute instructions to the users as to how to
Click to expand...
access
their old archive,
either to open it directly or to import it into the new .pst file.

I've also just learned that you can set the default AutoArchive file as part
of a .prf file. Here's the information from Microsoft:

You must change the AutoArchive through profile generation by using the
Outlook.prf file with the Modprof.exe file or the Newprof.exe file. The
following is a sample of the changes that you must
Click to expand...
make
in the Outlook.prf
file:

[Service1]
;----Outlook AutoArchive------
;True=On and False=Off
DoAutoArchive=True
;specify the full path to the archive pst file
AutoArchiveFileName = "M:\temp\archive.pst"


Along those same lines, you could potentially use the .prf file to put the
users' old archive file in the profile, so they don't have to go looking for
it.
Click to expand...
Click to expand...


.
Click to expand...
 
Sue,

According to Microsoft you can edit the prf file with
Notepad. You recommended using the utilities ModProf.exe
and NewProf.exe. I'm wondering if I should do what the
site says. Your the expert what do you think?

Thanks!

Glenn
-----Original Message-----
Interesting scenario. I may have missed a reference to Exchange 2003 in the
message that started this thread, so it's good to keep the discussion going.

One approach might be to run a one-time script to rename the old archive
..pst file. Outlook should automatically create a new one. You can then
distribute instructions to the users as to how to access their old archive,
either to open it directly or to import it into the new .pst file.

I've also just learned that you can set the default AutoArchive file as part
of a .prf file. Here's the information from Microsoft:

You must change the AutoArchive through profile generation by using the
Outlook.prf file with the Modprof.exe file or the Newprof.exe file. The
following is a sample of the changes that you must make in the Outlook.prf
file:

[Service1]
;----Outlook AutoArchive------
;True=On and False=Off
DoAutoArchive=True
;specify the full path to the archive pst file
AutoArchiveFileName = "M:\temp\archive.pst"


Along those same lines, you could potentially use the .prf file to put the
users' old archive file in the profile, so they don't have to go looking for
it.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers


Saw your article on pst(s), it's very good.

We have been using Outlook since Outlook 97 so the users
have legacy pst(s). We are going to migrate the users
from Office 9 and 10. Have the Office 2003 Resource Kit
and have been testing configurations made up from CIW and
a Default OPS created by Profile Wizard with just Outlook
chosen that is imported into the MST.

In testing when I try to manually activate AutoArchive
and setup the location to the legacy pst get !
message. "Microsoft Office Outlook is running in Unicode
mode against Microsoft Exchange server and cannot archive
items to non-Unicode Outlook 97-2002 Personal Folders
archive file. Please select or create a new Personal
Folders file that supports Unicode."

Since I am a Desktop Engineer and don't setup the Exhange
server is this a configuration issue with the Server or
can this be corrected in CIW "?" Ultimately, if in the
case of new users we would like to have them make the
unicode pst so I would like to keep the CIW default
settings in CIW if possible?

What we would ultimately like to do is have AutoArchiving
preconfigured and greyed out. In otherwords we have a
predetermined spot...a user's home drive that has an
existing Exchange folder with their existing pst. Still
have not been successful with this since the field Move
old items to: is defaulted (by MS) to users local
profile\local source\... on machine

Thank You,

Glenn one
or the other. Both
Click to expand...


.
Click to expand...
 
A .prf file is a text file so you certainly can edit it in Notepad if you
know what you're doing.

Modprof and Newprof are tools used to apply .prf file settings to Outlook
2000 and earlier versions. They are not needed in later versions.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers




glenn said:
Sue,

According to Microsoft you can edit the prf file with
Notepad. You recommended using the utilities ModProf.exe
and NewProf.exe. I'm wondering if I should do what the
site says. Your the expert what do you think?

Thanks!

Glenn
-----Original Message-----
Interesting scenario. I may have missed a reference to Exchange 2003 in the
message that started this thread, so it's good to keep the discussion going.

One approach might be to run a one-time script to rename the old archive
..pst file. Outlook should automatically create a new one. You can then
distribute instructions to the users as to how to access their old archive,
either to open it directly or to import it into the new .pst file.

I've also just learned that you can set the default AutoArchive file as part
of a .prf file. Here's the information from Microsoft:

You must change the AutoArchive through profile generation by using the
Outlook.prf file with the Modprof.exe file or the Newprof.exe file. The
following is a sample of the changes that you must make in the Outlook.prf
file:

[Service1]
;----Outlook AutoArchive------
;True=On and False=Off
DoAutoArchive=True
;specify the full path to the archive pst file
AutoArchiveFileName = "M:\temp\archive.pst"


Along those same lines, you could potentially use the .prf file to put the
users' old archive file in the profile, so they don't have to go looking for
it.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers


Saw your article on pst(s), it's very good.

We have been using Outlook since Outlook 97 so the users
have legacy pst(s). We are going to migrate the users
from Office 9 and 10. Have the Office 2003 Resource Kit
and have been testing configurations made up from CIW and
a Default OPS created by Profile Wizard with just Outlook
chosen that is imported into the MST.

In testing when I try to manually activate AutoArchive
and setup the location to the legacy pst get !
message. "Microsoft Office Outlook is running in Unicode
mode against Microsoft Exchange server and cannot archive
items to non-Unicode Outlook 97-2002 Personal Folders
archive file. Please select or create a new Personal
Folders file that supports Unicode."

Since I am a Desktop Engineer and don't setup the Exhange
server is this a configuration issue with the Server or
can this be corrected in CIW "?" Ultimately, if in the
case of new users we would like to have them make the
unicode pst so I would like to keep the CIW default
settings in CIW if possible?

What we would ultimately like to do is have AutoArchiving
preconfigured and greyed out. In otherwords we have a
predetermined spot...a user's home drive that has an
existing Exchange folder with their existing pst. Still
have not been successful with this since the field Move
old items to: is defaulted (by MS) to users local
profile\local source\... on machine

Thank You,

Glenn
-----Original Message-----
A PST cannot be both legacy and Unicode. It's either one
or the other. Both
work in OL2003. Only legacy (otherwise known as ANSI)
works in earlier
versions.

What is your configuration issue?
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



I see this is possibly via CIW. OK so a pst can be both
Legacy and Unicode. But why am I having a configuration
issue with AutoArchive if the pst setting is left at
default?


.
Click to expand...


.
Click to expand...
Click to expand...
 
Hello Sue,

Can't get the default folder setting for AutoArchive to
work enclosed is a modified prf file. The prf file was
orginal generated by CIW:
;Automatically generated PRF file from the Microsoft
Office Customization and Installation Wizard

;
**********************************************************
****
; Section 1 - Profile Defaults
;
**********************************************************
****

[General]
Custom=1
DefaultProfile=Yes
OverwriteProfile=Append
ModifyDefaultProfileIfPresent=TRUE

;
**********************************************************
****
; Section 2 - Services in Profile
;
**********************************************************
****

[Service List]
ServiceX=Microsoft Outlook Client
ServiceEGS=Exchange Global Section
Service1=Microsoft Exchange Server
ServiceEGS=Exchange Global Section
ServiceAM=Archived Messages
ServiceAAM=Auto Archived Messages

;*********************************************************
******
; Section 3 - List of internet accounts
;*********************************************************
******

[Internet Account List]

;*********************************************************
******
; Section 4 - Default values for each service.
;*********************************************************
******

[ServiceX]
CachedExchangeMode=0x00000002
CachedExchangeSlowDetect=TRUE

[ServiceEGS]
CachedExchangeConfigFlags=0x00000100
MailboxName=%UserName%
HomeServer=cclmailbox1

[Service1]
OverwriteExistingService=No
UniqueService=Yes
MailboxName=%UserName%
HomeServer=cclmailbox1
AccountName=Microsoft Exchange Server

[ServiceAM]
PathToPersonalFolders=f:\Exchange\archive.pst
RememberPassword=TRUE
EncryptionType=0x40000000
Password=
PersonalFolderName="Archived Messages"

[ServiceAAM]
;----Outlook AutoArchive---
;True=on ann False=off
DoAutoArchive=True
;Specify the full path to the archive pst file
AutoArchiveFileName=F:\Exchange\archive.pst

;*********************************************************
******
; Section 5 - Values for each internet account.
;*********************************************************
******

;*********************************************************
******
; Section 6 - Mapping for profile properties
;*********************************************************
******

[Microsoft Exchange Server]
ServiceName=MSEMS
MDBGUID=5494A1C0297F101BA58708002B2A2517
MailboxName=PT_STRING8,0x6607
HomeServer=PT_STRING8,0x6608
OfflineAddressBookPath=PT_STRING8,0x660E
OfflineFolderPath=PT_STRING8,0x6610

[Exchange Global Section]
SectionGUID=13dbb0c8aa05101a9bb000aa002fc45a
MailboxName=PT_STRING8,0x6607
HomeServer=PT_STRING8,0x6608
RPCoverHTTPflags=PT_LONG,0x6623
RPCProxyServer=PT_UNICODE,0x6622
RPCProxyPrincipalName=PT_UNICODE,0x6625
RPCProxyAuthScheme=PT_LONG,0x6627
CachedExchangeConfigFlags=PT_LONG,0x6629

[Microsoft Mail]
ServiceName=MSFS
ServerPath=PT_STRING8,0x6600
Mailbox=PT_STRING8,0x6601
Password=PT_STRING8,0x67f0
RememberPassword=PT_BOOLEAN,0x6606
ConnectionType=PT_LONG,0x6603
UseSessionLog=PT_BOOLEAN,0x6604
SessionLogPath=PT_STRING8,0x6605
EnableUpload=PT_BOOLEAN,0x6620
EnableDownload=PT_BOOLEAN,0x6621
UploadMask=PT_LONG,0x6622
NetBiosNotification=PT_BOOLEAN,0x6623
NewMailPollInterval=PT_STRING8,0x6624
DisplayGalOnly=PT_BOOLEAN,0x6625
UseHeadersOnLAN=PT_BOOLEAN,0x6630
UseLocalAdressBookOnLAN=PT_BOOLEAN,0x6631
UseExternalToHelpDeliverOnLAN=PT_BOOLEAN,0x6632
UseHeadersOnRAS=PT_BOOLEAN,0x6640
UseLocalAdressBookOnRAS=PT_BOOLEAN,0x6641
UseExternalToHelpDeliverOnRAS=PT_BOOLEAN,0x6639
ConnectOnStartup=PT_BOOLEAN,0x6642
DisconnectAfterRetrieveHeaders=PT_BOOLEAN,0x6643
DisconnectAfterRetrieveMail=PT_BOOLEAN,0x6644
DisconnectOnExit=PT_BOOLEAN,0x6645
DefaultDialupConnectionName=PT_STRING8,0x6646
DialupRetryCount=PT_STRING8,0x6648
DialupRetryDelay=PT_STRING8,0x6649

[Personal Folders]
ServiceName=MSPST MS
Name=PT_STRING8,0x3001
PathToPersonalFolders=PT_STRING8,0x6700
RememberPassword=PT_BOOLEAN,0x6701
EncryptionType=PT_LONG,0x6702
Password=PT_STRING8,0x6703

[Unicode Personal Folders]
ServiceName=MSUPST MS
Name=PT_UNICODE,0x3001
PathToPersonalFolders=PT_STRING8,0x6700
RememberPassword=PT_BOOLEAN,0x6701
EncryptionType=PT_LONG,0x6702
Password=PT_STRING8,0x6703

[Outlook Address Book]
ServiceName=CONTAB

[LDAP Directory]
ServiceName=EMABLT
ServerName=PT_STRING8,0x6600
UserName=PT_STRING8,0x6602
UseSSL=PT_BOOLEAN,0x6613
UseSPA=PT_BOOLEAN,0x6615
DisableVLV=PT_LONG,0x6616
DisplayName=PT_STRING8,0x3001
ConnectionPort=PT_STRING8,0x6601
SearchTimeout=PT_STRING8,0x6607
MaxEntriesReturned=PT_STRING8,0x6608
SearchBase=PT_STRING8,0x6603

[Microsoft Outlook Client]
SectionGUID=0a0d020000000000c000000000000046
FormDirectoryPage=PT_STRING8,0x0270
WebServicesLocation=PT_STRING8,0x0271
ComposeWithWebServices=PT_BOOLEAN,0x0272
PromptWhenUsingWebServices=PT_BOOLEAN,0x0273
OpenWithWebServices=PT_BOOLEAN,0x0274
CachedExchangeMode=PT_LONG,0x041f
CachedExchangeSlowDetect=PT_BOOLEAN,0x0420

[Personal Address Book]
ServiceName=MSPST AB
NameOfPAB=PT_STRING8,0x001e3001
Path=PT_STRING8,0x001e6600
ShowNamesBy=PT_LONG,0x00036601

;
**********************************************************
**************
; Section 7 - Mapping for internet account properties.
DO NOT MODIFY.
;
**********************************************************
**************

[I_Mail]
AccountType=POP3
;--- POP3 Account Settings ---
AccountName=PT_UNICODE,0x0002
DisplayName=PT_UNICODE,0x000B
EmailAddress=PT_UNICODE,0x000C
;--- POP3 Account Settings ---
POP3Server=PT_UNICODE,0x0100
POP3UserName=PT_UNICODE,0x0101
POP3UseSPA=PT_LONG,0x0108
Organization=PT_UNICODE,0x0107
ReplyEmailAddress=PT_UNICODE,0x0103
POP3Port=PT_LONG,0x0104
POP3UseSSL=PT_LONG,0x0105
; --- SMTP Account Settings ---
SMTPServer=PT_UNICODE,0x0200
SMTPUseAuth=PT_LONG,0x0203
SMTPAuthMethod=PT_LONG,0x0208
SMTPUserName=PT_UNICODE,0x0204
SMTPUseSPA=PT_LONG,0x0207
ConnectionType=PT_LONG,0x000F
ConnectionOID=PT_UNICODE,0x0010
SMTPPort=PT_LONG,0x0201
SMTPUseSSL=PT_LONG,0x0202
ServerTimeOut=PT_LONG,0x0209
LeaveOnServer=PT_LONG,0x1000

[IMAP_I_Mail]
AccountType=IMAP
;--- IMAP Account Settings ---
AccountName=PT_UNICODE,0x0002
DisplayName=PT_UNICODE,0x000B
EmailAddress=PT_UNICODE,0x000C
;--- IMAP Account Settings ---
IMAPServer=PT_UNICODE,0x0100
IMAPUserName=PT_UNICODE,0x0101
IMAPUseSPA=PT_LONG,0x0108
Organization=PT_UNICODE,0x0107
ReplyEmailAddress=PT_UNICODE,0x0103
IMAPPort=PT_LONG,0x0104
IMAPUseSSL=PT_LONG,0x0105
; --- SMTP Account Settings ---
SMTPServer=PT_UNICODE,0x0200
SMTPUseAuth=PT_LONG,0x0203
SMTPAuthMethod=PT_LONG,0x0208
SMTPUserName=PT_UNICODE,0x0204
SMTPUseSPA=PT_LONG,0x0207
ConnectionType=PT_LONG,0x000F
ConnectionOID=PT_UNICODE,0x0010
SMTPPort=PT_LONG,0x0201
SMTPUseSSL=PT_LONG,0x0202
ServerTimeOut=PT_LONG,0x0209
CheckNewImap=PT_LONG,0x1100
RootFolder=PT_UNICODE,0x1101

[INET_HTTP]
AccountType=HOTMAIL
Account=PT_UNICODE,0x0002
HttpServer=PT_UNICODE,0x0100
UserName=PT_UNICODE,0x0101
Organization=PT_UNICODE,0x0107
UseSPA=PT_LONG,0x0108
TimeOut=PT_LONG,0x0209
Reply=PT_UNICODE,0x0103
EmailAddress=PT_UNICODE,0x000C
FullName=PT_UNICODE,0x000B
Connection Type=PT_LONG,0x000F
ConnectOID=PT_UNICODE,0x0010

Any ideas?

Thanks!

Glenn
-----Original Message-----
AddStore creates a new .pst file or exposes an existing .pst file to the
current Outlook session. It does not convert from one type to another. To
convert, you'd have to create the new store, then copy or move all the
folders and items from the old store.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Sue,

After talking with my Project Manager I find they are now
interested in converting the legacy pst to unicode. Doing
some hunting I see there is a VBA method AddStore which
connects to an existing pst and creates a new pst. I
don't know if it will do the conversion it would be nice.
What do you know on this?

Thanks!

Glenn
-----Original Message-----
Interesting scenario. I may have missed a reference to Exchange 2003 in the
message that started this thread, so it's good to keep the discussion going.

One approach might be to run a one-time script to
Click to expand...
rename
the old archive
..pst file. Outlook should automatically create a new one. You can then
distribute instructions to the users as to how to
Click to expand...
access
their old archive,
either to open it directly or to import it into the new .pst file.

I've also just learned that you can set the default AutoArchive file as part
of a .prf file. Here's the information from Microsoft:

You must change the AutoArchive through profile generation by using the
Outlook.prf file with the Modprof.exe file or the Newprof.exe file. The
following is a sample of the changes that you must
Click to expand...
make
in the Outlook.prf
file:

[Service1]
;----Outlook AutoArchive------
;True=On and False=Off
DoAutoArchive=True
;specify the full path to the archive pst file
AutoArchiveFileName = "M:\temp\archive.pst"


Along those same lines, you could potentially use the .prf file to put the
users' old archive file in the profile, so they don't have to go looking for
it.
Click to expand...
Click to expand...


.
Click to expand...
 
Back
Top