https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
n
These are persistent MCS devices that were migrated from on-prem to cloud. We're trying to figure out how to correct this, and simply enabling auto-update of the DDCs (this was previously disabled) doesn't seem to do anything. The weird thing is that the DDC cache shows the correct controllers, so that appears to be updated. It's just the ini file that is bad.
What's also weird is that we're 99% sure that we manually fixed the INI file for these devices during the migration, but now they're back to being broken.
r
You need auto-update to be prohibited for the desktop to use listofddcs fiorst
is that what you menat by disabled
then you have to reboot after getting the policy plus the new list of ddcs
or jsut restart the dekstop service
it shoudl then recreate the personality .ini
n
Maybe that's my confusion. We initially had auto-update prohibited, but we just enabled/allowed it, and were expecting the file to get updated after 90 minutes.
r
when autoupdate is enabled it tell the vda to use the cache first
n
So when does the file get queried for the DDS? When auto-update is disabled?
DDCs
r
so the cache never gets updated wiht the new controllers
so by prohibiting that it will look at the list of ddcs first
n
The cache was still good with auto-update off
At this point, I'm trying to figure out a process for recreating the file... have not tried outright deleting it.
r
its hard to delete or change since you need to be system
n
Bouncing the desktop service and waiting hasn't done it, and I have a few minutes left before seeing if the reboot did.
Changed the perms of the file so that we had access to do so.
r
you can just delete the persoanlity.ini and the list of sids and then they have to be recreated using the list fo ddcs
n
Wait, where is this list of SIDS?
r
its a hideen system file
n
Are you talking about that cache file (XML) in C:\Program Files\Citrix\PvsVm\Service\PersistedData\Brokersomething
r
n
Yeah, been reading that page, but my eyes are bleeding
Okay, yeah, that's the file I was referring to.
You have to jump through a bunch of hoops to even access it.
So let me ask this then: with auto-update enabled, should we even care about the Personality.ini file?
r
But truthfully as long as when you installed the vda you chose do it later for the list of ddcs, and you use a policy for the new list and yo prohibit auto-update. Then it has always worked for me to change the controllers
n
We do set the list of DDCs via registry
Our silent VDA installs don't list out any controllers
r
but you cna use psexec to dlete the ini file
n
We can, yes... but do we even need to?
r
only if you cant figure out why its not working the other way
n
So kill both the ini file and the hidden cache XML file, bounce the desktop service?
r
But yes delete the personality.ini and use the wmi call martin discusses to find out wher ethe list of sid file is
n
Read that yesterday, too, haha
r
but hopefully you wont need that
n
Just checked, enabling auto-update and bouncing the VDA didn't correct that INI file
r
if you cnat get it let m eknow michael and i can get on a call wiht you if you have a vda to test on
but did you register wiht the new site
n
I definitely want to talk about it on Monday's working session
That's the thing, it is registered
r
i dont know how that file looks what you are seeing nmay not be an issue
n
I'm trying to get more info. I jumped into this thing mid-stream.
To me, enabling auto-update should be all that matters... don't care about this stupid file anymore
r
agreed
not unless its causing issues wiht registraiton
n
Apparently, while troubleshooting VDAs showing unregistered, this weird file is always on those devices. But they do eventually register, which is making this weird.
r
so a timing issue
n
Could be. I think it sounds like we want to see if you can join one of our working sessions next week so that we can just discuss it. Definitely better coming from somebody other than me, as this is all second hand.
r
Sure michael can see my calendar
and work out a time
n
Okay, good deal - thank you!
👍 1
Open in Slack
PreviousNext
Powered by