microsoft.com Home
http://www.microsoft.com/office/ork |
|
microsoft.com Home
|
|
|
|
||
|
http://www.microsoft.com/office/ork |
|||
You can customize the Profile Wizard to include only the settings you want to track. This is very helpful when you deploy Microsoft Office 2000 in stages with a default user profile.
For example, you can roll out Microsoft Excel, Microsoft Word, and Microsoft PowerPoint with one set of customizations now, and then roll out Microsoft Outlook and Microsoft Internet Explorer later. In this scenario, you can customize the Profile Wizard to track only the settings you need for each stage of your deployment.
To customize the performance of Profile Wizard, you edit the Proflwiz.ini file. Open the file in Notepad or another text editor, and then add or delete references to settings that you want to include or exclude. When you edit the Proflwiz.ini file, you can include or exclude specific applications, registry settings or Application Data folders, template files, and so on.
Each section of the Proflwiz.ini file contains comments documenting the usage and syntax for entries in that section. The default entries are designed to gather a complete set of user configuration data, including both files and Windows registry values, for Office 2000.
Note Some settings in a user profile are shared among applications in Office 2000. When you customize the Proflwiz.ini file for a staged deployment, make sure that you change only nonshared settings or that you set any shared settings to work correctly for all the applications before you save the Office profile settings (OPS) file.
When Office is deployed in stages, it’s easy to overwrite settings in previous user profiles. It’s even easier to overwrite settings when you aren’t the only administrator installing Office applications. The best way to control which settings are affected in a given deployment is to customize the Profile Wizard.
For example, you might invest a few late nights customizing Office 2000 in the lab. You run the Profile Wizard to capture your user profile settings. You don’t configure Outlook because someone else is installing Outlook next month. Then, right on schedule, you deploy Excel, Word, and PowerPoint with a default user profile.
One month later, your colleague deploys Outlook. Like you, he customizes Office 2000 in the lab and uses the Profile Wizard to capture his user profile settings. But he doesn’t customize the wizard to exclude settings for any of the other applications — the customized settings that you deployed and the customized settings that users have been working with for a month.
When your colleague installs Outlook, he accidentally changes your settings for Excel, Word, and PowerPoint. And, if he happens to use the Reset to defaults option, all of your OPS file settings are gone — along with any later user configurations — even if he didn’t explicitly change them in his profile.
You can avoid this bleary-eyed scenario by editing the Proflwiz.ini file to exclude all settings except those needed by the Office applications that you are deploying at any given time.
You can edit the Proflwiz.ini file to exclude selected settings when you run the Profile Wizard. You can also edit the Proflwiz.ini file to include additional files, folders, or registry subkeys and values when you create the OPS file.
Note If an OPS file is set to include an empty folder, that folder is created when the settings are restored.
The following table describes the contents of the Proflwiz.ini file. For a full description of each section, including examples of syntax, see the Proflwiz.ini file itself.
| INI file section | Contents |
|---|---|
| [IncludeFolderTrees] | Folders and subfolders in the Application Data tree. Files in these folders and subfolders are included in the user profile. |
| [IncludeIndividualFolders] | Same as [IncludeFolderTree] but includes only folders, not subfolders. |
| [IncludeIndividualFiles] | Same as [IncludeIndividualFolders] but includes only files. |
| [ExcludeFiles] | Files excluded from the user profile. Allows exclusion of individual files within included folders. |
| [FolderTreesToRemoveToResetToDefaults] | Folder trees to be deleted prior to writing data from OPS file. Every file in the tree is deleted. Use this section with caution. |
| [IndividualFilesToRemoveToResetToDefaults] | Files in the Application Data tree to be deleted prior to writing data from OPS file. |
| [SubstituteEnvironmentVariables] | Environment variables to substitute in registry value data of the type REG_EXPAND_SZ. |
| [IncludeRegistryTrees] | Keys and subkeys in the HKEY_CURRENT_USER root of the Windows registry. Values for these keys and subkeys are included in the user profile. |
| [IncludeIndividualRegistryKeys] | Same as [IncludeRegistryTrees] but includes only specific keys, not subkeys. |
| [ExcludeRegistryTrees] | Keys and subkeys in the HKEY_CURRENT_USER root excluded from the user profile. Values and subkeys under these keys are excluded. |
| [ExcludeIndividualRegistryKeys] | Same as [ExcludeRegistryTrees] but excludes only specific keys, not subkeys. |
| [ExcludeIndividualRegistryValues] | Same as [ExcludeRegistryKeys] but excludes only named values, not subkeys. |
| [RegistryTreesToRemoveToResetToDefaults] | Registry trees in the HKEY_CURRENT_USER trees to be deleted prior to writing custom values. All values and subkeys listed in this section are removed. |
| [IndividualRegistryValuesToRemoveToResetToDefaults] | Registry values in the HKEY_CURRENT_USER subkey values to be deleted prior to writing custom values. All values and subkeys listed in this section are removed. |
Note When you use the Profile Wizard to restore the settings from the OPS file, and use the Reset to defaults before restoring settings option, be aware that any customizations you have made to the ResetToDefaults sections of the Proflwiz.ini file are ignored. The settings in the ResetToDefaults section of the Proflwiz.ini file are added to the OPS file when the OPS is written. If you want to use your customized ResetToDefaults settings, use the Office Custom Installation Wizard to include the OPS file as part of the Office 2000 Setup process.
Top Friday, March 5, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. | ||
|
License
|