izkoenizmuri
Contributor
Contributor

Master Image Upgrade from LTSB1607 to LTSC1809

Jump to solution

Hi

We like to upgrade the images from LTSB to LTSC1809

First we have to find out, that upgrade only works without any snapshots on the master image vm. If there are any, the upgrade will fail.

Now we have a second problem, after upgrade sometimes the PERSONA profile won't load. sometimes it works, sometimes not. about 50%

with a freshly installed LTSC1809 image with nearly the same apps, the problem does not exist.

i can't see any hints in the logfiles or the eventlog why he could not load the profile

Anyone any idea

View 7.7, ESX 6.5

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
BenFB
Virtuoso
Virtuoso

A fresh install is always preferred but upgrades are supported. You need to uninstall the Horizon components before the OS upgrade.

Upgrade Requirements for Windows 10 Operating Systems (2148176)

Installation order of End User Computing Agents for User Environment Manager (UEM) and App Volumes (...

View solution in original post

0 Kudos
5 Replies
BenFB
Virtuoso
Virtuoso

A fresh install is always preferred but upgrades are supported. You need to uninstall the Horizon components before the OS upgrade.

Upgrade Requirements for Windows 10 Operating Systems (2148176)

Installation order of End User Computing Agents for User Environment Manager (UEM) and App Volumes (...

0 Kudos
izkoenizmuri
Contributor
Contributor

Hi

Thanks, it's looking good, before upgrade first uninstall view agent, after upgrade reinstall and it works perfect until yet

regards

Marc

0 Kudos
pdudas76
Enthusiast
Enthusiast

Not sure if you will experience this as well, but two things I experienced when trying to use LTSC was that boot up of the clones took forever. The Base image took forever to boot up as well if there was a snapshot in place, but without it booted instantly, but you need a snapshot to make a pool of clones so I was not sure of a way around it.

Hopefully, it is more compatible now.

0 Kudos
LukaszDziwisz
Hot Shot
Hot Shot

The workaround for now is to use VMFS 5 instead of 6. VMware is aware of it and currently working on it

0 Kudos
BenFB
Virtuoso
Virtuoso

This is a know issue that only applies to VMFS 6 and has the highest internal priority from VMware. The workaround is to use VMFS 5.

windows 10 1809 slow

0 Kudos