Upgrades

[Mark Brown]

I was curious how other facilities handle upgrades, either software or hardware.  The way they insist on doing it here seems like a lot of extra work, but I have no way to know if it’s normal procedure or not.

Basically, when we get an upgrade to Cloverleaf, they buy a new server (we use Windows 200X) to put it on, even though I remind them the current server is under-utilized and more than one version of Cloverleaf can be on one machine.  We use a lot of VB scripts for paging, monitoring, etc and when we move to a new machine, changes in the OS’s security settings etc always break the scripts.  The folks that build the server insist they have to give it a new name and new IP address which means I have to get with each vendor with in-bound messages and arrange to have them update the IP they send to.  

Is this the way everyone else does it?

Mark

Topic

[Debra Downs]

We most definitely do not do it this way.  We upgrade hardware when we approach the ‘necessity’ stage (we are on W2k).   When we do replace the server, we use the same I/P adderess, just for the reason you mention; too many vendors to coordinate with.

At our facility, whoever is responsible for the engine makes the upgrade decisions.

[Author]

Replies