I ran into this issue with OCS 2007 and thought it might come in handy for someone in the future. Lets say you deploy OCS 2007 in your environment, and in AD you use the phone number field for the office ext, and you want to keep that format. Lets also assume you are noticing that if you use this configuration you end up with warnings in communicator saying it cannot synchronize the addressbook. When you check the event log on your OCS server you see errors and warnings about the addressbook server. You won’t find a service for this component (at least I couldn’t find it), it appears to be built-in to the OCS server software. You also find a list of invalid AD phone numbers in your C:Program FilesMicrosoft Office Communications Server 2007Web ComponentsAddress Book FilesFiles directory.
So how can you keep your internal extensions in their current format and still communicator without having to see the annoying addressbook warning. Its not simple, but the fix is not too complex to impliment. Here is what to do. This assumes that you use a format such as “x 5555” for your extensions in AD for the users in the phone number field.
First, in the OCS 2007 console, right click on the forest, and go to properties, then select voice properties. Next, click the “Add” button to setup a new default location profile. Give it a name and a description. Next, under “Normalization Rules” click the “Add” button. Give this a name also and a description. Under translation, enter “^(x|X|x |X )“ without the quotes in the “Phone pattern regular expression” box. In the next box, enter “$`” Thats a dollar sign, immediately followed by the key to the left of the number one key on the top number row of your keyboard. To test this, enter an extension in the same format as you use in AD in the “sample dialed number:“ box. If it works you should see the resulting number in the format you want in the bottom text box.
Save you changes by clicking “ok” until you are back at the console screen. Then you just need to issue some commands on the server to update the address list, which are listed below: (NOTE: CD To the directory of your abserver.exe location)
Click Start, click Run, type cmd, and then click OK.
Type net start abserver, and then press ENTER.
Type abserver.exe –regenUR, and then press ENTER.
Type abserver.exe –syncNow, and then press ENTER.
Exit and re-start communciator on your PC/laptop and it should now load with no errors or warnings and you will now see your extensions listed.
I just came across this artile about a tool that automates the little known feature of custom presence in Communicator 2007. Those of you familiar with other IM platforms will appreciate the incorporation of this feature in Communicator 2007. Although as nice as this is, tell me Microsoft…why aren’t you building this into the GUI in the first place?
One of the things I found tricky about switching to Windows Vista was setting up local GPO Settings. I opened gpedit.msc and was intentionally trying to add a .adm file for Office Communicator 2007. I tried everything I knew how to get the .adm file to show up in gpedit, but I couldn’t figure it out. I tried copying the communicator.adm file to C:windowsinf and C:WindowsPolicy Files and nothing worked. I even ran across an article on converting .adm files to .admx format for Windows Vista using the ADMX Migrator. When I tried to convert the file, I got 126 errors and decided that this may not be the way to go. Finally I found an article on how to add the legacy file format and get the job done. Its actually already capable of loading the legacy .adm file locally, and here is how to do it…
1. Open gpedit.msc
2. Expand either computer configuration or user configuration
3. Right-click on the Administrative Templates folder and select “Add/remove templates”.
4. Browse for the .adm file you wish to load and select it for opening.
You now have the .adm file loaded and you can then make changes and configure the policy settings. Also I’d suggest turning off the User Access control option (under control panel > User Accounts) so that you don’t have 500 prompts from Vista asking if you are sure you want to do stuff. How annoying! 🙂