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

XenDesktop 7.14.1 Update MCS static dedicated Desktops


Question

Hello everybody,

 

recently we've deployed a pool of Win 7 dedicated linked-clones with static changes on local disk using MCS. VDA 7.14.1.14098 HDX3Pro. The GoldenMaster is hosted on XenServer 7.0 Build 125380c.

 

 

Now we've tried to updated the machinecatalogue with a new snapshotversion using the command below:

 

Publish-ProvMasterVmImage -ProvisioningSchemeName "CatalogueName" -MasterImageVM "XDHyp:\HostingUnits\XenServer\GM.vm\V1.snapshot\V2.snapshot\v3.snapshot"

 

The catalogue is running on snapshotversion V2 and we want to go v3.snapshot

 

The powershell output displays everything went fine:

 

 

TaskId                 : 03ee250c-79b3-41be-8a68-3d3a40305dd1
Active                 : False
Host                   : DDC01
DateStarted            : 08.08.2017 17:57:27
Metadata               : {}
Type                   : PublishImage
Status                 : Finished
CurrentOperation       : 
TaskExpectedCompletion : 08.08.2017 18:07:29
LastUpdateTime         : 08.08.2017 18:07:29
ActiveElapsedTime      : 602
DateFinished           : 08.08.2017 18:07:29
TerminatingError       : 
WorkflowStatus         : Completed
ProvisioningSchemeUid  : 84dc0d14-44ed-4ea0-b5e4-68bc1ce5b898
ProvisioningSchemeName : CatalogueName
MasterImage            : XDHyp:\HostingUnits\XenServer\GM.vm\V1.snapshot\V2.snapshot\v3.snapshot
HostingUnitName        : XenServer
HostingUnitUid         : 34faeba5-e041-4f25-abad-7fa7f8389c3c
TaskState              : Finished
TaskStateInformation   : Completed
TaskProgress           : 100
Warnings               : {}
DiskSize               : 24

 

In Citrix Studio, the machinecatalogue is correctly displayed running on Snapshot v3

 

If we now boot the XenDesktops, our newly installed Software is not available.

 

Could you give me hint why our worker don't boot in the new snapshot, or where to get some logfiles etc.

 

Many thanks in advance

 

 

Link to comment

7 answers to this question

Recommended Posts

  • 0

Dominic, If you have created dedicated static machines then when you update the catalog only new machines created will use that new snapshot. Existing machines won't be updated. 

 

If you are looking to have machines which you can update, you need to either use non-persistent machines or look into app-layering feature.

 

Dedicated machines need to be managed as you would a regular desktop with suitable tools like SCCM.

 

If you don't mind loosing all the changes to your existing dedicated machines you can just create new machines in the catalog and assign them to your users and delete the old catalog which started life based on the older snapshot.

 

You may also want to read about the different catalog types here: http://docs.citrix.com/en-us/xenapp-and-xendesktop/7-14/install-configure/machine-catalogs-create.html

Thanks Martin

  • Like 2
Link to comment
  • 0

Dominic, If you have created dedicated static machines then when you update the catalog only new machines created will use that new snapshot. Existing machines won't be updated. 

 

If you are looking to have machines which you can update, you need to either use non-persistent machines or look into app-layering feature.

 

Dedicated machines need to be managed as you would a regular desktop with suitable tools like SCCM.

 

As Martin said, the dedicated/static desktops are just that, static. You wont be able to push updated snapshots to them the same way you can pooled random desktops.

Your best bet for pushing updated packages and patches to dedicated/static desktops is something like SCCM.

 

You can update the image monthly to include new patches  or software so that any new static desktops that get created are already patched.

Link to comment
  • 0
On ‎8‎/‎9‎/‎2017 at 7:52 AM, Bruce Coleman1709158411 said:

 

As Martin said, the dedicated/static desktops are just that, static. You wont be able to push updated snapshots to them the same way you can pooled random desktops.

Your best bet for pushing updated packages and patches to dedicated/static desktops is something like SCCM.

 

You can update the image monthly to include new patches  or software so that any new static desktops that get created are already patched.

Bruce, using the powershell commands here, I should be able to perform monthly maintenance on the master image, take a new snapshot then have new created virtual desktops created with the latest patches or apps that were applied in the latest snapshot? Meaning I can maintain one Machine catalog, but as the year progresses just have the catalog updated via powershell to point to a new snapshot and new Vm's are created while the old Vm's are still functional?

Link to comment
  • 0
13 hours ago, Timothy Lynch1709158806 said:

Bruce, using the powershell commands here, I should be able to perform monthly maintenance on the master image, take a new snapshot then have new created virtual desktops created with the latest patches or apps that were applied in the latest snapshot? Meaning I can maintain one Machine catalog, but as the year progresses just have the catalog updated via powershell to point to a new snapshot and new Vm's are created while the old Vm's are still functional?

 

Yes. Only newly provisioned machines will reflect the changes you make to the base image disk. This article has the full details on how to do this: https://support.citrix.com/article/CTX129205

Link to comment
  • 0
On 7/17/2019 at 1:18 PM, Josh steiner1709160356 said:

Has anyone accomplished updating the snapshot on a persistent machine catalog using Nutanix AHV has your hypervisor? Seems like CTX129205 does not apply in that scenario.

confirmed it works for Nutanix AHV just now.

 

# Citrix Support article: https://support.citrix.com/article/CTX129205

cls
asnp citrix*

#List all Provisioning Schemes

Get-ProvScheme


# Target specific Prov Scheme
$ProvSchemeName = "EnterProvScheme"

 

#List Prov Scheme for respective Name
Get-ProvScheme -ProvisioningSchemeName $ProvSchemeName

 

#Find the new path for the new snapshot (this lists all of the VMs/Snapshots, so you have to find the correct entry
#The 'CompanyCluster01' will auto populate in Powershell IDE, but will be based on your company naming. DON'T USE CompanyCluster01
Get-ChildItem -Recurse -Path 'XDHyp:\HostingUnits\CompanyCluster01' | Sort Name

 

#Set the new Image, this is the 'FullPath' attribute from the above command
Publish-ProvMasterVMImage -ProvisioningSchemeName $ProvSchemeName -MasterImageVM "XDHyp:\HostingUnits\CompanyCLUSTER01\MASTER10_11_7_19_VDAUpgrade_MCSOfficeFix.template"

 

#Now go into Studio and add a machine

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