Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1282 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enterprise console upgrade from v2.0

C3PO

Hi folks,

I've been asked to help out a fellow college, who are running console 2, EM Library 1.3, endpoints on 7.6.

They have a new server available, running 2003, and want their console upgraded and moved to this.

My question is, is it worth it to plough through all the required upgrades, followed by a server transfer?  Or could I just install console 4 or 4.5 on the new server, turn off the console on the old server (still required as a DC) and try to find and protect the clients on the network?  Just trying to save some time and possible headaches....

Thanks

:5270


This thread was automatically locked due to age.
Parents
  • 0

    The bigger question is if you don't mind re-protecting the clients is order to get them pointing at the new server with the right certificates.  If you can, I'd recommend that as it's less prone to error. ... You can always configure an AD start-up script to run setup.exe from the new distribution point maybe based on some condition

    Personally I wouldn't say that it's less prone to error but that's because we have administrative rights on about 15% of our (potential) clients and in turn only a small fraction of "our" machines is in AD and we rarely use the AD techniques. I've always used the mrinit.conf approach (basically you can either point the machines to the new server which then provides them with the new updating policies or assign new policies from the old server to direct them to the new CIDs) - once I had to "reincarnate" a server using also a DNS alias. It probably depends on the available tools and expertise.

    But no - I'm not disagreeing with you, Jak :smileywink: 

    Christian

    :5281
Reply
  • 0

    The bigger question is if you don't mind re-protecting the clients is order to get them pointing at the new server with the right certificates.  If you can, I'd recommend that as it's less prone to error. ... You can always configure an AD start-up script to run setup.exe from the new distribution point maybe based on some condition

    Personally I wouldn't say that it's less prone to error but that's because we have administrative rights on about 15% of our (potential) clients and in turn only a small fraction of "our" machines is in AD and we rarely use the AD techniques. I've always used the mrinit.conf approach (basically you can either point the machines to the new server which then provides them with the new updating policies or assign new policies from the old server to direct them to the new CIDs) - once I had to "reincarnate" a server using also a DNS alias. It probably depends on the available tools and expertise.

    But no - I'm not disagreeing with you, Jak :smileywink: 

    Christian

    :5281
Children
No Data