Jump to content
Welcome to our new Citrix community!
  • 0

PVS 1912.0.0 LTSR - Windows Services Stop after vdisk promoted to Test or Production


Arve Beckstrom

Question

Hi, we're experiencing the same problem as in this post:
https://discussions.citrix.com/topic/380977-citrix-pvs-windows-services-stop-after-vdisk-promoted-to-test-or-production/

 

Except we're running with the following versions:

VMware ESXi, 6.5.0
Windows Server 2019 Version 1809 (17763)
Citrix Virtual Apps and Desktops 7 1912 LTSR
Citrix Provisioning Server x64 1912.0.0 LTSR

 

Basically, something happens after image version 10 or twelve (merged or not, it’s the same).

 

The following services won’t start, and clients cannot connect.

Base Filtering Engine
DHCP Client
Diagnostics Policy Service
IKE and AuthIP IPsec Keying Modules
Network Location Awareness
Windows Firewall

 

Would really like to find out what’s causing this without having to reverse the image.

Link to comment

5 answers to this question

Recommended Posts

  • 0

Does the issue occur even without booting the version in mainteance?
And occurs consistently, all targets and reboots?
So if version 11 is the last known working version, create a version on top of this version, promote directly to production and test if it boots and services start succesfully.
If the issue occurs, it may be an interaction which occurs during KMS handling or Cached secrets cleanup (during these operations the vdisk is mounted directly on the PVS server for some file handling). These operations would be the only source of change between working version and non working version.

These options can be disabled on the vdisk properties
General tab -> Check "Cached secrets cleanup disabled"
MS Vol Licensing tab -> Check "None"
The vdisk cannot be in use to configure these options.
To "manually" achieve the same, once vdisk version has been created (and modified as needed once we are sure this is source of issue), back up the version avhdx file. Promote to production, and then copy back the backedup avhdx file. 


 

Link to comment
  • 0

Hello,

I had the same problem with 2019 Server, VDA 2203 LTSR CU1 and PVS 1912 LTSR CU5

After promoting my vDisk from maintenance to test, I was unable to log on  with the message 

"An attempt was made to logon but the network logon service was not started"

 

I tried to change and follow the tips provided in this fill (change secret credentials, settings licensing KMS to none) but nothing changed.

As soon as I put my vDisk to maintenance, I'm able to log on.

 

@Arve, did you find a way to resolve your problem ?

 

Thanks,


Fred

Link to comment
  • 0
On 9/2/2022 at 10:51 AM, Frédéric LOUKA said:

Hello,

I had the same problem with 2019 Server, VDA 2203 LTSR CU1 and PVS 1912 LTSR CU5

After promoting my vDisk from maintenance to test, I was unable to log on  with the message 

"An attempt was made to logon but the network logon service was not started"

 

I tried to change and follow the tips provided in this fill (change secret credentials, settings licensing KMS to none) but nothing changed.

As soon as I put my vDisk to maintenance, I'm able to log on.

 

@Arve, did you find a way to resolve your problem ?

 

Thanks,


Fred

Hello Frederic,


Did you find the solution about this problem ?

I have the same problem with 2022 Server VDA 2203CU2.

Thanks,


William

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...