Step 1: Determine the configuration of 8DOT3 name creation
To determine whether 8DOT3 name creation is enabled, run the following command from an elevated command prompt. (Here, we assume that the transaction log files are on drive C.)
fsutil 8dot3name query c:
If the expected output returns something that resemblbes the following, 8DOT3 name creation is enabled:
The volume state is: 0 (8dot3 name creation is enabled).
The registry state is: 2(Per volume setting-the default).
Based on the above two settings, 8dot3 name creation is enabled on C:
Or, the expected output may return something similar to the following:
The volume state is: 0 (8dot3 name creation is enabled).
The registry state is: 0 (Per volume setting - the default).
Based on the above two settings, 8dot3 name creation is enabled on C:
This indicates that drive C has 8DOT3 name creation enabled.
Make sure that you run this command on the volume that contains the transaction logs. You can also use the following if you use mount points:
fsutil 8dot3name query Volume{928842df-5a01-11de-a85c-806e6f6e6963} You will have to substitute the volume GUID to match your volume's GUID. To determine volume and GUID for a specific drive, run the following command:
Depending on your requirements, you can set 8DOT3 name creation to be disabled either for all volumes or on a volume-by-volume basis, as is outlined in step 3. It is most important that you make sure that the volume that contains the transaction logs is disabled for 8DOT3 name creation.
Step 2: Check Group Policy for disable 8DOT3 name creation
Before you try to disable 8DOT3 name creation, you should be aware that this setting can be controlled through Group Policy. Please check to determine whether Group Policy is configured to change the following registry key on the Exchange servers:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation"=dword:00000002
If this setting is controlled through Group Policy, remove this setting from the Group Policy settings for the Exchange servers, and set the NtfsDisable8dot3NameCreation DWORD to a value of
2. This allows for individual volume changes.
Note If a value of
0 is used, you can't change volume configuration.
For more information about the
Fsutil 8dot3name command, go to the following Microsoft TechNet website:
Step 3: Change 8DOT3 name creation
To disable 8DOT3 name creation for all volumes, run the following command:
If you prefer to disable only on individual volumes that contain the transaction logs, run the following command:
fsutil 8DOT3name set c: 1
Note In this command, c is the letter of the drive that contains the transaction logs.
Or, you can run on a specific volume. To do this, run the following command:
fsutil 8dot3name query Volume{928842df-5a01-11de-a85c-806e6f6e6963} After you change the volume's configuration to disable the 8DOT3 name creation, you can verify that the setting is disabled. To do this, run the following command again:
fsutil 8DOT3name query c:
This causes all new files that are created or copied on this volume not to generate a 8DOT3 name for the file name. However, all existing files still contain the 8DOT3 name. Therefore, you have to resolve this.
Step 4: Remove 8DOT3 names for existing transaction logs
Option 1
The preferred option is to run a full backup on the Exchange databases. This causes the transaction logs to be truncated and removes the existing logs that have 8DOT3 names. After all transactions logs that contain 8DOT3 names are truncated, database moves will not fail.
Option 2
If the backup option is not available, you have to manipulate the copy of all transaction logs to make sure that the 8DOT3 names are removed from the files. To do this, follow these steps:
- On a server that contains the passive copies of the database, stop the Microsoft Exchange Replication service.
- In Windows PowerShell, run the following command:
stop-service msexchangerepl
- In Windows Explorer, locate the folder in which you are storing transaction logs.
- Select all the transaction logs of type Enn*.log, and move them to a temporary folder. Make sure that you move only the transaction logs of type Enn*.log. You should move no other file types.
- move all transaction logs back to their original location. In this move process, the 8DOT3 names are removed.
- Repeat this process for all transaction logs for all passive databases.
- Restart the Microsoft Exchange Replication service:
start-service msexchangerepl
- Move the mounted (active) copy of the database to a copy on which the transaction logs are manipulated:
Move-ActiveMailboxDatabase DB2 -ActivateOnServer MBX1 -MountDialOverride:None
- Stop the Microsoft Exchange Replication service, and then again move transaction logs to a temporary location and then back to their original location.
- Start the Microsoft Exchange Replication service. Now, database failure during a move-activemailboxdatabase action should not occur.