Exchange 2013 Prerequisites

The prerequisites that are needed to install Exchange 2013 on a Windows Server 2008 R2 SP1 computer depends on which Exchange roles you want to install. Read the section below that matches the roles you want to install.

Mailbox server role or combined Mailbox and Client Access server roles

---

Follow the instructions in this section to install the prerequisites on Windows Server 2008 R2 SP1 computers where you want to do one of the following:

• Install only the Mailbox server role on a computer.
• Install both the Mailbox and Client Access server roles on the same computer.

Do the following to install the required Windows roles and features:

1. Open Windows PowerShell.
2. Run the following command to load the Server Manager module.
   
   Import-Module ServerManager
   

3. Run the following command to install the required Windows components.
   
   Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI
   

After you've installed the operating system roles and features, install the following software in the order shown:

1. Microsoft .NET Framework 4.5
2. Windows Management Framework 3.0
3. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
4. Microsoft Office 2010 Filter Pack 64 bit
5. Microsoft Office 2010 Filter Pack SP1 64 bit
6. Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)
7. Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2)
8. Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution) 
9.  
10.  http://technet.microsoft.com/en-us/library/bb691354.aspx 
11. 
    

How to configure Lync 2010 on Android (Lync 2010)

How to configure Lync 2010 on Android (Lync 2010)

http://plexhosted.com/billing/knowledgebase/230/How-to-configure-Lync-2010-on-Android-Lync-2010.html

• Synopsis

  This guide will show you how to configure Lync 2010 on Android.

• Applicable to

  All hosted Lync 2010 accounts.

• Prerequisite

  • a hosted Lync 2010 account
  • Lync 2010 Mobile Client

• How to

1. Run your Lync 2010 Mobile Client.

2. Enter your credentials - e-mail and password.

3. Click on the Options and choose Server Settings.

4. Turn off Auto Detect Server option and setup servers manually using the following urls:
   External Discovery Address:
   https://autodiscover.lync.plexhosted.com
   Internal Discovery Address:
   https://autodiscover.lync.plexhosted.com

5. Return to the main page, enter your password again. Click Sign In button and you would be able to see signing in screen.

6. When you sign in to the Lync mobile client you can see configuration screen. Click on the button Next.

7. You will see your phone number, click on the button Next.

8. Click the button Done to finish configuration.

9. You can see the screen with your information.

10. To change your status click on the status section under your username.

11. To start chatting click on the contact you want to chat and choose Send an IM icon. Then you can type your message and click the button Send.

12. You can see and manage your conversations using the tab Chats.

the delegates settings were not saved correctly. cannot activate send-on-behalf-of list

http://support.microsoft.com/kb/2593557
One of my customers came to me with the following issue and asked if there were “better” solutions available than they found using their own Internet research. They use a mix of Outlook 2007 and Outlook 2010 clients and a lot of shared mailboxes. The access to these mailboxes is granted through group memberships, which have “full mailbox access” and “send-as” permissions granted.  Outlook is configured to use a second profile for the Shared Mailbox access.

The Symptom:

In the phase of testing their mailbox migration to Exchange 2010 Sp1 RU6 they encountered the following issue trying to delegate Calendar permissions using the “Outlook delegation wizard” on their shared mailboxes:


“The Delegates settings were not saved correctly. Cannot activate send-on-behalf-of-list. You do not have sufficient permission to perform this operation on this object”

Troubleshooting steps:

If you do an Internet research there appear to lots of people complaining about this exact behaviour. The two most popular described solutions are the following:
1. Using the “IgnoreSOBError” – “SendOnBehalf” Registry key to silently drop the error message and proceed with permission assignment. With the usage of this key the described error message is just dropped by Outlook and the selected permissions out of the delegation wizard are applied (without setting the SendOnBehalfof permission).
The SendOnBehalf Permission is not needed to act as calendar delegate. If the delegate has to use the “send on behalf of” permission for writing email “in behalf of” this has to be done by an administrator using the Exchange Management Shell or Exchange Management Console.
Outlook 2007 Registry key:
HKCU\Software\Microsoft\Office\12.0\Outlook\Preferences or
HKCU\Software\Policies\Microsoft\Office\12.0\Outlook\Preferences
Dword: IgnoreSOBError value = 1
Outlook 2010 Registry key:
HKCU\Software\Microsoft\Office\14.0\Outlook\Preferences or
HKCU\Software\Policies\Microsoft\Office\14.0\Outlook\Preferences
Dword: IgnoreSOBError value = 1
2. Create a new RBAC role and strip all parameters for “GrantSendOnBehalf plus Identity” and add the user who should be able to do their delegation without an error. In this case the Outlook Wizard will finish successfully and the delegate will be added to the list of “publicDelegates”.
The downside of this solution about using this “Organization wide” RBAC role is that the user is now able (using remote PowerShell) to “GrantSendOnBehalf” in every mailbox, not only his delegated mailboxes.

http://blogs.technet.com/b/mspfe/archive/2012/06/26/solving_2d00_the_2d00_delegates_2d00_settings_2d00_were_2d00_not_2d00_saved_2d00_correctly_2d00_error_2d00_on_2d00_exchange_2d00_2010.aspx