AnsweredAssumed Answered

Implications of PI Server name changes in collective

Question asked by AlistairFrith on Jun 14, 2017
Latest reply on Dec 12, 2017 by AlistairFrith

We are planning a large infrastructure change that will involve new servers with new names replacing existing servers in a collective. The collective name is also likely to change. I've seen a white paper concerning changing a server name but this is a collective and the servers within it.

 

The existing servers are named companyV8PIPn where V8 relates to the fact that it is a virtual machine running Windows Server 2008. These servers will be replaced with new VMs running Windows Server 2012 and the new machines will be called companyV12PIPn.

 

Can we just add each new server to the collective and then remove the old ones with no impact to any clients or interfaces? There are around 150 interfaces spread among a large number of interface servers and I have no idea how many Processbook and Datalink files might be referencing these servers.

 

The collective itself is named after the first PI Server in it: companyV8PIP1. What are the implications of changing that name?

 

Regards,

 

--- Alistair.

Outcomes