Custom presence states in OCS – revisited again

I posted a while back about custom presence states (here and here). Well it turns out that a change made to an updated version of Communicator, requires (by default) that the custom state XML file is downloaded from a “secure” URL (so ruling out the file:// URL type).

I’ve posted my XML file to SkyDrive (since it’s available with an SSL connection and tends to be available from everywhere).

If you want to use the same URL, just open the following registry file and it will point your Communicator client at my XML file…

Registry file

Otherwise, add your own URL to the registry at

HKEY_LOCAL_MACHINE\SOFTWARE
\Policies\Microsoft\Communicator
in a string value called CustomStateURL.

(tip – if you don’t trust me, download the REG file and drag/drop it into Notepad to verify that it’s not going to do bad things to your machine).

Comments

• Anonymous
  January 01, 2003
  Between OCS 2007 R2 release candidate and RTM, the custom presence rules changed. You can no longer use the file:// method to specify the XML file to use for setting your custom presence. A long time ago, I posted about custom presence in OCS 2007 R1

• Anonymous
  January 01, 2003
  Whilst I’m on the subject of OCS, voice and presence , I noticed that Ewan has updated his document on

• Anonymous
  January 01, 2003
  digg_url = "http://blogs.technet.com/eileen_brown/archive/2009/02/27/more-on-custom-presence-states-in-ocs.aspx";digg_title

• Anonymous
  January 01, 2003
  Mr Dalton figured it out yesterday: http://blogs.technet.com/ewan/archive/2009/02/06/custom-presence-states-in-ocs-revisited-again.asp

• Anonymous
  February 08, 2009
  Awesome find. Good to know custom presence is still available.