Release Notes for Microsoft® Identity Integration Server 2003 Resource Tool Kit

Welcome to the release notes for Microsoft Identity Integration Server (MIIS) 2003 Resource Tool Kit. These release notes contain important information that was not available when the product documentation for MIIS 2003 Resource Tool Kit was written.

You can find additional information at the Web sites that are listed at the end of this document.

The following are known issues at the time of release for MIIS 2003 Resource Tool Kit:

• Microsoft .NET Framework 1.1 or higher is required for the MIIS 2003 Resource Tool Kit tools to run properly.
• To run the tools from a remote shared folder, you must set the .NET Framework trust level on each tool.
  
  To set the .NET Framework trust level
  1. Click Start, Programs, Administrative Tools, Microsoft .NET Framework 1.1 Wizards, then click Trust an Assembly.
  2. Browse to the folder where the MIIS 2003 Resource Tool Kit is installed, and select the tool that you want to run remotely.
  3. Set the trust level to Full Trust.
• PCNSLookup.vbs returns error 424: Object required. PCNSLookup.vbs will return this error when the domain name passed to it cannot be located.
• PCNSLookup.vbs will not connect to the target domain by using an account that has a quotation mark (") in the password, for example
  
  cscript PCNSLookup.vbs /u:test-domain\administrator Pa$$"0rd /d:test-domain
  
  In this case, PCNSLookup.vbs will return the usage help.
• The project generated by the MIIS Provisioning Assistant may return CS0219 warnings when it is compiled. These warnings can be ignored.
• MIISInfoBackup has a limitation of 248 characters for the path that the tool is run from, and for the path that is specified in the <OtherInfo><CopyFolder><FolderPath> node. If the path is greater than 248 characters, the following message will be displayed:
  
  "There was an error while copying additional folders. Please refer to the log file for detailed information"
  
  The log file MIISInfoBackup.log will indicate the destination folder that failed.

For product overviews, case studies, and other news about Microsoft Identity Integration Server 2003, see the Microsoft Identity Integration Server 2003 Web site.(http://www.microsoft.com/)

To post questions about Microsoft Identity Integration Server 2003 to the microsoft.public.metadirectory newsgroup, see the Microsoft Web site.

To search for technical support information and self-help tools for Microsoft products, see the Microsoft Knowledge Base.(http://www.microsoft.com/)

Information in this document, including URL and other Internet Web site references, is subject to change without notice. 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.

©2004 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, MS-DOS, Windows, Windows NT, Visual Basic, Visual C#, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.