To ensure your users don’t have to deal with the first-launch experience (where they have to press Next, choose from a blank list of networks, then press Finish before they can use Outlook), we need to configure a couple of Registry entries.The easiest way to accomplish this is via Group Policy Preferences.I won’t go into too much details, but basically you can configure Group Policy Preferences by using Server 2008, 2008 R2, Vista or Windows 7 Group Policy Management tools.

outlook not updating exchange-11outlook not updating exchange-75

To configure the required values, you need to create (or modify) a user policy that will apply to your Outlook users.

Using Group Policy Preferences, add two new Registry settings to configure the following values: Action: Replace, Hive: HKCU, Key Path: Software\Microsoft\Office\Outlook\Social Connector, Value Name: Alert User If No Networks Configured, Value Type: DWORD, Value Data: 0 (Decimal) Action: Replace, Hive: HKCU, Key Path: Software\Microsoft\Office\Outlook\Social Connector, Value Name: First Run Version, Value Type: DWORD, Value Data: 65536 (Decimal) Once configured the Outlook Social Connector should deploy to client machines, and be enabled with no user interaction.

Word of caution – always make sure you test these changes for yourself first in your own test environment before deploying to real clients. As always, feel free to leave any comments or suggestions for how this article could be improved…

Hi, With Exchange 2013 deployments already in place, I’ve wanted to share with you all some “new” behaviors, tips and more to help you prevent headaches and issues 🙂 With regards to two previously posts – Prevent Outlook Anywhere (aka RPC over HTTP) from being automatically configured in Exchange 2007 with autodiscover and also Authentication pop ups and annoyances with Exchange 2007 / 2010 and Outlook Anywhere – this post is some sort of a follow-up.

With Exchange 2013, Outlook Anywhere (aka RPC over HTTP/s) is the default method for Outlook clients connections – that is no more direct RPC connections to the servers for Outlook clients.

Exchange 2013 will essentially require you to utilize Autodiscover and Outlook Anywhere to actually get your Outlook client connected. This information will come useful if you are getting ready or already started to deploy Exchange 2013, I’ll try to keep it simple and write this down as a list of things to consider so this will be rather easy to all.

It’s been a while since I’ve been thinking of writing a blog post about various aspects of Outlook Anywhere that people have been asking questions about. Given how long this blog post is overdue, I plan to cover a lot of topics, from frequently asked questions to common misconceptions to problems with Outlook Anywhere to suggested solutions for different problems.

One of the new features in Exchange 2010 is the ability to import contact photos, store them in Active Directory against each user, then show them in both Outlook and Lync.

It’s great to help identify who you’re emailing and who has emailed you, and can avoid making embarrassing mistakes.