VMware Horizon Community
hunterok
Enthusiast
Enthusiast

AppVolumes Writable Volumes migration Windows 7-->Windows 10 Ent LTSB

I need to migrate our Instant Clones from Windows 7 x64 to Windows 10 x64 Ent LTSB. We use App Volumes 2.12 and Horizon 7.03 (7.1)

As far as I know it is suggested to create new Appstacks  for every Windows version. If I do so will users be able to use their current wrtitable volumes with Windows 10? Or I need to go a fresh deployment with data wipe?

Reply
0 Kudos
6 Replies
Lakshman
Champion
Champion

Writable volumes will not pertain User Installed Apps between Windows 7 and Windows 10.

Reply
0 Kudos
Ray_handels
Virtuoso
Virtuoso

You could theoraticly use a Windows 7 writable volume with a Windows 10 machine. I would nog suggest it to be honest as my guess is the W7 profile will not work with the W10 machine but this is more of a Windows issue than an Appvolumes issue per say.

What you need to do is to go to the writable volume, click edit and select Windows 10 (x64) as an extra operating system.

And as said, my guess is that it wont work but you could give it a shot.

Reply
0 Kudos
hunterok
Enthusiast
Enthusiast

Reply
0 Kudos
Ray_handels
Virtuoso
Virtuoso

Yes that would be an option.

Although to be honest I haven't seen a tool that works perfectly well with transferring settings cross OS.

I would suggest recreating the writable volume (or creating a new one, that's better said) for the users.

Reply
0 Kudos
AppVol_ArtR
VMware Employee
VMware Employee

We recommend creating new writable volumes for Win10, even though we don't know what will break if you try reusing your older writables.  The likelihood of incompatibility is greater with UIA+Profile volumes than it is with UIA-only volumes.

MSKB article 3056198 notes that Microsoft's Roaming Profile feature keeps separate profiles for several different versions of the OS.

  .v2  Vista and Win7

  .v3  Win8

  .v4  Win8.1

  .v5  Win10 1507 and 1511

TechNet article jj649079 adds .v6 for Win10 1607 and 1703.

Roaming Profile redirects the %APPDATA% folder.  App Volumes UIA+Profile volumes redirect %APPDATA%, %LOCALAPPDATA%, and a few other folders, potentially making them even more sensitive to version changes than Roaming Profile.  So at a bare minimum, we should follow Roaming Profile's version compatibility restrictions.

Reply
0 Kudos
szilagyic
Hot Shot
Hot Shot

I have tried doing that exact same thing.  When Windows 10 mounts the Writable Volume and brings in the Windows 7 profile, the login fails, due to the changes that Msft made between Windows 7 and 10.  In researching it more, the consensus is to use the Msft Migration Tool.  Which, is difficult for VDI because the user cannot be logged in when the profile is copied.  In the end we've just had to manually copy selected profile data folders, which works every time.

Reply
0 Kudos