I have installed Exchange 2013 Mailbox and Client Access Roles on a Windows 2012 Server.  Loadgen has been installed on a Windows 8 client.  All are joined to the domain and are able to resolve DNS.  I've used Loadgen to generate users, distribution groups and contacts, but when I try to initialize the mailboxes if fails with this (a segment from the init log)

StoreBuilder.General Error: 0 : 08/28/2014 16:10:47 -- Diagnostic context (user: '3bcc2049-322b-449a-9164-d1e4dca5393a'):
 distinguishedName 'CN=W2K12-C 62ACEED7-LGU000019,OU=mbdb2,OU=Users,OU=LoadGen Objects,DC=QA137,DC=com', exchServerDn '/o=QA137/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=W2K12-C', userDn '/o=QA137/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=62ACEED7-LGU000019', mailNickName '62ACEED7-LGU000019', emailAddress xxx.
StoreBuilder.General Error: 0 : 08/28/2014 16:11:07 -- Diagnostic context (user: '2ea501ff-f029-41a6-b9f1-b223eb960c02'):
 distinguishedName 'CN=W2K12-C 62ACEED6-LGU000000,OU=mbdb1,OU=Users,OU=LoadGen Objects,DC=QA137,DC=com', exchServerDn '/o=QA137/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=W2K12-C', userDn '/o=QA137/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=62ACEED6-LGU000000', mailNickName '62ACEED6-LGU000000', emailAddress xxx.
Engine.General Warning: 0 : 08/28/2014 16:11:07 -- Caught a non-fatal exception in executeTaskStub. The exception was handled by the task module: Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 49064   dwParam: 0x3
    Lid: 59431   EMSMDB.EcDoConnectEx called [length=144]
    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6BA][latency=12003]
    Lid: 62184 
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 2388
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-28T23:11:07.0970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 13
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 1352
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 1
    Lid: 12952   d

I believe this has to do with the exchange certificates, I've since installed ADCS on one of my domain controllers thinking this would allow me to generate the needed certificate...but I'm having trouble. When I generate the exchange req and import it to the ADCS, it fails to generate the cert because it isn't associated with a template. 

Can someone help me out?  This is a test environment and I really need to get something accomplished.

Hi Gents 

I am currently planning to upgrading one of our clients Exchange 2010 Server to Exchange 2013. I know that the simplest solution would be install exchange 2013 with CU2 and make the 2010 coexisting but below is what my limitations are

Currently - Customer is on a SBS physical server that has Exchange 2010 SP1 installed, only 30 clients at the moment. 

I have already prepared a server 2012r2 vm where i will install the Exchange 2013, My question is, can i simply just install the new exchange 2013 in the new VM server, Export all the mailbox as pst from the exchange 2010 server and then import all the mailbox pst into exchange 2013?

Given that they only have 30 clients and the current server is a physical server, i don't have enough time to plan a p2v migration or upgrade current exchange 2010 to sp3 for the coexistence to work so i thought maybe exporting and importing pst will be a better solution. can someone confirm if this will work or if you have tried this method at all ?

mail client use ms.outlook 2007, everything ok when it's use first time after setup, next business day it's show error and status disconnect

"Task 'Microsoft Exchange Server' reported error (0x8004011d): 'The server is not available. Contact your administrator is this condition persists."

i've follow this instruction,but not works.

*support.microsoft.com/kb/923575

*forums.msexchange.org/Error_%280x8004011D%29_The_server_is_not_available/m_30795900/tm.htm

note.first time after setup mail client,there's no certificate required pop-up, now each time open it, it's show certificate alert

in security alert,show cross : the name on the security certificate is invalid or does not match the name of the site

Hello,

I'm trying to move mailboxes from Exchange 2007 to 2013. The move request seems to be stuck in the "Syncing" mode.
Exchange 2007 environment consists of CAS and MBX servers, Exchange 2013 has both roles on the same machine.
Mail traffic between servers, to/from internet works without issues.
Where would I start to troubleshoot it?

Thanks.

Memento Mori

hi there,

i need some help here... in the instalation of exchange server 2012 apear this error on mailbox roles: transport service.

how i renew the certificate? that the program ask...

thanks.

Error:
The following error was generated when "$error.Clear(); 
          Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
          {
            Install-AuthCertificate -DomainController $RoleDomainController
          }
        " was run: "System.Security.Cryptography.CryptographicException: The certificate is expired.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Dear all,

after migrating from Exchange 2007 (part of SBS 2008) to Exchange 2013 I came upon an issue with my OAB. All users state that they cannot download the OAB from their Outlook 2010/2013 clients. I checked serveral things on my Exchange 2013 server:

• I made sure that both InternalURL as well as ExternalURL are configured for my Ex2013 OAB
• I made sure that my Ex2013 OAB has been configured as Default OAB within my organization
• I made sure that Outlook "Test EMail-AutoConfiguration" receives a valid OAB URL (https://servmsx.eggs.local/oab/f34d6b53-9957-4c56-aa53-222e65b13157/) and identity
• I made sure that all corresponding Mailboxes have a OutlookAddressBook property configured (pointing to my Ex2013 OAB)

The Ex2013 OAB Name is "OAB (Default Web Site)", InternalURL is "https://servmsx.eggs.local/OAB", OfflineAddressBook is "\Standard-Offlineadressbuch (Ex2013)".

I tried to access the OAB with IE with URL "https://servmsx.eggs.local/oab/f34d6b53-9957-4c56-aa53-222e65b13157/", receive a logon prompt, enter valid credentials and then receive an HTTP 500 error. IIS Auth settings for Virtual Directory OAB are as follows:

• Name                          : OAB (Default Web Site)
• BasicAuthentication           : False
• WindowsAuthentication         : True
• OAuthAuthentication           : True
• InternalAuthenticationMethods : {WindowsIntegrated, OAuth}
• ExternalAuthenticationMethods : {WindowsIntegrated, OAuth}
• When checking the file system on my Ex2013 under "D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB" I don't find any subfolder "f34d6b53-9957-4c56-aa53-222e65b13157" as stated in the URL from Outlook. Only "bin", and web.config. No XML files or anything.

when executing "Get-OfflineAddressBook "Standard-Offlineadressbuch (Ex2013)" | fl" I receive:

• RunspaceId                       : 23cf835c-016b-45f5-97a5-a66ecbcacdb5
• Server                           :
• AddressLists                     : {\Globale Standardadressliste}
• Versions                         : {Version4}
• IsDefault                        : True
• PublicFolderDatabase             :
• PublicFolderDistributionEnabled  : False
• GlobalWebDistributionEnabled     : False
• WebDistributionEnabled           : True
• LastTouchedTime                  :
• LastRequestedTime                :
• LastFailedTime                   :
  LastNumberOfRecords              :
• LastGeneratingData               :
• MaxBinaryPropertySize            : 32768
• MaxMultivaluedBinaryPropertySize : 65536
• MaxStringPropertySize            : 3400
• MaxMultivaluedStringPropertySize : 65536
• ConfiguredAttributes             : {OfficeLocationUnicode, ANR, ProxyAddresses, ANR, PhoneticGivenName, ANR,GivenName, ANR, PhoneticSurname, ANR, Surname, ANR, Account, ANR,PhoneticDisplayName, ANR, DisplayName, ANR, IsOrganizational, Value,                                   ExternalMemberCount, Value, TotalMemberCount, Value, ModerationEnabled, Value,            DelivContLength, Value, MailTipTranslations, Value, ObjectGuid, Value...}
• DiffRetentionPeriod              : 30
• Schedule                         : {So.05:00-So.05:15, Mo.05:00-Mo.05:15, Di.05:00-Di.05:15, Mi.05:00-Mi.05:15,Do.05:00-Do.05:15, Fr.05:00-Fr.05:15, Sa.05:00-Sa.05:15}
• VirtualDirectories               : {SERVMSX\OAB (Default Web Site), SERVMSX\OAB (Exchange Back End)}
• AdminDisplayName                 :
• Identity                         : \Standard-Offlineadressbuch (Ex2013)
• IsValid                          : True
• ExchangeVersion                  : 0.20 (15.0.0.0)
• Name                             : Standard-Offlineadressbuch (Ex2013)
• DistinguishedName                : CN=Standard-Offlineadressbuch (Ex2013),CN=Offline Address Lists,CN=Address Lists Container,CN=First Organization,CN=Microsoft                                   Exchange,CN=Services,CN=Configuration,DC=eggs,DC=local
• Guid                             : f34d6b53-9957-4c56-aa53-222e65b13157
• ObjectCategory                   : eggs.local/Configuration/Schema/ms-Exch-OAB
• ObjectClass                      : {top, msExchOAB}
• WhenChanged                      : 14.08.2014 11:31:38
• WhenCreated                      : 14.08.2014 11:24:50
• WhenChangedUTC                   : 14.08.2014 09:31:38
• WhenCreatedUTC                   : 14.08.2014 09:24:50
• OrganizationId                   :
• OriginatingServer                : GAIA.eggs.local
• ObjectState                      : Unchanged

What else is there to check? Any help would be greatly appreciated.
Alex

Alexander Ollischer Diplom-Wirtschaftsinformatiker (FH) Citrix & Microsoft Certified Engineer (CCEA, CCEE, MCSA, MCSE, MCDBA, MCTS) Afontis IT+Services GmbH Baierbrunner Straße 15 81379 München Deutschland Telefon (089) 74 34 55-0 Fax (089) 74 34 55-55 mailto:a.ollischer@afontis.de http://www.afontis.de http://www.itganzeinfach.de Amtsgericht München, HRB 109 005 Geschäftsführer: Thomas Klimmer

Hallo,

I am trying to migrate Exchange mailboxes from Exchange 2007 in Domain Forrest COM to Exchange 2013 in Domain Forrest DOM.

The setup: Exch2007 run on a Windows Server 2008R2 server and the DC of Forrest COM runs on another&nbsp;Windows Server 2008R2 server.

Exchange 2013 runs on a Windows Server 2012 server&nbsp;and the DC of Forrest DOM runs on another&nbsp;Windows Server 2012 server.</p><p>From the DC of Forrest A I start a remoter PowerShell session to connect the CAS server of Exchange 2013 using "Invoke" comand:

$LocalCred is the credential of Exchange and AD admin of forrest DOM.

$RCred and $RemoteCred are the credentials of Exchange and AD admin of forrest COM.

The result of this invoke coamnd is:

PowerShell remoting is enabled on CAS Exchange 2013.

If I run the same comand which is in the invoke script block via RDP session on the CAS Exchange 2013 it works.

Tell me if further information is needed.

Thanks a lot in advance.

Frank

Hello,

We currently have 2 Exchange 2010 SP3 servers in 1 DAG. Both servers host CAS, Mailbox and Hub Role.

I want to introduce a 3^rd Exchange 2013 Server and slowly move users onto a new DAG I build in Exchange 2013.

Can I create a 3^rd Exchange 2013 Server with CAS and Mailbox Server Role and make the 3^rd Exchange server (2013) a member of the existing (2010) CAS array then slowly perform local move requests for users mailboxes from my Exchange 2010 DAG to the Exchange 2013 DAG without any disruption to my outlook, OWA and AS clients?

Exchange 2010 (Windows 2008 R2)

Exchange 2013 (Windows 2012 R2 DataCenter)

Hi,

Im trying to set up IP Block List Providers on a very simple Exchange environment consisting of two servers.

Server1 = Client Access and Mailbox roles (domain joined)
Server2 = Edge role (not domain joined) 

I Setup my Block Lists Providers on Server1 then run the PowerShell command "Get-IPBlockListProvider" which then returns the providers I setup. Now if I change to Server2 and run the same PowerShell command it does not list any configuration. My first thought was that the AD LDS instance on the edge was not updated so I ran the command Start-EdgeSynchronization -ForceFullSync -Server Server1 -TargetServer Server2 to force an update on the edge, then Test-EdgeSynchronization –FullCompareMode which reports everything as synchronized.

Why is the configuration not showing on the Edge? Could there be a communication issue or should I be adding the Block List Providers Directly on the Edge without being able to see the configuration from Server1?

The reason I suspect communication is because when I open the ECP on Server1 (FrontEnd) click Servers and double click the Edge (Server2) I get the following error message “An error occurred while accessing the registry on the server"Server2.domain.local". The error that occurred is: "The network path was not found". Ive checked the DNS, im able to ping the DC and the front end (server1) from the edge. Im also able to map the C$ share of the DC and Front End. 

Appreciate any help on this. 

Hi all

Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?

Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.

So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.

What did I overlook or not understand, or am I making migration more complex than needed?

Thanks for reading and best regards
/Maurice

PS: here were some of my pre-post readings: Exchange 2003-2013 co-existence, even better Exchange 2003-2013 co-existence, Exchange 2010-2013 co-existence slides, Upgrading ActiveSync to Exchange 2010,

I currently have an Exchange 2010 server with all the roles installed.  Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error.  When I installed Exchange 2013, I got an error saying I had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left.  There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group.  This deletion caused my access to my public folders to get messed up.  I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA.  I also get this error when trying to access either Default or System Public Folders.  "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\' -server 'ExchangeServer' "

My Public Folder Database exists and is mounted.  Any help is appreciated.

Regards, Md Ehteshamuddin Khan All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Hi everyone,

afternoon

I am trouble i am trying to migrate from 2007 to 2013, i have done pre-req.. 2007 SP3 rollup 10 n all other

same DC i am trying to install Exchange 2103, Error log is below

hope someone will get me out of it

Error:
The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter)
          {
            $createNewOab = $false;
            $oabName = $null;
            $oabAddressList = $null;
            $oabVdirs = $null;
            $oabGlobalWebDistribution = $false;
            $oabConfiguredAttributes = $null;

            Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
            $defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
            if ($defaultOab -ne $null)
            {
              Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + "; checking its version");
              if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -lt 0)
              {
                Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older; will create a new OAB");
                $createNewOab = $true;
                $oabName = $defaultOab.Name + " (Ex2012)";
                $oabAddressList = $defaultOab.AddressLists;
                $oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
                $oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
              }
              else
              {
                Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2012 or newer; will not create a new OAB");
              }
            }
            else
            {
              Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
              $createNewOab = $true;
              
              $oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
              $nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController -ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
              if ($nonDefaultOabWithDefaultName -ne $null)
              {
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Offline address book " + `
                  $nonDefaultOabWithDefaultName.Name + `
                  " already exists: " + `
                  $nonDefaultOabWithDefaultName.DistinguishedName + `
                  ". Use administrative tools to change it to default OAB.");
              }

              $allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
              if ($allGals -eq $null -or $allGals.Count -eq 0)
              {
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Couldn't find the default global address list. The default offline address book can't be created.");
              }
              elseif ($allGals.Count -gt 1)
              {
                $createNewOab = $false;
                Write-ExchangeSetupLog -Warning `
                  ("Found " + $allGals.Count + " default global address lists. You can have only one default global address list in your organization. The default offline address book will not be created.");
              }
              else
              {
                $oabAddressList = $allGals[0];
                Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
              }
            }

            if ($createNewOab)
            {
              if ($oabGlobalWebDistribution -eq $false)
              {
                $currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
                $allOabVdirs = @(Get-OabVirtualDirectory -DomainController:$RoleDomainController);
                $e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
                if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
                {
                  foreach ($oabVdir in $allOabVdirs)
                  {
                    if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion, $e15MinimumServerVersion) -gt 0)
                    {
                      $oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server -DomainController:$RoleDomainController).Site.DistinguishedName;
                      if ($oabVdirSiteDn -eq $currentAdSiteDn)
                      {
                        $oabVdirs = $oabVdir;
                        break;
                      }
                      elseif ($oabVdirs -eq $null)
                      {
                        $oabVdirs = $oabVdir;
                      }
                    }
                  }
                }

                if ($oabVdirs -ne $null)
                {
                  Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual directory " + $oabVdirs.Name);
                }
                else
                {
                  Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories; OAB will be configured without distribution.");
                }
              }

              try
              {
                Write-ExchangeSetupLog -Info ("Creating new default OAB.");
                $newOab = New-OfflineAddressBook `
                  -Name $oabName `
                  -AddressLists $oabAddressList `
                  -VirtualDirectories $oabVdirs `
                  -GlobalWebDistributionEnabled $oabGlobalWebDistribution `
                  -IsDefault $true `
                  -DomainController:$RoleDomainController;
              }
              catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
              {
                Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object already exists; it may have been created by another instance of setup.");
              }

              if ($oabConfiguredAttributes -ne $null)
              {
                Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " + $oabConfiguredAttributes);
                Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
              }
            }
          }
        " was run: "The task wasn't able to connect to IIS on the server 'XCHNG1.Lab.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
".

Hi,

I have outsourcing my migration from exchange 2010 to exchange 2013, but the job isn't finish and i'm alone for finish.

The 2010 environnement :

2 cas with nlb.
2 Dag serveur.

There is intergration with 2013 farm like this :

2 cas server with a news cas adresse
2 dag server.

Everythin is publish in TMG.

I can move bal from a database to an other database. The migration can take effect. The action I Don't know is to remove 2010 server after all bal migration, and change CAS NLB adresse (IP and DNS) of the news 2013 exchange serveur.

It's diffucult to apprehend the nlb adress change.

Thank for your help.

Regard

Hello!

We are planning on moving our Exchange 2013 installation to a new server. It is currently on a Foundation 2012 Server which is also a Domain Controller. I know this is not optimum but our previous system administrator was not very qualified when this was deployed.

I have installed a new Windows 2012 R2 server, added AD roles and installed all the prerequisites for Exchange 2013 and then installed Exchange 2013.

I believe I know how to migrate all the mailboxes as well as the public folder mailbox, however I am still unsure of a few things:

1) I have read that the new public folder mailbox should have all the permissions of the old public folder mailbox. However when I log onto the ECP of the new exchange installation, I see the public folder mailbox of the old server with all the permissions. Where would I set the permissions of the new public folder mailbox before I migrate the public folder via exchange command applet?

2) Regarding all the settings for the exchange server, were these automatically migrated to the new server? Because I see them all when I log onto the new server ecp.

3) Besides user mailboxes, public folder mailbox, offline address book, and smtp connectors, is there anything else I need to configure on the new server?

4) Once all the above have been done, how would I remove the old exchange 2013 server correctly? (We want to completely decommission it i.e. AD, Domain Controller, Exchange).

Thank you for reading!

Environment: 

1x On-premise Exchange 2013 Server with CAS role

1x On-premise Exchange 2013 Server with Mailbox Role

DIRSYNC

All users migrated to Exchange Online

Questions:

1. In removing the Hybrid Configuration, there's a step that requires the On-premise EAC to be used. However when I open the EAC in the On-premise CAS server I'm redirected to the Exchange Online OWA page. Question is how to open the EAC in on-premise when all users have been migrated to Office 365? Is there a need to off-board the admin mailbox in order to run the EAC?

2. I need to decommission the On-premise Exchange 2013 Mailbox with the intention of reclaiming the storage space used by the databases. The on-premise Exchange 2013 CAS server will be used to manage the Exchange attributes and will not be decommissioned. Can you point me to a documentation on how to properly remove the Exchange 2013 Mailbox role?

Thanks.

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

Hello,

We have one Exchange 2007 Server and we want to migrate it to Exchange 2013.

We installed three Exchange 2013 SP1, the first that we installed was in a Windows Server 2012 and the other two Windows Server 2012 R2.

Now, we want install another one in Windows 2012 R2 (same name, same IP) , because DAG doesn't work with 2012 and 2012 R2.

But my doubt is:

What are the steps to remove the Exchange in Windows 2012? Is so easy like uninstall from Control Panel -Uninstall a Program... or we need to do something more to remove the actual Exchange completly from Active Directory.

Thanks in advance.

When i try to upgrade exchange 2010 service pack 2 to service pack 3, while upgrading hub transport role there is a error pop up that " a failure occurred while trying to update metabase properties.

The system cannot find the path specified. "

this is the error please can anyone help me to fix my issue.

Regards.

Ashane.

Ashane Deshapriya ( MCP )

Good morning,

I was referred from http://community.office365.com/en-us/f/158/t/261575.aspx and was hoping you would be able to assist me with the inquiry below.  Thank you!

When creating a new user mailbox, the Display name defaults to "First name, Initials, and Last name" (as confirmed by http://technet.microsoft.com/en-us/library/jj991919(v=exchg.150).aspx).  More specifically, the default is "First name, SPACE, Initial(s), PERIOD, Last name".  Our Exchange 2010 environment is presently configured to format new mailbox display names to "Last name, SPACE, First name, SPACE, Initial".  We are in the process of testing Exchange 2013 for migration from Exchange 2010 with existing mailboxes of 5,000+ and need to configure Exchange 2013 to default the display name utilizing the same format as established through Exchange 2010.  How can this be accomplished?

Seth