I am upgrading a physical Windows 2003 32 bit server running 3.4.364.32 to a Virtual Windows 2008 R2 that will run 64 bit running PI Server 2012.
I would like to do as much work as possible in advance before arriving on site and completing the final steps. The source server is on a completely isolated control network at another plant.
I need a second (or third) set of eyes on the process that I would like to take. Please J
- In office- Build Windows 2012 server X amount of days prior to actual upgrade. Install prerequisites, patches and 3.4.375.99 64 bit server on the new target server.
- In office -Force archive shift on source server. Typical archives are 19-23 days on this server.
- In office - Once new PI server passes health checks, import required files and all but last archive from source. Rename and IP of target server (it’s not on the network that the source server is at this point)
- In office - Upgrade target server to PI Server 2012. Do health checks.
- On site - On day of upgrade ensure interface is buffering, unplug network cable of source PI server.
- On site - Insert new VM server containing the preconfigured PI server into control network. The NIC on the new PI server is disabled in VM Sphere client.
- On site- Bring in last archive from source PI server. Do health checks.
I will be referencing the following:
KB00507 - How to preserve the PI Server ID after moving a PI Server to a different machine
KB00530 - Upgrading to 64-bit PI Server while moving to 64-bit hardware
PI Server 2012 Installation and Upgrade Guide
If the steps above don’t work - Johnson City, TN 1 423 610 3800 or Philadelphia, PA 1 215 606 0705
Thank you very much for your time.