Chime Sample Application Creates Debug DLLs
Alerts and Localize Code Samples Not Localized
Volume Management Code Samples Not for Production Use
Change Encoding for Alert E-mail When Changing Server Language
The Chime sample application builds debug versions of its dynamic-link libraries (DLLs). The debug versions will not function on a system that does not contain msvcrtd.dll. This is not an issue on a development system.
The Alerts and Localize code samples located in the \SDK\WebUI folder of the Server Appliance Kit CD are not localized and will not function properly if the server language is set to a language other than English.
The volume management code samples are to be used as a guide for development and testing only and are not intended to be used "as is." Instead, you can use these samples to help you develop your own volume-management add-in. While developing your volume-management add-in, you should follow best practices and make your code as secure as possible. Microsoft recommends that you follow the practices described in the book Writing Secure Code written by Michael Howard and David LeBlanc, available from Microsoft Press.
If your customer's e-mail client does not support UTF-8 encoding, the character encoding used by Alert E-mail can be changed by changing a registry entry.
To set the character encoding, edit the following registry value:
HKLM\Software\Microsoft\ServerAppliance\LocalizationManager\Resources\LanguageID
LanguageID is one of the following values:
To set the character encoding, change the third string in the multistring value to one of the following, as appropriate:
Note that these values might change. For the currently supported values, see the MSDN Library at the Microsoft Web site (http://msdn.microsoft.com/).
The following sections contain information your customers may need in order to use your server appliance successfully. You should pass this information on to your customers as appropriate.
The Shares column of the Manage Shadow Copies Web UI page shows only the number of folders shared using the Microsoft SMB protocol. Folders shared using other protocols are not counted unless they are also shared using the Microsoft SMB protocol.
An administrator should not install the Remote Desktop Web Connection component of Internet Information Services if the Shares Web site is enabled on the Windows Storage Server 2003 server appliance. Because Remote Desktop Web Connection and the Shares Web site use the default port for HTTP (80), they cannot run on the same computer.
Using the Web user interface (UI), administrators cannot create shares with a name longer than 80 characters. They should use Remote Desktop if it is necessary to create a share with a longer name.
When publishing shares to DFS roots, only the 16 most recently used DFS root names are saved. Publishing a share to a seventeenth unique root will overwrite the least recently used DFS root name. Any shares that were previously published to this root will no longer appear to be published in the Web UI, but they will still in fact be correctly published.
Mount points and volumes that do not have drive letters assigned to them are not supported in the Web UI. Such volumes will appear in volume lists, but an attempt to perform any action on them will fail.
When using directory quotas, setting a threshold at 100% for a non-passive directory quota will never generate an event or alarm even though the Web UI allows the administrator to do so. This is because the quota is enforced and the user is never allowed to reach 100%.
If a quota is not associated with a user, then the Web UI displays "Information not available" for that entry and its properties cannot be viewed, nor can the quota be deleted using the Web UI. To delete a quota that is not associated with a user, the administrator must use Remote Desktop to connect to the server.
The WQuinn Storage Manager feature that alerts users who exceed their quotas by sending a popup message relies on NetBIOS to work. Consequently, for this feature to function properly, NetBIOS must be sufficiently enabled in the network infrastructure to support the net send Name message command being run on the server and received by the user's client computer.
The following sections describe proper procedures to follow when changing the server appliance language.
When the administrator uses the Web UI to change the server language, the administrator must also log in to the server using Remote Desktop and use Regional and Language Settings in Control Panel to change the text services and input language as well as the language used in menus and dialog boxes.
When the administrator changes the language of the server appliance Web UI, the administrator should also configure the Web browsers used to administer the server to use the same default language as the language selected for the Web UI. If the server and browser languages do not match, date, time or currency formats may be displayed incorrectly.
When using Alert E-mail on a server with the language set to Japanese, Chinese or Korean, the administrator should set the input locale to the appropriate language.
To set the input locale, use Remote Desktop to connect to the server. In the Regional and Language Options tool in Control Panel, click the Languages tab, click Details, and then select the appropriate language in the Default input language list. Next, click the Advanced tab and select the same language in the Language for non-Unicode Programs list. Finally, select the Default user account settings check box, and then click OK.
The following sections contain information about Microsoft Services for Network File System that you should consider making available to your customers.
The Web UI cannot be used to create, modify, or delete an NFS group name that contains more than 25 multibyte characters. Multibyte characters are used in the Chinese, Japanese, and Korean languages. If the customer must work with group names containing more than 25 multibyte characters, the administrator must connect to the server using Remote Desktop and use Microsoft Services for Network File System Administration.
The NFS mount protocol supports only ANSI characters. Consequently, double-byte character set (DBCS) characters are not supported in Network File System (NFS) share names. If the administrator attempts to create an NFS share with a name containing one or more DBCS characters, no error will be displayed, but the share will not be created.
The maximum number of users that can be listed for explicit user mapping is 750. Consequently, the Explicit User Mapping page in the Web UI will time out if the passwd and group files list more than 750 users. If more than 750 explicit user mappings are required, the administrator must connect to the server using Remote Desktop and use Microsoft Services for Network File System Administration to manage the user maps instead of the Web UI.
Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 1998–2003 Microsoft Corporation. All rights reserved.
Active Directory, ActiveX, FrontPage, JScript, Microsoft,
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.