/build/static/layout/Breadcrumb_cap_w.png

Upgrading to 8.X on Hyper-V problems?

Hello all,

I have the V7.2.101 version of the SMA running in Hyper-V on a Server 2012.
I attempted an upgrade to the 8.X version. It "looked" like it upgraded OK, however the network adapter of the K1000 stopped communicating with the network. 

I tried setting the IP to DHCP on the SMA, but it would only grab an APIPA address. Setting the SMA back to a static address did not help either. The SMA would not connect to the network. I finally had to rename the .VHDX file for the drive, copy in a backup copy of the .VHDX, and restore the backup from the night before.

Has anyone else tried to update to 8.X on the Hyper-V version in 2012?
Has anyone else had problems on Hyper-V 2012?
Does the 8.X version only work on the Hyper-V versions in 2012R2 and up?

I've looked but did not see any caveats regarding the version of Hyper-V that it runs on, but I could have missed something. 

Regards

2 Comments   [ + ] Show comments
  • very strange...

    Check these two KBs

    https://support.quest.com/kace-systems-deployment-appliance/kb/153445

    https://support.quest.com/kace-systems-deployment-appliance/kb/195580

    If you are in compliance with those steps, then maybe pull backups, spin up an 8.0 VM and restore backups, test, and get rid of the old one. - Channeler 7 years ago
  • currently there seems to be an issue with FreeBSD in Hyper-V for Windows 2012 (R2 and 2016 work well)
    the Bugnumber for that is: K1-19714
    Probably support can help. - Nico_K 7 years ago

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ