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

MCS golden image Updates not seen inside VDI VMs after a successful catalog update. XD7.15 LTSR CU4


Kedar Pavaskar1709157578

Question

Issue: MCS golden image Updates not seen inside VDI VMs after a successful catalog update.

 

That is, after performing a change inside the Master VM (golden Image) such as application updates and new installation, and performing a catalog update. The update goes through fine without any errors inside the Studio. However, when seen inside the VMs the performed changes and updates aren’t seen!

Background: few weeks ago to troubleshoot an MCS update issue, the following blog was followed. Where Metadata values were Changed and I do not Remember Reverting. 

 

https://www.citrix.com/blogs/2016/04/04/machine-creation-service-image-preparation-overview-and-fault-finding/

 

Even Creating a new Machine catalog with the master VM(Golden image) shows no error and the new catalog creates the vdi VMs , but stays unregistered and when connected to the VMs on the hypervisor shows that the VMs hostnames are that of the Golden Image.

Which I believe is something to do with the metadata changes and the ImageManagementPrep command.

 

Running the powershell cmdlet “Get-ProvServiceConfigurationData” results in ImageManagementPrep_DoImagePreparation = False 

Hence ran Remove-ProvServiceConfigurationData -Name ImageManagementPrep_NoAutoShutdown –AdminAddress < Controller Address> with no errors. However, ImageManagementPrep_DoImagePreparation value still shows False.

 

Please help in reverting the metadata changes so that i could successfully redeploy the catalog updates. 

thank You. 

image.png.9224d1f0177fe757f925c62f0621a101.png

Link to comment

2 answers to this question

Recommended Posts

  • 1

Instead of "Remove-ProvServiceConfigurationData -Name ImageManagementPrep_NoAutoShutdown –AdminAddress < Controller Address>" 

can you run "Set-ProvServiceConfigurationData -Name  ImageManagementPrep_DoImagePreparation -value $True

 

Please try this command and then run Get-ProvServiceConfigurationData to see if the value changes, after if it does change try running the catalog update and see if the changes made in the catalog are available inside the VDI. 

do update here on the findings.  

  • Like 2
Link to comment
  • 0

thanks! that fixed it 

On 12/2/2019 at 2:31 PM, Kedar Pavaskar said:

Instead of "Remove-ProvServiceConfigurationData -Name ImageManagementPrep_NoAutoShutdown –AdminAddress < Controller Address>" 

can you run "Set-ProvServiceConfigurationData -Name  ImageManagementPrep_DoImagePreparation -value $True

 

Please try this command and then run Get-ProvServiceConfigurationData to see if the value changes, after if it does change try running the catalog update and see if the changes made in the catalog are available inside the VDI. 

do update here on the findings.  

 

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...