Professional Web Hosting, Perl Scripting And Developing Blog

Part 3: Windows Server 2003 Upgrades and Migrations Chapter 9 Microsoft Windows Server 2003 Inside Out Automated Migration By creating customized scripts (using variables such as %UserName%) to collect and restore user state information, and using Remote Installation Services (RIS) with tailored answer files to automate the new operating system (OS) installation, you can completely automate the migration process. This can minimize the amount of IT labor required, yet demands a bit more planning and design. User-Driven Migration Although not the method most likely to be used in most corporate networks, having users perform the migration process by using the File and Settings Transfer Wizard can minimize IT labor and can allow the users greater discretion in the movement of their information from one computer to another. Preparing for Migration To prepare to migrate your servers or domains to Windows Server 2003, you must identify the specific users, groups, services, computers, domains, and trust relationships that are within the scope of the migration. Identify the source domain that contains the information (users, groups, etc.) from which you want to migrate, and identify the destination (target) domain to which this information will be migrated. To document the migration, enable auditing on both the source and destination domains by using either of the two following methods: . In Windows 2000 and Windows Server 2003, start Active Directory Users and Computers. Right-click the domain you want to work with, and select Properties. In the Group Policy tab of the Properties dialog box, select the domain policy, and then click Edit. This displays the Group Policy Object Editor. In the Group Policy Object Editor, expand Computer Configuration, Windows Settings, Security Settings, Local Policies, and then select Audit Policies. In the right pane, double-click Audit Account Management, and then select Define These Policy Settings. Under Audit These Attempts, select Success and Failure, and then click OK. . In Windows NT, load User Manager for Domains, go to Policies, click the Audit menu option, enable Audit These Events, and select both Success and Failure for User And Group Management. Prior to actually performing a migration, it is useful to perform a test run to determine its effects (by viewing the logs and reports generated). To test first, select the Test The Migration Settings And Migrate Later option in each of the ADMT wizards. By doing this, you can identify errors that occur in the migration of security principals or domain information and can correct the underlying configuration factors that caused any errors before performing the actual migration. By repeating this process of doing a test run and correcting errors, you can eliminate errors in the migration. 256
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.

Part 3: Windows Server 2003 Upgrades and Migrations Migrating to Windows Server 2003 When migrating user accounts, user names are limited to 20 characters in length anything beyond 20 characters is ignored. Tip Null values in source domains do not overwrite values in the destination domain. Commonly, when you migrate from Windows NT Server 4, the network environment is structured into Windows NT account domains and Windows NT resource domains. During the migration process, the user and group information is copied from the account domains, and the service account and local group information is copied from the resource domains. All this information is integrated into the destination domain. When migrating from Windows NT, always migrate the account domains first and then the resource domains this will establish the user and group accounts prior to migrating resource permissions referencing those accounts. Determining the Approach to Migration You can use a variety of approaches when migrating the systems on your network. These approaches can be categorized as manual, scripted, automated, and user-driven. Manual Migration The manual migration approach uses USMT and includes the following steps: 1 Acquire the user state information (by using Scanstate.exe). 2 Deploy the new operating system. 3 Load the new operating system with the user state information (by using Loadstate.exe). Chapter 9 Tip Manual migration is Information Technology (IT) labor-intensive, doesn t scale, and has increased error potential. Scripted Migration Scripted migration requires that you write migration scripts to acquire and load user state information; yet, once written, the migration process involves the following steps: 1 Use scripts to acquire user state information. 2 Use the scripts for unattended installation of the new operating system. 3 Use the scripts to load user state information into the new operating system (requires you to log on as Administrator). Tip Although it still requires significant IT labor, scripting the migration can reduce error potential and speed migration.
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 Microsoft Windows Server 2003 Inside Out Chapter 9 Movetree is used to do the following: . Move security principals to a new domain and delete them from the source domain . Migrate user passwords Normally, you should use ADMT to migrate users, computers, and groups; use Movetree to move directory objects that are not migrated by ADMT (such as members of default groups such as Administrators or Domain Admins). Third-Party Migration Tools Independent vendors produce migration tools that provide much of the same functionality as the Microsoft tools. Each product is different, however, and the features and benefits of each must be evaluated in the context of your migration environment and process. Following are two third-party tools: . Quest Fastlane Migrator http://www.quest.com/migrator/ . Aelita Enterprise Directory Manager http://www.aelita.com General Considerations for Migrations Consider your source and destination (target) domains involved in the migration. The target domain must be an Active Directory domain running in Native mode (either Windows 2000 or Windows Server 2003). When evaluating your migration scenario, you must determine which types of migration you can do. There are two types of migrations: . Interforest migrations Migrating from a Windows NT domain or a different Active Directory forest. . Intraforest migrations Migrating from an Active Directory domain within the current forest. Intraforest migration can also be used to consolidate multiple Active Directory domains into a single domain, easing management of users and groups under a single set of policies. You must establish trust relationships between the destination domain and all domains trusted by the source domain (use the Trust Migration Wizard to assess and implement domain trusts for migration). To be migrated, the source objects must be security principals users, security groups (including Windows NT 4 local groups, domain local groups, and global groups), or computer accounts. Any account (or other source object) that has a SID that already exists in the destination domain or forest cannot be migrated. For example, irrespective of the domain of origin, built-in accounts such as Administrators and Power Users cannot be migrated because they use identical SIDs. 254
From our experience, we can recommend PHP Web Hosting services, if you need affordable webhost to host and run your web application.

Part 3: Windows Server 2003 Upgrades and Migrations Migrating to Windows Server 2003 For more information about customizing these .inf files, refer to the USMT .inf Commands.doc that is contained in the Windows Server 2003 Deployment Kit. Migrated information includes the following: . File types migrated .ch3, .csv, .dif, .doc, .doc, .dqy, .iqy, .mcw, .oqy, .pot, .ppa, .pps, .ppt, .pre, .rqy, .rtf, .scd, .sh3, .slk, .txt, .wk?, .wpd, .wps, .wq1, .wri, .xl? . User folders migrated Cookies, Desktop, Favorites, My Documents, My Pictures . User settings migrated Certificates, fonts, keyboard, localization, mapped network drivers, mouse, network printers, screen saver, sounds, taskbar, Microsoft Outlook/ Outlook Express configuration and mail files, dial-up configuration, Microsoft Office System configuration, and Microsoft Internet Explorer configuration. Tip The certificates used by the Encrypting File System (EFS) are not migrated by USMT or the File and Settings Transfer Wizard. Files that are encrypted on the source computer are decrypted when written to the destination computer. File and Settings Transfer Wizard The File and Settings Transfer Wizard is a user-based migration tool that allows users to transfer their configuration settings and data from one computer to another. Although not designed for corporate deployments or mass migrations, it can allow users to transfer their settings, files, and folders from one computer to another without requiring administrative assistance. This tool is installed on clients running Windows XP in the System Tools menu. Click Programs or All Programs, Accessories, System Tools, File Settings And Transfer Wizard. Migration Scripts A set of scripts (starting with Clonepr.vbs) is provided in the Windows Support Tools for migrating security principals. Although these scripts do copy security principals to the new domain, leaving the source domain intact, they do not migrate user passwords and are used only for interforest migration of security principals (including migrating from Windows NT 4 to Windows Server 2003 or Windows 2000). The Clonepr.vbs script completes the following tasks: . Uses Clonegg.vbs to copy global groups, Clonelg.vbs to copy local groups, and Cloneggu.vbs to copy all global groups and users . Adds the security identifiers (SIDs) from the source domain to the SID history for the new account in the destination domain by using Sidhist.vbs The Movetree Utility The Movetree utility is used in intraforest migration of security principals. Movetree is a command-line program and is part of the Support Tools provided with Windows Server 2003 (located in the SupportTools folder on the product CD). Chapter 9
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 9 ADMT ADMT consists of a set of wizards designed to help you migrate users, groups, computers, service accounts, trusts, and security settings on objects. ADMT also provides support for migrating accounts from the directory of Microsoft Exchange Server 5.5. The primary operations of this tool are available on the Action menu and include the following: . User Account Migration Wizard . Group Account Migration Wizard . Computer Migration Wizard . Service Account Migration Wizard . Trust Migration Wizard . Security Translation Wizard . Exchange Directory Migration Wizard Other Microsoft Migration Tools In addition to ADMT, Microsoft provides several other tools that can assist in certain migration scenarios. These tools include User State Migration Tool (USMT), File Settings and Transfer Wizard, migration scripts, and the Movetree utility. USMT You can automate the migration of user settings and data by using USMT, an administrative wizard designed to assist in the deployment of Microsoft Windows XP clients in an enterprise network environment, specifically in the migration of user settings. This administrative tool was initially shipped with Windows XP in a folder off the root of the product CD called ValueAddMsftUsmt. USMT comprises a set of tools, which perform the user state acquisition and the loading operations, and a set of information files (.inf files), which determine what information gets migrated. USMT operations (and related executable files) include the following: . Acquire user state information (Scanstate.exe) . Load the user state information to a new computer (Loadstate.exe) USMT information migrated (and related .inf files) includes the following: . Operating system settings (Migsys.inf) . User settings (Miguser.inf) . Application settings (Migapp.inf) Also, the Sysfiles.inf file is used to tell USMT about files (such as operating system files) that should not be migrated, irrespective of any other USMT configuration settings. 252
In case you need affordable webhost to host your website, our recommendation is ecommerce web host services.

Part 3: Windows Server 2003 Upgrades and Migrations Chapter 9 Migrating to Windows Server 2003 Selecting the Migration Tools . . . . . . . . 251 Migrating User Accounts . . . . . . . . . . . . 268 General Considerations Migrating Passwords . . . . . . . . . . . . . . . 271 for Migrations . . . . . . . . . . . . . . . . . . . . 254 Migrating the Computers. . . . . . . . . . . .273 Determining the Approach Merging Groups during Migration. . . . . . 275 to Migration. . . . . . . . . . . . . . . . . . . . . . 255 Migrating Domain Trusts . . . . . . . . . . . .277 Preparing for Migration. . . . . . . . . . . . . 256 Migrating Service Accounts . . . . . . . . . .279 Migrating Security Principals . . . . . . . . 257 Security Translation . . . . . . . . . . . . . . . .280 Performing the Migration: Generating Migration Reports . . . . . . . . 282 An Overview . . . . . . . . . . . . . . . . . . . . . 258 Migrating Group Accounts. . . . . . . . . . . 259 Migration involves moving account information from an existing domain to a new domain. You use migration instead of an upgrade process for a number of reasons, not the least of which is when the server must provide optimal performance (for instance, in environments where high server availability is essential). Likewise, when a new installation is preferred for hardware or software reasons, migration is the logical approach to providing the needed user and group information. Although it depends upon the migration scenario, once a migration has been successfully completed, the source domain often can be removed and its server hardware reallocated. Selecting the Migration Tools All the user, group, service, computer, domain, trust, and security information can be migrated by using an application called the Active Directory Migration Tool (ADMT). There are also several migration tools from independent vendors such as Aelita, NetIQ, and Quest (Fastlane) that provide similar functionality. Whether you are migrating from Microsoft Windows NT, Microsoft Windows 2000, or from one Microsoft Windows Server 2003 forest to another, ADMT enables you to move account information from the source domain (from where the information is being migrated) to the destination domain (to where the information is being moved). The tasks involved in migration are centered around the transfer of information concerning security principals and security settings.
You want to have a cheap webhost for your apache application, then check apache web hosting services.

Part 3: Windows Server 2003 Upgrades and Migrations Microsoft Windows Server 2003 Inside Out Chapter 8 Upgrade the PDC When you are ready to begin the upgrade process, start Windows Setup from a Windows NT 4 command line, and run Windows Server 2003 Setup (Winnt32) either from the product CD or from a network distribution folder. During the upgrade, Setup will run the Active Directory Installation Wizard, which performs the following tasks: . Prompts you to create a new forest or join an existing forest and to create a new domain tree or join an existing one . Establishes the directory datastore, Kerberos, which establishes parent child trust . Copies schema, configuration, and domain directory partitions from the parent domain . Copies security principals stored in the Security Account Manager (SAM) into the directory and converts groups as discussed previously by establishing corresponding accounts in Active Directory. User and global group accounts are put into the Active Directory Users container, computer accounts are put into the Computers container, and Windows NT 4 local groups are put in the Builtin container. These container objects (Users, Computers, and Builtin) are not organizational units (OUs) and are not subject to administrative changes (moving, deleting, renaming). Post-PDC Upgrade When the upgrade of the PDC has been completed, you can commence with upgrading the BDCs until all domain controllers are running Windows Server 2003. Tip A Windows NT 4 PDC that has been upgraded to Windows Server 2003 is able to continue to replicate security principal changes to Windows NT 4 BDCs. Once all domain controllers are upgraded (and replication has completed), proceed with upgrading member servers. Tip Upgrading Windows NT applications Prior to upgrading existing Windows NT applications, look at the Relnotes.htm file in the Docs folder of the Windows Server 2003 product CD. You can also test the compatibility of applications with Windows Server 2003 by using the Application Compatibility Toolkit (available at the Microsoft Web site at http://msdn.microsoft.com/compatibility). You can also use the Program Compatibility Wizard to test and enable compatibility settings that might allow applications to operate correctly. Some applications, such as disk management tools, developed for earlier versions of the Windows Server operating system will not work correctly even in compatible modes and could pose risks to the integrity of the installation. 250
Check Tomcat Web Hosting services for best quality webspace to host your web application.

Part 3: Windows Server 2003 Upgrades and Migrations Upgrading to Windows Server 2003 . Global catalog Although not one of the roles identified as an operations master, the global catalog is a required role performed by at least one domain controller in every forest (and commonly implemented with at least one global catalog per site). A global catalog contains a reference to, and a partial attribute set for, every object in the Active Directory forest. In addition to the operations master roles and global catalog there is a server role involved in managing intersite replication for Active Directory. Servers supporting intersite replication are referred to as bridgehead servers. Converting Windows NT 4 Groups to Windows Server 2003 Groups The Windows NT 4 security groups are upgraded to related groups in Windows Server 2003 as follows: . Windows NT 4 local groups become domain local groups. . Windows NT 4 global groups become global groups. Chapter 8 Note Clients running earlier versions of the Windows operating system continue to work with the upgraded groups, yet they see universal groups as global groups. Troubleshooting Domain local groups are not correctly displayed in Windows NT 4 Windows Server 2003 domain local groups cannot be correctly referenced by Windows NT 4 administrative tools used on member servers running earlier versions of the Windows operating system. You can use administrative tools in the Windows Server 2003 Administration Tools pack (Adminpak.msi file in the I386 folder on the product CD or %SystemRoot%System32 folder after installation) to display the local groups and manage them on servers running earlier versions of the Windows operating system. Performing the Upgrade from Windows NT 4 Upgrading a Windows NT 4 domain begins by creating or verifying adequate backups and establishing a private network. . Back up the PDC Prior to beginning the actual upgrade process of the Windows NT 4 PDC, verify that you have tested backups and (at least one) operational BDC for the domain taken offline. . Create an isolated network You might want to take the upgrade off of your enterprise network (or do the upgrade during off- peak hours), so as to prevent user, application, and service access to the domain controller during the upgrade process.
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 Inside Out Chapter 8 Unlike Windows NT 4, domain controllers now require DNS Windows NT 4 was based on NetBIOS network operations, yet this is no longer the case for Windows networking. Beginning in Windows 2000 and continuing in Windows Server 2003, Windows network operations are based on using DNS as the core location service for everything from domain controllers and global catalogs, to Kerberos servers and other network services. To locate network services, Windows 2000 and Windows Server 2003 use service resource records, enabling identification of the Internet Protocol (IP) address and ports used to support Transmission Control Protocol/Internet Protocol (TCP/IP) network services. If your Windows NT domain already has DNS deployed, you must delegate the DNS zone for the new Windows Server 2003 domain before upgrading the PDC. Establishing Operations Masters Once all Windows NT 4 domain controllers have been upgraded to Windows Server 2003, assess and define the operations master roles for each of the domain controllers. Windows Server 2003 domain controllers can perform in a variety of operational roles. In fact, every Active Directory forest and domain must supply domain controllers performing the operations master roles. The required forest roles are as follows: . Schema Master A forest-wide role that manages updates to the schema within Active Directory . Domain Naming Master A forest-wide role that manages the addition or removal of Active Directory domains The required domain roles are as follows: . RID Master A domain-wide role that manages the allocation of RIDs, which are combined with the domain security identifier (SID) to uniquely identify objects in the directory. . Infrastructure Master A domain-wide role that is responsible for managing references from local directory objects to objects in other domains. Tip Normally, an Infrastructure Master should not also be assigned as a global catalog, because this prevents the Infrastructure Master from functioning correctly. . PDC Emulator A domain-wide role that provides backward compatibility to clients running earlier versions of Windows (supporting both NTLM and Kerberos authentication) and also provides time synchronization. 248
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 Managing Disk Partitions Managing disk partitions in Windows NT differs from managing them in Windows Server 2003, and NTFS partitions are converted during installation (with backward compatibility supported for file allocation table [FAT] and FAT32 partitions). Even though only 1.5 GB of disk space is required for a new installation, a little more than 2 GB of disk space is required to upgrade (thus, you cannot upgrade Windows NT server installations on FAT partitions, because doing so exceeds the partition boundaries for the FAT partition). Windows NT 4 fault-tolerance configurations mirroring (redundant array of independent disks [RAID] 1) and disk striping with parity (RAID 5) are not supported by Windows Server 2003. Prior to upgrading Windows NT 4 servers that use these methods, verify you have a backup of the data contained on the fault- tolerant volumes, and then disable the fault- tolerant configuration. Windows NT disk partitions are now referred to as basic disk (meaning, not dynamic) partitions. Beginning in Microsoft Windows 2000 (and including Microsoft Windows XP and Windows Server 2003), the use of dynamic disk partitions became available. Dynamic disk partitions cannot be modified during upgrade. Upgrading Domain Controllers When you re ready to begin upgrading your Windows NT 4 domain controllers, after verifying that you can and want to upgrade the server hardware, begin the process by backing up your domain controllers and taking at least one updated BDC offline for the duration of the upgrade process. Keep this offline BDC as a rollback server in case of serious upgrade errors resulting in an inoperative primary domain controller (PDC). Depending upon the criticality of your existing domain infrastructure, you might want to have multiple backups set aside for rapid recovery of your existing network functionality. For the same reason that you make and keep redundant backup tapes, when upgrading domains it makes sense to keep redundant BDCs (at least long enough to verify a successful upgrade). . Upgrade the PDC To upgrade the Windows NT 4 domain controllers on your network, begin by upgrading the PDC and allow time to assess whether it has been upgraded correctly. . Upgrading BDCs After the PDC is upgraded, next upgrade all of the BDCs. Chapter 8
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.