Using the Client Version Filter to upgrade from 2.x to 3.x

• Wednesday, 28 October 2009 4:48 PM

   

   
  

  0
  I just used the info on Aaron Tiensivu's blog ( http://blog.tiensivu.com/aaron/archives/1865-Demystifying-the-Office-Communicator-2007-R2-Client-Auto-Update-feature-and-how-to-setup-it-up.html ) to upgrade a MOC R2 client from 3.5.6907.0 to the latest patch level, and it worked great (Thanks, Aaron!).

  
  

  I tried it again in an attempt to upgrade a 2.x version of MOC to the same latest version, but when I do this, MOC throws an error about not being able to sign in. Is this even possible, or are we going to have to use SMS or Configuration Manager to deploy version 3.5.6907.x of the MOC client?

  
  

  Thanks.