The case of the missing Personality.ini. I have noticed that with VDA 2203, the Personality.ini is no longer created by default on the root of the C drive, but have struggled to locate some valid information to confirm this. Is this correct? My takeaway is that the Personality.ini is only created when using PVS and MCS. And from VDA 2303 Citrix changed MCS so it creates an MCSPersonalility.ini instead of a Personality.ini. Is this accurate? The main reason I ask is because I had some of my health check scripts getting the content of the Personality.ini, which is now causing errors.

On PVS, I have seen both. Even with a fresh installed VDA.The installer creates a MCSPersonality.ini and a Personality.ini. I think this is due to the introduced PvsVmAgent.exe.

Yeah, the new company where I am working have updated a heap of standalone VDAs to 2203 and there is no personality.ini at all! So this is what my health checks read, similar to BIS-F and Sacha Thomet's script. It's frustrating not to be able to locate some formal documentation on these changes.

Cool. So a default install of the VDA, which includes the MCS components by default, installs the PvsVmAgent service and probably no longer creates the personality.ini. I would then say if you create an MCS image, it creates the MCSPersonality.ini. And if you install the PVS Device Target Agent, you then get the Personality.ini back as expected. So a standalone build with MCS components no longer contains a Personality.ini. I wonder if a standalone build without the MCS components contains a Personality.ini? Would have to do a test to prove that. Either way, I still need to change the code in the health check scripts not to rely on the presence of an ini file.