Hello,

Here's the set up:

2 Servers:  2008 R2 Sp1.    One active one passive. These are the servers that contain DB's that need to be moved

2 Servers:  2012 R2 Stnd    Want same set up one active one passive, These are the destination of DB's from above

All are part of same domain.

Are there any step by step guides out there for this?

Thanks for any and all information!

I have an IIS ARR server which points back to my exchange server. OWA and ECP work perfectly fine.

I have set it up with the following guide:

http://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx

The only thing that is not working is Outlook connectivity (both internally and externally).

I get the following error message on the MS connectivity test:

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

RPC Proxy can't be pinged.
     
Additional Details
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (401) Unauthorized.Type: Microsoft.Exchange.Tools.ExRca.Extensions.MapiTransportException

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

I tested the exchange server direct (i.e. without ARR) and it works as expected. I think it has something to do with the credentials not being passed between ARR and the exchange server because if I am on the local network, I can go straight to the exchange server / rpc (via https://servername/rpc) and it prompts for credentials once and gives me a blank page (expected) whereas if I go via ARR it prompts for credentials but doesn't accept them (just prompts again and again and again).

Anyone manage to fix this issue?

Thanks.

We have about 500 users coming from a notes env.  to our env of exchange 2010.   They want to bring their emaisl with them.   We may be provided by NSF files by their mail admin and then we use a third party tool to convert to pst.  Question .. what is the best approach, what will happen to recurring appointments, tasks,  encrypted items? Their admin will/may config mail forwarding at his end pointed  to their mbxs on exchange server at our end. Not sure what strategy he/we adapt.  How would you do or done this kinda migration? Whats were the lessons learnt and what shud we consider.  Much appreciated- tnx! there will be none or have no relationship or trust of any kind between these 2 orgs.

I am bit puzzled and frustrated with this issue I have in my lab.  I have exported my test mailboxes from my 2010 environment (other settings are minor and easily reproduced), and uninstalled 2010.  Next I went and installed 2013 RTM from TechNet.

The first time I installed 2013 the install was successful, but when the ECP came up it was just a empty browser window - it would never display.  So I thought, maybe there was something left over from the previous 2010 server.  I blew away the OS (was 2008 R2) and built a clean 2012 server.  Installed all the Exchange 2013 prerequisites, extended the Schema and installed 2013 using all the defaults in the wizard.

This time the the ECP login came up, but here is where it gets puzzling and frustrating.  I put my Admin credentials in (this account has all proper group membership that I'm aware of) and the screen goes blank for a second and then the OWA login is displayed.  The ECP never comes up again, just goes straight to the OWA login.  If I enter my credentials in the OWA login, the screen just flashes and the password field clears but doesn't login.

I have tried uninstalling and cleaning up AD and reinstalling, but the same thing keeps happening.  I can't help but think it has something to do with permissions, but I'm not sure what that would be.

I installed Exchange 2013 on 2 brand new Server 2012 virtual machines, one with the mailbox role and another with the CAS roles. The installation completed without errors but I cannot log on to the ECP (or OWA for that matter). As I enter my user/pass, the password field goes blank and a number of event log entries are added (see below).

I'm using the default administrator account (also Enterprise Admin, Domain Admin and member of the Organization Management security groups). I mail-enabled the account with enable-mailuser + enable-mailbox. I can execute Exchange Powershell cmdlets when logged on with this account, so security looks good.

The problem is OWA/ECP which consistenly logs the following errors when I attempt to access the OWA:

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

I have spent hours wading through log files and posts, and cannot get my head around this one. 

Hi All,

Getting extremely frustrated now with a new Exchange 2013 installation on a Windows Server 2012 VM...

After having a lot of problems with the installation (didn't uninstall visual c++ which caused failure, then needed to delete the AD Microsoft Exchange System Objects group due to permission failures, etc) I've now got a fully installed Exchange server. Still, now I cannot figure out how to fix my next problem - Accessing the EAC/ECP.

I've searched every possible web guide/forum thread and the only one which is the same issue I'm having is this one: http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/89c42771-78c9-4d94-88e5-557320eccc71 

Unfortunately, as you can see in that thread, it is still unresolved. 

Current Issue: trying to access https://localhost/ecp (or any other variation) returns a 404 Not Found.

The error page points the physical path to c:\inetpub\wwwroot\ecp however that folder does not exist. I have tried manually changing the IIS site (Exchange Back End) to point its physical path to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\ecp which seems to be valid, however it doesn't work...

Not sure what else to do... HELP!

Oli

I keep getting the following error:

Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter)
          {
            $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
            if ($arbUsers.Length -ne 0)
            {
              $mbxname = $arbUsers[0].name;
              $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
              {
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if ($dbs.Length -ne 0)
                {
                  enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
                }
              }
            }
          }" was run: "Active Directory operation failed on servername.domain.com. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
Active directory response: 0000207D: UpdErr: DSID-03151222, problem 6002 (OBJ_CLASS_VIOLATION), data -1814126740".

When I go into ADSI Edit:

Configuration > CN Services > Microsoft Exchange > OrganizationName >  Administrative Groups > Exchange Administrative Groups > Databases

I have 3 Mailbox Databases listed. Should I delete 1 or all of them?

Hello,

I've installed Exchange 2013 into Exchange 2010 infrastructure
[ single Exchange 2010 server; single AD site; AD = 2003 ],
and moved one mailbox [ Test user ] to Exchange 2013.

When I login internally through 2013 OWA to access mailboxes on 2010, then proxy works fine.
When I login internally through 2010 OWA to access mailboxes on 2013, then a message appears:
    Use the following link to open this mailbox with the best performance: with link to 2013 OWA...

What is wrong ?
I've checked and changed settings by:
Get-OwaVirtualDirectory, Set-OwaVirtualDirectory

[PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex10\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*

Server                        : EX10
Name                          : owa (Default Web Site)
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
RedirectToOptimalOWAServer    : True
LegacyRedirectType            : Silent
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://ex10.contoso.com/owa
ExternalUrl                   : https://ex10.contoso.com/owa

[PS] C:\work>Get-OwaVirtualDirectory -Identity 'ex13\owa (Default Web Site)' | fl server,name, *auth*,*redir*,*url*

Server                        : EX13
Name                          : owa (Default Web Site)
ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
RedirectToOptimalOWAServer    : True
LegacyRedirectType            : Silent
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   : https://ex13.contoso.com/owa
ExternalUrl                   :

best regards Janusz Such

We are an organization running a hybrid environment exchange 2010 sp3 RU5 with an Office 365 tenancy

We acquired a company running exchange 2013.  Our usual process is to setup visibility both ways and do cross org mailbox moves into our hybrid environment and move their accounts to the cloud from there.  

When I run the new-moverequest from the ex 2010 CAS server to pull the mailbox from ex2013 into our org I get this error:

The remote server doesn't support client 'CAS server FQDN' version (14.3.178.0 caps:05FEFF). Missing functionali

ty: 'TenantHint'.

    + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException

    + FullyQualifiedErrorId : 7D20C51B,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

Can you not pull a mailbox from 2013 back into 2010?

Hi all,

I am in the testing stages of a cross-forest mail migration (2008 SP2 forest with exchange 2010 SP3 to 2012R2 with 2013 Sp1)

The account is prepared with the Prepare-MoveRequest.ps1, mailbox is moved (either with new-moverequest or new-migrationbatch OR from the ECP portal) user account moves without issue, no failed items. user is prompted to restart outlook, the expectation is that when the user re-opens outlook it should be pointing to their new moved mailbox. for older mailboxes this does not work. I have to go in and manually create a new profile and search for their account.

Now the interesting part. I create a new user in the new forest, user our create user script (from the mailbox forest it finds the user, creates the local user then adds mailbox and links to the user account in the new forest) once this is done,  I can wait for replication then prepare the new forest account to migration (mail enable and run Prepare-Moverquest) once I move the mailbox and reclogged in, the mailbox was pointing properly to the new exchange environment!

Any thoughts on why any older (longer then a couple days) would fail out?

any thoughts or suggestions would be appreciated!

Hi there,

i tried a lot and did a lot of research so i just want to share that information. When you try to open the Public Folders from XP Client you receive:

Windows 7 works fine.

The Mailbox it self works fine, Outlook 2007 or 2010 (patched) makes no difference, Autodisdover works fine.

Regkey for XP is allready set:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"lmcompatibilitylevel"=dword:00000003

Auth is set to NTLM.

We found this:

1. Critical: 12/4 Outlook (all version) on Windows XP cannot access Exchange 2013 CU3 modern Public Folders, when their mailbox is on 2013 CU3 server
   • Only critical if you have Windows XP clients, which many organizations still do
   • Workaround: Have users use OWA or W7+ workstation

http://blog.jasonsherry.net/2013/11/25/exchange-2010-sp3-ru3-2013-cu3-released/

-> We have a Support-Case running and ill update you.

I am about to migrate a Windows Server 2003r2 Active Directory that has an Exchange 2003 server. This domain started as an NT4 domain and has been upgraded to its current level and is working well.

I plan to migrate to Server 2012R2 and Exchange 2013.

The domain is relatively small. I can migrate (I think, with an intermediary ‘08R2 server), or I can start a fresh ‘12R2 Forest/Domain and fresh Exchange.

I would prefer to migrate, but I am worried about namespace issues.

Current namespace is      internaldomain.loc    and machines are  servername.internaldomain.loc   .

NetBIOS domain name is        internaldomain    

Users are identified as   internaldomain\username   or    internaldomain.loc\username

The Active Directory DNS server is set with forwards to our ISPs DNS servers.

We have real world      externaldomain.com   MX record forwarded through our firewall to port 25 on our Exchange server.

Is it still a supported practice in Server 2012R2 to keep internal DNS  internaldomain.loc    and the external reference  externaldomain.com    ?

One of my SSL SAN certificate vendors mentioned something about  .loc   and   .local   suffixes being disallowed on new certificates. We do not use any web interfaces to Exchange internally, and if we did for any reason, I do not mind the warning message about the certificate not being trusted (internally).

All our internal access to the Exchange server 2013 will be from Outlook 2010 or Outlook 2013.

I think all the external services such as Active Sync, Outlook Anywhere, or Outlook Web Access, or the AutoDiscover service can be referenced to the  externaldomain.com     name and internally to the Exchange Server’s external facing interface just like I do in Windows Server 2008R2 and Exchange 2010, but I am not completely sure.

I have done a certain amount of research and think I can just migrate with my current namespace, but I would like to make sure I don’t create issues.

Can I migrate with my current namespace?

I think this is straightforward, but I would like some expert opinions and advice please.

I will post this in the Windows Server and Exchange server forums.

Thank you.

Hello,

I am running a windows SBS 2011 standard system and there was currently an update for Exchange 2010 Rollup 2 Service Pack 3 and it keeps failing.  It says that it cannot find the installation package (exchangeserver.msi) and it is looking for it in E:\Software\Exchange2010-SP3-x64\ folder but there never was this folder.  There is only an Exchange2010-SP3-x64.exe file.

The only exchangeserver.msi file that I find on the server any where is in C:\ProgramFiles\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1 but it won't accept it (says not authorized for this update or something alike).

Please help.  It is currently causing issues with email.  Some of the features are not working because it says exchange is currently under maintenance.

Any suggestions would be greatly appreciated.  Thank you.

Hi Guys,

I got this error message keeps popping up in the event viewer like every minute.. i have no clue what is this error message is for. can anyone give me some idea or point me to the right direction

Exchange 2013 running 2 node DAG. the error message is found on the passive node.

"The Microsoft Exchange Migration Workflow service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service."

Thanks

Hi All,

Over the past 2 days this update has tried to run on the server in the evening but ends up failing. When it fails it is causing all of our exchange services to stop working and when we try to check e-mails the following day we find out the e-mail service has been offline since the update.

Is there anything specific we need to do before running this update?

Cheers,

Hello, 

We are in the process of deploying Exchange 2013 into our Exchange 2010 Org.  We are using an F5 to load balance all services. We are doing some initial testing and have not cut over autodiscover or other URLs yet to 2013.  We are using host files on the local testing machines to point the URLs to 2013.    OWA, Activesync, ecp work with no issue through the F5 VIP.   However, we are having issues with Outlook.  If our host file entries point to a single server, Outlook functions normally.  If the host file entries point to the F5 VIP, it keeps prompting for creds and will never connect.

Just wondering if anybody has run into this or has any guidance as far as OA and F5 deployment.

Thanks

Hello, guys!

I need your help. I've just tried to make an update my Exchange Server with CU5 and get an error:

"$error.Clear(); 
          Uninstall-CrimsonManifest -DefinitionXml "bin\ActiveMonitoringEvents.man";

          Install-CrimsonManifest `
            -DefinitionXml "bin\ActiveMonitoringEvents.man" `
            -MessageDll "bin\ActiveMonitoringEventMsg.dll" `
            -ProviderName "Microsoft-Exchange-ActiveMonitoring"
        "The following error occurred: "System.InvalidOperationException:Failed to perform event manifest action (manifest = C:\Program Files\Microsoft\Exchange Server\V15\bin\ActiveMonitoringEvents.man, event = install-manifest,exitcode   = 5, errors = The publishers and channels are installed successfully. However, we can't enable one or more publishers and channels. Access is denied.
)
   in Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   in Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   in Microsoft.Exchange.Management.SystemConfigurationTasks.InstallCrimsonManifest.InternalProcessRecord()
   in Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   in Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Help me, please!!!

What should i do to resolve this problem???

Microsoft Certified IT Professional Server Administrator

Microsoft Certified IT Professional Server Administrator