Hi All,

Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.

I have followed the guide for public folder migration here http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.

We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.

However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them fine from the ECP - just not from outlook.

It also appears some users cannot see some folders that they have permissions to.

Can anyone assist with some ideas to resolve ?

Thanks.

Hi,

I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.

We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.

All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa url) also redirects me to https://legacy.domain.com/owa just fine.

HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.

Anyone any tips where to search?

Many thanks in advance.

Best regards and many thanks in advance, Eric Vegter

I'm fairly sure the issue is related to the fact that I had installed Exchange server 2013 CU1 on a Windows server 2012 box, and then uninstalled it. I then installed Exchange Server 2013 SP1 after rebuilding the servers to 2012 R2.

When I try to install a Mail App I get the error "Exchange Server doesn't support the requested version.".  I don't see any correlated errors in the event logs to figure out what exactly is going on.  If I use the powershell commandlet get-app to see what apps are available for a user I get the same thing.

I do have Exchange Server 2010 SP3 servers in my domain that I will eventually be migrating off of.  If anyone can give me some pointers of where to look for what might be broken I'd really appreciate it.

We are in the middle of an Exchange 2013 migration from 2007 and this is the 2nd time I've encountered this issue.  The migrated user cannot open outlook or log into owa.  The error that is thrown in owa is below.  I cant really find any info on this error.  Also, notice the date.  No idea where its getting that.  We've moved about 7000 users and I've seen this on two of them.  I'd appreciate any insight on this.  Thanks.

X-OWA-Error: SDServerErr;Microsoft.Exchange.UM.UMCommon.InvalidPrincipalException
X-OWA-Version: 15.0.847.32
X-FEServer: server01
X-BEServer: server01.domain.com
Date: 1/2/1601 2:47:50 PM

Rich

Hi,

When using New-MailboxImportRequest to import PST files to Exchange 2013 CU2 we end up with a succesful import. When the end-user tries to reply to an old e-mail the "To" field is just populated with the Display Name of the user that sent the mail. Not the smtp or X500 address. See the attached picture.

If we use Outlook to import the issue does not occurs.

We have tried with different versions of Exchange as source mailsystem and different versions of Outlook as export tool with the same result.

Is this a known issue?

Best regards, Jesper

I'm running into problems preparing the schema in my AD.   We currently have Exchange 2010 SP3 installed onsite with our Office365 tenant space.   We have been upgraded to V15 in Office365.   I followed the instructions and connected via powershell to our tenant space and generated the MyTenantOrganizationConfig.XML file.   Running the exhange setup with /TenantOrganizationConfig switch comes back with not supported with /PrepareSchema.   Runing setup with just the /TenantOrganizationConfig doesn't work either.   Both URL links below don't work, the first one just takes you to a general Exchange page.

Welcome to Microsoft Exchange Server 2013 Cumulative Update 1 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.

Performing Microsoft Exchange Server Prerequisite Check

    Prerequisite Analysis                                     FAILED
     A hybrid deployment with Office 365 has been detected.  Please ensure that you are running setup with the /TenantOrganizationConfig switch.  To use the TenantOrganizationConfig switch you must first connect to your Exchange Online tenant via PowerShell and execute the following command: "Get-OrganizationConfig | E
xport-Clixml -Path MyTenantOrganizationConfig.XML".  Once the XML file has been generated, run setup with the TenantOrganizationConfig switch as follows "/TenantOrganizationConfig myTenantOrganizationConfig.XML".
If you continue to see this this message then it indicates that either the XML file specified is corrupt, or you are attempting to upgrade your on-premises Exchange installation to a build that isn't compatible with the Exchange version of your Office 365 tenant. Your Office 365 tenant must be upgraded to a compatible
version of Exchange before upgrading your on-premises Exchange installation. For more information, see:http://go.microsoft.com/fwlink/?LinkId=262888
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.DidTenantSettingCreatedAnException.aspx

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

I have a new Exchange 2013 SP1 server on a 2012 R2 OS where I've installed both Mailbox and Client Access roles in an existing Exchange 2010 environment.  Initially ran into some DNS issues that caused errors installing the Client Access server, but I fixed those, removed Exchange 2013 and reinstalled with no errors.  In every scenario so far, trying to access the ECP redirects you to the 2010 OWA.  I have been scouring threads for hours and tried everything I've seen, but to no avail.  I have tried:

1) Using the https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15 URL, which still redirects to the 2010 OWA

2) Creating a new user account with all of the same rights as the domain admin but has no mailbox, which redirects to the 2010 OWA and throws an error that there is no mailbox.

3) Setting the domain in IIS authentication settings for the ECP on both the 2013 and 2010 server.

Does anyone have any ideas here on what to try next?

I recently began working on deploying our new 2013 Exchange server into a network I inherited. The network has two domains with a trust between them all on the same IP segment, calling them Domain1.local and Domain2.local. The Exchange server is connected to Domain1.local and I need to get users from the Domain2.local added to Exchange so everyone is getting email. To top this off our email MX comes from two external domain names, Domain1.com and Domain2.org. I will need to be able to send and receive email from those .com and .org domains and disseminate them to the two .local domains. I have looked almost everywhere to resolve these issues but I am kind of stuck right now. Any help or information leading to the right direction would be helpful, like do I need to rename the internal domains to reflect the external ones, etc... I'm really new to Exchange and went through every walk through and CBT I could find.

Thanks a bunch.

I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken

(1)Clone the Exchange1 and turn it off

(2) Brought the Clone Exchange2, renamed it, change the IP configurations,

(3) Re-ran the ADprep/Doamin prep

(4) Checked the ASDIedit to verify the Schema/configuration in AD

(5) Restarted I and was able to logon to the Exchange2

(6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database

-----------------------------------------------------------------------------------------------------------------

What I did to fix this:

(7) Rejoin the Exchange1 to the domain - and was able to logon

(8) Unable to access ECP or OWA of any of the two servers.

(9) Errors received - Fix the configuration file of the application

My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?

Hi,

I tried to do a migration from Exchange 2007 to Exchange 2013 about 2 months ago. I used this document http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

But I also used this technet one http://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx

However when bringing up the Exchange 2013 mail server there was no mail flow (when using the default receive connectors) after moving all the mail boxes from Exchange 2007 which meant I had to move all the mailboxes back. Infact there was no mail flow within the Exchange 2013 server (I.E. when emailing from user1 to user2 that were both hosted on Exchange 2013 the mail would not send, it would stay in the outbox of user1). When I discovered that there was a mail flow issue I started googling and change a whole bunch of things and now I cannot remember what I changed and what the defaults values are. What is the best way to move forward from here. We are currently still running Exchange off the Exchange 2007 server but I still have all the mailboxes on the 2013 server so I cannot uninstall exchange 2013 to start over.

Environment:

Win Server 2003 R2 SP2 GC running Exchange 2007 SP2

Win Server 2012 R2 PDC GC

Win Server 2012 R2 SharePoint 2013

Problem:

When I tried to migrate from the exchange 2013 from the exchange 2007 I get the following message from the Exchange 2013 setup;

Issue:

I downloaded Exchange 2007 sp3 but when I install it I get the following error message which will not allow me to continue no matter how many times I reboot, the good thing after rebooting is you do not have to start from the begin and picks up where it left off;

Summary: 10 item(s). 5 succeeded, 1 failed.

Elapsed time: 00:52:33

Organization Preparation

Completed

Elapsed Time: 00:19:23

Preparing Setup

Completed

Elapsed Time: 00:03:09

Remove Exchange Files

Completed

Elapsed Time: 00:13:37

Preparing Files

Completed

Elapsed Time: 00:00:02

Copy Exchange Files

Completed

Elapsed Time: 00:08:28

Hub Transport Role

Failed

Error:

Unable to cast COM object of type 'Interop.MSClusterLib.ClusterClass' to interface type 'Interop.MSClusterLib.ISCluster'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{F2E606E4-2631-11D1-89F1-00A0C90D061E}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Warning:

An unexpected error has occurred and debug information is being generated: Unable to cast COM object of type 'Interop.MSClusterLib.ClusterClass' to interface type 'Interop.MSClusterLib.ISCluster'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{F2E606E4-2631-11D1-89F1-00A0C90D061E}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

Elapsed Time: 00:07:53

Client Access Role

Cancelled

Mailbox Role

Cancelled

Management Tools

Cancelled

Finalizing Setup

Cancelled

I have been searching the internet and have not found anything related to this and anything I do find related to SQL or office.

Any tips, links or helpful information with be appreciated greatly as I would like to put this behind me!

Regards,

Dividu

Hi Guys,

Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.

step by step docs will be more helpful to achieve this goal..

Regards,

Aanand Singh

Hi Experts,

I am facing issue while installing exchange 2013 sp1 in mixed(2007, 2010 and 2013) environment, the issue is: CAS role not installing/configuring "Echangeweb" (ews) virtual directory if i install only CAS role. If i install CAS role and mailbox role then there is no issue, everything is fine.

In single CAS role installation, "EWS" folder is creating inside "Exchangeweb" folder but it shows empty folder.

If any one have any idea please let me know, why this is happening? was i am doing anything wrong while installing?

Regards,

Ravi Nalla

Hewlett-Packard

ravinalla

Hi

I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise Admins" and "Schema Admins"

in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case

I have to install exchange 2013 in windows Server 2008 r2 sp1

the functional level  2008 R2 I getting these errors please help.

Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx

Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx

Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx

Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx

Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.  See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

I have got this information from digicert http://www.digicert.com/internal-names.htm  is there any way to ensure all clients works properly.

Should we have to change our internal domain names to external ones, this will be a problem and visible. It gives us insecured feeling.

Experts please throw your views.

Thanks!

Regards, Ganesh, MCTS, MCP, ITILV2 This posting is provided with no warranties and confers no rights. Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

When installing the sp1 update for exchange 2013 we came across these errors:

    The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
 $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
 -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
 -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'exchangeserver.domain.local/Exchange Back End'.
Parameter name: VirtualDirectoryName".

     The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
 $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
 -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
 -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'exchangeserver
\ECP (Exchange Back End)' couldn't be found on 'dcserver.domain.local'.".

     The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
 $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
 -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
 -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'exchangeserver
\ECP (Exchange Back End)' couldn't be found on 'dcserver.domain.local'.".

I have not been able to find any information on the cause of these errors, any help would be appreciated.

Hi everyone,

I've successfully installed multiple Mailbox and CAS 2013 SP1 servers into an existing Exchange 2010 environment.

However, when I get to the Edge Transport role on a separate server, at step 7 of 9, it throws the following error:

Error:

The following error was generated when "$error.Clear(); 
	new-ExchangeServer" was run: "Value cannot be null.
Parameter name: Cannot get child of ADObjectId:	this is a GUID based ADObjectId.".

Any ideas what could be causing this? I haven't been able to find anything of significance while searching around...

Thanks!

Is it possible (and functional) to put both things on single server?

with best regards

bostjanc

Hi there,

we transfered all Public Folders from Exchange 2003 to 2010 to 2013 SP1. We have some Calendars with PublicFolderClientPermission Author witch includes EditOwnedItems and DeleteOwnedItems

Unfortunately the Author Rights wont work after migration. it seems like the creator of the object got lost.

since i never notices that in transitions from exchange 2003 to 2010, i think that should be related to the exchange 2013 transition.

Can anybody approve or disprove that behavior?

thanks alot