Exchange and OCS Google custom search

Exchange and OCS Google custom searchI have created a Custom Search engine using Google custom search. I have set it up to only search the sites, blogs and technical resources that I have specified. I will use this search engine when troubleshooting and finding useful information. The point is to remove all the unnecessary hits you get from using the regular search engine and make sure I get hits from the brightest bloggers out there.

I have tried to collect good blogs and resources for Exchange and OCS and have made a list of the sites that are added. Try it out and please let me know if there are sites that should be in the search engine and I’ll add them.

Update 11.08.09: Added Exchange and OCS blogs from Pointbridge

Update 14.08.09 added the following blogs taken from the great collection over at the Communicatins Server Team:

Update 07.02.10 added the following blogs

Update 02.05.10 added the following blogs

Update 24.10.10 added the following blog

How to partition addressbook by Organizational unit using WMI

I tried to partition address book by organizational unit using WMI settings with no luck using this guide:

The goal was to have different organizations hosted on the same server, but without them being able to search each other.

I took me some time to find out that the guide missed some final steps. I have here pasted the whole walkthrough and the additional steps are from 17 and forward

UPDATE: For OCS 2007 R2 you need to replace step 4 to 7 with these steps:

  • Query
  • Select * from MSFT_SIPAddressBookSetting where backend = “<Poolserverinstance>”

The original steps fro OCS 2007 R1 is as follow:

  1. Click ‘Start’ -> ‘Run’ and type ‘WBEMTEST’
  2. Click ‘Connect’
  3. Under ‘Namespace’ type ‘root\cimv2’ and click ‘Connect’
  4. Click ‘Enum Classes’
  5. Click ‘Recursive’ and then ‘OK’
  6. Locate MSFT_SIPAddressBookSetting and double-click it
  7. Click ‘Instances’
  8. Double-click the instance
  9. Under ‘Properties’ find ‘PartitionOutputByOU’ and click ‘Edit Property’
  10. The default value is FALSE, change this to TRUE
  11. Click ‘Save Property’
  12. Click ‘Save Object’
  13. Click ‘Close’
  14. Click ‘Save Object’
  15. Click ‘Close’
  16. Click ‘Exit’
  17. Delete all the files in the addressbook share, server level not client level
  18. Open command prompt and navigate to the location to ABServer.exe
  19. Run ABServer -regenUR
  20. Run ABServer -syncnow
  21. Close Communicator, start it and sign in again
  22. Then it should work

See this post over at Inside OCS for a complete refence guide about WMI:

Phones and Devices Optimized for Microsoft Office Communicator

Optimized for OCSAn important part of implementing Unified Communication in an organization is to use equipment that is supported by OCS. Products that are Optimized for Microsoft Office Communicator can be found over at technet using this link:

I have tested a lot of the Polycom products, including CX-5000 (Round Table), the Microsoft webcams and the Jabra  bluetooth headset. All these products works right out of the box when using Office Communicator, and my customers are really impressed by how simple it is to use these products.  To quote what one customer said: “I knew these products where easy to use, but when it worked right out of the box and without the need to restart the communicator client surprised me. This is something my users will adopt really quick.” 

Save password in MOC

If you have users with computers that are not joined to the same domain that their OCS account is homed to, the users always have to type the password when logging on using Communicator. This is the default setting in Communicator. There is a registry setting for enabling the “remember password” checkbox in the Communicator sign in dialog. I have tested it with non domain joined computers and it works like a charm. Here’s what you do

  1. Open Registry editor
  2. Locate the following key
    1. HKLM/Software/Policies/Microsoft/Communicator
  3. If the key is not there
    1. Create the Communicator folder
    2. Create the key as DWORD and give it the name SavePassword
  4. Set SavePassword=1.  
  5. This enables a checkbox to save password in MOC login dialogue.
  6. After the password is entered it is saved into the registry
  7. HKCU/Software/Microsoft/Communicator/AccountPassword
  8. This registry key store in hashed value. Changing the hash requires re-entering the password.

Original article found over at

Motivating UC Users

I saw this great post over at It was about how to implement UC successfully in a business. See the conclusion below

To sum up, in order to motivate end users to use their UC capabilities, begin the process with a sponsorship team and head cheerleader, get your CXOs to set an example, get users throughout the organization excited about UC, and provide the training necessary to encourage proper usage of the solution

View the entire blog,

I saw this great keynote from Avaya at VoiceCon 2008 talking about what UC is for different types of users in an organization. It is something to keep in mind when implementing UC successfully. Check it out,