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

MCS Catalog machines not updating


tylital520

Question

Hi all,

 

I have a problem updating Machine Catalog in XenDesktop 7.14. I have updated the "golden image" taken a new snapshot and clicked "Update Machines" in Citrix Studio. As a rollout strategy I've selected "immediately".

 

Everything seems to go fine, thing start to happen on our vCenter (version 6.0) and there are no errors. On the machine catalog details the "Disk image" name changes to the new snapshot.

 

But the machines are not updating. They are still using the old snapshot.

 

If I try to create a new machine catalog from the new snapshot everything goes fine, so the snapshot doesn't seem to be the issue.

 

If I run the "Test machine catalog" I get errors:

 

Test that the account exists.

Check that the account specified is known to the AD Identity service and is present in AD.

 

The nominated account 'xxxx' could not be found in AD.
Check in AD if the account exists but is inaccessible for some reason; if necessary, create it manually.

 

 

If I click the "Manage AD Accounts" there are twice as many accounts as there are allocated machines. I can see the machine AD accounts in "readable format" e.g. domain\machine-name$. For these the "State" says "in use". Then there's others in SID format, and and the "State" says "Tainted".

 

 

 

Machine catalog details:

 

Machine type: Desktop OS (virtual)

Provisioning method: machine creation services

Allocation type: Random

 

Link to comment

6 answers to this question

Recommended Posts

  • 0

Hi all,

 

I have a problem updating Machine Catalog in XenDesktop 7.14. I have updated the "golden image" taken a new snapshot and clicked "Update Machines" in Citrix Studio. As a rollout strategy I've selected "immediately".

 

Everything seems to go fine, thing start to happen on our vCenter (version 6.0) and there are no errors. On the machine catalog details the "Disk image" name changes to the new snapshot.

 

But the machines are not updating. They are still using the old snapshot.

 

If I try to create a new machine catalog from the new snapshot everything goes fine, so the snapshot doesn't seem to be the issue.

 

If I run the "Test machine catalog" I get errors:

 

 

If I click the "Manage AD Accounts" there are twice as many accounts as there are allocated machines. I can see the machine AD accounts in "readable format" e.g. domain\machine-name$. For these the "State" says "in use". Then there's others in SID format, and and the "State" says "Tainted".

 

 

 

Machine catalog details:

 

Machine type: Desktop OS (virtual)

Provisioning method: machine creation services

Allocation type: Random

https://www.citrix.com/blogs/2012/01/16/fixing-tainted-ad-accounts-in-xendesktop-5/

 this should help

Link to comment
  • 0

 

This really doesn't explain why the accounts are tainted in the first place. Is this a "feature" in XD 7.x and MCS when you try to update the machine catalog? Also, I have 30 machines in my catalog, and there are already 30 machine accounts in "Manage AD Accounts" that say "in use". Then there are the 30 other machine accounts in SID format that say "tainted". What happens if I fix the tainted accounts. Do I then have double amount of machine accounts? How does the catalog react to this?

Link to comment
  • 0

I tried to Repair the accounts but it didn't work. I then removed the tainted accounts via Studio, and tried updating the catalog again.

 

I checked the datastores after the "update machines" finished (with no errors). On some of the datastores there are two vmdk-files in the "baseDisk-Datastore-xxx" folder, and when I check the vmdk-file of an individual VDI I can see that it is still pointing to the old snapshot.

 

On some datastores there's a new vmdk-file in the "baseDisk-Datastore-xxx", and the old one is gone, and virtual machine's vmdk-file on that datastore is pointing to the new vmdk in "baseDisk-Datastore-xxx".

 

So for some reason, the "update machines" only work partially. Most of the VM's do not update. What is causing this? Also, should the MCS create a new folder for the new "golden image", or should it copy the vmdk-file to the same folder as the old one? On some of the datastores both vmdk-files (old and new) are in the same folder, and on one of the datastores the vmdk-files are in separate _1 and _2 folders.

Link to comment
  • 0

I am seeing the same thing. After updating the master image and selecting all the update immediately options the VMs do not update.

 

I have found a workaround of putting the machines into maintenance mode, shutting them down, deleting them and the associated AD accounts then adding new machines. This seems to update the VMs to the latest master image.

 

Is there any resolution to this issue? This topic has been open for over 2 years!

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