Professional Web Hosting, Perl Scripting And Developing Blog

Part 3: Windows Server 2003 Upgrades and Migrations Upgrading to Windows Server 2003 . Make a dword entry (the name is arbitrary) with a value of 1 in the following registry node: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW3SVC RetainW3SVCStatus . If performing an unattended installation, set DisableWebServiceOnUpgrade=false (in the [Internet Server] section of the Unattend.txt file). The following are also some baseline changes in security configuration: . Default is more restrictive The default security settings for new installations of Windows Server 2003 are more restrictive than Windows 2000 Server (or Windows NT 4). Windows Server 2003 Setup will, however, retain existing security settings during an upgrade (i.e., the existing security configuration will not be enhanced by upgrading). . Internet Explorer is more restrictive Internet Explorer is set up with an enhanced security configuration, which by default disables scripting, ActiveX controls, file downloading, and the browser virtual machine. Also, Internet zone security settings are set the same as Restricted zone, and by default all sites are assigned to the Internet zone. Pass-through authentication of user credentials is blocked outside of the Local Intranet zone. These Internet Explorer settings can be configured by using the Advanced tab of the Internet Options icon on Control Panel. . Downloading software updates Because of the security enhancements set in Internet Explorer, you might be unable to download software updates from the Internet until you add those sites to the Trusted zones. Verify an Upgrade Recovery Plan Because upgrade processes can and do err, verify that you have an effective recovery plan in place prior to commencing with an upgrade. Likewise, a migration can include removing information from the source domain; thus, prior to either an upgrade or migration, you should make sure that you have verified backups. You can create an image of the system partition prior to upgrading so that you can restore its original state quickly if needed. Verify the method of backup (network share, CD, DVD) and restoration (network connectivity, imaging software, drivers, etc.) before beginning an upgrade or migration. Create the Emergency Repair Disk in case the upgrade does not complete successfully. If you are upgrading an existing Windows 2000 domain or forest, the Active Directory schema information must be updated before you can begin. Run the Active Directory Preparation Wizard (Adprep.exe) with the /Forestprep parameter to upgrade the forest data and with the /Domainprep parameter to upgrade the domain information. Normally, this process is successful, but it can fail, and, worst case, it can render the domain controller inoperative. To ensure that you can recover from such disasters, you should do a full backup of two domain controllers from each domain in the forest before running the ADPREP /FORESTPREP command and verify the backup media. Chapter 8
We recommend high quality webhost to host and run your jsp application: christian web host services.

Part 3: Windows Server 2003 Upgrades and Migrations Chapter 8 Microsoft Windows Server 2003 Inside Out Upgrade Issues A range of network services and applications require consideration and preparation prior to upgrading the hosting servers. . Itanium (IA-64) versions of Windows Server 2003 The Itanium (IA-64) versions do not support 16-bit applications (with the exception of Microsoft Windows Acme setup), nor do they support 32-bit device drivers. Likewise, 32-bit drive management utilities and 32-bit antivirus programs do not operate on 64-bit versions of Windows Server 2003, and the 32-bit Web components cannot be loaded in the 64-bit version of Microsoft Internet Explorer. . UDDI and SQLXML You can t run Universal Description, Discovery, and Integration (UDDI) and Microsoft SQL Server 2000 Web Release (SQLXML) on the same machine because of their differing requirements for Microsoft Internet Information Services (IIS) support. SQLXML requires the Isolation mode used by IIS 5, while UDDI uses the new worker process Isolation mode of IIS 6. . Cluster service Upgrading Windows 2000 Cluster service to Windows Server 2003 Cluster service requires that you restart the Cluster service. To restart this service, you must log on using an account that is a member of both the local Administrators group as well as the Domain Admins group. When you upgrade from Windows NT Cluster service, the security descriptor does not contain the system security identifier, or SID (see Microsoft Knowledge Base article 812876). . Windows 2000 SP3 required for Windows Server 2003 admin tools Windows Server 2003 administrative tools can be used only to manage Active Directory on a server running Windows 2000 Server if it has Service Pack 3 (SP3) or is using unsigned Lightweight Directory Access Protocol (LDAP) traffic. Inside Out IIS is not installed by default Although there are many changes in IIS between Windows 2000 and Windows Server 2003, the key change of interest here is that it is no longer installed by default if IIS isn t already installed on the server that you are upgrading to Windows Server 2003, it won t be installed during the setup process. Even if IIS is installed, it will not be started automatically when the server starts up, even if it was configured to do so before the upgrade. Security is tighter by default on new installations of IIS in Windows Server 2003, yet if you upgrade an existing IIS Web server, the Windows Server 2003 default security constraints will not be applied to this installation. For further information on IIS 6, see IIS 6 Administrator s Pocket Consultant, by William R. Stanek (Microsoft Press, 2003). You can either set the service to start automatically after installation or preconfigure the system to support IIS. To enable IIS to retain its operational status after the upgrade, you must prepare the server by performing the following steps: . Secure the IIS server by using the IIS Lockdown Tool, which is available at http:// www.microsoft.com/windows2000/downloads/recommended/iislockdown/default.asp. 230
You need excellent and relaible webhost company to host your web applications? Then pay a visit to Inexpensive Web Hosting services.

Part 3: Windows Server 2003 Upgrades and Migrations Chapter 8 Upgrading to Windows Server 2003 General Considerations for Upgrades . . 229 Upgrading from Windows NT 4 . . . . . . . 245 Upgrading from Windows 2000 . . . . . . 232 Whether you can upgrade an existing server to Microsoft Windows Server 2003 depends on hardware compatibility, available disk space, and adequate hardware resources (such as the CPU and RAM). Upgrading to Windows Server 2003 is also dependent upon the existing Windows version on the target system Setup will only upgrade Microsoft Windows NT 4 Server (with Service Pack 5 or later) and Microsoft Windows 2000 Server to Windows Server 2003. To upgrade to Windows Server 2003, you must take into account different considerations depending upon whether you are currently running a Windows NT 4 network environment or a Windows 2000 based network with the Active Directory directory service already implemented. Yet there are also issues common to each of these scenarios, such as whether the server hardware is adequate. For many companies running Windows NT 4 servers, it is questionable whether the server hardware can adequately support Windows Server 2003 operational requirements. General Considerations for Upgrades Before you begin the upgrade process, you must consider several areas of information, including the most basic, such as whether your existing hardware and software support upgrading to Windows Server 2003. If upgrades are not supported, starting off with a new installation on new server hardware and migrating the user and group information to the new server might be your only option. You can upgrade a system to Windows Server 2003 only if you re currently running Windows NT 4 Server with Service Pack 5 or later or a Windows 2000 Server platform. Further, servers running Windows NT 4 Enterprise Edition or Windows 2000 Advanced Server must be upgraded to Windows Server 2003, Enterprise Edition. Additionally, Windows 2000 Server using the Remote Storage service must be upgraded to the Enterprise Edition of Windows Server 2003.
Searching for affordable and proven webhost to host and run your servlet applications? Go to Linux Web Hosting services and you will find it.

Part 3: Windows Server 2003 Upgrades and Migrations Microsoft Windows Server 2003 Inside Out Chapter 7 The following are additional factors to review: . Disk partitions Assess the disk partitions on the servers you want to upgrade. Certain constraints apply to upgrades; you cannot upgrade servers on a FAT partition, for instance, or those using Windows NT 4 fault-tolerant configurations. . Windows services Consider whether you want to phase out some legacy services, such as WINS. Don t be too hasty, though; by leaving the service installed and running for a while after the upgrade, you can ensure that network operations will continue uninterrupted during the transition away from the old service. . Windows applications Look at your existing applications and assess their functionality and compatibility. Check compatibility issues carefully because there are likely to be issues with each application. Don t rely on just what the vendor has to say do a bit of additional sleuthing, check out newsgroups (both at the vendor s site and public ones), ask colleagues what they have encountered, and so on. Tip No more POSIX or OS/2 support If you currently have applications that are operating in either the POSIX or OS/2 subsystem in a Windows NT 4 environment, you must replace these applications, because those subsystems are no longer supported. Alternatively, you could leave a server, or a few servers, in place to support the older applications. In either case, this is a decision to make early in the process, so the changeover is completed in plenty of time, and the impact on the network can be managed. 228
Searching for affordable and proven webhost to host and run your servlet applications? Go to Linux Web Hosting services and you will find it.

Part 3: Windows Server 2003 Upgrades and Migrations Preparing for Upgrades and Migration Note Windows NT 4 groups are converted for Active Directory When upgrading Windows NT 4 to Windows Server 2003, local groups are upgraded to domain local groups, and global groups are upgraded to Active Directory global groups. Down-level clients continue to see the upgraded groups as their Windows NT 4 equivalents and will regard universal groups which don t exist in Windows NT as global groups. Upgrading Windows NT 4 Servers When you re upgrading servers that run Windows NT 4, you are likely to encounter incompatible or inadequate hardware, so you should give the system hardware and installed software a thorough review. After all, the baseline requirements for Windows NT 4 server hardware are quite a bit lower than for Windows Server 2003, which requires a minimum of a Pentium 133-megahertz (MHz) processor, 128 MB of RAM, and more than 2 GB of disk space. Another thing to remember is that Windows Server 2003 might not support some of the adapters and devices used in Windows NT 4 systems. As a result, you should expect to upgrade at least some components of the Windows NT 4 server hardware (upgrading the network adapter, for example, or adding a hard disk) to facilitate reasonable performance under Windows Server 2003. Chapter 7 For more information about the compatibility of specific adapters and devices, see the Windows Server Catalog at http://www.microsoft.com/Windows/catalog/server and the Hardware Compatibility List at http://www.microsoft.com/whdc/hcl/search.mspx. Inside Out Minimum requirements do not yield optimal results Technically, Windows Server 2003 will run on a 133-MHz Pentium with 128 MB of RAM. Performance would be far from optimal, however, and it is questionable whether such a server would actually make it into a production environment or how long it would last if it did. Consider the size of your network and the expected load on the server, and decide whether each upgraded server will perform adequately in your environment. If not, replace it if possible. Hardware is relatively inexpensive, especially when compared with the long-term costs and inconvenience brought about by using an outdated, inadequate, or unstable system.
If you are looking for affordable and reliable webhost to host and run your business application visit our ftp web hosting services.

Part 3: Windows Server 2003 Upgrades and Migrations Microsoft Windows Server 2003 Inside Out Chapter 7 additional Windows NT domain hitting the maximum number of objects is no longer an issue. There are benefits to having fewer domains, such as faster searches, fewer domain controllers, simplified management, and a network that is easier to use. Unfortunately, there are also likely to be roadblocks to eliminating domains politics and inertia, to start with. For more information about the Active Directory planning process, see Part 7, Managing Active Directory and Security. You must design the DNS namespace(s) for Active Directory (the domains and domain trees), as well as any additional DNS domains you want to support. Determine which Windows NT domains will be maintained, whether additional domains will be added, and where in the DNS domain tree(s) each of your existing domains will go. When you upgrade each domain s primary domain controller, you must know where in the DNS namespace that specific domain is assigned. Caution Support for Windows NT 4 domain controllers is provided in the initial Active Directory configuration, but it is dropped once you switch the domain to Windows Server 2003 functional level. Make sure that you are really finished using Windows NT before making the switch. You can t go back once you make the change. Restructuring Domains If you re upgrading domains from Windows NT 4 to Windows Server 2003 on a one- to-one basis, you will initially have multiple (perhaps many) domains. If so, you can collapse multiple domains into a single one to simplify your Active Directory implementation. You can perform the domain restructure operations at two times: . Restructuring domains after upgrading In most circumstances, you will want to upgrade the domain controller and then migrate the user, group, and computer accounts settings to domains in your actual Active Directory forest. This method frees you from the Windows NT 4 limitations and allows you to take advantage of the ADMT as a means of restructuring your domains. . Restructuring domains before upgrading If you have only a few domains to merge, you can restructure your Windows NT 4 domains prior to upgrading to Windows Server 2003. You must keep in mind, however, that all the standard Windows NT 4 limitations apply. This means that if the Security Accounts Manager (SAM) database will get too large or replication traffic will be an issue, you should wait to restructure domains until after you have upgraded the server. Remember that the domain controllers from a domain that is subsumed go offline, so make sure there are no additional services or applications running on them before making the change. 226
In case you need quality webspace to host and run your web applications, try our personal web hosting services.

Part 3: Windows Server 2003 Upgrades and Migrations Preparing for Upgrades and Migration Preparing for an Upgrade from Windows NT 4 to Windows Server 2003 Upgrading from a Windows NT 4 networking environment requires a substantial amount of assessment and planning. The move from a network environment employing Windows NT domains to a network based upon Active Directory is a major change, and one with far- reaching implications. In addition to the technical aspects of shifting from a NetBIOS-based network to one centered on DNS and LDAP, there are administrative issues for IT management, and the business side of the company is sure to have opinions concerning information management. Although Active Directory might be the most significant change from Windows NT to Windows Server 2003, it is by no means the only one. Many additional services (particularly Internet-related ones) have been added when Windows NT shipped, after all, the Internet was but a small blip on Microsoft Corporation radar. Namespace in Windows NT vs. Active Directory Each Windows NT 4 domain is a single flat namespace with no internal or external hierarchy, while Active Directory domains exist within a DNS tree where each domain can map to a domain within the Active Directory tree. A single Windows NT domain can contain users and a few types of resources (such as file servers), and on many small networks, they do. There are significant limits on the number of objects per Windows NT domain the theoretical limit is 40,000, yet few servers running Windows NT perform well when approaching that limit. Accordingly, many Windows NT 4 networks employ multiple domains linked by trust relationships that are manually configured (sometimes laboriously so) to allow user authentication and access to resources. Active Directory transcends these Windows NT limitations: a single Active Directory domain can hold millions of users, servers, computers, and many additional kinds of objects representing a major shift in network management. By providing effectively limitless domains and automatic trusts, Active Directory offers domain structures based on IT functionality, not product limitations. Moving from Windows NT Domains to Active Directory You have to move your existing domain structure from one to the other from multiple independent domains linked by explicit trust relationships to a single tree with a domain hierarchy, wherein all domains automatically trust each other. This is a big change, and it is a good idea to take a step back from your existing domain design when considering what your Active Directory domain tree will look like. Domain design is different in Windows Server 2003; remember, the most common reason for adding an Chapter 7
Note: If you are looking for cheap and reliable webhost to host and run your mysql application check mysql web server services.

Part 3: Windows Server 2003 Upgrades and Migrations Microsoft Windows Server 2003 Inside Out Chapter 7 Following are the results of storing DNS data in various locations: . DNS zone files leave replication to DNS and require administrative configuration. . Windows 2000 Active Directory integrated zones cause DNS data to be replicated to all domain controllers in the domain. . The forest application partition (ForestDnsZones) causes the DNS data to be replicated to all DNS servers in the forest. . The domain application partition (DomainDnsZones) causes the DNS data to be replicated to all DNS servers in the domain. Identify Server Roles You must identify the network services and server roles that an upgraded server or domain controller will need to perform. Network services commonly employed include DNS, Dynamic Host Configuration Protocol (DHCP), Windows Internet Naming Service (WINS), Routing and Remote Access Service (RRAS), Terminal Services, and Internet Authentication Service (IAS). Depending upon expected load, servers can host one or more network services. Carefully assess servers that are domain controllers review your ability to upgrade the server hardware and which secondary roles (such as global catalog server) the server will perform. Consider server performance and operational requirements for domain controllers on your network. Although large networks commonly have dedicated DNS servers, on small networks a server might provide multiple network services (such as DNS and DHCP) in addition to domain controller roles such as Active Directory access, Kerberos, and global catalog operations. Evaluate which operations master roles the domain controller will support; forest-wide roles (Schema Master and Domain Naming Master) and/or domain-wide roles (RID Master, Infrastructure Master, and PDC Emulator). Tip The PDC Emulator supplies the Windows Time Services to synchronize all other domain controllers in the domain servers that are assigned this role should receive particularly close scrutiny to ensure system reliability. For upgrades from Windows 2000, you can continue to use the assigned operations master roles, yet operations master roles must be determined for each domain controller when upgrading a Windows NT 4 domain controller. For more information on operations master roles, see the section entitled Establishing Operations Masters on page 248. 224
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.

Part 3: Windows Server 2003 Upgrades and Migrations Preparing for Upgrades and Migration To raise the forest functional level, you must be logged on using an account that is a member of the Domain Admins group in the forest root domain or a member of the Enterprise Admins group in Active Directory. Start Active Directory Domains and Trusts, and right-click the root node, then select the Raise Forest Functional Level option. In the Raise Forest Functional Level dialog box, select an available forest functional level, and click Raise. The operation cannot be reversed. All domains in the forest must be at Windows Server 2003 domain functional level to be able to change to the Windows Server 2003 forest functional level. If you are unable to raise the forest function level, click Save As in the Raise Forest Functional dialog box to save a log file detailing the domain controllers in the forest that still need to be upgraded from Windows NT or Windows 2000. You can raise domain functional levels in much the same way. Again, you must be logged on using an account that is a member of the Domain Admins group in the forest root domain or a member of the Enterprise Admins group in Active Directory. Start Active Directory Domains and Trusts, right-click the domain, then select the Raise Domain Functional Level option. In the Raise Domain Functional Level dialog box, select an available domain functional level, and click Raise. The operation cannot be reversed. Make sure you understand the implications of raising functional levels before you do this. See Choosing Domain and Forest Functional Levels, earlier in this chapter, for details. Identify DNS Namespace and Storage DNS is central to network operations in Windows Server 2003. Active Directory domains use DNS for locating domain controllers, global catalog servers, Kerberos Key Distribution Centers (KDCs), and for using Lightweight Directory Access Protocol Uniform Resource Locators (LDAP URLs). Upgrading a Windows NT network requires a defined DNS namespace, as well as organized DNS services and replication (as described in Chapter 2). Identify the DNS domain information that will be required during the upgrade, as follows: . When upgrading Windows NT 4 domain controllers, you must implement the domain controller within the context of your IT namespace, planning for DNS and Active Directory. . When upgrading Windows 2000 domain controllers, in most situations you will leverage the existing DNS namespace. Consider whether the (upgraded or migrated) server(s) will be supporting DNS. If the server will be a DNS server, how you choose to store the DNS zone records has implications for replication of the DNS information. You can store DNS zone records in traditional zone files, in Windows 2000 Active Directory integrated zones, or in the new forest and domain application partitions. Chapter 7
From our experience, we are can tell you that you can find a reliable and cheap webhost service at Java Web Hosting services.

Part 3: Windows Server 2003 Upgrades and Migrations Chapter 7 Microsoft Windows Server 2003 Inside Out An important limitation for upgrading servers that run Windows 2000 is that Windows Server 2003 cannot be installed on a dynamic disk partition in a certain situation if Windows 2000 was installed on a disk without any partitions and configured directly as a dynamic disk volume, Setup will fail. You must first revert the dynamic disk partition to basic or remove the partition during setup and create a new basic partition. Dynamic disk partitions can be reestablished (by using Disk Administrator) once Windows Server 2003 is installed. Choosing Domain and Forest Functional Levels In evaluating the upgrade or migration path, determine the forest and domain functional levels needed for your network environment (functional levels determine the types of domain controllers and features supported). Table 7-2 shows the types of domain controllers supported by each functional level. Table 7-2. Domain Controllers and Functional Levels Types of Domain Controllers on Network Domain Functional Level Forest Level Windows NT 4, Windows 2000, Windows Server 2003 Windows 2000 Mixed Windows 2000 Windows 2000, Windows Server 2003 Windows 2000 Native Windows 2000 Windows NT 4, Windows Server 2003 Windows Server 2003 Interim Windows Server 2003 Interim Only Windows Server 2003 Windows Server 2003 Windows Server 2003 Advantages to Windows Server 2003 forest functional level include replication enhancements (Active Directory, global catalog, group membership), deactivating schema objects, dynamic auxiliary classes, forest-level trusts, domain renaming, linked value replication, InetOrgPerson password handling, and tracking the last logon time. Inside Out Setting the functional levels Upgrading the first domain controller from Windows 2000 to Windows Server 2003 assigns the forest functional level to Windows 2000 and the domain functional level to Windows 2000 Mixed. For an upgrade from Windows NT 4 to Windows Server 2003, the domain and forest are set to Windows Server 2003 Interim function level. 222
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.