Professional Web Hosting, Perl Scripting And Developing Blog

Part 3: Windows Server 2003 Upgrades and Migrations Microsoft Windows Server 2003 Inside Out If the server hardware includes a Small Computer System Interface (SCSI) hard disk drive subsystem, Windows Server 2003 might not provide drivers to support it, and you might need to use a driver from the vendor of the SCSI subsystem. To use a vendor-supplied driver during Setup, you must have it on a floppy disk. Press F6 at the beginning of the setup process (a Press F6 message is displayed on screen) to tell Setup to use this alternative SCSI driver. Chapter 8 Tip Determine driver compatibility When it is not clear whether your SCSI or other mass storage device driver will be compatible with Windows Server 2003, you can determine this by beginning the installation process. Setup will detect whether it recognizes the mass storage device hardware and has a device driver for it; if it does not, it will stop and display an error regarding the disk or controller. Upgrading Different Versions of Windows NT 4 For each server running Windows NT 4 that you are upgrading, evaluate the existing operating system and determine to which version of Windows Server 2003 you can upgrade. To select a version, assess the following: . If upgrading from Windows NT 4 Server, you can upgrade to either Windows Server 2003, Standard Edition, or Enterprise Edition. . If upgrading from Windows NT 4 Server Enterprise Edition, you must upgrade to Enterprise Edition. . If upgrading an earlier version, such as Windows NT 3.51, you must upgrade to Windows NT 4 and then upgrade to Windows Server 2003. All four versions of Windows Server 2003 (Standard, Enterprise, Datacenter, and Web) run on the Intel 32-bit platform, yet only the Enterprise and Datacenter versions run on the Intel Architecture 64 (IA-64) platform. Tip Only a limited subset of Terminal Services functionality is supplied in Standard Edition for full Terminal Services functionality, the Enterprise Edition of Windows Server 2003 is required. Inside Out Datacenter Edition is not an upgrade option Windows Server 2003, Datacenter Edition, is not available as a stand-alone operating system, and it is not available as an upgrade product. The Datacenter Edition is original equipment manufacturer (OEM) provided only, installed and configured on vendor-supplied hardware (from vendors such as Hewlett-Packard, Dell, and many others). 246
We would like to recommend you tested and proved virtual web hosting services, which you will surely find to be of great quality.

Part 3: Windows Server 2003 Upgrades and Migrations Upgrading to Windows Server 2003 How to Create DNS Partitions Manually The new DNS application directory partitions are created automatically by the Active Directory Installation Wizard (Dcpromo) when it configures DNS for Active Directory. Yet, if the automatic DNS configuration is bypassed (by you opting for manual configuration), the default DNS application partitions (ForestDnsZones and DomainDnsZones) are not created. To create the default DNS application partitions, you can use the DNS admin tool or the DNS command-line tool. Type the following: dnscmd ServerName /Createbuiltindirectorypartitions /Forest (or /Domain or /Alldomains). Upgrading from Windows NT 4 When upgrading servers that run Windows NT 4, review the system hardware, network services, and application software on the server. You must verify that the hardware will run Windows Server 2003, determine which Windows Server 2003 product is needed, and identify the required network services. You also must check for configuration issues, such as whether the Windows NT 4 server is using a fault-tolerant drive configuration. Determine Server Hardware Compatibility When preparing to upgrade servers running Windows NT 4, you might find server hardware that is incompatible and/or that would provide marginal performance for running Windows Server 2003. This is because the requirements to operate Windows NT 4 (486/33, 16 MB of RAM, 124 MB of disk space) are substantially lower than the hardware requirements to run Windows Server 2003. Windows Server 2003 hardware requirements demand a minimum of a Pentium 133-MHz processor (Datacenter Edition, however, requires at least a 400-MHz processor), 128 MB of RAM, and 1.5 GB of hard disk space (2 GB for an upgrade). Because adapters in servers that run Windows NT 4 are less likely to be supported than equivalent hardware in servers that run Windows 2000, you should closely evaluate compatibility issues by checking the Windows Server Catalog at http://www.microsoft.com/Windows/catalog/ server and Microsoft s Hardware Compatibility List (HCL) at http://www.microsoft.com/ whdc/hcl/search.mspx. You can and should check the compatibility of server hardware prior to upgrading to Windows Server 2003. You can check hardware compatibility by using either of the following methods: . Type winnt32 /Checkupgradeonly at the command line (in the I386 folder on the Windows Server 2003 distribution CD). . Select the System Compatibility option on the Setup menu. Regardless of whether you use the preceding compatibility checks, Setup will perform the compatibility analysis at the beginning of the upgrade and will report the results on-screen and store them in the %SystemRoot% folder (in the Upgrade.txt file). Chapter 8
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.

Part 3: Windows Server 2003 Upgrades and Migrations Microsoft Windows Server 2003 Inside Out Chapter 8 schema master For the Schema Master role domain naming master For the Domain Naming Master role 8 Type quit at the Fsmo Maintenance prompt, and type quit at the Ntdsutil prompt. Upgrading Windows 2000 Users and Groups During an upgrade of a server (or domain controller) running Windows 2000, the local (and domain) user information, including profiles, rights, permissions, and group memberships, is retained. With minor changes (in universal groups), Windows 2000 groups are directly upgraded to the same groups in Windows Server 2003. One of the main changes (from Windows 2000) in the handling of universal groups is that the universal group information is cached on local domain controllers and no longer must contact a global catalog to authenticate a member. Windows 2000 Member Server Upgrades Upgrading Windows 2000 member servers to Windows Server 2003 is comparatively more straightforward than upgrading domain controllers. You still must assess the server hardware and verify its compatibility with Windows Server 2003, and you must determine whether it meets the baseline hardware requirements for the CPU (at least 128 megahertz [MHz]), 256 MB of RAM, and 2 GB or more of hard disk space. At this point, you should review your IT planning information regarding servers that provide key network services, specifying servers to upgrade and identifying network operating system (NOS) version, services provided, and order of implementation. You must check the network services that are running on the member server and review for any specific considerations or configuration issues that must be taken into account prior to, or immediately following, the upgrade process. Your planning information should define the servers to upgrade, identify installed and updated NOS versions, and specify the roles and services the servers will provide postupgrade. Upgrading DNS Services Upgrading Windows 2000 DNS to Windows Server 2003 is mostly a transparent upgrade with some enhancements to DNS namely, the capability to create application directory partitions to store DNS records that are used to replicate DNS information on a domain- wide and forest-wide basis. In Windows 2000 Active Directory integrated zones, all domain controllers in the domain receive the DNS replications. To remain compatible with Windows 2000 domain controllers hosting integrated zones, when you choose a replication option, opt to replicate the DNS records to all domain controllers in the domain. Once you ve upgraded fully to Windows Server 2003, you change the replication so that only domain controllers that are also DNS servers get DNS information. 244
Searching for affordable and reliable webhost to host and run your web applications? Go to our java web server services and you will be pleased.

Part 3: Windows Server 2003 Upgrades and Migrations Upgrading to Windows Server 2003 Changing Operations Masters You must be prepared to seize (that is, forcibly take) the operational master roles held by the domain controller being upgraded in the event that the upgrade is unsuccessful. . To seize the Infrastructure Master, RID Master (which pertains to relative identifiers, or RIDs), and PDC Emulator roles, in Active Directory Users and Computers, right- click the domain, select Operations Master, then click the needed RID, PDC, or Infrastructure tab. Select Change to transfer the operations (RID, PDC, or Infrastructure) master role to the target server. . To seize the Domain Naming Master role, in Active Directory Domains and Trusts, right-click the Active Directory Domains And Trusts node, and select Operations Master. Select Change to switch the Domain Naming Master role to another server. . To seize the Schema Master role, in the Active Directory Schema tool, right-click the Active Directory Schema node, and select Operations Master. Select Change to transfer the Schema Master role. . To seize the Global Catalog role, in Active Directory Sites and Services, navigate to SitesDefault-First-Site- NameServersServerNameNTDS Settings, right-click the NTDS Settings node, select Properties, and then click the Global Catalog option. You can also seize roles from the command line: 1 Ensure that the current domain controller with the role you want to seize is permanently offline. If the server can be brought back online, don t perform this procedure unless you intend to completely reinstall this server. 2 Log on to the console of the server you want to assign as the new operations master. You can log on to the console locally or by using Remote Desktop. 3 Click Start, click Run, type cmd in the Open box, and then click OK. 4 At the command prompt, type ntdsutil. This starts the Directory Services Management tool. 5 At the Ntdsutil prompt, type roles. This puts the utility in Operations Master Maintenance mode. 6 At the Fsmo Maintenance prompt, type connections, and then, at the Server Connections prompt, type connect to server followed by the fully qualified domain name of the current Schema Master for the role, such as: connect to server engdc01.technology.adatum.com 7 Once a successful connection is established, type quit to exit the Server Connections prompt, and then, at the Fsmo Maintenance prompt, type seize and then the identifier for the role to seize. The identifiers are as follows: pdc For the PDC Emulator role rid master For the RID Master role infrastructure master For the Infrastructure Master role Chapter 8 243
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.

Part 3: Windows Server 2003 Upgrades and Migrations Microsoft Windows Server 2003 Inside Out Chapter 8 Tip To use Windows Server 2003 administration tools with Windows 2000 domain controllers, you must install Service Pack 3 (or later) on your Windows 2000 domain controllers. To perform an interactive upgrade process, complete the following steps: 1 Insert the CD, and select Install. 2 Setup checks compatibility, shows the compatibility screen, and then writes the Upgrade.txt file to %SystemRoot%. 3 Setup copies installation files and then reboots. 4 Setup presents the option to perform an upgrade or a new installation; you should select to perform an upgrade. 5 Setup copies files, configures settings, finalizes installation, and then reboots. Upgrading Windows 2000 Domains Other than the schema changes made using the Active Directory Preparation tool, Windows 2000 domains remain logically and operationally the same after upgrading to Windows Server 2003. Similarly, domain functional levels stay the same after upgrade: . If you are currently operating in Windows 2000 Mixed mode, upgrading leaves the domain functional level at Windows 2000 Mixed. . If you are currently operating in Windows 2000 Native mode, upgrading leaves the domain functional level at Windows 2000 Native. Depending upon the range of Windows server operating systems you are supporting on your network, you might want to raise the domain and forest functional levels after upgrade. For example, if after upgrade you are using Windows 2003 domain controllers, and you don t need to support domain controllers running earlier versions of Windows, you can gain extra functionality by changing the Windows Server 2003 domain and forest levels. Selecting Active Directory Functional Levels When you have upgraded all of the domain controllers in your environment to Windows Server 2003 Active Directory, you can then raise the forest and domain functional levels to Windows Server 2003, which enables an entire set of new features. You can change the domain and forest functional levels using the Active Directory Domains and Trusts administrative tool. . To modify the functional level of a forest, right-click the Active Directory Domains And Trusts node, and select Raise Forest Functional Level. . To modify the functional level of a domain, right-click the domain name, and select Raise Domain Functional Level. 242
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.