Monthly Archives: August 2008
MS has released an updated documentation about the Archiving and CDR server role
Get it here:
Office Communications Server 2007 Document: Archiving and CDR Server Deployment Guide
MS has released a planning tool for OCS 2007 Edge server deployment.
The tool askes a lot of questions about certificates IP addresses and othe infrastructure related items, and generates a report based on your answers.
Its a nice tool to get an overview of tasks and configurations needed to deploy the Edge Server role
Get it here:
The Edge Planning Tool for Microsoft Office Communications Server 2007 provides settings for configuring your perimeter network based on information that you provide to the tool.
There is an updated version of the OCS BPA tool out from Microsoft.
Heres what is new:
Even if it’s a bit off-topic, here’s some experience I’d like to share. (Mostly because I spend a lot of time finding out myself)
The new Windows Server 2008 Terminal Services provides us with many new feature and server roles, which I will not cover here. But working with them also adds new questions to the game.
I have been working on publishing a Terminal Service Gateway (TSGW) & Terminal Service Web Access (TSWA) with Microsoft ISA Server 2006.
If we just put aside the ISA server for a moment. When publishing TSWA using TSGW, the users are prompted for login twice. Once for the web access page, which provides users with a list of published applications, and secondly when they connect to an application, for login to the terminal server.
So I wanted to provide this service to the users using single sign-on (SSO) with ISA servers SSO features, using form based authentication (also provided by ISA). So when users access the URL of the TSWA, they are authenticated through a HTML form, rather than a Windows login dialog box, and only asked to supply login credentials once, having the ISA SSO pass the login credentials to TSWA page and the Terminal Server
Let me put it short; this is not possible!
It works fine when it comes to the TSWA page. Logging on at the HTML login form (form based authentication (FBA)) provides access to the list of published applications. But accessing any application on the terminal server will fail, by users being prompted for credentials over and over again.
The reason being that ISA server is not capable of providing SSO data for the TSGW and the Terminal Server, where the application is. ISA server SSO is mostly for web page login, and not for Terminal Service. If SSO is enabled on the ISA server, the system is not able to let you authenticate directly (ISA server intercepts the login request) and therefore users cannot logon to the application.
Knowing this, I would like to see some SSO features in Windows Server 2008 Terminal Services, or maybe it belongs to the ISA Server. But SSO for the new TS architecture is greatly missed.
Please don’t hesitate to post updates if you have found a way around this, or if the above is unclear in any way.
August is as always very quiet, also when it comes to news about Microsoft products. But being as curios about the next version of OCS, as you probably are, here’s what I got since my last post.
The release date seems to (unofficially) be December 2008. I have no doubt that there are strong forces inside Microsoft that wants this version out on the street this year, and with good reason. Many companies are adopting OCS, and are amazed with the features of Unified Communications from Microsoft, and are pushing forward to unified there communications solutions. The benefits are real, both in supporting the information worker, and in user productivity.
Other UC solutions from more traditional VoIP manufactures, seems the lack in functionality and user experience when they are compared to Microsoft UC, on all front except the basic phone system functionality, where MS UC still cannot stand alone.
This will certainly be addressed in the upcoming version of OCS, the Office Communications Server 2007 R2.
So what’s next…
I have blogged about the features of R2 for the last couple of months, and still its only my best guesses, next I would be thrilled to see it in action. As a commentator wrote on this blog, its more likely to be a “new build” than just an update package, like we saw with Windows Server 2003 R2. Alone based on the rumor that R2 is going 64-bit only, we can conclude that we need to setup new servers.
Earlier I posted about the TAP program for OCS 2007 R2, and it is live for a few selected customers. Whether there are going to be a public or closed beta program is not certain yet, but I will surely keep you updated on this.
Stay tuned for more updates (http://it-proknowledge.blogspot.com/search/label/OCS%202007%20R2)
Microsoft has released an updated article about the common problem with errors regarding synchronization of the address book.
The article includes new information, and links to older articles on the same issue:
Microsoft has released another update for Office Communicator 2007. The patch fixes the following issues found in MOC 2007:
954642 (http://support.microsoft.com/kb/954642/) Error message when you restart Outlook after you log off Windows without exiting Communicator 2007: “A data file did not close properly the last time it was used and is being checked for problems”
954648 (http://support.microsoft.com/kb/954648/) How to disable instant messaging in Communicator 2007
954649 (http://support.microsoft.com/kb/954649/) When you use Communicator 2007 together with a GN9350 headset to make a call, the call ends when you mute the microphone
954651 (http://support.microsoft.com/kb/954651/) Communicator 2007 downloads the full offline address book every 30 days
Get the patch here:
The patch replaces previos patches for MOC 2007.
For information about slipstreaming the patch to update the MOC install files see here: