Hello, my Server Edition is currently installed on a Windows Server 2008 R2 VM. Microsoft has ended support for this OS so I need to move my Server Edition to a new VM with a current server OS. Is this possible or do I need to reinstall Server Edition on the new VM? I've asked Avaya for instructions but what they sent me doesn't exactly apply to my situation. My biggest fear is that my licensing will become invalid and take down my system for a hours. Thanks guys.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Moving Server Edition to a new VM
- Thread starter damascus9
- Start date
You should try and move the server via Hyper-V manager
it will still disable your licensing and you have to redo them but you have 30 days to do that.
Joe
FHandw, ACSS (SME)
Remembering intrigrant 2019
it will still disable your licensing and you have to redo them but you have 30 days to do that.
Joe
FHandw, ACSS (SME)
Remembering intrigrant 2019
If you move the VM to the new host licensing shouldn't be affected as long as the VMs hardware settings don't change.
But since Avaya only started supporting Hyper-V in 10.1 and on Windows Server 2012 R2 & 2016 the question is if this was installed from the .ISO image and have Hyper-V tools been installed manually?
If so for a supported solution you might wanna reinstall R10.1 or R11 using the Hyper-V image.
"Trying is the first step to failure..." - Homer
But since Avaya only started supporting Hyper-V in 10.1 and on Windows Server 2012 R2 & 2016 the question is if this was installed from the .ISO image and have Hyper-V tools been installed manually?
If so for a supported solution you might wanna reinstall R10.1 or R11 using the Hyper-V image.
"Trying is the first step to failure..." - Homer
bahmonkeys
Systems Engineer
Just export modules and backup data. Install the Voicemail Pro on the new VM (fresh install). Restore backup, modules and all Wav files needed. Point the Avaya IPO Manager Voicemail to the new server.
Licensing: It will not become invalid as long you have the same version as you have on the old server or if you have the upgrade license then everything will be fine.
Keep the old server active when you are changing to the new server so if something happens, you can always go back to the old server.
Licensing: It will not become invalid as long you have the same version as you have on the old server or if you have the upgrade license then everything will be fine.
Keep the old server active when you are changing to the new server so if something happens, you can always go back to the old server.
bahmonkeys
Systems Engineer
Thanks Janni78.
Build a new server edition from scratch. You can restore all configurations on the server edition even the license. You will need to migrate or move the licenses you have on the old server to the new server which will generate a new ID.
Build a new server edition from scratch. You can restore all configurations on the server edition even the license. You will need to migrate or move the licenses you have on the old server to the new server which will generate a new ID.
- Thread starter
- #8
You might wanna consult someone who understands virtualization.
The VM is the same OS, it uses Linux.
The OS hosting all VM will be a new version.
But since Server Edition was never supported on WS2008 R2, you do wanna reinstall the VM using the Hyper-V image provided by Avaya.
"Trying is the first step to failure..." - Homer
The VM is the same OS, it uses Linux.
The OS hosting all VM will be a new version.
But since Server Edition was never supported on WS2008 R2, you do wanna reinstall the VM using the Hyper-V image provided by Avaya.
"Trying is the first step to failure..." - Homer
bahmonkeys
Systems Engineer
@Janni78
Yes of course, if there is a lot of valuable data I would take my time migrating correctly to the New Server VM.
This is the server edition of Avaya, there isn't much important data that can not be backed up and restored really quickly. Building an Avaya VM takes less than an hour and importing data doesn't take that long.
The longest part of this build is waiting for Avaya to send you the New migrated licensee. This can all be built and tested before ever moving from the old server.
Yes of course, if there is a lot of valuable data I would take my time migrating correctly to the New Server VM.
This is the server edition of Avaya, there isn't much important data that can not be backed up and restored really quickly. Building an Avaya VM takes less than an hour and importing data doesn't take that long.
The longest part of this build is waiting for Avaya to send you the New migrated licensee. This can all be built and tested before ever moving from the old server.
@bahmonkey
I don't follow.
If it's a VM you just move the VM from one Host to another, no need to rebuild it.
The problem with OPs question is that he has confused a VM with a Hyper-V host.
The Server Edition VM can't be Windows 2008, but the Hyper-V host can be. If the new host is on newer Windows OS nothing stops you from just moving the VM the the new host.
But the main problem is that if his VM is on W2008 it's unlikely the SE is installed with a proper Hyper-V image.
It was possible to run SE on Hyper-V earlier by just installing the .ISO even though it wasn't supported, since it now is it's better to use the proper image which gives you Hyper-V tools as well.
"Trying is the first step to failure..." - Homer
I don't follow.
If it's a VM you just move the VM from one Host to another, no need to rebuild it.
The problem with OPs question is that he has confused a VM with a Hyper-V host.
The Server Edition VM can't be Windows 2008, but the Hyper-V host can be. If the new host is on newer Windows OS nothing stops you from just moving the VM the the new host.
But the main problem is that if his VM is on W2008 it's unlikely the SE is installed with a proper Hyper-V image.
It was possible to run SE on Hyper-V earlier by just installing the .ISO even though it wasn't supported, since it now is it's better to use the proper image which gives you Hyper-V tools as well.
"Trying is the first step to failure..." - Homer
- Status
Similar threads
- Locked
- Question