We’ve had some questions about how to deploy a custom dictionary in an organization. To deploy a custom dictionary, administrators can use the following approach:
- Create a Visual Basic script to copy the custom dictionary file to the local computer.
- Update registry settings to use the custom dictionary.
- Execute the Visual Basic script as part of a logon script.
The following section lists the registry keys to update to use the new custom dictionary, NewCustom.dic, for example. To do this, use Registry Editor, regedit.exe. For information about using regedit, see Configure the Registry.
This approach sets the Custom dictionary file as the default, and configures it as enabled. It specifies the NewCustom.dic file as the second dictionary, and sets it to enabled. It also removes the culture tag to apply to all languages.
The following registry keys and values must be added or updated:
- “HKEY_CURRENT_USERSoftwareMicrosoftShared ToolsProofing Tools1.0Custom Dictionaries” /v “1” /t REG_SZ /d CUSTOM.DIC /f
- “HKEY_CURRENT_USERSoftwareMicrosoftShared ToolsProofing Tools1.0Custom Dictionaries” /v “1_state” /t REG_BINARY /d 01000000 /f
- “HKEY_CURRENT_USERSoftwareMicrosoftShared ToolsProofing Tools1.0Custom Dictionaries” /v “2” /t REG_SZ /d NewCustom.dic /f
- “HKEY_CURRENT_USERSoftwareMicrosoftShared ToolsProofing Tools1.0Custom Dictionaries” /v “2_state” /t REG_BINARY /d 01000000 /f
The following registry key must be deleted, if it exists:
- “HKEY_CURRENT_USERSoftwareMicrosoftShared ToolsProofing Tools1.0Custom Dictionaries” /v “2_culturetag” /f
To deploy the logon script to users, administrators can use Group Policy to assign a User Logon Script. For information about using Group Policy Management Console and User Logon Scripts, see the following resources:
- Group Policy Management Console
- Using Startup, Shutdown, Logon, and Logoff Scripts
- Set Up Scripts on the Domain Controller
- Assign User Logon Scripts
As an alternative, administrators who have deployed Office 2010 can use the Office Customization Tool (OCT) to add the custom dictionary file and add registry values. The OCT can be used for maintaining an Office 2010 installation. Note that there are two versions of the OCT in Office 2010, one for 32-bit Office 2010 and one for 64-bit Office 2010. The OCT is available only with volume licensed versions of Office 2010 and the 2007 Office system. To determine whether an Office 2010 installation is a volume licensed version, check the Office 2010 installation disk to see whether it contains a folder named Admin. If the Admin folder exists, the disk is a volume license edition.
To use this method, administrators perform the following tasks:
- Run the OCT and use the Add files option in the Additional content section to add the custom dictionary file.
- Use the Add registry entries option, and click Add to add the registry keys.
- Use the Remove registry entries option, and click Remove to remove a registry key.
- When the changes are complete, save the Setup customization .msp file.
- Deploy the customization .msp.
For more information about using the OCT, see the following resources: