This article was previously published under Q188856
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Names of standard folders in an Exchange mailbox, such as the Inbox, SentItems, Public Folders, and so on, appear in different languages when seenfrom the client program.
Most of the standard folders seen from the client are stored on the server,but they are initially created and named by the first client to access thecorresponding mailbox after it is created. Thus, if the first client youuse to access a new mailbox is a French client, standard folders like theInbox or Sent Items are given French names. After a folder is named, itretains that name unless you explicitly change it from the client. So if aclient in a different language subsequently is used to access the mailbox,these standard folders still retain names in the language used by theclient that created them. This does not affect functionality, but it may besomewhat confusing in appearance.
Additionally, some folders are on the server (for example, all of theserver mailbox folders). Others may be in a local .pst file, and stillothers are "virtual" folders that have no real existence (such as thePublic Folders folder, which simply serves as a tree node for the public-folder tree of the organization). The server folders have names in thelanguage of the client that first created them. Similarly, the .pst foldershave names in the language of the client that created them (which may havebeen a different client from the one that created the server folders).Finally, the virtual folders always have names in the language of theclient that is currently displaying them (because they have no existenceindependent of the client program). The net result is that you may seestandard folders with names in a variety of languages, if clients indifferent languages have been used to access the mailbox or any .psts.
Again, none of this affects functionality, and you may change the names ofthe folders at any time. The problem is only aesthetic.
The names of the folders can be changed at any time, at your discretion, from your client program.
Some clients (for example, Outlook 2000 or older) do not allow the names of certain standard folders (for example, the Inbox) to be changed, but this is a client restriction and not an intrinsic limitation of Exchange. In these cases, you must use a different client (such as the older Exchange client) to modify the folder names.
Outlook 2002 clients can run a command line switch to rename the default folders to the language of the client. To do this, click Start, click Run, and then type Outlook.exe /resetfoldernames. Outlook will start normally and the default folder names will be in the language of the client.
With Outlook 2002 and the CIW or CMW you might want to reset folder names for all users when you deploy Outlook to synchronize users' folder names to the User Interface Language of their version of Outlook. This could be useful, for example, if a corporate-wide process has initialized new mailboxes before new users have started Outlook for the first time. In this case, the mailboxes will end up with default folders in the language of the server. (Note that users can, instead, specify the /resetfoldernames option on the Outlook.exe command line to synchronize the folder names on their computer.)
To reset folder names when deploying Outlook, perform the following steps:
In the Custom Installation Wizard, go to the Add/Remove Registry Entries page.
Click Add to add a registry entry for ResetFolderNames.
On the Add/Modify Registry Entry page, select or type the following:
Under Root:, click to select HKEY_CURRENT_USER.
Under Data type:, click to select Dword.
In the Key: field, type Software/Microsoft/Office/10.0/Outlook/Setup.
In the Value name: field, type ResetFolderNames.
In the Value data: field, type 1.
Any non-zero value will cause Outlook to synchronize the user's folder names to the User Interface Language of Outlook.
Click OK to save the entry.
This behavior is by design.
If you are administering a multilingual user community, you may want tosuggest to users that they use a client in their preferred language toaccess their mailbox for the first time, so that the folders are created inthe language they prefer. Note that only the language of the clientmatters; the settings of the OS and the server are not important.
In the case of mixed wide-character (DBCS/Unicode) clients and otherclients, folders named in a wide-character client may have names that looklike garbage characters when seen from other clients that do not supportwide-character strings. This has no effect on functionality, but it canmislead users into thinking that the system is "broken." Wide-characternames display correctly only with clients and operating systems that canhandle wide-character strings (such as Japanese or Chinese versions of suchproducts).
NOTE: References to the client software in this article are generic andrefer to any program that can create or modify folders. This includes notonly traditional e-mail client programs but also administrative migrationor support utilities that access stores to perform various functionsunrelated to normal sending and receiving of e-mail. These latter programsoften create folders also, and when they do, generally they create thefolders in the language of the program. This is an important considerationwhen using utilities like ExMerge (BackOffice Resource Kit III). Thelanguage version of these utilities should be carefully chosen when theyare used by administrators.