BlackBerry support for OCS 2007 R2

Yes today I got my Blackberry to log into the OCS 2007 R2 Enterprise server today.  The trick is having a OCS 2007 R1 CWA server in place prior to loading R2.  I sure hope RIM fixes that as that is going to cause alot of problems.

OCS 2007 R2 Windows Server 2008 R2

So I thought I would be brave and try to install OCS 2007 R2 on Windows Server 2008 R2.  That was fun…  Lets just say there is a reason it is not supported.  It actually installed but getting the edge server to work correclty with the enterprise front end server is the problem.  So in short do not do it until Microsoft approves it.

Office Communications Server 2007 R2 Web Scheduler is here!

Thanks to Luke for the information on the new R2 Web Scheduler.  It can be found here…

It’s finally available here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6d6848ec-e7d6-41f4-82d9-5bed3526fcbd

Millions Switch from Notes to Exchange

“In our last fiscal year (July 2008-June 2009), more than 4.7 million people began the switch to Exchange and SharePoint from Notes”, Exchange marketing director Julia White posts on the Unified Communications blog.

Read more here:

http://blogs.technet.com/uc/archive/2009/07/23/notes.aspx

Exchange 2010 Poll

Office Communications Server 2007 R2 Group Chat Hotfixes

We recently opened a Microsoft support case regarding some issues with the Group Chat application that is part of OCS 2007 R2.  We applied the hotfix that was released yesterday and so far so good.  You can get the hotfix below.

Client update
http://support.microsoft.com/kb/969818

Server update
http://support.voxns.com/kb/969819

Update Email policy for all users

Here is the PowerShell command for ensuring all users are required to use the default email policy.  This is useful if some admins have unchecked the box for some users.

Get-mailbox | set-mailbox  -emailaddresspolicyenabled:$true

OWA HTTP Redirect URL in Exchange 2007 sp1 on server 2008

This is not as easy as it sounds.  Here is what I done.

By default, IIS7 has built-in automatic HTTP Redirect feature which allows us to redirect to any URL without us having to write any custom scripts.

To accomplish the task, you can follow these steps on the CAS server role hosting OWA:

Step 1:

0, install http redirect feature in the IIS role

1,Log on Interne Information Services (IIS) Manager

2, Switch back to Features view of the "Default Web Site" and double click on "Error Pages".

3, In the Actions pane, click on "Edit Feature Settings" and under "Error Responses", select: "Custom Error Pages". Then click OK

4, In the Actions pane, click on "Add" and configure the following

a) Status code: 403.4

b) Click on Respond with a 302 redirect and provide the absolute URL: https://owa.mycompany.com/owa

Note: Make sure you are using "https"

Step 2:

1,Open IIS 7 Manager

2,Highlight the Default Website and ensure we are in the Features View

3, Double click on HTTP Redirect icon

4, Check the option "Redirect requests to this destination:" and type the absolute OWA URL: https://owa.mycompany.com/owa

5, Under Redirect Behavior section, select the option "Only redirect requests to content in this directory (not subdirectories)"

6, From the drop down, select the Status code: Found (302)

7, Click Apply to save the settings

8, Run IISRESET /noforce command in CMD for the settings to take effect.

Exchange Event ID 9554

I recently encountered some weird Event ID 9554 erros appearing in the event log with the following details…

Unable to update Mailbox SD in the DS. Mailbox Guid: 00e30e16-0f89-4b65-bbcc-f39e7ed1ffe6. Error Code 0×80070005

I found a tool called ADFIND that can be downloaded here:  http://www.joeware.net/freetools/tools/adfind/index.htm

Basically what is happening is that the permissions for the GUID’s mentioned in the log are not inheriting the permissions from the parent.  We had 2 accounts doing this and another admin had modified the individual permissions for those accounts and caused the error.

Using the ADfind tool you can find out the actual user name of the account having the problem and go to properties in AD users and computers and check the allow inheritable permissions from parent to propagate to the user.

Use this syntax:

C:\AdFind>adfind -gc -b "" -binenc -f " msExchMailboxGUID={{GUID:00e30e16-0f89-4b65-bbcc-f39e7ed1ffe6}}" –dn

You should receive a user account in the output.  Replace the GUID information with information from your own error.

New Theme

I was getting kind of tired of looking at the old theme so I decided to change it up a bit.  What does everyone think?  Is it easy to read?