A Unified Communication Blog
Get Adobe Flash player

Monthly Archives: May 2008

Symantec has released Service Pack 3 to Enterprise Vault 2007.

See the message from the EV Guys at Symantec and get the download links from there blog:


I have just made a brand new Exchange 2007 SP1 CCR cluster on a Windows 2008 platform for one of my customers, and that kind of environment needs to be backed up from time to time.
And since HP Data Protector 6 doesn’t support Windows 2008 before version 6.1 which is scheduled to be released in September, I decided to test Microsoft Data Protection Manager 2007 which has support for both Exchange 2007 SP1 CCR clusters and Windows 2008.
From other bloggers and forums on the internet I have found that I’m not the only one which has got at lot of “fun” with DPM 2007 in that kind of environment.
So I will like to share some of the experience I have got with the product so fare and hopefully help others.

Problem 1: Installing the agent on Windows 2008
I had/have like many others problems with remote installing the agent to Windows 2008 servers. But the last installation I made I have disabled the Windows firewall before I pushed the agent to the servers. And that worked the first time with no problems.
Also remember to install the feature pack 1:
x86: http://www.microsoft.com/downloads/details.aspx?FamilyID=e9e1fe35-b175-40a8-8378-2f306ccc9e28&displaylang=en

x64: http://www.microsoft.com/downloads/details.aspx?FamilyID=ad5cd1a2-9b87-4a2c-90a2-9dbaf1024310&DisplayLang=en

With Feature Pack 1 you get System State Support for Windows 2008, SQL 2008 Support and better tape support.

I haven’t found the golden way to remote install the agent when Windows firewall is enabled (yet), But I have seen in other blogs that File and Print Service and WMI MUST be enabled in the firewall on the server that you try to push the agent to.

Problem 2: How-to Protect Exchange 2007
I did like many others – installed the DPM and when I couldn’t get it to work I read the manual.
My first problem was that I couldn’t see or select my Exchange stores in the Protection Group wizard.

Solution: Install EMC on the DPM server (with the same patch level), and on the same drive as the DPM.
Copy ese.dll and eseutil.exe to the DPMBIN folderAnd run this command on the DPM server:
Fsutil hardlink create “C:Program FilesMicrosoftDPMbineseutil.exe” “C:Program FilesMicrosoftExchange Serverbineseutil.exe”
The fsutil requires that DPM and EMC is installed on the same drive, otherwise the command will fail.

Link to the agent Prerequisites in the manual: http://technet.microsoft.com/da-dk/library/bb808827(en-us).aspx#ExchangeServerDatabaseUtilities

Problem 3: Protecting Windows 2003 Server
Before you deploy the DPM agent to Windows 2003 servers remember to install the VSS patch.http://support.microsoft.com/kb/940349/
I didn’t install the patch on my first 2003 server, and it took 30 min for the server boot – not cool for a production server.

Problem 4: Couldn’t see the virtual cluster node
As I wrote in the beginning, one of my installations was to protect a Windows 2007 CCR SP1 cluster installed on two Windows 2008 servers.
I manage to install the agent on both nodes in the cluster with no problems. Afterwards I could also see the virtual cluster name, but I couldn’t see or select my virtual exchange server.
After some time I found the problem – a failure in my CCR cluster.
I had at some point after I have installed the cluster created a new storage group and mailbox store which I then later on deleted from the EMC. No problem with that – but it seems like that there might be a bug somewhere (either in Exchange or in Windows 2008), because the deleted mailbox store was still a resource in my Failover cluster management tool.
After I deleted the failed resource in FCM then I could see my virtual exchange server name in the “Protection Group wizard” – and then backup works.

Problem 5: Can’t select System State on Windows 2008 Server
When I’m selecting my Windows 2008 servers I can only see “All Shares” and “All Volumes” but not my System State.

Solution: Install Feature Pack 1 and you will get Windows 2008 System State Support.

x86: http://www.microsoft.com/downloads/details.aspx?FamilyID=e9e1fe35-b175-40a8-8378-2f306ccc9e28&displaylang=en

x64: http://www.microsoft.com/downloads/details.aspx?FamilyID=ad5cd1a2-9b87-4a2c-90a2-9dbaf1024310&DisplayLang=en

There is no support for 64-bit in Office Communications Server 2007, however the word out there is saying that it will be supported in the upcoming version of OCS, called Office Communications Server 2007 R2. (Coming this fall)

UPDATE: (July 28.)
A comment posted about the upcoming version of OCS 2007 R2 release date on this blog, states that the new release will be 64 bit only….. However this is not confirmed.

Office Communications Server Product Roadmap (Unified Communications)

There have been a lot of questions since the lastest article about the future of OCS. (http://it-proknowledge.blogspot.com/2008/04/office-communications-server-2007-r2.html)

So heres a summary:

Office Communications Server 2007 R2

OCS 2007 was relased in second half of 2007. Microsoft is working on a new release of OCS called Office Communications Server 2007 R2. Like Windows Server 2003 R2, this version is an updated version with new features (and probably many bug fixes)

OCS 2007 R2 is not officially announced yet, so there isno official release date of the product. My sources do say that its second half of 2008, and targeted for october-november release.

Office Communications Server 2009

OCS 2009 is the next, and will bring us a new version of the product. Here we can expect a lot of new features, and the plans for the product is quit empressive.

The product is targeted for release in second half 2009

The release dates are not officicial (eg. The products are not official), but knowing how much man-power and money Microsoft puts in to the Unified Communications solution, I am betting on the dates on this roadmap will hold.

I will post again soon, with information about what features we can expect of the products.


There still seems to be some problems locating the official download site for Office LiveMeeting Client. Doing some simple searches at google/live explains this. Its simply hidden to well on MS.com :)

So heres the URL :

Microsoft Office LiveMeeting 2007 Client:

And dont forget
Conferencing Add-in for Microsoft Office Outlook

Get morer Live Meeting resouces here:

Office Communicator has an software package to enable Multilingual User Interface (MUI), but this is not the case for the LiveMeeting client.

The LiveMeeting client (and the Outlook Conferencing add-in) has this functionality built-in the original software package, and no additional download is nessesary.

However, Microsoft has added more languages in the latest release of the client (and will probably add more in the future)

Get the latest version here:


Microsoft has released a Multilingual User Interface (MUI) Package for Microsoft Office Communicator 2007

The packaged includes the following languages:

Arabic, Bulgarian, Chinese – Simplified , Chinese – Traditional, Chinese Hong Kong , Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hebrew, Hindi, Hungarian, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Polish, Portuguese (Portugal), Portuguese-Brazil, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish &Ukrainian.

Controlling the language used is done from inside the Communicator or from registry

OCS MUI download:
OCS MUI Whitepaper:

Office Communications Server 2007 synchronizes the address book once every day. This is ok for normal operations, but in tests and troubleshooting scenarios, this can be a bit annoying.

To work around this problem, you can create a simple .bat file to do a manual synchronization of the address book, to update the details of the users from Active Directory.

After synchronization, you still need to log off the Office Communicator client, and log back on to get the client to download the updated address book.
Create a .bat file (absync.bat)

Put the following command in the file (update the path, if you haven’t used the default)

“C:Program FilesMicrosoft Office Communications Server 2007ServerCoreabserver.exe” -syncnow

Let me know if you have any problems.

Office Communicator displays the following warning to users:

some calls to and from people outside of your corporate network may not connect due to server connectivity problems. Try Signing out and signing back in. If this problem continues, contact your system administrator with this information.

This is most often because of faulty configuration of the Front-end and Access Edge server.

Verify the listening ports of the Access Edge server and the Front End server that they match.
Verify connection on the specified port (do a telnet on the A/V port)

Let me know if you have any probles (post comments below)


I have seen this error many times out there. Its to do with the Mediation server that is unable to contact the A/V Authentication server on the OCS Access Edge server. There are many reasons for this, there being a lot of places to set the references for Mediation, FE and Access Edge server.

Heres some places to look:

- Verify that alle Mediation servers are added to the Access Edge servers “verified” internal servers list
- Verify that alle Front End servers are added to the Access Edge servers “verified” internal servers list
- Verify that the A/V Authentication server is configured on the Mediation Server (and pointing to the Access Edge server holding this service)
- Verify firewall configuration by telnet to the A/V aut. port from the Mediation Server
- Verify that the Access Edge server is configured on the Mediation Server and Front End Server

Please continue to comment

For OCS 2007 R2 problems, also refer to this post:


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 77 other subscribers

Follow me on Twitter