And if you want to know why, and what the consequences are...have a look at this great post from the Microsoft Exchange Team itself:
Dude, Where's My Single Instance?
Ilse
And if you want to know why, and what the consequences are...have a look at this great post from the Microsoft Exchange Team itself:
Dude, Where's My Single Instance?
Ilse
Just published @ http://www.techdays.be, there will be two sessions on OCS 14, the next big OCS release, delivered by François Doremieux.
Who is François Doremieux?
Francois is a Director of Engineering in the Office Communications Product Group. He has spent the past 7 years contributing to drive Microsoft Unified Communications and Voice efforts. His current role consists in closely working with early adopters and leading customers, helping them define their UC strategy and deploying OCS. In turn, he brings these customers requirements into the Product Group product specification and development process. Francois’ primary technical domain is voice interoperability with IP-PBX.
Prior to joining Microsoft, Francois fulfilled leadership roles at Level(3), AT&T and Comcast.
Francois resides in Colorado and uses Microsoft UC tools to telecommute.
He will talk about:
Session 1, Introduction to Microsoft Communications Server “W14”
Positioning and main features for Microsoft Communications Server “W14”, with emphasis on Voice and Collaboration capabilities
Session 2, New voice capabilities and infrastructure in Microsoft Communications Server “W14”
Detailed description of voice features in Microsoft Communications Server “W14”, with discussion of implications on topology and interoperability
So, be fast, and register today for the TechDays!
Hope to see you there!
Ilse
Then the Office Communications Server Team blog has some good news for you:
Free Instructor-Led Training for end-users: Introduction to Office Communicator
Here’s a copy-paste of the information posted:
“This live course is held in a virtual classroom via Office Live Meeting. It will allow hands-on experience to build knowledge, skills, and confidence to use Office Communicator more effectively.
These features will be covered in this high-level overview:
Click here to register: https://events.livemeeting.com/967/15027/reg.aspx?pc=05”
Ilse
I have always loved this feature ever since I first noticed it when diving into Exchange 2007.
For more information about this web service, and how it is used by multiple applications like Microsoft Office Outlook 2007 and later, and the Microsoft Office Communications Server Phone Edition, I would like to refer to this article on MsExchange.Org (Exchange Autodiscover).
In this blog post I just want to highlight how you can change the default behavior of Microsoft Office Outlook when figuring out the Client Access server to connect to use the Autodiscover web service.
When you launch Microsoft Office Outlook 2007/2010, Outlook will try to connect to a Client Access server using the given e-mail address. Imagine we want to configure a mailbox with a given e-mailaddress Ilse,VanCriekinge@TestAccount.Com.
Outlook will use the given SMTP Domain of TestAccount.com, and try to reach the Client Access server using the following order:
If this fails, the next try will be:
If this fails, the next try will be a local discover of xml files that may contain information on the Client Access server to be contacted.
If this fails, the next try will be a redirect to:
If this fails, the last step will be to locate a service record:
When holding the Ctrl button, and right-click the Outlook icon in the system tray, you can test the Autoconfiguration and troubleshoot Autodiscover configuration settings.
If this fails, Outlook will not be able to connect to a Client Access server in your environment to retrieve the following pieces of information:
In some cases it might be necessary to change the default behavior or Microsoft Outlook.
An example might be that you have two organizations, sharing the same namespace. Imagine a namespace of ProExchange.Global, shared by both forest A and forest B. When clients login to the domain, they will be services by Active Directory and retrieve the necessary settings. But when trying to launch Microsoft Office Outlook from the outside, there will be one autodiscover record pointing to a Client Access server in Forest A, which won’t help a user from Forest B….
In that situation it might be very useful, if you can help Outlook to query a Client Access server in Forest B directly.
Example situation =
• Situation: Move user x from organization A to organization B.
• Organization A = ProExchange.Global
• Organization B = Sunshine.Edu + ProExchange.Global
• User ivancriekinge has two smtp addresses:
When a user from Organization B, ivancriekinge logs into to the domain itself, there is no problem, since Active Directory will be queried:
When a user from Organization A, administrator logs into to domain itself, there is no problem, since Active Directory will be queried
When user administrator logs in from a non-domain joined machine, there is no problem, since the service record points to a Client Access server in Organization A.
But when user ivancriekinge logs into from a non-domain joined machine, the problem occurs, since the Client Access server in Organization A doesn’t know anything about user ivancriekinge, located in Organization B.
To make user a Client Access server is queried in Organization B, we can use an XML file, which includes the URL to use!
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<Account>
<AccountType>email</AccountType>
<Action>redirectUrl</Action>
<RedirectUrl>https://autodiscover.sunshine.edu/autodiscover/autodiscover.xml</RedirectUrl>
</Account>
</Response>
</Autodiscover>
Then you need to configure the client machine to query that XML file by adding the following registry key:
- for Outlook 2007:
HKCU\Software\Microsoft\Office\12.0\Outlook\Autodiscover
- for Outlook 2010:
HKCU\Software\Microsoft\Office\14.0\Outlook\Autodiscover
STRING_value <your_namespace> = path to XML file
HKCU\Software\Microsoft\Office\12.0\Outlook\Autodiscover
- for Outlook 2010:
HKCU\Software\Microsoft\Office\14.0\Outlook\Autodiscover
DWORD_value, PreferLocalXML = 1
And then it will work :-)
Yes :-)
If you don’t want autodiscover to check a few steps, you can include one or more of the following keys.
Outlook 2007:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover
Outlook 2010:
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover
•"ExcludeHttpRedirect"=dword:0
•"ExcludeHttpsAutodiscoverDomain"=dword:0
•"ExcludeHttpsRootDomain"=dword:0
•"ExcludeScpLookup"=dword:0
•"ExcludeSrvLookup"=dword:0
•"ExcludeSrvRecord"=dword:0
Autodiscover is a wonderful feature! Once configured correctly it will save you quite some time!
Ilse