Does anyone else do maintenance on the app vol SQL database?
We are seeing:
[2019-02-27 04:36:26 UTC] P3496DJ2683937 INFO Cvo: Unable to find AD entry for Computer <NT_D\VDIDEV1$||conflicted1933;> with ObjectGUID: 6B3D4548-7690-4695-AA06-5E0D75BDF321
[2019-02-27 04:36:26 UTC] P3496DJ2683937 ERROR Cvo: Unable to save "Computer <NT_D\VDIDEV1$>":
Feb 28 2019 04:03PM | Failed to save Computer "Computer <NT_D\VDIHNE5$>" during AD synchronize |
Feb 28 2019 04:03PM | Unable to save "Computer <NT_D\VDIHNE5$>": |
The response from vmware tech support was to delete records from a table:
Right Click on the Table : dbo.computers and select “Edit Top 200 Rows”.
Delete all the entries for the VDI’s. You can select multiple VDI’s in a bunch and delete them
We have VMware Knowledge Base set up as a re-occuring DB job
Hmmm strange. Normally supports suggest not to touch the database as long as it is working. You could end up with very strange behavior if you remove the wrong records.
We do change some settings in the database from time to time but be very very careful with that, make a backup before you start, try not to have a lot of users logged in etc.
Also. If your database is FUBAR i'd suggest just creating a new one. Most of the time this is quicker and better than fiddling around in it. Appstacks and writables are being imported after you set up the database.
We have VMware Knowledge Base set up as a re-occuring DB job
Agreed. I thought it was an interesting suggestion.
That's why I posted...wanted to throw it out to people 'in the trenches'.
da2125,
Thank you. I appreciate the feedback and the KB!