My little Communicator application for publishing custom presence has been non-functional for some folks. I spent some time trying to fix it and think I figured out most of the problem – it works just fine for users who have made the required registry edit manually or previous to running the application. If the user never has created the necessary registry key for enabling custom presence, the application never worked. I’ve been completely unsuccessful in creating a legitimate fix so I’ve resorted to a cheapskate approach and made the application now require UAC privileges. If you were having problems I would try this updated version, but if the old version worked for you and you are not an Administrator on your box, I’d recommend sticking with the old version for now. Another solution would be to simply run the original version in an Administrator context by right-clicking on the application and choose “Run as Administrator.”
I’m hoping to get a better solution up soon, but this works as a stop-gap.
Download: Communicator Custom Presence Tool 1.1
On the note of a better solution – I’m not much of a programmer so maybe someone has an idea for me.
My problem is a normal user in Vista does not have write privileges to the HKEY_CURRENT_USER\Software\Policies\Microsoft key. It seems odd, especially considering that’s within the HKCU hive. So the application fails when it tries to create the HKCU\Software\Policies\Communicator key. The .XML file gets created just fine, but Communicator will never look for it because the registry key to tell it so never got set. So how the heck can I use VB to say “Open this registry key, add the permission to create a subkey?” Is it even possible without the user having write access on that key? Every time I try programmatically I get denied access, even if I open the parent key for editing. It’d be swell to be able to do this without requiring a UAC prompt.
If I ever figure that one out I have some cool ideas for a nicer GUI and 2.0 release.