Exchange Server Share

… Information sharing on Exchange Server …

Exchange 2010 Beta1: Bunch of FAQs, Tips & Known Issues

Exchange 2010 has many new features, advance administration methods, significant changes in Information Store to give better performance, new and simple high-availability approach and role based access control features for permissions. Sounds great so who doesn’t want to start testing this early version, Exchange 2010 Beta1.

As we know that Exchange 2010 product is still under development and being optimized, so here are certain FAQs, Tips and Known Issues which might help you to evaluate it easily and save your time while finding solutions or workarounds on some common queries and issues.


1. Production Use?

First question comes in your mind while testing Exchange 2010 Beta1 is, can I use Exchange 2010 Beta 1 in production?
~ Answer is "NO", here is an official article from Exchange Team on why you shouldn’t use Beta in production environment. 
Reference: "Can I install Exchange 2010 Beta in production?"

2. Windows 2008 Editions

~ Exchange 2010 can be installed on Windows 2008 & Windows 2008 R2 but wait…

2.1 Can I install Exchange 2010 on Windows 2008 Server Core?
~ No, Exchange 2010 can NOT be installed on Windows 2008 Server Core, it requires full edition of Windows 2008 Standard or Enterprise.
~ Reason is, Exchange requires some of the components which are not supported on Windows 2008 Server Core, example is .Net Framework.

2.2 Can I use Exchange 2010 Beta 1 with Windows 2008 R2?
~ Yes, you can use Windows 2008 R2 but read below couple of points.

2.2.1 Which build of Windows 2008 R2 I can use for Exchange 2010 testing?
Exchange 2010 Beta1 PowerShell & WinRM are incompatible with post 7000 build of Windows R2 and requires wire-level change so it can be installed only on build 7000 of R2 and not on later builds so keep in mind if you are planning to install it on R2.

2.2.2 You may get below error while accessing EMC on Windows 2008 R2.

Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. It was running command ‘Discover-ExchangeServer -UseWIA $true’.

This is know issue and to solve it follow below two steps…
     ~ Disable “Anonymous Authentication” on PowerShell virtual directory of IIS.
     ~ Enable remote powershell for user with below cmdlet in “Exchange Management
        Shell (Local Powershell)”
        Set-User “User Name” -RemotePowerShellEnabled $true

3. Coexistence

Coexistence with legacy Exchange versions (2007or 2003) is NOT supported with Exchange 2010 Beta1. We may need to wait for next release of Exchange 2010.

4. Installation

4.1 Domain & Forest Functional Levels of your AD environment.

Exchange 2010 requires Domain and Forest (both) Functional Levels to at least Windows 2003. You can refer below articles to raise Functional Levels of your AD to Windows 2003.
References: Raise the Domain Functional Level 
                     Raise the Forest Functional Level

4.2 Setup fails at Hub Transport Server role installation with below error.

The execution of: “$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }”, generated the following error: “Service ‘MSExchangeTransport’ failed to reach  status ‘Running’ on this server.”

~ This could be because you have disabled IPv6 in Local Area Connection. Correct method to disable IPv6 is with Registry Key and remove the entry from hosts file.
Refer below article.

Reference: Exchange 2010: Hub Transport Role Installation Fails

4.3 You get below error while running installation.

"An error occurred while copying file D:\Exchange2010-Beta1-x64\…\templates editor.msc"

~ Copy Setup dump to local hard drive and execute Exchange 2010 setup from there.
~ Make sure that account, being used to run Exchange 2010 setup, has Domain, Enterprise and Schema Admin rights.

4.4 You may get below error while installing additional Mailbox Server in Exchange 2010 Beta1 environment.

"Object reference not set to an instance of an object"

~ This might be due to "Admin Audit Log Agent" Cmdlet Extension Agents enabled in your environment. This will be resolved in later builds but current Workaround for this problem is disable Admin Audit Log Agent with below cmdlet.
          Disable-CmdletExtensionAgent "Admin Audit Log Agent"
Understanding Cmdlet Extension Agents
Disable a Cmdlet Extension Agent

5. Exchange Management Console / Shell Tips

5.1 When you try to access EMS/EMC with newly created administrator account, you get below error.

Connecting to remote server failed with the following error message : Access is denied.
At C:\Program Files\Microsoft\Exchange Server\V14\bin\ConnectFunctions.ps1:154 char:28
+         $global:r = new-pssession <<<<  -connectionURI
https://$fqdn/powershell -ConfigurationName Microsoft.Exchange -Authentication NegotiateWithImplicitCredential -SessionOption $sessionOption #-erroraction  silentlycontinue
    + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : RemoteRunspaceOpenFailed


Connecting to remote server failed with the following error message: Access is denied. It was running command ‘Discover-ExchangeServer -UseWIA $true’

You need to enable Remote Powershell for newly created Admin account with below cmdlet.
          Set-User “User Name” -RemotePowerShellEnabled $true

5.2 When you click on CAS Server properties you may get below error.

Microsoft Exchange
Unable to create IIS (Internet Information Service) directory entry. Error Message is: Access is denied.
. HResult = -2147024891 It was running command ‘get-ActiveSyncVirtualDirectory’.

This is know issue with current Beta1 and you need to add "Microsoft Exchange Security Groups\ Exchange Trusted Subsystem" group to Local Administrators group on all Exchange servers and Restart the CAS server.

5.3 If you create User with ADU&C and enable mailbox with EMC/EMS, now while removing the same mailbox in EMC you get below error.

Active Directory operation failed on This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-03151D12, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

Solution: You need to use EMS to remove the mailbox with Remove-Mailbox cmdlet.

5.4 How to manage mailbox folder permission with EMS.

This is one of the New Mailbox and Recipient Functionality in Exchange 2010. Let’s take an example here, if you want permission on a folder named "SharedFolder1" of  User1’s mailbox to User2 in Exchange Management Shell.

~ You can use Add-MailboxFolderPermission cmdlet. But what is the format of folder name which we should pass in cmdlet to give permission? So, format should be blow.

Add-MailboxFolderPermission -Identity User1:\SharedFolder1 -AccessRights Editor -User User2

6. Mailbox Access & Client Issues

6.1 How can I access Exchange 2010 mailbox?
~ You can access mailbox with MAPI clients like Outlook 2007 or 2003, OWA premium experience with IE, FireFox & Safari browser or Windows Mobile 5.0, 6.0 devices.

6.2 Outlook 2007 is not able to access mailbox and/or unable to start "MSExchange Rpc Client Access" Service.
This is know issue and it will be corrected in later build. Workaround is to add below two registry keys on Exchange 2010 Server.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ MSExchangeIS\ParametersSystem]
"Mapi Rpc Endpoint Registration"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ MSExchangeRPC\ParametersSystem]

6.3 Outlook 2003 is unable to access mailbox.
RPC/MAPI Mailbox access with Outlook 2003 may not work while testing in Beta1, you need to use Outlook 2007 to gain mailbox access. You may use RPC/HTTPs method with Outlook 2003 to access Mailbox.

7. Public Folders Access & Client Issues

7.1 Public Folder Support in Exchange 2010

Public Folder is fully supported in Exchange 2010 life cycle as Exchange team is already announced earlier.
Reference: Updated Exchange Public Folder Guidance
But you need to start looking for other alternative if PFs are being heavily used in your organization, Share Point is a good alternative from that stand point.

7.2 Where is Public Folder option in OWA?

Public Folder, Notes, Tasks, Views etc… modules are not included in current Beta, these will be available in later builds.

7.3 Unable to access Public Folder in Outlook 2007 and you get below error.

"Cannot expand the folder. The set of folders cannot be opened. Your profile is not configured"

Public Folder access has problem with MAPI/RPC Outlook 2007 profile and can not be accessible, this will be corrected in later build.

8. Outlook Web Access

8.1 Certain features (like drag and drop items) are not yet fully implemented in this version of Beta to work on Firefox and Safari web browser so you can still find some gaps and which will be covered by RTM.

8.2 OWA, where is integrated IM and Presence functionality?
~ IM & Presence functionality is not yet included into Beta1 so we may need to wait for next build releases.
~ However You need to have Office Communications Server 2007 R2 installed in your environment to have basic IM functionality then you can configure an integration between OCS and Exchange OWA to connect together and give you status indication (presence information) of other persons, have chat with them etc…

8.3 OWA gives blank display with below in address bar
You may need to reinstall CAS server role and IIS.

9. Exchange Control Panel (ECP)

9.1 When you click on Options in OWA to login on ECP, again it asks for authentication.
~ This is expected behaviour in Beta1 because ECP virtual directory doesn’t support FBA yet. This will be corrected by RTM releases of Exchange 2010.

9.2 Authentication fails when you click on Options button in OWA and you get below error.

Unexpected Error – An error occurred and your request couldn’t be completed. Please try again.

~ This happens if you are accessing OWA with FQDN of your OWA address like but didn’t set urls on virtual directories.
~ You need to set InternalURL to https://FQDNofExchange/OWA and ExternalURL to of OWA virtual directory with Set-OWAVirtualDirectory cmdlet.

Set-OWAVirtualDirectory “Owa (Default Web Site)” –InternalURL “https://FQDNofExchange/owa” –ExternalURL “”

~ Similarly for ECP directory with Set-ECPVirtualDirectory cmdlet. Once these are configured it prompts for passwords (Refer #9.1) and authentication redirects to ECP.

Set-ECPVirtualDirectory “Ecp (Default Web Site)” –InternalURL “https://FQDNofExchange/ECP” –ExternalURL “”

10. Archive or Alternate Mailbox

10.1 How to create Archive Mailbox?
You can use below cmdlet to create archive mailbox. In later builds you can create archive mailbox in EMC too.

New-AlternateMailbox -Name User-Archive -Mailbox UserName -Type Archive
Reference: New-AlternateMailbox

10.2 Where will be Archiving mailbox created?
~ Archive mailbox will be created automatically on the same mailbox database where primary mailbox of user is available.

10.3 Does discoveries feature work on Archive mailbox to find emails by Compliance Officer?
Yes, Compliance Officer can search emails from Archive Mailbox. Exchange Control Panel (ECP) is an interface for Discovery feature of Exchange 2010.

10.4 How to access Archive Mailbox?
It can be accessed via OWA or Outlook 2010 but unfortunately OWA doesn’t have that feature included in current Beta1 to access Archive Mailbox and beta version of Outlook 2010 will be released in Q3 so we may need to wait until next build of Exchange 2010 available.

11. MailTips

11.1 What are supported clients for MailTips feature?
~ MailTips are supported in OWA and Outlook 2010.
~ But current Exchange 2010 public beta doesn’t have this feature module ported in OWA and Outlook 2010 Beta has not released yet so we may need to wait for next releases of Exchange 2010…
Reference: Introducing MailTips

12. High Availability & Recovery

12.1 Database Availability Groups (DAG)

12.1.1 You get below error while adding a server into DAG by using EMC.

Insufficient permissions to view the network shares on machines <FileShareWitness>. Error code 5.

~ This is known issue, remote powershell can add a server in DAG since it requires to install Windows Failover Cluster (WFC) components which are not accessible through remote powershell.
~ Use "Exchange Management Shell (Local Powershell)" to add the server into DAG with Add-DatabaseAvailabilityGroupServer cmdlet.

Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer E2010SRV1

Reference: Add-DatabaseAvailabilityGroupServer

12.2 What is the alternative of Recovery Storage Group (RSG)?

~ As we know that there Storage Group concept is deprecated and we have only Databases so now we can use Recovery Databases for recovery purpose.
~ Here are cmdlets to create Recovery Database and to restore mailbox.
New-MailboxDatabase -Recovery <DatabaseIdParameter> –Server <StoreMailboxIdParameter>
Restore-Mailbox -Identity <MailboxIdParameter> -RecoveryDatabase <DatabaseIdParameter> -RecoveryMailbox <StoreMailboxIdParameter>



Hope this article helps you to test Exchange 2010 Beta1 with greater comfortably and yeh, most of these know issues will be corrected in later builds or by RTM release…


Written by Amit Tank

May 3, 2009 at 10:24 am

20 Responses

Subscribe to comments with RSS.

  1. Hi Amit,

    Really great, for someone trying hands on Exchange 2010, this is going to help immensely.

    Thanks for these pointers and tips !


  2. […] the rest here: Exchange 2010 Beta1: Bunch of FAQs, Tips & Known Issues « Exchange … Ads by GoogleComputer Support – Instant Help – – Call: […]

  3. […] Amit also reviews a long series of known issues and FAQ items […]

  4. […] by Amit Tank on 2009/05/03 Exchange 2010 Beta1: Bunch of FAQs, Tips & Known Issues – Amit […]

  5. Hey Bro, Great efforts and its really imformative.


    Arun Kumar

    May 5, 2009 at 5:33 pm

  6. Awesome information, Amit.


    May 5, 2009 at 11:05 pm

  7. […] Exchange 2010 Beta1: Bunch of FAQs, Tips & Known Issues […]

  8. Hey Amit, very good effort. Thanks

    Zohaib Hafeez

    May 8, 2009 at 10:27 am

  9. Hello Amit,
    Excellent information.



    May 13, 2009 at 5:35 pm

  10. Very helpful stuff. I think there’s a typo, under “9. Exchange Control Panel (ECP)” for the set-ecpvirtualdirectory you want to set that on “ECP (default web site)” not “owa (default web site)”.


    May 15, 2009 at 8:15 pm

  11. Hey KB,

    Thanks for identifying, I just corrected it…

    Amit Tank

    May 15, 2009 at 9:09 pm

  12. hi
    On the installation topic you mentioned like raise the Domain Functional level to windows 2003, i think it wont work, we need to raise the domain functional level to Windows 2003 native mode which is not supportable in Windows 2003 Domain Controllers.


    June 30, 2009 at 9:00 am

  13. @drajkumar: Sorry, I didn’t get your point here on “we need to raise the domain functional level to Windows 2003 native mode which is not supportable in Windows 2003 Domain Controllers”

    Can you explain bit more on why it is not supportable?

    Amit Tank

    June 30, 2009 at 10:01 am

  14. This what you have mentioned above

    4. Installation

    4.1 Domain & Forest Functional Levels of your AD environment.

    Exchange 2010 requires Domain and Forest (both) Functional Levels to at least Windows 2003. You can refer below articles to raise Functional Levels of your AD to Windows 2003.

    but to install Exchange Server 2010 we need to raise the Domain and Forest functional level to Windows Server 2003 Native mode, In windows 2003 domain controller, we cant raise the domain and forest functional level to windows Server 2003 native we need a Domain controller on Windows Server 2008 to install Exchange Server 2010 beta.


    July 2, 2009 at 10:22 am

  15. @drajkumar: Well, I am using Windows 2003 Domain Controller with “Windows 2003” Forest and Domain functional level without any problem in Exchange 2010 environment…

    Amit Tank

    July 2, 2009 at 2:17 pm

  16. Anyone got mailtip working? I have Outlook 2010 installed.


    July 29, 2009 at 9:17 am

  17. I have just installed Exchange 2010 Beta on Windows Server 2008 R2.

    When I open Exchange Management Console, it shows the Microsoft Exchange On-Premise, but fails to connect to the server itself. If I try to choose any option to work with, it gives error:
    Cannot Bind Parameter ‘SessionOption’. Cannot convert the “Microsoft.WSMan.Management.SessionOption” value of type “Microsoft.WSMan.Management.SessionOption” to type “System.Management.Automation.Remoting.PSSessionOption”. It was running command ‘Discover-ExchangeServer -UseWIA $true”.

    I have tried to execute the command
    Set-User Administrator -RemotePowerShellEnabled $true
    It says:
    WARNING: The command completed successfully but no settings of ‘’ has been modified.

    The domain and forest functional level is Windows Server 2008 R2. Domain controller is on the physical box and Exchange 2010 beta is hosted on Virtual Server on HyperV.

    Any help on this is appreciated.

    Thank you.


    July 31, 2009 at 4:47 pm

    • What version of 2008 R2 are you using?
      It will only work on RC build, not RTM.


      August 5, 2009 at 9:22 am

    • Yes, as CY said, current Exchange 2010 public beta works only on the build 7000 of Windows 2008 R2 normally.

      Amit Tank

      August 5, 2009 at 9:41 am

  18. I found that the bindings in port 80 of the default website where causing this problem!! I turned it to default and started conecting again!!


    December 16, 2009 at 8:44 pm

Comments are closed.

%d bloggers like this: