Heres the TechNet doc. About whats included in the SP1 for Exchange 2007: What’s New in Exchange Server 2007 SP1 To download Exchange 2007 SP1, see Exchange Server 2007 Downloads. New Deployment Options
Microsoft Exchange Server 2007 Service Pack 1 (SP1) introduces many new features for each server role. This topic discusses the new and improved features that are added when you install Exchange 2007 SP1.
Client Access Server Role Improvements
Improvements in Transport
Mailbox Server Role Improvements
Unified Messaging Server Role Improvements
Heres the TechNet doc. About whats included in the SP1 for Exchange 2007:
What’s New in Exchange Server 2007 SP1
To download Exchange 2007 SP1, see Exchange Server 2007 Downloads.
New Deployment Options
FYI: I found an interesting article from TechNet magazine, that describes some of the OC GUI enhancements of Exchange 2007 SP1:
Improvements to Unified Messaging
Unified Messaging was an exciting part of the initial Exchange Server 2007 release. Service Pack 1 builds upon this functionality, introducing many new features and enhancements. Some of the features require you to deploy Office Communications Server 2007 in the same Active Directory forest, but there are many features that don’t require Office Communications Server. I can’t cover all of the changes to Unified Messaging here, but I will run through some of the notable additions. If you want to read more about Unified Messaging, check out “Deploying Unified Messaging with Exchange Server 2007″ in this issue of TechNet Magazine for more information.
First I’ll touch on some of the new features that do require Office Communications Server 2007. There is now support for media streams to traverse firewalls and for high-fidelity voice messages. There is notification of forwarding when leaving voice messages when the destination uses call forwarding. Users can access Outlook Voice Access from Office Communicator 2007 without entering a PIN. There is integration of missed call notification e-mail messages and voicemail notification with Office Communicator 2007 (see Figure 5). And much more.
Figure 5 Voicemail notification in Office Communicator
One of the enhancements to Unified Messaging that doesn’t require Office Communications Server is support for the Secure Realtime Transport Protocol (SRTP). The initial release of Exchange Server 2007 offers two security modes: unsecured and secured. The secured mode only encrypts the Session Initiation Protocol (SIP) traffic, and the RTP traffic is unencrypted. In SP1, there are three modes: Unsecured, SIP secured, and Secured. In SIP secured mode, only the SIP traffic is encrypted, not the RTP traffic. In Secured mode, both the SIP and RTP traffic are encrypted. You can also configure Mutual Transport Layer Security (MTLS) for dial plans using the Exchange Management Console.
Other changes include the new Enable Unified Messaging Wizard, which you can use to add an SIP or E.164 address for a user; configuring the URI type for a dial plan using the Exchange Management Console; and Quality of Service (QoS) support using DiffServ for tagging media traffic was added to SP1.
Full article here: http://www.microsoft.com/technet/technetmag/issues/2007/12/SP1/default.aspx
Update (December 2008)
After a lot of troubleshooting I have to admit that this is not going to work. See the follow-up article here: http://it-proknowledge.blogspot.com/2008/12/federation-branding.html
After some investigation, i found that even if it isn’t documented anywhere in the OCS 2007 doc kit, its is possible to brand incoming and outgoing federation connections, with a logo or icon. This works well for federations, where it is possible to show a icon next to your users name in the federated partners MOC client. Also it is possible to “brand” incoming federation traffic, with an icon that shows this contact is external from the company (this works only if the specific federation partner don’t use branding, in this case, there icon will be shown) Branding also works for public IM, so that Windows live/MSN users can see an logo next to the contact in the chat session.
It pretty basic:
All you need is to get hold of the ResKit from LCS2005, and install this package. It will install the necessary files, and you just need to follow the instructions in the readme
From the readme file:
Microsoft Office Live Communications Server 2005 with SP1 SDK
Copyright (C) 2005 Microsoft Corporation. All rights reserved.
Branding.am is an SPL script that demonstrates adding a branding URL to the
presence body of SIP messages. The Branding URL is added as an
tag in the presence body for all messages that contain presence documents that are
leaving the enterprise network and are destined to a partner network. The application
also allows a URL to be added to messages that are entering the enterprise network if
clients can then contact this url and download the branding image for display.
A default federation branding URL may also be specified. This URL will be added
to all messages entering the enterprise from a federated network if the message
does not have one already. This feature is optional.
This sample demonstrates:
- Modifying the presence body of NOTIFY messages
- Network edge awareness
Creating and deploying icons
Before the Branding application can be deployed, the icon itself must be
created and deployed. If the icon is to be displayed in Microsoft Office
Communicator 2005, the icon must conform to the following rules-
- File format is .png.
- File size does not exceed 8 KB.
- Icon dimensions must be 16 x 16 pixels.
- Maximum 32 bits per pixel.
This program supports deployment of two icons for federated traffic,
one for presence documents leaving the network and one for presence documents
entering the network. The external icon is the one displayed to external
users on behalf of local users. Both icons must be deployed on an external facing
Web server that allows browsers to display the image from inside and outside
the local domain by using the URLs specified in the BrandingUrl and
IncomingDefaultFederationBrandingUrl variables, respectively. Only HTTPS
(secure HTTP) URLs will work with all supported clients.
Configuration and Setup
To install and run this sample, you will need the following software:
- Microsoft® Windows Server™ 2003
- Microsoft Office Live Communications Server 2005[MC1], Access Proxy
- Microsoft Office Live Communications Server 2005 SDK
1. First, open the Branding.am script and change the BrandingUrl property [MC2]to contain
the appropriate branding image for your deployment.
2. Optionally, edit the IncomingDefaultFederationBrandingUrl property to contain the
appropriate default federation branding image for your deployment. For details, see the Remarks section
3. Click Start, click Control Panel, and then double-click Administrative Tools.
4. Double-click Computer Management. In the navigation pane, expand Services and Applications, and then click Microsoft Live Communications
5. Right-click the Applications node, and then click Properties and then click add.
6. Click Browse, and then locate Branding.am.
7. In the Application Name box, type Branding.
8. In the URI box, type http://www.microsoft.com/LC/SDK/Samples/Branding
9. Click OK.
10. Start the Live Communications Server service.
By default, the branding application is configured to add the branding URL only
to outgoing messages that are bound for federated partners.
By specifying an incoming default federation branding URL, you can add a
branding URL to messages that enter the enterprise from federated [MC3]partners. This behavior
is helpful in the following scenario:
- Fabrikam[MC4].com is federated with Contoso.com.
- Contoso.com does not add a “Contoso” brand icon, so Contoso users in Fabrikam.com
will look like any other enterprise user.
- If the Fabrikam.com administrator decides that such federated users should be
distinguishable from enterprise users, he or she can choose to
supply a default federation URL that will be appended to all messages from federated partner domains.
- Fabrikam.com users will see the default federation icon if none is supplied
by the federated domain.
What you need is the LCS 2005 Resource Kit (http://www.microsoft.com/downloads/details.aspx?FamilyID=D21C38E5-5D8F-44C7-BA17-2CC4F85D8B51&displaylang=en) witch include the script (branding.am) file and the complete read me.
Wondering wether or not i could expect that Communicator Mobile would update the presence status when making af call for the mobile phone, i did som investigation. Heres what i found:
The current release of Windows Mobile and Office Communicator 2007 Mobile (MoCo), does not allow the update af presence status. Actually there are no integration at all, other than the ability til make a call or send an email from the
This might be a combination af lack of functionality in the WM OS and the MoCo client, but the future look bright with the coming realeses of both.
I found some information about Windows Mobile 6 R2:
Watch the CE 6.0 R2 Virtual Launch webcast now and see Kevin Dallas, General Manager for Windows Embedded, unveil CE 6.0 R2 at Embedded Technology 2007 in Yokohama, Japan. Windows Embedded CE 6.0 R2 adds even more exciting technologies to the CE 6.0 operating system – technologies that embedded developers can use to boost their creative capabilities and easily establish connections to Windows Vista, Windows Server 2008 and other devices.
ABOUT WINDOWS EMBEDDED CE 6.0 R2
Build cutting edge connected devices with CE 6.0 R2. The new and updated technologies in R2 enable you to bring innovative devices to market faster while offering your customers unparalleled connected experiences.Get an in-depth look at what’s new in Windows Embedded CE 6.0 R2, including:
Quickly develop small footprint device scenarios and connect to Windows Vista and Windows Server 2008
Build richer end user experiences and develop new capabilities into your product with WSD technologies
Create exciting device scenarios such as VOIP video and 3-way audio with new VOIP technologies