Best Practices When Installing Or Migrating to Windows Server 2008 R2

By Tim P Johnson

Windows Server 2008 R2 is the latest Microsoft server operating system. There are some challenges to fully unleash its potential. Proper hardware configuration, installation, configuration and hardening security allow to use its full range of possibilities. Here is a list of best practices when upgrading or migrating to Windows 2008 R2 server.

• Verify that your hardware, devices, and drivers are supported by Windows Server 2008 R2.
• Make sure that your hardware configuration meets or exceeds minimum or recommended hardware requirements.
• Create full system documentation and schedule a backup of your system.
• Be consistent when naming servers and client workstations. Use names that clearly identify the role of new server, for example dhcp.domain.com for dhcp server, wsus.domain.com for windows server update services, sql.domain.com for sql database, etc.
• Use the Windows Server 2008 R2 Initial Configuration Tasks Wizard to conduct post installation tasks.
• When highest level of security is required use Windows Server Core installation option. Reduced number of services and components reduce potential surface of malicious infiltration.
• Use only Internet-standard characters in your computer name. This includes the letters A-Z (upper and lowercase), the numbers 0-9, and the hyphen.
• Test your backups. On regular basis verify backup integrity and test restore in lab environment.
• First thing after installation is finished rename administrator account and assign strong password. Enforce strong passwords through group policy settings.
• Install only the roles and features that will be necessary. Any additional features reduce server stability and security.
• Utilize Performance Monitor to capture performance data on regular basis to identify bottlenecks in system performance.
• Install Network Policy Server role to gain more granular control over user access to networks and services.
• If using VPN connections install at least two network cards in the server that handles VPN clients. Avoid using PPTP VPN connection type, utilize L2TP over IPSec encryption.
• Standardize servers hardware. Restoring backups after disaster to dissimilar hardware is problematic and often unsuccessful. If for some reason hardware standardization is not possible consider virtualizing physical servers.
• Create installation image and utilize Windows Deployment Services to automate installation process.

Tim has been writing articles online for nearly 2 years. He specializes in computer security. You can also check out his latest website at http://www.dorseymetrology.com/ which provides information about optical comparators.

Article Source: http://EzineArticles.com/?expert=Tim_P_Johnson

Article Source: http://EzineArticles.com/4338617