We are deploying a VMware Horizon View 5.3 system with Windows 7 x64 linked-clone desktops to a medical centre.
Their medical management software stores each users printer settings under HKCU in the registry on the linked-clone desktops. It stores the "Workstation Name" and Printer Settings for "A4 Letters", "A5 Receipts", "Scripts" etc.
This format of storing printer settings is not really compatible with a linked-clone deployment. We have written scripts that exports this information "at will" - i.e. click on an icon on the desktop, and then reapplies the saved information when a user logs on.
The doctor then sets all of his desired printer settings in the medical application, clicks "Lock Printer Settings" icon on the desktop (saves registry settings and user details to central store). These settings are then imported into the registry based on the username when a user logs back on - no doubt getting a different linked-clone desktop.
This works fine, however - here lies the problem:
ViewPersona only "syncs" the registry every 10 minutes (as set by GP). If a doctors changes his printer settings and then immediately uses the "Lock Printer Settings" script, it exports the previous printer settings and the ViewPersona has not yet had time to "Sync". I know we could change the GP to SYNC every 1 minute, but it is still is not foolproof.
So, question: is there a way to force the ViewPersona to "SYNC" by running a script - initiated by the user, from their linked-clone Windows 7 desktop?
I would envision that we would incorporate this into the current "Lock Printer Settings" script. i.e. Sync the ViewPersona, and then export registry items.
Any help would be appreciated.
Cheers,
JD.