Finally released and with some much needed compatibility updates to better support Exchange 2007 SP1 on Windows 2008.

A note from the MS Exchange Team…


  • 950138 ( You are prompted for your credentials three times and you receive an error message when you use the Outlook Anywhere feature to connect to an Exchange Server 2007 Service Pack 1–based server that is running Windows Server 2008
  • 951251 ( A MAPI application does not work correctly if Exchange 2007 is installed on a Windows Server 2008 server
  • 948896 ( Certificates that contain wildcard characters may not work correctly on an Exchange 2007 Service Pack 1-based server

Click here to download the update…

Click here to review the associated KB article (952580)…

Click here to read my post on installing Exchange 2007 SP1 on Windows Server 2008…

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

Can’t wait to try this out…things are getting very interesting. How long before someone loads this on their laptop?


Microsoft® Hyper-V™ Server 2008 is a stand-alone product that provides a simplified, reliable, cost-effective and optimized virtualization solution enabling organizations to improve server utilization and reduce costs. It allows organizations to consolidate workloads onto a single physical server and is a good solution for organizations who want a basic and simplified virtualization solution for consolidating servers as well as for development and test environments. Low utilization infrastructure workloads, departmental applications and simple branch office workloads are also candidates to virtualize using Hyper-V Server 2008.

So just what is Hyper-V?

(from the MS Virtualization Team blog)

  • Hyper-V Server 2008 was built using the Windows hypervisor and other components, including base kernel and driver technologies. Microsoft Hyper-V Server 2008 shares kernel components with Windows Server 2008.
  • Microsoft Hyper-V Server 2008 contains a sub-set of components that make up Server Core deployment option of Windows Server 2008, and has a similar interface and look and feel. But as you know, Server Core has roles like DNS, DHCP, file. Hyper-V Server 2008 is just virtualization.
  • Because Hyper-V Server 2008 shares kernel components with Windows Server 2008, we don’t expect special hardware drivers to be required to run Microsoft Hyper-V Server.
  • The maximum number of guest instances that can run on Microsoft Hyper-V Server 2008 is 128 (of course this is dependent on the hardware, memory and workloads). Additionally, each guest OS must have a valid license.
  • Hyper-V Server 2008 runs/upports all the guest OSes supported by its big brother, WS08 Hyper-V. See here for a complete list.

The Virtual PC guy’s post on Hyper-V Server 2008…

Here’s a screenshot of Hyper-V Server 2008 after first logon:

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

An update to Forefront for OCS was just released to the Microsoft Downloads site.

Click here to download…

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

Francois Doremieux,& Jerome Berniere have written a great article that talk to the changes around Direct SIP with IP-PBX for Office Communication Server 2007 with the August 2008 OCS updates. These updates allow OCS 2007 to talk with non-RFC3966 compliant IP-PBXs. In other words, the updates allow OCS to remove the “+” from the outgoing dial string and deal with no “+” on incoming dial strings.


What is changing?

This change gives administrators the possibility to set up Office Communications Server so that it can directly interoperate with IP-PBX using E.164 globally routable telephone numbers without RFC3966’s mandated “+” prefix. Additionally, Office Communications Server will now be able to interoperate with IP-PBX within a private dialing plan, exchanging locally routable private numbers.

What is Direct Sip with IP-PBX?

Direct SIP with IP-PBX is a variation in which the calls are exchanged over IP between the Mediation Server and an IP-PBX, without the use of back to back IP/PSTN gateways (i.e. in IP all the way, without transcoding between IP and TDM).

Why did Microsoft not support Direct Sip with IP-PBX until now?

Microsoft actually had built that capability from the start both into the product and into the OIP, in a standard-based way, and was ready to support Direct SIP with IP-PBX that qualified in the OIP. However, testing showed that few if any IP-PBX were capable of meeting the standards-based specifications for Direct SIP interoperability and OIP qualification.

How can I use Direct SIP with IP-PBX on OCS 2007?

The changes are accessible to users of Microsoft Communications Server 2007 via update packages as described in the following Microsoft Knowledge Base articles:

Click here to read the article…

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)