Windows 2000 Essay, Research Paper
Microsoft? Windows? 2000 Professional,
Windows 2000 Server, and
Windows 2000 Advanced Server
Release Notes
This papers provides late-breaking or other information that supplements the Microsoft Windows 2000 certification.
Information in this papers, including URL and other Internet Web site mentions, is capable to alter without notice. Unless otherwise noted, the illustration companies, organisations, merchandises, people, and events depicted herein are fabricated and no association with any existent company, organisation, merchandise, individual, or event is intended or should be inferred. Complying with all applicable right of first publication Torahs is the duty of the user. Without restricting the rights under right of first publication, no portion of this papers may be reproduced, stored in or introduced into a retrieval system, or transmitted in any signifier or by any agencies ( electronic, mechanical, run offing, entering, or otherwise ) , or for any intent, without the express written permission of Microsoft Corporation.
Microsoft may hold patents, patent applications, hallmarks, right of first publications, or other rational belongings rights covering capable affair in this papers. Except as expressly provided in any written license understanding from Microsoft, the trappings of this papers does non give you any licence to these patents, hallmarks, right of first publications, or other rational belongings.
? 1999 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Active Directory, DirectX, FrontPage, NetMeeting, Outlook, PowerPoint, Visual Basic, Visual C++ , Visual FoxPro, Visual InterDev, Visual Studio, Windows, Windows Media, and Windows NT are either registered hallmarks or hallmarks of Microsoft Corporation in the United States and/or other countries/regions.
This merchandise contains artworks filter package ; this package is based in portion on the work of the Independent JPEG Group.
The names of existent companies and merchandises mentioned herein may be the hallmarks of their several proprietors.
Contentss
Introduction
Networking and Communicationss
Change and Configuration Management ( IntelliMirror )
Windows Management Instrumentation
Security
Directory Servicess
Component Servicess
Microsoft Data Access Components
Internet Servicess
Microsoft Windows 2000 Server Media & # 8482 ; Servicess
Storage Notes
Hardware
Application Notes
Printing Notes
Terminal Servicess
Windows 2000 Advanced Server
Introduction
This papers provides late-breaking or other information that supplements the Microsoft Windows 2000 certification. The Windows 2000 compact phonograph record ( Cadmium ) includes the undermentioned release notes files:
? Read1st.txt, which contains of import preinstallation information and is located in the Windows 2000 CD root directory
? Installation chapters from the Getting Started Guide, which include system demands information and are located in the Setuptxt booklet on your Windows 2000 Cadmium
? Readme.doc, which contains compatibility and post-installation notes and is located in the Windows 2000 CD root directory
? The Hardware Compatibility List. For the most up-to-date list of supported hardware, see the Hardware Compatibility List at the Microsoft Web site ( hypertext transfer protocol: //www.microsoft.com/hcl/ ) . Your Windows 2000 Cadmium includes a transcript of this list ( drive: SupportHcl.txt ) that was accurate as of the day of the month Windows 2000 was released.
To reexamine the latest Application Compatibility information, see the Microsoft Windows 2000 Product Compatibility Web site at:
hypertext transfer protocol: //www.microsoft.com/windows2000/compatible/
To reexamine the latest release notes and updated information for Windows 2000, see the Microsoft Knowledge Base on the Microsoft Personal Online Support Web site at:
hypertext transfer protocol: //support.microsoft.com/support/
Networking and Communicationss
The undermentioned subdivisions describe Windows 2000 issues related to networking and communications.
Routing and Remote Access
This subdivision describes a known issue related to Windows 2000 Routing and Remote Access.
Enabling Windows NT? 4.0 RAS Servers in a Windows 2000 Domain
If you are utilizing Windows NT 4.0 Remote Access Service ( RAS ) waiters in a Windows 2000 sphere, they must be running Service Pack 4 ( SP4 ) or subsequently. Otherwise, they can non entree the Windows 2000 sphere accountants to verify that a user has dial-in permissions. Besides, if you set up a Windows NT 4.0 RAS or Routing and Remote Access Service ( RRAS ) waiter as a member of a Windows 2000 sphere, you must do certain accommodations to Active Directory & # 8482 ; so that the waiter can entree the Remote Access certificates of sphere histories.
You can set Active Directory to let Windows NT 4.0 RAS waiters by utilizing either of the undermentioned methods:
? When you create a Windows 2000 sphere by utilizing the Active Directory Installation ace to upgrade a waiter to a sphere accountant, select the option to let bequest waiters to entree Active Directory. If you enabled this entree when you created the sphere, no farther action is required.
? If you add a Windows NT 4.0 RAS waiter to a sphere that has non been adjusted to let bequest server entree, you can utilize the undermentioned bid to set sphere security for bequest server entree:
cyberspace localgroup & # 8220 ; Pre-Windows 2000 Compatible Access & # 8221 ; everyone /add
After put to deathing this bid, you must re-start the sphere accountant.
TAPI
This subdivision describes issues related to TAPI in Windows 2000.
ATI-TV Tuner Video Cards Are Not Supported for Use With TAPI
TAPI does non back up the usage of ATI picture cards that incorporate Television tuners, including but non limited to ATI-TV, ATI-TV WONDER, and All-in-Wonder theoretical accounts. This will be addressed in a future release.
Kodak USB Cameras Are Not Supported
Windows 2000 does non include drivers for Kodak Universal Serial Bus ( USB ) cameras. To download the latest drivers, visit the Kodak Web site at:
hypertext transfer protocol: //www.kodak.com/
This will be addressed in a future release.
Note
Web references can alter, so you may be unable to link to the Web site mentioned here.
DHCP
In the online Help for the Dynamic Host Configuration Protocol ( DHCP ) waiters, the instructions that describe how to travel a DHCP database from one waiter to another are uncomplete. For complete instructions, see the Knowledge Base on the Microsoft Personal Online Support Web site at:
hypertext transfer protocol: //support.microsoft.com/support/
Autonet
On a multi-homed computing machine, if two or more interfaces are utilizing an Automatic Private Internet Protocol Addressing ( APIPA ) -based reference at the same time, the routing behaviour of the computing machine for any finish on the APIPA subnet is inconsistent. For more information about this Autonet issue, visit the Knowledge Base on the Microsoft Personal Online Support Web site at:
hypertext transfer protocol: //support.microsoft.com/support/
Change and Configuration Management ( IntelliMirror )
The undermentioned subdivision describes Windows 2000 issues related to alter and constellation direction.
Group Policy
It is strongly recommended that you limit the computing machine name used by sphere accountants to 15 characters. Longer computing machine names may do the installing failure of applications that are deployed by utilizing the Software Installation snap-in to Group Policy. For more elaborate information, see the Knowledge Base on the Microsoft Personal Online Support Web site at:
hypertext transfer protocol: //support.microsoft.com/support/
Besides, to reexamine information about a related issue, see the & # 8220 ; Active Directory Domain Name Length Restriction & # 8221 ; subject subsequently in this papers.
Windows Management Instrumentation
The undermentioned subdivision describes Windows 2000 issues related to Windows Management Instrumentation ( WMI ) .
WMI ODBC Driver
When you upgrade your computing machine to Windows 2000, the old installing of the WMI unfastened database connectivity ( ODBC ) driver is deleted. The Windows 2000-compatible driver for WMI ODBC is located on the Windows 2000 Cadmium in the ValuAddMSFTMGMTWBEMODBC booklet.
Security
The undermentioned subdivisions describe issues related to Windows 2000 security characteristics.
Certificate Servicess
This subdivision describes issues related to Certificate Services in Windows 2000.
Certificate Services Setup Fails
If the name of the computing machine contains non-International Alphabet 5 ( IA5 ) characters, such as non-English characters, Certificate Services Setup fails. Use merely IA5 characters to call a computing machine. This will be addressed in a future release.
PKI Services Fail If the DNS Computer Name Is Greater than 64 Fictional characters
If the to the full qualified Domain Name System ( DNS ) computing machine name is greater than 64 characters, Public Key Infrastructure ( PKI ) services fail. This causes the undermentioned procedures to neglect:
? Enterprise Certificate Authority ( CA ) installing
? Domain accountant and computing machine automatic registration
? Internet Protocol Security ( IPSec ) registration
Installation of Certificate Services in a Child Domain
To put in Certification Services for a kid sphere in the endeavor, you must be a member of the Enterprise Administrators group, which is in the parent sphere.
CA Service Stops Running After a File System Upgrade from FAT to NTFS
The CA service Michigans running after a file system ascent from FAT to the NTFS file system. The undermentioned message appears in the application log:
& # 8220 ; Certificate Services did non get down: Unable to initialise the database connexion for *Your CA Name here* . Class non registered 0 & # 215 ; 80040154. & # 8221 ;
As a workaround, uninstall the CA service and so re-install it utilizing the same CA name, cardinal brace, and database as the old installing.
Ascent of Subordinate CA from Windows NT 4.0 Certificate Server
After you upgrade a subsidiary CA that is running Windows NT 4.0 Option Pack Certificate Server 1.0 to Windows 2000, you must execute a CA reclamation operation and make a new CA certification with the Basic Constraints field set to True for the CA value. Before the SP6 release of Windows NT 4.0, the Certificate Server 1.0 merchandise did non put the CA value to True in the Basic Constraints field in the CA certification. In SP6, if you are put ining the CA for the first clip, the CA value is set to True in the CA certification. In Windows 2000, if you are put ining the CA for the first clip or if you are executing a CA reclamation operation on an bing CA, the CA value is set to True in the CA certification.
Default Security Settings
This subdivision describes issues related to the default security scenes in Windows 2000.
File and Registry Permissions Are Changed During Upgrade
The default security scenes for a clean installing are besides applied when you upgrade to Windows 2000. Using the same default security scenes ensures that entree permissions for the register and for Windows 2000 system directories and files are set systematically. However, if the default security scenes are non sufficient after you upgrade to Windows 2000, you should reapply any custom scenes that you applied before the ascent.
Windows NT 4.0 Users May Need Power User Capabilities After Upgrade
The default security scenes for a clean installing are besides applied when you upgrade to Windows 2000. For more information about how these default security scenes are applied, see & # 8220 ; File and Registry Permissions Are Changed During Upgrade, & # 8221 ; earlier in this papers.
In Windows 2000, the permissions for users who do non hold decision maker or power user privileges are well more secure than in Windows NT 4.0. As a consequence, most non-certified bequest applications do non run successfully for typical users of Windows 2000. Therefore, after you upgrade to Windows 2000 and default security scenes are applied, you may necessitate to give power user capablenesss to Windows NT 4.0 users.
When you upgrade from Windows NT 4.0 Workstation, you can supply power user capablenesss automatically by adding the Interactive group to the Power Users group. Then, when Windows NT 4.0 users log on locally, they become power users on Windows 2000. Because Windows 2000 power users have the same entree control permissions as Windows NT 4.0 users, these users can go on to run non-certified bequest applications after they upgrade to Windows 2000.
Notes
When you upgrade from old versions of Windows 2000 or put in Windows 2000 Server, the Interactive group is non added to the Power Users group.
Certified Windows 2000 applications run successfully for a typical user on Windows 2000. Therefore, certified applications offer the highest degree of security without giving application functionality.
Service Account Must Be Manually Added to the Power Users Group After Upgrade
The default security scenes for a clean installing are besides applied when you upgrade to Windows 2000. For more information about how these default security scenes are applied, see & # 8220 ; File and Registry Permissions Are Changed During Upgrade, & # 8221 ; earlier in this papers.
After the default security scenes are applied in Windows 2000, services that antecedently ran under a non-administrative or non-system context on Windows NT 4.0 may no longer work decently. This occurs because Windows 2000 users have fewer permissions than Windows NT 4.0 users. Therefore, after you upgrade to Windows 2000, you must manually add the service history to the Power Users group.
High Encryption Pack & # 8212 ; Upgrading from 128-bit Encoding on Down-Level Platforms
When you upgrade the 128-bit version of Windows 95 with Microsoft Internet Explorer 3.02 to Windows 2000, the encoding is reduced to 40-bit. As a workaround, you can put in the Windows 2000 High Encryption Pack, which enables you to upgrade to 128-bit encoding.
EFS Recovery and Private Key Issues When Joining a New Windows 2000 Domain
When you upgrade a computing machine from Windows 95 or Windows 98 to Windows 2000, you may see jobs after fall ining the new sphere because of issues with Encrypting File System ( EFS ) recovery and migrating private cryptanalytic keys. After you upgrade the computing machine, you should non utilize EFS until the computing machine really joins the new sphere. If you use EFS before your computing machine joins the sphere, any files that you encrypt with EFS are unaccessible to your sphere logon history. In add-on, you should non run applications that use private cryptanalytic keys until the computing machine really joins the new sphere. If you generate and use private cryptanalytic keys before your computing machine joins the sphere, these keys are unavailable to your sphere logon history.
Directory Servicess
The undermentioned subdivisions describe issues related to Windows 2000 directory services characteristics.
Active Directory Domain Name Length Restriction
The fully-qualified DNS name of an Active Directory sphere, for illustration example.microsoft.com, is restricted to 64 USC Transformation Format 8 ( UTF-8 ) bytes in length. This bound does non use to computing machine names.
One ASCII character is equal to one UTF-8 byte in length. Non-ASCII characters, such as other Unicode characters, have a variable length encoding that can be up to three bytes in length. To gauge the size of a name in bytes, count each ASCII character as one byte and each non-ASCII character as three bytes.
Before you deploy Active Directory, verify that all of your planned sphere names do non transcend 64 UTF-8 bytes in length.
Message Line uping
This subdivision describes issues related to the installing of Message Queuing.
Installing Message Line uping on Computers that Do Not Have MSMQ 1.0 Installed
This subdivision describes issues related to the installing of Message Line uping on computing machines that do non hold Microsoft Message Queue Server ( MSMQ ) 1.0 installed.
Administrative Permissions Required to Run Message Queuing Setup
The undermentioned permissions are required to put in Message Line uping on a computing machine:
? When you install Message Queuing in either a workgroup or a sphere environment, you must hold local administrative permissions for the computing machine.
? If you are put ining Message Line uping on a Windows 2000 sphere accountant, you must hold permission to make the msmqSettings object that represents the computing machine on which you are put ining Message Queuing. The msmqSettings object is located under the applicable waiter object. This applicable waiter object is located under the Servers object, which is located under the applicable site object in Active Directory Sites and Services.
Alternatively, you can hold domain administrative permissions, or you can belong to the Domain Administrators group, which has this permission by default.
? If you are put ining a Message Line uping waiter with routing enabled on a non & # 64979 ; sphere accountant, you must hold permission to make the applicable waiter object that represents the computing machine on which you are put ining the Message Line uping waiter. This object is located under the Servers object, which is located under the applicable site object in Active Directory Sites and Services.
Alternatively, you can hold enterprise administrative permissions, or you can belong to the Enterprise Administrators group, which has this permission by default. In add-on, if? when you are prompted during Message Line uping Setup? you enter the name of a Message Queuing waiter that is running on a Windows 2000 sphere accountant in the local sphere, domain administrative permissions are sufficient.
For more information about object permissions for Message Queuing, see Windows 2000 Help.
Installing Message Line uping in a Windows 2000 Workgroup
For a computing machine that is a member of a Windows 2000 workgroup, Message Queuing is automatically installed to run in workgroup manner. Workgroup manner means that the ability of the computing machine to entree Active Directory is disabled. For more information about workgroup manner, see Windows 2000 Help.
In add-on, if you move a computing machine from a workgroup to a sphere, Message Queuing automatically attempts to fall in the new sphere. However, the new sphere must be a Windows 2000 sphere, and it must incorporate a Message Line uping waiter that is running on a Windows 2000 sphere accountant with a Global Catalog server enabled. In this instance, Message Queuing operates in sphere manner, which means that entree to Active Directory is enabled.
Installing Message Line uping in a Windows 2000 Domain
This subdivision describes issues related to put ining Message Queuing in a sphere environment.
Operating in Workgroup or Domain Mode
If you are put ining Message Queuing in a sphere environment, you can choose whether or non the computing machine operates in workgroup manner ( no entree to Active Directory ) or in domain manner ( entree to Active Directory ) by snaping the Manually choice entree manner to Active Directory check at the beginning of Message Queuing Setup.
Security Restrictions for Windows 2000 Domains
All operating constellations? other than Windows 2000 sphere users & # 8217 ; computing machines that are running Message Line uping on Windows 2000? present security restrictions in Windows 2000 spheres. These restrictions pertain to the following operating constellations:
? In a mixed-mode sphere environment where users & # 8217 ; computing machines are running MSMQ 1.0 on Windows NT 4.0, Windows 95, or Windows 98, and these computing machines entree Message Queuing waiters running on Windows 2000 sphere accountants. If these users are logged on with Windows 2000 sphere histories, this restriction besides applies.
? In a mixed-mode sphere environment where users & # 8217 ; computing machines are running Message Line uping on Windows 2000 in a Windows NT 4.0 sphere, and these computing machines entree MSMQ 1.0 accountant waiters.
? In a Windows 2000 sphere environment where users & # 8217 ; computing machines are running Message Line uping on Windows 2000, and these users are logged on with Windows NT 4.0 sphere histories.
? In a Windows 2000 sphere environment where users & # 8217 ; computing machines support merely the Internetwork Packet Exchange ( IPX ) protocol.
? In an environment where users are logged on with a Local User history regardless of the operating system.
If any of these operating constellations apply to your organisation, so to back up these users, you should weaken security for Active Directory. When Message Line uping Setup prompts you during the first installing of Message Line uping on the first Windows 2000 sphere accountant in your wood, select the diminished permissions option.
Stipulating a Server Name During Message Queuing Setup
Message Line uping Setup may motivate you to come in the name of a waiter. In most instances, you should come in the name of a Message Queuing waiter that is running Windows 2000. You can stipulate the name of an MSMQ 1.0 accountant waiter ( such as the primary endeavor accountant [ PEC ] or a primary site accountant [ PSC ] ) alternatively, but this scenario is supported merely if you are put ining an independent client. For all other installing types, Setup fails.
First Installation of Message Queuing in a Domain Must Be on a Domain Controller
You must put in Message Line uping on a Windows 2000 sphere accountant before you install Message Queuing package on any other computing machine in your sphere. In add-on, to back up Message Line uping clients, this sphere accountant must hold the Trust computing machine for deputation belongings enabled.
On a Windows 2000 sphere accountant running Windows 2000, this belongings is enabled by default. If this belongings is disabled, Message Line uping clients can non link to the sphere accountant, and the clients display symptoms similar to when a Message Line uping waiter is offline.
Message Line uping with Routing Enabled and Message Queuing on a Domain Controller Must Be Installed at Every Site
You must put in Message Line uping on a Windows 2000 sphere accountant for each Windows 2000 site. In add-on, you must put in Message Line uping with routing enabled on a non-domain accountant at every site that has Message Line uping clients ; this can be installed on the same waiter computing machine. Failure to put in Message Queuing and Message Queuing with routing enabled may do messages non to make their finishs across sites.
Besides, to back up MSMQ 1.0 clients running on Windows NT 4.0 in a Windows 2000 sphere, you must put in Message Line uping on a Windows 2000 sphere accountant that is configured as a Global Catalog waiter.
Installing Message Line uping on an IPX-Only Computer
When you install Message Line uping on an IPX-only computing machine that is running Windows 2000, you must come in the name of a Message Queuing waiter that is running on a Windows 2000 sphere accountant when you are prompted to make so during Setup. This waiter must be in the local sphere.
Installing Message Line uping Using a Windows NT 4.0 Domain User Account
When you install Message Line uping on a computing machine that is running Windows 2000 and you use a Windows NT 4.0 sphere user history, you should hold at least one Message Line uping waiter that is running on a Windows 2000 sphere accountant in the local sphere. If this is non possible, you must come in the name of a waiter that meets this standard when you are prompted to make so during Setup.
Installing MSMQ 1.0 on Windows NT 4.0 in a Windows 2000 Domain
When you install MSMQ 1.0 on a computing machine that is running Windows NT 4.0 in a Windows 2000 sphere, you must come in the name of a Message Queuing waiter in the local sphere when you are prompted for the name of a PSC during Setup. This Message Line uping waiter must be running on a Windows 2000 sphere accountant that is besides configured as a Global Catalog waiter.
In add-on, if you plan to put in MSMQ 1.0 on computing machines that are running Windows NT 4.0 in a new Windows 2000 sphere, you should choose the pre & # 64979 ; Windows 2000 compatible cheque box when you run Setup for the first Windows 2000 sphere accountant in the local sphere.
If you plan to put in MSMQ 1.0 on computing machines that are running Windows NT 4.0 in an bing Windows 2000 sphere, you should verify that the Everyone group is a member of the & # 8220 ; pre-Windows 2000 Compatible Access & # 8221 ; group in this sphere.
? To add the Everyone group to the pre-Windows 2000 Compatible Access group
1. In the MMC, open the Active Directory Computers and Users snap-in.
2. In the console tree, double-click Builtin.
3. Right-click pre-Windows 2000 Compatible Access, and so snap Properties.
4. On the Members check, chink Add, and so in the list, select Everyone ( if needed ) .
5. Click OK.
Installing MSMQ 1.0 on Windows 95 or Windows 98 in a Windows 2000 Domain
When you install MSMQ 1.0 on a computing machine that is running Windows 95 or Windows 98 in a Windows 2000 sphere, you must come in the name of a Message Queuing waiter in the local sphere when you are prompted for the name of a PSC during Setup. This Message Line uping waiter must be running on a Windows 2000 sphere accountant that is besides configured as a Global Catalog waiter.
Besides, you must be granted the Create Computer Objects permission, which is located under the Computers booklet object in Active Directory Users and Computers, because the computing machine object for these computing machines does non be in Active Directory. For more information about the Create Computer Objects permission, see Windows 2000 Help.
Reinstalling Message Line uping in a Multi-Domain Environment
When you uninstall Message Line uping on a computing machine in a multi-domain environment, you must wait for Active Directory reproduction to happen before you reinstall Message Line uping on the same computing machine.
Installing Message Line uping on a Windows 2000 Server Cluster
Message Queuing is dependent on the Microsoft Distributed Transaction Coordinator ( MS DTC ) service on a waiter bunch. To successfully put in Message Line uping on a Windows 2000 waiter bunch, you must first manually constellate the MS DTC service.
? To manually constellate the MS DTC service
1. Make a bunch practical waiter, which is a bunch group incorporating a Disk resource and a Network Name resource.
2. On the computing machine node that hosts the bunch practical waiter, run Comclust.exe, which is located in the WinntSystem32 booklet.
3. Run Comclust.exe on the other nodes. Do non re-start any node until Comclust.exe has been successfully started on all nodes in the waiter bunch.
4. Restart each computing machine node.
Now you can put in Message Line uping on each node.
Note
The installing may neglect, and a message may look bespeaking that you lack the necessary permissions. In this instance, allow yourself permission to make the MSMQ constellation ( msmq ) object, which is located under the computing machine object stand foring your bunch practical waiter, and so run Message Queuing Setup once more. This permission is besides required to pull off the bunch practical waiter by utilizing the Computer Management snap-in.
As an option, you can run Message Queuing Setup with an history that has domain administrative permissions. By default, domain administrative permissions include the permission to make the msmq object. This will be addressed in a future release.
Configuring Cluster Resources for Message Line uping
In Windows 2000 Help, the process that describes how to configure a bunch resource for Message Queuing is wrong ; you should finish Step 11 before you complete Step 10. The sequence of all the other stairss is right.
Installing Message Line uping Using Unattended Setup
When you use unattended apparatus to put in a Message Line uping waiter with routing ( RS installing type ) , the reply file book automatically attempts to decide the site to which the computing machine belongs. If subnets in your web are non configured right, Message Queuing Setup may neglect to decide the site. In this instance, you must stipulate the default site incorporating the Message Line uping waiter that is running on a Windows 2000 sphere accountant with which this waiter will pass on.
? To stipulate the default site
* Add the undermentioned entry to your unattended apparatus reply file:
Site = *your_domain_controller_site_name*
Upgrading MSMQ 1.0 on Computers Runing Windows 2000
This subdivision describes issues related to upgrading MSMQ 1.0 on computing machines that have been upgraded to the Windows 2000 operating system.
Upgrading an MSMQ 1.0 Enterprise to Windows 2000
The procedure of upgrading your MSMQ 1.0 endeavor to Windows 2000 is called migration. You must execute this multi-step procedure right and in the proper sequence. It is of import that you understand all the issues and deductions involved in migration. For specific information about the issues, readying, and executing of migration, see & # 8220 ; Migrating from MSMQ 1.0 & # 8221 ; on the Migration FTP site at:
file transfer protocol: //ftp.microsoft.com/bussys/distapps/Msmq/Win2000/Migration/
Upgrading MSMQ 1.0 on a Server Cluster
This subdivision provides elaborate information about how to upgrade the different MSMQ 1.0 computing machine types on a waiter bunch. Unless otherwise stated, utilize the undermentioned general order of events to upgrade MSMQ 1.0 on all computing machine types on a waiter bunch:
1. For a clustered PEC or PSC, run the Message Line uping Upgrade ace ( Mqmig.exe ) . See the note below.
2. Upgrade the operating system of the node to Windows 2000 Advanced Server.
3. Upgrade the MS DTC resource.
4. Upgrade the MSMQ resource.
To upgrade a bunch node to Windows 2000 Advanced Server, the computing machine must be running Windows NT Server 4.0 Enterprise Edition with SP4 or SP5. Windows 2000 does non back up a turn overing ascent of a Windows NT 4.0 waiter bunch with MSMQ 1.0 installed.
Note
When you upgrade the MSMQ resource, the Message Queuing Upgrade ace may motivate you for the name of a waiter. You should come in the name of a Message Queuing waiter that is running on Windows 2000 instead than the name of an MSMQ 1.0 accountant waiter such as the PEC or a PSC. Otherwise, the ascent fails.
Upgrading the MS DTC Resource
After you upgrade the operating system on each node to Windows 2000 Advanced Server, and before you upgrade the MSMQ resource on any node, you must utilize Cluster Administrator to upgrade the MS DTC resource to an active/active constellation.
To upgrade the MS DTC resource on a waiter bunch, finish the stairss in the undermentioned process.
? To upgrade the MS DTC resource on a waiter bunch
1. Take the MS DTC bunch resource offline.
2. Verify that all services dependant on the MS DTC bunch resource? including the services for Message Queuing, Component Services, Microsoft SQL Server, and Microsoft COM Transaction Integrator ( COMTI ) ? are stopped.
3. On the node that hosts the bunch practical waiter incorporating the MS DTC bunch resource, from the bid prompt, run Comclust.exe. This plan is located in the system booklet ( typically, C: WinntSystem32 ) .
4. On each of the staying nodes, run Comclust.exe. Do non convey the MS DTC bunch resource back on-line until Comclust.exe is running on all nodes in the waiter bunch.
5. Manually restart all dependant services, and so convey the MS DTC bunch resource back online.
Upgrading the MSMQ Resource
After you successfully finish the process for upgrading the MS DTC resource as described in the old subject, & # 8220 ; Upgrading the MS DTC Resource, & # 8221 ; utilize the Configure Message Queuing Cluster Resources ace to upgrade the MSMQ resource to supply active/active fail-over support.
? To upgrade the MSMQ resource
1. Click Start, point to Programs, point to Administrative Tools, and so snap Configure Your Server.
2. From Configure Your Server, click Finish Setup, and so snap Configure Message Queuing Cluster Resources.
3. Follow the instructions that appear in the Configure Message Queuing Cluster Resources ace.
You must hold endeavor administrative permissions or belong to the Enterprise Administrators group to run the Configure Message Queuing Cluster Resources ace on computing machines that hosted MSMQ 1.0 waiters ( PEC, PSC, BSC, or Routing waiters ) before the ascent.
Upgrading MSMQ Routing Servers, BSCs, and Independent Clients on a Server Cluster
You should upgrade the MSMQ 1.0 routing waiters and MSMQ 1.0 Backup Site Controllers ( BSCs ) on a waiter bunch to Message Line uping waiters with routing enabled. You should upgrade MSMQ 1.0 independent clients to Message Line uping independent clients.
To upgrade these computing machines on a waiter bunch, finish the stairss in the undermentioned process.
? To upgrade the MSMQ routing waiters, BSCs, and independent clients on a waiter bunch
1. Upgrade the operating system on each node to Windows 2000 Advanced Server.
2. Use Comclust.exe to upgrade the MS DTC resource on each node.
3. Use the Configure Message Queuing Cluster Resources ace to upgrade the MSMQ 1.0 resource on each node.
Upgrading the PEC and PSCs on a Server Cluster
In Windows 2000 Message Queuing deployment, the function of the PEC and the PSCs is delegated to Message Line uping waiters running on Windows 2000 sphere accountants. Because Windows 2000 sphere accountants can non be clustered, upgrading the PEC and PSCs to Windows 2000 is a multi-step procedure. During Thursday
is procedure, the MSMQ Information Store ( MQIS ) information is imported from the PEC or PSC to a Message Line uping waiter that is running on a Windows 2000 sphere accountant located outside of the waiter bunch.
You must execute this upgrade procedure right and in the proper sequence. It is of import that you understand all the issues and deductions involved in this procedure. For specific information about the issues, readying, and executing of the PEC and PSCs upgrade on a waiter bunch, see & # 8220 ; Migrating from MSMQ 1.0 & # 8221 ; on the Migration FTP site at:
file transfer protocol: //ftp.microsoft.com/bussys/distapps/Msmq/Win2000/Migration/
NTLM Version 2 Authentication for Windows 95 and Windows 98 Directory Services Clients
For information about how to enable and disable Windows NT LAN Manager ( NTLM ) version 2 and LAN Manager ( LM ) hallmark for Windows 95 and Windows 98 Directory Services clients, visit the Knowledge Base on the Microsoft Personal Online Support Web site at:
hypertext transfer protocol: //support.microsoft.com/support/
Component Servicess
The undermentioned subdivisions describe issues related to Windows 2000 Component Services characteristics.
Component Services Setup
Depending on the current constellation of your operating system, you may meet some of the undermentioned issues that relate to upgrading bing installings of Microsoft Transaction Service ( MTS ) and Component Services:
? If you are utilizing either MTS 2.0, which is portion of the Windows NT 4.0 Option Pack, Component Services automatically replaces MTS. All user-defined bundles will be upgraded to COM+ applications. All constituents should work as they did under MTS 2.0.
? If you are utilizing MTS 1.0, Component Services automatically replaces MTS. However, user-defined bundles are lost, and you must re-create them.
? If you are utilizing either MTS 1.0 or MTS 2.0 and you have installed the SDK option, the SDK files are removed. You may desire to put in the latest Component Services SDK, which is available with the Microsoft Platform SDK.
? If a Component Services application is marked as non mutable, the Comrepl.exe public-service corporation or the Iissync.exe public-service corporation does non decently retroflex its individuality. For this release, you must tag the application as mutable before originating the reproduction. For extra information about Comrepl.exe, see the Component Services online certification. For extra information about Iissync.exe, see the Internet Information Services ( IIS ) certification. This will be addressed in a future release.
? When you re-install over a Component Services application that has been marked as non deletable, neither the Component Services snap-in nor the Component Services administrative interfaces return an mistake. However, the application is non updated. For this release, you must either tag the application as deletable or modify the installing codification to look into whether an application exists before put ining it.
To download Component Services certification and samples, see the Microsoft Platform SDK: COM Components Web site at:
hypertext transfer protocol: //www.microsoft.com/msdownload/platformsdk/com.htm
Upgrading MTS 2.0 Installations to
Windows 2000 with Component Services
When you upgrade a computing machine running Windows NT 4.0 with Windows NT 4.0 Option Pack, Windows 95 with Personal Web Server from the Windows NT 4.0 Option Pack, or Windows 98 with Personal Web Server to Windows 2000, Setup automatically migrates all bing MTS bundles to Component Services applications.
Note
Before you use, import, or export the migrated bundles, it is of import to reexamine the migration log file that is generated during the migration procedure even if the ascent appears successful. If this migration fails or encounters a job that is non fatal, a message appears and an event log entry or log file is generated that describes the ground for the failure.
As an surrogate attack to migrating MTS 2.0 bundles to Component Services, do the followers:
1. Use the MTS 2.0 Package Export characteristic to export the MTS bundles on the computing machine running Windows NT 4.0, Windows 95, or Windows 98. This export procedure produces a.pak file for each exported bundle and a aggregation of other files.
2. Perform a clean installing of Windows 2000, or cancel the MTS bundles and ascent to Windows 2000.
3. Use the Application Install characteristic of the Component Services administrative tool to put in the.pak files on a Windows 2000 computing machine.
Application Proxy Installation
If an application placeholder ( .msi file ) for the same waiter application is re & # 64979 ; exported, before you install the new application placeholder, you must uninstall the earlier application placeholder from the computing machine. Otherwise, both application placeholders appear when you open Add/Remove Programs in Control Panel. Additionally, alterations contained in the new application placeholder may non be applied to the computing machine. No message or mistake log is generated. This will be addressed in a future release.
Upgrading from Component Services ( Beta Version ) with MSCS
If you are upgrading from a old beta version of Windows 2000 on a Microsoft Cluster Server ( MSCS ) bunch with the Component Load Balancing ( CLB ) router enabled, you may hold configured the bunch for usage with the CLB service. You need to take the earlier constellations to avoid unneeded mistakes in the event log.
? To take the earlier constellations
* At the bid prompt, type:
comclust -r
Microsoft Distributed Transaction Coordinator
This subdivision describes issues related to the MS DTC.
Performing Distributed Minutess with
Windows NT 3.51 and Windows NT 4.0
MS DTC uses a new protocol for executing distributed minutess on Windows 2000. As a consequence of this protocol alteration, a distributed dealing can no longer flux from a Windows 95, Windows 98, Windows NT 3.51, or Windows NT 4.0 computing machine to a Windows 2000 computing machine. However, a distributed dealing can flux from a Windows 2000 computing machine to any of these computing machines.
If you are running the Window NT 4.0 Option Pack, you can besiege this restriction by put ining either Windows NT 4.0 SP4 or SP5. If you are running Windows NT 4.0, you can besides besiege the job by put ining QFE 810, which is located at:
file transfer protocol: //ftp.microsoft.com/bussys/distapps/MTS/Public-Fixes/usa/DTC/SvcPack/
No spot is available for Windows 95, Windows 98, or Windows NT 3.51.
Reinstalling MS DTC After Installing Microsoft SQL Server & # 8482 ;
Whenever you install SQL Server 6.5, SQL Server 7.0, or any SQL Server 6.5 or SQL Server 7.0 SP release, you must reinstall MS DTC. This reinstallation is necessary because SQL Server Setup installs an disused version of MS DTC that is incompatible with Component Services on Windows 2000.
? To reinstall MS DTC on a non-clustered system
1. Stop the MS DTC service. Besides stop any services that depend on MS DTC, including Component Services, Microsoft SQL Server, Microsoft Message Queuing, and Microsoft COMTI.
2. Execute the Dtcsetup.exe plan, which is located in the System32 booklet.
3. Restart any services that depend on MS DTC.
? To reinstall MS DTC on a bunch with an bing MS DTC bunch
1. Use the MSCS Cluster Administrator to halt the MS DTC bunch resource. Besides stop any services that depend on MS DTC, including Component Services, Microsoft SQL Server, Microsoft Message Queuing, and Microsoft COMTI.
2. Execute the Dtcsetup.exe plan, which is located in the System32 booklet, on the node that controls the MS DTC bunch resource. When you are prompted to put in MS DTC on the other nodes in the bunch, run Dtcsetup.exe on those nodes.
Do non re-start any system until MS DTC Setup has been successfully run on all systems in the bunch.
3. Restart all systems and besides any services that depend upon MS DTC.
MS DTC Does Not Support
Rolling Ascents on MSCS Clusters
MS DTC does non back up turn overing ascents on MSCS bunchs. When you install MS DTC on a bunch, you must make the followers:
1. Stop MS DTC.
2. Upgrade MS DTC on all nodes in the bunch.
3. Restart MS DTC.
These stairss are necessary because MS DTC maintains a individual MS DTC log file for the full bunch, and the new information has been added to the MS DTC log file for the Windows 2000 release.
In-Memory Database
After measuring client feedback from the Microsoft Windows 2000 Beta Program, Microsoft has determined that the In-Memory Database ( IMDB ) does non wholly address the demands of most client scenarios. The IMDB does non back up question processing or stored processs, and it requires clients to implement a different database entree method.
The Transactional Shared Property Manager ( TSPM ) , which was built on top of IMDB, has besides been removed from Windows 2000. However, the Shared Property Manager engineering that was ab initio released with MTS in Windows NT 4.0 is still available with Component Services in Windows 2000.
For extra information about IMDB, see the & # 8220 ; What Happened to IMDB? & # 8221 ; subject on the MSDN Web site at:
hypertext transfer protocol: //msdn.microsoft.com/library/techart/whatimdb.htm
Removing COMTI Components with Component Services and Windows 2000
COMTI is a constituent of SNA Server 4.0 and subsequently. When you remove a COMTI constituent from a Component Services application, it does non vanish from the COMTI Remote Environment window glass. However, the constituent is removed from the COM+ Application Components window glass. Although this produces an inconsistent show, you can deploy a new constituent with the same Class ID without doing an mistake.
Microsoft Data Access Components
Microsoft Data Access Components ( MDAC ) is automatically installed with Windows 2000. To obtain the most current information about MDAC 2.5 and known MDAC issues, see the MDAC release notes, which are installed at:
*system drive* : Plan FilesCommon filesSystemADO
MDACReadme.htm
For more information about MDAC, see the Microsoft Universal Data Access Web site at:
hypertext transfer protocol: //www.microsoft.com/data/
Internet Servicess
The undermentioned subdivision describes Windows 2000 issues related to Internet services characteristics.
Internet Information Services
To obtain the most recent information about installing, certification, and other known IIS issues, type the undermentioned nexus into the address saloon of your browser ( or snap Start, chink Run, and type the nexus ) :
file: % systemroot % HelpIishelpIisHtmCoreReadme.htm
where % systemroot % is your Windows 2000 installing way, including thrust and directory ( for illustration, C: Winnt ) .
IIS is non installed by default on Windows 2000 Professional. If you can non see the IIS release notes from the nexus above, you need to put in IIS by utilizing Add/Remove Programs in Control Panel.
Client Certificate Is Not Trusted or Is Invalid
A job in the certification trusts list ( CTL ) may do the following 403.16 message to expose for valid certifications:
& # 8220 ; Client certification untrusted or invalid & # 8221 ;
As a workaround, put in a transcript of the root certification from the Trusted Root Certification Authorities to the Intermediate Certification Authorities shop for the Local computing machine. This will be addressed in a future release.
Can non Change Anonymous Account
IIS 5.0 restricts alterations to the Windows 2000 user history for anon. hallmarks that are made below the service degree and that contain an & # 8220 ; IUSR_ & # 8221 ; history prefix. This limitation ensures proper operation of the IUSR_computername history, which should non be altered in any manner. If you require multiple anon. hallmark histories, create new histories that do non incorporate the & # 8220 ; IUSR_ & # 8221 ; history prefix, assign history permissions to log on locally, and so add the histories to the Guest User group.
Microsoft Windows 2000 Server Media & # 8482 ; Servicess
The undermentioned subdivisions provide information and describe issues that affect Windows Media Services, an optional constituent of Windows 2000.
Loging Multicast and Unicast Client Information in Netscape Navigator
Netscape Navigator 3.04 may neglect to obtain the Uniform Resource Locator ( URL ) of the Web page that contains the embedded client. This prevents the client information & # 8212 ; the URL value of the Cs ( Referrer ) field & # 8212 ; from being decently logged when you use Netscape Navigator 3.04.
Using Windows Media Services Components and Microsoft Site Server with the Membership Authentication Plug-In
A known & # 8220 ; boot race & # 8221 ; job exists when you use Windows Media Services constituents with Microsoft Site Server version 3.0 and you have enabled the Site Server Membership Authentication circuit board. This circuit board does non lade when Windows Media Services starts, and clients can non link to Windows Media Services.
When this job occurs, the Windows 2000 Server Event Log service does non log the mistake. To verify the failure, usage Windows Media Administrator to link to Windows Media Services. Windows Media Administrator messages appear, bespeaking that the circuit board has non started and motivating you to re-start the Windows Media Unicast service.
As a workaround, re-start the Windows Media Unicast service.
HTTP Streaming Can Cause Mistakes
After enabling Hypertext Transfer Protocol ( HTTP ) cyclosis in the Windows Media Administrator, you must re-start your computing machine. Otherwise, the Windows Media Services Event Log fills up with mistake events.
Storage Notes
The undermentioned subdivisions describe Windows 2000 issues related to storage.
Offline Booklets
Do non utilize the Offline Folders characteristic with Distributed File System ( DFS ) volumes or portions.
File Systems
After you convert a FAT file system to NTFS, all files and booklets are set with the undermentioned Access Control List ( ACL ) :
? Administrators Full Control ( non inherited )
? System Full Control ( non inherited )
? Everyone Full Control ( inheritable )
You can repair the heritage scenes at the root of the volume in Microsoft Explorer.
? To repair the heritage scenes at the root of the volume in Microsoft Explorer
1. In Microsoft Explorer, right-click the root directory, and so snap Properties.
2. On the Security check, chink Advanced.
3. Double-click the Administrators entry.
4. On the Permission Entry page, alteration Apply onto: to This booklet, subfolders and files.
5. Double-click the System entry.
6. On the Permission Entry page, alteration Apply onto: to This booklet, subfolders and files.
7. Click OK.
Logical Disk Manager
This subdivision describes known issues that apply to the Logical Disk Manager.
Disks That Are Members of Fault & # 64979 ; Tolerant Sets ( Mirror or RAID & # 64979 ; 5 )
If you upgrade from a old version of Windows 2000, a disc that is a member of a fault-tolerant set ( mirror or RAID & # 64979 ; 5 ) may go orphaned during graphical user interface ( GUI ) & # 64979 ; manner Setup. No information is lost. You can utilize the Disk Administrator MMC snap-in to reconstruct the disc.
? To utilize the Disk Administrator MMC snap-in to reconstruct the disc
1. Get down the Disk Administrator MMC snap-in.
2. For a mirror disc, click Resynchronize Mirror, or for a RAID & # 64979 ; 5 disc, click Regenerate Parity.
The excess information for the volume is rebuilt.
Making Logical Drives Within Extended Partitions on Basic Disks
If you are upgrading from Windows NT 4.0 to Windows 2000 and you attempt to make logical thrusts within drawn-out dividers on basic discs, a thrust geometry interlingual rendition mistake may do the Logical Disk Manager to expose the undermentioned message:
& # 8220 ; Parameter is incorrect. & # 8221 ;
This may besides happen with natural installings on discs with no signatures. No workaround is available at this clip.
Converting System or Boot Volumes from Basic to Dynamic
You should change over system or boot volumes from basic to dynamic independent of any other volume transition. In peculiar, before you attempt to import discs from another computing machine, re-start your computing machine.
Mirroring Combined System & # 64979 ; Boot Volumes on Systems with OEM Partitions
Mirroring combined system & # 64979 ; boot volumes on systems with Original Equipment Manufacturer ( OEM ) dividers may necessitate excess attention. Whenever you mirror your system or boot divider, you should verify that the system starts from both the original and freshly created mirrored dividers. On systems with OEM dividers, complete the undermentioned stairss:
1. Ensure that the mark disc for the mirror is basic.
2. Make a basic divider equal to the size of the OEM divider.
3. Convert the disc to dynamic.
4. Mirror the system & # 64979 ; boot volume.
Backup
This subdivision describes known issues that apply to Windows 2000 Backup.
Backup of Remote Storage Files by Legacy Backup Applications
Legacy backup applications include Windows NT 4.0 and earlier versions of Backup, and besides any third-party backup applications that do non transport with Windows 2000 and make non acknowledge distant storage files. When utilizing bequest backup applications to back-up distant storage files which are migrated to tape, Remote Storage clears by default the files with the FILE_OPEN_NO_RECALL option and streams the migrated information from tape straight to the backup application. On a volume with big measures of distant storage files, this may bind up the waiter for long periods of clip as it reads the information from tape and streams it to the backup application. Besides, the bequest backup client may take an drawn-out period of clip to wholly backup the volume.
If you do non necessitate to backup the information in the distant storage files utilizing the bequest backup application, you can jump these files. On the waiter incorporating the distant storage files, if a register value of type REG_DWORD: exists and is set to a non-zero value for the HKEY_LOCAL_MACHINE SystemCurrentControlSet
ServicesRsFilterParametersSkipFilesForLegacyBackup register key, the distant storage files are skipped by the bequest backup application. By default this value is non present in the register. Therefore, you must add this to the register to jump the backup of distant storage files by the bequest backup application.
Caution
Falsely redacting the register may badly damage your system. Before doing alterations to the register, you should endorse up any valued informations on the computing machine.
? To jump the backup of distant storage files
* Cut and glue the undermentioned text into a.reg file, and burden it into the register by utilizing regedit.exe:
REGEDIT4
[ HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesRSFilterParameters ]
& # 8220 ; SkipFilesForLegacyBackup & # 8221 ; =dword:00000001
Restoring the IIS Metabase While the IIS Administration Service Is Runing
The IIS Administration Service does non keep open the metabase file. Therefore, if you restore the metabase file while the IIS Administration Service is running, the file is overwritten by the transcript in memory when the service shuts down. Then, when you restart the computing machine, the IIS-managed services do non work.
As a workaround, before reconstructing the IIS metabase, halt the IIS Administration Service and all the other IIS-managed services. If you do non hold the IIS Administration Service installed when you restore the IIS metabase, no action is required.
Restoring the System State from a Backup Set
When you restore the system province on a computing machine that is running Windows 2000 from a backup set, do non try to re-join the Windows sphere until after the system province has been restored. If you attempt to rejoin the sphere before the system province is restored, the computing machine may react with a message indicating that its computing machine history is losing.
Mounting Required Media During a Backup or Restore Operation
Do non utilize the Removable Storage Manager to mount tapes. When you perform a backup or restore operation, ever rely on Windows 2000 Backup to mount the needed media.
Computer Not in Domain After System State Restore
After you restore everything on the computing machine, you must rejoin the computing machine with the sphere, even though the Network Identification indicates that the computing machine is already portion of the sphere. If the computing machine does non rejoin the sphere, the undermentioned message appears:
& # 8220 ; Trust relation failure. & # 8221 ;
This occurs because the alone identifier for the computing machine on the web changed during the system province rebuild procedure. As a workaround, fall in a workgroup, re-start the computing machine, rejoin the sphere, and so re-start the computing machine once more.
Restoring Applications with Long File Names
In some instances, when you restore application with long file names, Microsoft Office applications may neglect after the restore operation. This failure occurs because some constituents ( specifically Office ) register the location of their double stars in the register utilizing the short name ( 8.3 name ) . This short name may indicate to an wrong location after the application is restored because the short name coevals is based upon which application was installed foremost. Therefore, after you restart the computing machine, you must reinstall the applications that failed.
Target Must Be every bit Large as the Original Backup Drive
You must execute the restore operation on dividers that are the same size ( or larger ) as the dividers that are backed up. In some instances, Windows 2000 Backup may run out of disk infinite while reconstructing to the same volume. As a workaround, do certain that sufficient free infinite is available for the restore operation. When Backup restores active files, it requires some excess disc infinite. Backup restores files to impermanent locations, and so moves them to the right location when you restart the computing machine. This procedure besides requires excess disc infinite.
Removing Merely One Piece of Media from a Backup from a Library
If you remove merely one piece of media from a backup from a library, you may lose informations. If you remove the first piece of media from a spanned save set and so choose the delete media from system option in Removable Storage Manager for any of the other elements of that save set, all media belonging to that save set on the thrust is erased. If you do non desire to wipe out your tapes, maintain all of your spanned save sets together.
Backup Fails to Get down a Scheduled Job Because the Incorrect Media is in the Drive
When an unexpected tape is mounted in the thrust, Windows 2000 Backup does non get down the scheduled backup operation. When Backup runs, it expects to compose to a specific piece of media. If this media is non in the thrust and you are non utilizing a modifier, the backup operation fails. No presentment of this failure is provided because the backup operation is running without the user interface ( UI ) . The backup log identifies the failure.
Backup Stops While Crossing Multiple Disks
When Windows 2000 Backup encounters a write-protected disc while crossing multiple discs, it stops running. As a workaround, do certain that none of the media utilizing for the backup operation is write-protected.
Backup Shows Incorrect Elapsed and Estimated Times
Windows 2000 Backup shows the elapsed and estimated times falsely. No workaround is available at this clip. You can disregard the displayed clip.
Backup Can non Detect If a Remote Drive Is Removable
Windows 2000 Backup can non observe if a distant thrust is removable. It assumes that all mapped thrusts are fixed discs. If a remotion storage device ( for illustration, a Jazz thrust ) is located and shared from another computing machine on the web, and the distant device is mapped to the local computing machine, Backup does non observe that the device is removable. As a workaround, do non map a distant thrust that is removable. Alternatively, execute the backup operation to a distant difficult disc, and so copy the files to the removable media.
Restore Does Not Acknowledge Media When Spanned Across Different Formats
The restore operation does non acknowledge media when it is spanned across different formats. If you restore informations that has been spanned across several pieces of media and if the file systems differ across the media ( for illustration, some media are in NTFS and some are in FAT ) , the restore operation does non acknowledge some media as being portion of the backup set.
Backing Up to an 8-mm AME Tape on an Exabyte EXB-220 Changer
When you back up to 8-mm AME tape on an Exabyte EXB-220 modifier, Windows 2000 Backup reports a & # 8220 ; write file grade & # 8221 ; failure. You should upgrade this microcode to the latest 6.4.3 version.
Files Located at the End of a Large Backup Set
Files that are located at the terminal of a big backup set may non reconstruct. This can impact 1000000s of files on informations volumes larger than 100 GB. As a workaround, you can utilize independent package seller ( ISV ) backups that usage self-loaders. Alternately, run your backup operation in sections ( get down lower in the volume tree ) .
Backup Restores Some Extra Files from Remote Storage Media
Windows 2000 Backup restores some extra files from Remote Storage media. When Backup is used to reconstruct tapes created by Remote Storage, extra files may be created. Distant Storage Manager uses these files, and they have no value outside of the this system. No workaround is available at this clip. You can disregard these files.
Path Names Greater than 1000 Fictional characters in Length
When way names are greater than 1000 characters in length, an entree misdemeanor occurs in NTBackup.exe. Avoid utilizing long way names for restore operations.
Restoring an Encrypted File
that has a File Hard-Linked to it
Restoring an encrypted file that has a file hard-linked to it destroys the nexus to the original file. You must manually re-link the file after the restore operation is completed.
Runing Backup over Terminal Servicess
When you run Windows 2000 Backup over Terminal Services, some scenes may acquire confused. Backing up thrust letters that are mapped on both the local computing machine and the distant computing machine may do Backup to halt responding at the prompt ( Task Manager ) for scheduled backup operations.
Restoring Exchange
If you attempt an Exchange restore operation, the Exchange Service must be running. If this service is non running, no options display for the Exchange restore operation.
Performing a Complete System Restore
If you perform a complete system restore operation from tape, you must first finish a minimum installing of Windows 2000 in the same directory as the old installing. If the directory or thrust is different, the system restore operation fails. Note that clean installings do non let an installing location other than the default directory. In the instance where the old installing was non in the default Winnt directory, you must finish a 2nd, minimum installing in the non-default location. If the
