Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

MSExchange RBAC Event ID 265 error

$
0
0

Hi

I get the following error ever hour on a clean install of Exchange 2013 CU2 in a VM environment.

Any help appreciated.

Log Name:      Application
Source:        MSExchange RBAC
Date:          10/09/2013 7:27:01 a.m.
Event ID:      265
Task Category: RBAC
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EXSERVER.DOMAIN.local
Description:
(Process w3wp.exe, PID 6804) "User  Org:  Cannot get the VanriantConfigurationSnapshot, Exception is thrown Microsoft.Exchange.Data.DataValidationException: The property can't be empty.
   at Microsoft.Exchange.Data.PropertyBag.set_Item(PropertyDefinition key, Object value)
   at Microsoft.Exchange.Data.Directory.ADPropertyBag.set_Item(PropertyDefinition key, Object value)
   at Microsoft.Exchange.Data.PropertyBag.UpdatePropertyDependents(ProviderPropertyDefinition propertyDefinition, Object value)
   at Microsoft.Exchange.Data.PropertyBag.set_Item(PropertyDefinition key, Object value)
   at Microsoft.Exchange.Data.Directory.ADPropertyBag.set_Item(PropertyDefinition key, Object value)
   at Microsoft.Exchange.Data.ConfigurableObject.set_Item(PropertyDefinition propertyDefinition, Object value)
   at Microsoft.Exchange.Configuration.CmdletFlight.GetSnapshot(ADRawEntry executingUser, IRecipientSession recipientSession)"

Regards
Brad


Migration LOtus Domino 853Toward E2013 CU2 with Quest NME 48

$
0
0

Hello Guys,

I am in search of somebody who uses NME 48 to migrate to E2013 CU2 from Lotus 853.

Pb : All the messages with a size superior to 500 Ko(Kb) indicate a limitation of  information store when migrated.

Below a sample of an error message :

17:22:15 Error: message size exceeds that authorized for this user (this is translated the real msg is in French :Error: La taille du message en cours d'envoi dépasse celle autorisée pour cet utilisateur)

17:22:15 Component: Microsoft Exchange Information Store

17:22:15 Low level error: 000004DA

We verify that : no restrictrion on IS, no quota on user mailbox, send (with Outlook 2010 and Outlook 2013)Inside the E2013 org message until 12 Mo (the limit we specified) is all right (test send receive Attachment etc...).

Event viewer with no warning, no error, everything all right.

Found this in quest forum :

1) The mail message if too large for the Exchange Information Store

2) The mailbox has reached capacity

3) Changes to the Transport and Storage limits in Exchange Information Store may not have taken effect yet. May sure to restart the Transport Service for the change to take effect

These 3 points have been checked and doesn' matter in the exchange 2013 organisation.

Configuration : 2 DC 2 E2013 2 Lotus Domino 853 in the same AD Domain, no complication !

Does anybody meet with this situation and could solve it ?

Help would be appreciate because we are stuck because of that restriction.

Patmoy


BOAT

Migrating PST files gives winmail.dat attachments

Big Headache re-installing exchange

$
0
0

I have had to re-install exchange but during install just after it installs the transport roles section 7 it hangs with the following screen. Any help please

Error:

The following error was generated when "$error.Clear();

            Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";

            $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");

            $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");

            Write-ExchangeSetupLog -Info "Loading FipFs snapin";

            Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;

            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false

Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false

            # Copy Microsoft Engine to Engines folder during the install

            $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");

            $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");

            $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");

            $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath

            if(! $MicrosoftEngineExists)

            {

              Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL

            }

           

          " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".

Error:

The following error was generated when "$error.Clear();

            Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";

            $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");

            $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");

            Write-ExchangeSetupLog -Info "Loading FipFs snapin";

            Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;

            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false

            Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false

            # Copy Microsoft Engine to Engines folder during the install

            $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");

            $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");

            $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");

            $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath

            if(! $MicrosoftEngineExists)

            {

              Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL

            }

           

          " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".

Exchange Server 2010 SP3 RU3 - OWA - Out of Office issue

$
0
0

Hi,

We have just upgraded out test lab to Exchange 2010 SP3 RU3. 

We have 2 CAS-servers and 2 Mailbox-servers. All servers er fully patched.

Question - reason for upgrading is that our Production environment is running Exchange 2010 SP2 RU7, and we have issues with IE 11(light mode only) which is resolved in SP3 RU3. But we have discovered a another issue after upgrading. 

After upgrading Exchange,  IE 11 is fixed at the login screen, and we can now choose which login methode we want to use, so this is good. 

But if you login with IE 11 chosse Options > See all Options > Organize E-mails > Automatic Replies - then the page is blank.

If you choose to use Firefox or Chrome everything is working correctly.. 

Does any else have the same problem?

OWA redirection Exchange 2013 to Exchange 2010

$
0
0

Hi All,

my environment is coexist between Exchange 2010 and Exchange 2013 CU3, I want my user login to OWA 2013 and automatically redirect if the user have a mailbox on 2010 server. Can I use same URL name ? example I open mail.mydomain.com 2013 and can redirect to mailbox 2010 with same URL (mail.mydomain.com) I only want Exchange 2013 publish to the internal and external.


Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter:@ikrisna

Installed CU3 on a CU1 Exchange 2013 Server and Now Have to Keep Restarting Transport Service Every 15 Mins

$
0
0

Hello

I was running Exchange Server 2013 CU1 on a Windows Server 2012 server and decided to update it to CU3.

The first attempt led to a failure due to the fact that I had to first uninstall KB2874216: https://dirteam.com/blogs/davestork/archive/2013/09/25/failed-exchange-server-2013-cu2-install-due-to-security-update-2874216.aspx

This also left all the Exchange services disabled again so I had to re-enable them all in services.

After CU3 said it was successfully installed I restarted the server but then realised that external email seemed to stop coming in.

If I telneted to the server on port 25 it said

421 4.3.2 Service not available

If I restart the transport service then it works for a short while (about 15 minutes) and then goes back to saying service unavailable.

I have had to write a script and add a scheduled task to restart the transport service every 15 minutes to keep mailflow working.

I then decided to set up a new server with CU3 but after Exchange is installed on this second server it seems to have created 3 mailbox databases all of which are dismounted. If I try to create another database then I get this error:

An inconsistency in the Active Directory was detected: Database 'Mailbox Database RWS-MAIL1' is expected to be in a database availability group but the value for its MasterServerOrAvailabilityGroup property ('RWS-MAIL1') is not valid. This may be a defect in the product and this should be reported to Microsoft Product Support.

I have waited 24 hours and tried again but still get the same error and the database I tried to create appears there as well but all are dismounted.

Please can someone suggest anything I can try to resolve this.

I have one server where the transport service doesn't work properly and another where I can't create any mailboxes.

Before CU3 everything was working normally on the first single server.

Thanks

Robin


Robin Wilson


Error installing Exchange 2013

$
0
0
Hello,

We are in the process of installing Echange 2013 in an existing Exchange 2010 origanization. The current 2010 server has Exchange 2010 SP3.

Account I am using is Enterprise, Schema and domain admin.

-Schema update ok.

-prepareAd ok.

When installing Exchange 2013 on the Windows 2012 Server, we get errors during installation of the Transport Role.

All relevant errors are below. Anyone has an idea as to what is going wrong? thanks.

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

"The following error was generated when "$error.Clear();

register-ComInteropTLB "Was run:" Process execution failed with exit code 100.".

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

Also errors in the ExchangeSetup log:

12/23/2013 09:11:46.0439] [2] Active Directory session settings for 'Register-ComInteropTlb' are: View Entire Forest: 'True', Configuration Domain Controller: 'xx-ADC001.xxx.xxx', Preferred Global Catalog: xx-ADC001.xxx.xxx', Preferred Domain Controllers: '{ xx-ADC001.xxx.xxx}'
[12/23/2013 09:11:46.0439] [2] Beginning processing register-ComInteropTLB
[12/23/2013 09:11:46.0455] [2] Starting: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\regasm.exe with arguments: /tlb:"D:\Program ‎Files\Microsoft\Exchange Server\V15\Bin\ComInterop.tlb" "D:\Program ‎Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Transport.Agent.ContentFilter.ComInterop.dll"
[12/23/2013 09:11:46.0720] [2] Process standard output: Microsoft .NET Framework Assembly Registration Utility version 4.0.30319.17929
for Microsoft .NET Framework version 4.0.30319.17929
Copyright (C) Microsoft Corporation.  All rights reserved.
Type library exporter warning processing 'Microsoft.Exchange.Data.Transport.Interop.IProxyCallback.SetWriteStream(writeStream), Microsoft.Exchange.Transport.Agent.ContentFilter.ComInterop'. Warning: Type library exporter could not find the type library for 'System.Runtime.InteropServices.ComTypes.IStream'.  IUnknown was substituted for the interface.

[12/23/2013 09:11:46.0720] [2] Process standard error: RegAsm : error RA0000 : An error occurred while saving the exported type library: I/O Error. (Exception from HRESULT: 0x80028CA2 (TYPE_E_IOERROR))

[12/23/2013 09:11:46.0736] [2] [ERROR] Process execution failed with exit code 100.
[12/23/2013 09:11:46.0736] [2] [ERROR] Process execution failed with exit code 100.
[12/23/2013 09:11:46.0736] [2] Ending processing register-ComInteropTLB
[12/23/2013 09:11:46.0736] [1] The following 1 error(s) occurred during task execution:
[12/23/2013 09:11:46.0736] [1] 0.  ErrorRecord: Process execution failed with exit code 100.
[12/23/2013 09:11:46.0736] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 100.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Tasks.RunProcessBase.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[12/23/2013 09:11:46.0736] [1] [ERROR] The following error was generated when "$error.Clear();
 register-ComInteropTLB

" was run: "Process execution failed with exit code 100.".
[12/23/2013 09:11:46.0736] [1] [ERROR] Process execution failed with exit code 100.
[12/23/2013 09:11:46.0736] [1] [ERROR-REFERENCE] Id=TransportCommonComponent___c05511cd334841e7bc1a36550871cf9d Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/23/2013 09:11:46.0736] [1] Setup is stopping now because of one or more critical errors.
[12/23/2013 09:11:46.0736] [1] Finished executing component tasks.
[12/23/2013 09:11:46.0767] [1] Ending processing Install-BridgeheadRole
[12/23/2013 09:12:20.0637] [0] End of Setup
[12/23/2013 09:12:20.0637] [0] **********************************************

"


Migration from 2007 and Archive Mailbox PST import question

$
0
0

Our enterprise will be migrating from Exchange 2007 SP3 to Exchange 2013 CU3 very shortly. Exchange 2013 is set up and I am in coexistance mode currently. Everything is working fine with the legacy redirection, I have tested some mailbox migrations and they work fine. We currently use Mimosa Nearpoint as a third party email archive product.

As part of this migration from 2007 to 2013, we plan on moving away from Mimosa Nearpoint and utilizing the Exchange 2013 Archive Mailbox feature. We will give each user an Archive Mailbox. We have the ability to export the users existing archive out of NearPoint to .PST files and then migrating them directly into the users Archive Mailbox using the "New-MailboxImportRequest -IsArchive" powershell commandlet. This has been tested and works fine with one very important exception.

When I export from Nearpoint, I have to export the entire contents of the archive, I cannot set date ranges. So when I do an export, it also contains the contents of the user's mailbox. I have managed folder policies in place in the Exchange 2007 environment which delete all contents of the mailbox older than 60 days, but when I import the .PST to the archive, it imports ALL items into the Archive Mailbox. So I have 60 days worth duplication of items.

It is my understanding that if I imported the Archive .PST directly into the users production mailbox in the 2013 side, that it would not import duplicate items. I am trying to find out if there is any process which will do the same thing with me importing directly into the users Archive Mailbox.

Thanks you,

Active Directory Dies

$
0
0

We have 3 Active Directory Controllers. Two our on one side of our network (A+B) and one is on the other side of a VPN connection (C). When the VPN connection goes down A and B lose all information until they can reconnect with C. This is a recent development since we replaced a new PIDC (A). A query shows that A has all the roles but a dcdiag /test:advertising on A shows:  

 Starting test: Advertising
    Warning: DsGetDcName returned information for
    \\C.domain, when we were trying to reach A.
    SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
    ......................... A failed test Advertising

When I run the same test on B I get the same error replacing A with B. 

Has anyone seen this before? My network is in a fragile state and I desperately need answers.

Unable to access Exchange 2013 EAC/ECP webpage

$
0
0

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

Exchange 2013 CU3 compatibility with .NET 4.5.1

$
0
0

Can we apply the .NET 4.5.1 update or does Exchange 2013 require plain 4.5?

Thank you!

Exchange 2013 Public Folder Migration Problem

$
0
0

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.

Loop on ECP page login (exchange 2013)

$
0
0

Hi,

I am migrating an Exchange 2007 server to Exchange 2013.
I installed CU2, but now I can not log on https://localhost/ecp, loop it on this page without an error message.

Thanks for reply.

Guillaume

Exchange 2013 CU2 Outlook Anywhere not working

$
0
0

Hi, I have installed an single Exchange 2013 CU2 over Win2012. Valid SSL Certs are in place. Internal communications are working.

OWA is working almost perfectly internally and externally over SSL.

Problems:

1- At OWA level, no option is offered to download attachment. Only preview is permitted for ANY filetype that is an office document (excel, word, ppt). If filetype is an image, then save/download is available.

2- Testing with EXCA ActiveSync

The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.

Attempting the FolderSync command on the Exchange ActiveSync session.
Exchange ActiveSync returned an HTTP 500 response (Internal Server Error).
Diagnostics: 
AAA==_S111_Error:ADOperationException1:Active Directory operation failed on VM-DC-002.ourdomain.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 _Mbx:VM-EXCH13-001.ourdomain.com_Dc:VM-DC-002.IFARHU.GOB.PA_Throttle0_DBL7_DBS1_CmdHC-

3- Testing Outlook Anywhere

Attempting to ping RPC proxy correo.ourdomain.com.
 	RPC Proxy can't be pinged.
	Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Headers received:
request-id: 1711b40e-d416-4f8f-ada1-876c5e8719e0
X-CasErrorCode: EndpointNotFound
X-FEServer: VM-EXCH13-001
Content-Length: 0
Cache-Control: private
Date: Tue, 24 Dec 2013 06:57:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 222 ms.

4- No phones or remote Outlook 2013 clients can be configured, perhaps due to problems in "2" and "3".

We only allow port 443 on the firewall, as we want all to go over SSL. Do I need another port?

No pop3, no IMAP allowed. No load balancer in place. Only a single Exchange 2013 installed CU2 fully updated with default options.

I have read:

http://technet.microsoft.com/en-us/library/dd439371(EXCHG.80)

http://infused.co.nz/2013/05/13/exchange-2013-outlook-anywhere-rpc-settings/

For me, having managed Exchange 2003, 2007 and 2010, moving to RPC over HTTP is a big pain. Also, since this is a simple install I cannot understand why is not working, I have no clear visibility on errors.

Please advice.

Thanks,



Exchange 2013 & Exchange 2007 Co-exist - Problems with Outlook anywhere proxy

$
0
0

Hi,

Got EX13 and EX07 in co-exist. Pointed all the external URL to EX13. ActiveSync proxies to 2007 and OWA redirects to legacy url with SSO. Working perfectly!

But with Outlook Anywhere it does not work. Mailboxes on EX13 works good, but not for EX07 user.

Error message from MRCA:

Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server "internalFQDN ofbackend EX07 server"

The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.

Exchange 2013/2007 coexistence: Configure Exchange 2013 directories on both 2013 CAS servers?

$
0
0

I'm in the middle of setting up a Exchange 2013 and Exchange 2007 coexistence. My current Exchange architecture looks like this:

Exchange 2007

MKE Site:

Ex-CASHub01 - CAS/Hub transport

Ex-CASHub02 - CAS/Hub transport/Active Sync

Ex-MBX01 - mailbox server

Exchange 2013

LA Site:

LA-CAS01

LA-MBX01

LA-MBX02

MKE Site:

MKE-CAS01

MKE-MBX01

MKE-MBX02

Resources online I've found show that when configuring virtual directories for Exchange 2013 to provide the identity of my 2013 CAS server but I have two. Do I configure that on both 2013 CAS boxes? Also, when configuring the legacy namespace and creating the DNS records, am I to assume that I need to create 2 host A records for my 2013 CAS boxes to point to my "MAIL" record? 

Here are the online resources I'm following to guide me:

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx

http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx

Autodiscover sending .local address to remote users

$
0
0

We have an sbs 2011 server and are trying to use the autodiscover feature for clients that are not located in the office.  The problem we see is everything works except the exchange server address it uses is "domain.local" instead of "domain.com".  I have read a ton of blogs but cant seem to find what I need to change so the server name given to the remote users is the local name.

TIA,

Josh


TIA Josh

Getting Error while installing Exchange 2013 on server 2012

$
0
0

Error During Exchange 2013 Mailbox Transport Role Install On Server 2012 

    Question

  • I was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:

    Step 8 of 15: Mailbox role: Transport service

    Error:
    The following error was generated when "$error.Clear(); 
              $maxWait = New-TimeSpan -Minutes 8
              $timeout = Get-Date;
              $timeout = $timeout.Add($maxWait);
              $currTime = Get-Date;
              $successfullySetConfigDC = $false;

              while($currTime -le $timeout)
              {
                $setSharedCDCErrors = @();
                try
                {
                  Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
                  $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

                  if($successfullySetConfigDC)
                  {
                    break;
                  }
                  Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
                }
                catch
                {
                  Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
                }

                Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
                Start-Sleep -Seconds 30;
                $currTime = Get-Date;
              }

              if( -not $successfullySetConfigDC)
              {
                Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
              }
            " was run: "Unable to set shared config DC.".

Low impact mailbox movement from Exchange 2010 to 2013 - Can both environment work with different namspace

$
0
0

We are running Exchange 2010 SP2 on a single domain single site with four servers

mail1 - CAS,HT,Mbox ()DAG member)
mail2 - CAS,HT
mail3 - CAS,HT,Mbox (DAG member)
mail4 - mbox (DAG member)

We do not have a CAS array and intend to use mail.domain.com namespace this time when we upgrade to 2013.

Our three 2010 servers mail1,mail2 and mail3 are published on public DNS and are accessible externally over different ISP links and our clients have their outlook 2011 Mac and few other IMAP accounts configured using mail1.domain.com, mail2.domain.com or mail3.domain.com

We are planning  transition to Exchange 2013 with another four servers as :
Ex13CAS1 - CAS
Ex13CAS2  - CAS
Ex13Mbox1 - Mbox in DAG
Ex13Mbox2 - Mbox in DAG
we also will have a hardware load balancer before the CAS servers and will use mail.domain.com 

Question:

Our concern is for Mac clients / IMAP accounts that are configured manually which will have impact once we move the namespace. We want to check the possibility if both setup can coexist independently for a period while we help all such users to conveniently move to exchange 2013.

Since users are at different geographical locations with manual account configuration  it would be big overhead in reconfiguring each user account who all will lose connectivity as we move the namespace. Is there a way we setup Exchange 2013 with the new name space but keep these client using their existing configuration with existing namespace and gradually move them in batches causing minimum impact. ie same domain two name space.
 
In other words, Is it possible that users keep using mail1,mail2 or mail3 as per their present configuration while we move the users gradually to the new single name space mail.domain.com i.e. can both exchange setup be functional over different ISP links independently. if we transit to a single namespace, users that are moved get their 2013 mailbox but the users still on 2010 continue to use their mail accounts with mail1\mail2 or mail3.domain.com instead of getting proxied from 2013 CAS. Please suggest a correct approach in this situation. 


Viewing all 7008 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>