Outlook 2003 ADM AD template

[Don]

Why does the Outlook 2003 ADM AD template not have descriptions?
Why does the Outlook 2003 ADM AD template allow you to make the default
storeage location of Personal Folders on a mapped network drive?
The descriptions could have been well used to detail the useage guidlines
(dos and don'ts) of each configurable parameter in the ADM.
The ADM would do well to seperate the PST and OST storage location options.

 

[Sue Mosher [MVP-Outlook]]

Why does the Outlook 2003 ADM AD template allow you to make the default

storeage location of Personal Folders on a mapped network drive?

Because the .adm format doesn't support rules like that.

The descriptions could have been well used to detail the useage guidlines
(dos and don'ts) of each configurable parameter in the ADM.

That's a good suggestion, which you can make to Microsoft by posting through the web interface for these newsgroups.

The ADM would do well to seperate the PST and OST storage location options.

That has already been done with a post-SP1 hotfix -- "You cannot specify a separate folder to store the .ost file when you use the ForcePSTPath value in Outlook 2003" (MSKB article -- 896591):

Key: HKCU\Software\Microsoft\Office\11.0\Outlook
Value name: ForceOSTPath
Value type: REG_EXPAND_SZ (expandable string value)
Value data: Path to default location where you want Outlook to create ..ost files. Environment variables such as %userprofile% are supported.

If you do not enable this setting, Outlook automatically creates .ost files in the %userprofile%\Local Settings\Application Data\Microsoft\Outlook\ folder or in the path set for the ForcePSTPath registry value.