Persona v's Persistant Disk

[smiler1]

Hi All

We have been deploying a number of pools recently but would like to create
them as stateless floating pools. However due to some small, but fundamental, in-house
developed programs we have to create the pools with Persistent disks. I don’t
understand the difference between the profile redirection that happens with persistent
disks in comparison with the redirection that happens with persona. We can easily
replicate the problem but each time we refresh our pool using when it is
configured to use persona management the said application has to be set up
again from scratch. All other user persona info is fine.

Anyone know of a persona expert or knowledge base article that may help me
here?

Regards

Steve

[mittim12]

Do you know where the application writes it's settings in the profile?     Also did you verify that the local profile is syncing with the profile repository?

[smiler1]

Hi Mittim

No sorry, we cannot see where the settings get written, we think it might be in the registry, we have used many tools to try and work it out but had no luck. Im just wondering what the difference is between persistant disk that redirects the profile and persona that also redirects the profile....

[mittim12]

From a high level the difference is that Persona uses an agent to assist in syncing the profile to a set file repository where as persistent disk the profile is just redirected to a secondary locally attached disk.      When your testing did you refresh the pool with the persistent disk to make sure the same problem wasn't present?

[smiler1]

Yes the problem wasn’t present after refreshing using a persistent disk