Centre d’abonnement

Des informations en temps réel du chef de file de l'industrie TI.
windows-server-2003-eos-coexistence-between-new-and-old-servers

Windows Server 2003 EOS: Coexistence between New and Old Servers

5 Feb 2015 by Trent Viavattene

With Windows 2003 end of service (EOS) coming up in less than six months, it’s time to start making the transition to a newer, updated server platform. Part 1 and Part 2 in this five-part series help your organization jumpstart the transition. What’s next? How to avoid the next pitfall.

Pitfall No. 3: Inconsistent or Absent Coexistence between Old and New Servers

This means the data pulled from the Microsoft 2003 operating system must communicate with the new, chosen target server. Outlined below is how to guarantee an effective transition of your organization’s records, data and information to the new server platform:

  1. Make sure there is a defined cutover plan between source and target servers. This includes changes in DNS references, updated logon scripts, updated access rights, and final validation of target server functionality before allowing end users access to the new environment. It is critical to the success of any migration strategy to have a defined plan for the target infrastructure well before any migrations start. Insight’s discovery process fully identifies and defines the migration strategy for your Windows 2003 infrastructure.
  2. Establish and communicate downtimes for cutover. Another critical component for a successful migration is that all users are informed of and comply with established downtimes for applications. If users are able to continue using the application versions resident on the source server data inconsistency will occur and result in potential data loss.
  3. Preserve permissions, security settings and access points to the network and resources. The migration from the source to target servers leaves room for human error in the transfer of settings between the servers. The same application install paths or static server references in the application configuration must be maintained in order to ensure functionality and accessibility of your applications once they are resident on the target server. Insight has defined a migration strategy to minimize dependence on manual installation of the applications on the target servers and will automate the transfer of all application configuration onto the target server, thereby reducing overall risk associated with the migration.

Get more information on how to address the Microsoft Windows Server 2003 end of service by visiting www.insight.com/ServerIgnite or calling 800-INSIGHT.

The post Windows Server 2003 EOS: Coexistence between New and Old Servers appeared first on Insight ON.