Exchange DAG replication accross WAN (traffic not showing on port 64327

January 20, 2016, 2:19 pm

≫ Next: mailbox move from ex2010 to ex2013 still pointing to CAS Array 2010

≪ Previous: Exchange DAG cannot remove server

$

0

0

Hello Everyone

I need to do some sourced based routing on our Exchange replication traffic and from what I have read and what Get-DatabaseAvailabilityGroup mx-dag -Status | FL says all traffic should be on 64327 the default port.  When I monitor this traffic that is not what I actually see.  I see some traffic on this port but only a small percentage, like 40 mg out of 400 mg total traffic between nodes.  The rest of the ports are all over the place.  

Is there something I am supposed to do to ensure all the replication traffic is on a static port.

Thanks

---

mailbox move from ex2010 to ex2013 still pointing to CAS Array 2010

January 21, 2016, 2:17 pm

≫ Next: Restore emails from Exchange 2010 database to an Exchange 2013 mailbox

≪ Previous: Exchange DAG replication accross WAN (traffic not showing on port 64327

$

0

0

When I move a mbx which is in cache mode from ex2010 to exchange 2013 it moves successfully. When I open it on the target ex2013 server the Outlook shows it is DISCONNECTED. When I do the email config test and click on Test email Config that shows the connection to correct server (exchange 2013 rpcclientaccess) but when I click on the Connection Status it shows the CAS Array FQDN of the exchange 2010 from where the mailbox was moved.

If I create a new profile it works.  What is causing this? Why is still looking at the old CA Array of 2010.

Thanks in adv.

Restore emails from Exchange 2010 database to an Exchange 2013 mailbox

January 22, 2016, 8:57 am

≫ Next: Slooow mailbox move from Ex2010 SP3 RU10 to Exchaneg 2013 SP1 CU10

≪ Previous: mailbox move from ex2010 to ex2013 still pointing to CAS Array 2010

$

0

0

We have migrated completely to Exchange 2013 and decomissioned our 2010 exchange server. I have saved the databases from our 2010 server just incase we needed to restore anything from them. I now need to restore emails from a 2010 database and place them into a 2013 mailbox.  What are the steps to accomplish this?

Slooow mailbox move from Ex2010 SP3 RU10 to Exchaneg 2013 SP1 CU10

January 21, 2016, 1:44 pm

≫ Next: The inbound proxy probe failed 3 times over 15 minutes.

≪ Previous: Restore emails from Exchange 2010 database to an Exchange 2013 mailbox

$

0

0

Testing moves from 2010 to 2013 by creating new mailboxes with 2/3 items in them and they take around 1o mnts.

I even disable the MRS Throttling still no speed.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeResourceHealth

change the “MRS” REG_DWORD key from 1 to 0

Restarted the Exchange Mailbox Replication service

Also disabling indexing on the target DB doesn't help

looks like others having the issue too.  thanks in adv<o:p></o:p>

The inbound proxy probe failed 3 times over 15 minutes.

January 25, 2016, 1:15 am

≫ Next: Cluster without administrative access point one node status is down

≪ Previous: Slooow mailbox move from Ex2010 SP3 RU10 to Exchaneg 2013 SP1 CU10

$

0

0

env: exchange 2013 cu10, 2 CAS+MBX servers.

Getting error about inbound proxy probe failing, and  FEPActiveMonitoring is disabled.

The inbound proxy probe failed 3 times over 15 minutes.
No connection could be made because the target machine actively refused it 127.0.0.1:25
Probe Exception: 'System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:25
   at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port)
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SimpleSmtpClient.Connect(String server, Int32 port, Boolean disconnectIfConnected)
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1 cmd)
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1 cmd, ConnectionLostPoint connectionLostPoint)
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
   at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
   at System.Threading.Tasks.Task.Execute()'
Failure Context: 'No connection could be made because the target machine actively refused it 127.0.0.1:25'
Execution Context: ''
Probe Result Name: 'OnPremisesInboundProxy'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: ''

Also getting in other node:

The inbound proxy probe failed 3 times over 15 minutes.
Server 127.0.0.1 on port 25 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
.
Probe Exception: 'System.Exception: Server 127.0.0.1 on port 25 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
.
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Failure Context: 'Server 127.0.0.1 on port 25 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
.'
Execution Context: ''
Probe Result Name: 'OnPremisesInboundProxy'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '

Cluster without administrative access point one node status is down

January 24, 2016, 6:36 am

≫ Next: Redirect from Exchange 2010 to Exchange 2013 OWA

≪ Previous: The inbound proxy probe failed 3 times over 15 minutes.

$

0

0

Hi,

I have two Exchange 2013 sp1 CU9 servers in DAG.

 

One of my servers cannot connect to File Share Witness, although the network is ok.  My NMS didn’t catch any network issues.

If I run

Get-ClusterNode | ft name, nodeweight, state -AutoSize

It shows that server status is down.

In EventLog of this server I see:

"Cluster node <servername> could not to join the cluster because it failed to communicate over the network with any other node in the cluster. Verify the network connectivity and configuration of any network firewalls."

I didn't find problems with share and security rights on FSW. (exchange trusted subsystem is a member of local administrators group)

How Can I fix this issue and return server to cluster?

As far as cluster without administrative access point use Failover clustering MMC is not an option.  Are there any useful commands for troubleshooting and fixing my cluster problems?

 

Redirect from Exchange 2010 to Exchange 2013 OWA

January 25, 2016, 5:17 am

≫ Next: Exchange 2010 Database Copy Failed and Suspend

≪ Previous: Cluster without administrative access point one node status is down

$

0

0

This redirect was working fine ... nothing was changed to break this.  Since it works out of the box, any ideas where I should be looking for issues? thanks. 

Exchange 2010 Database Copy Failed and Suspend

January 12, 2016, 2:42 am

≫ Next: Exchange 2013 Disaster Recovery design

≪ Previous: Redirect from Exchange 2010 to Exchange 2013 OWA

$

0

0

Content index state: FailedAndSuspended" after moving the database path: "requesting index reseed" error message

---

Exchange 2013 Disaster Recovery design

January 26, 2016, 12:51 am

≫ Next: Exchange 2013 - DAG issues

≪ Previous: Exchange 2010 Database Copy Failed and Suspend

$

0

0

Hi,

In my environment i have plan to place 2 servers in DC and 1 server in secondary site. All 3 servers will in place in single DAG. Can you please suggest if this design is good. Also, can you please help me to with useful link for DC / DR configuration.

My criteria is to use single name space for DR servers.

Thanks.

Amit kumar

---

Amit

Exchange 2013 - DAG issues

January 26, 2016, 1:02 am

≫ Next: Exchange recovery fails

≪ Previous: Exchange 2013 Disaster Recovery design

$

0

0

Hi All,

I am currently building out a sandbox domain, prior to then building it again for the live environment in a month or two, I am keen to cluster / make full use of HA wherever possible, I have built out 2 exchange servers, both hosting a db - then configured them into a DAG.

The problem I am having is that currently if i simulate a failure (i.e. power down one of the two servers), I can see a few minutes later that the DAG has worked...and successfully failed both db's over to the remaining server that is up, however the outlook client sitting on my test machine, disconnects and completely fails to reconnect until the other server is powered back on.

The web client (https://server/owa) seems to work fine.

Any thoughts / suggestions would be greatly appreciated (in the meantime im going to go back to reading logs yay).

Kind regards

Xsag

Exchange recovery fails

January 26, 2016, 5:17 am

≫ Next: Exchange 2013 to Exchange 2010 OWA Proxy Not Working :-( Something went wrong"

≪ Previous: Exchange 2013 - DAG issues

$

0

0

Hello,

I've been trying to recover a lab Exchange 2013 server using the process at the following address;

https://technet.microsoft.com/en-us/library/dd876880%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

I have completed all the prerequisit steps, but after running the command - setup /m:ReceiverServer /IAcceptExchangeServerLicenseTerms - the setup doesn't complete and tell me to check the logs, which are displayed below.

[01/25/2016 22:08:31.0757] [0] **********************************************
[01/25/2016 22:08:31.0757] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
[01/25/2016 22:08:31.0757] [0] **********************************************
[01/25/2016 22:08:31.0757] [0] Local time zone: (UTC) Dublin, Edinburgh, Lisbon, London.
[01/25/2016 22:08:31.0757] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[01/25/2016 22:08:31.0757] [0] Setup version: 15.0.847.32.
[01/25/2016 22:08:31.0757] [0] Logged on user: UCANYWHERE\rpassey.
[01/25/2016 22:08:31.0772] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[01/25/2016 22:08:31.0818] [0] Command Line Parameter Name='mode', Value='RecoverServer'.
[01/25/2016 22:08:31.0818] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[01/25/2016 22:08:31.0818] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
[01/25/2016 22:08:32.0292] [0] RuntimeAssembly was started with the following command: '/m:RecoverServer /IAcceptExchangeServerLicenseTerms /sourcedir:D:"'.
[01/25/2016 22:08:32.0292] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[01/25/2016 22:08:32.0292] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[01/25/2016 22:08:32.0308] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[01/25/2016 22:08:32.0323] [0] Copying Files...
[01/25/2016 22:08:32.0338] [0] Starting copy from D:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[01/25/2016 22:08:38.0028] [0] Finished copy from D:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[01/25/2016 22:08:38.0043] [0] File copy complete. Setup will now collect additional information needed for installation.
[01/25/2016 22:08:38.0058] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[01/25/2016 22:08:43.0029] [0] Setup is choosing the domain controller to use
[01/25/2016 22:08:49.0651] [0] Setup is choosing a local domain controller...
[01/25/2016 22:08:53.0414] [0] Setup has chosen the local domain controller FE-DC-01.ucanywhere.net for initial queries
[01/25/2016 22:08:54.0576] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.  See the Exchange setup log for more information on this error.
[01/25/2016 22:08:54.0576] [0] [ERROR] Couldn't find the Enterprise Organization container.
[01/25/2016 22:08:54.0576] [0] Setup will use the domain controller ''.
[01/25/2016 22:08:54.0576] [0] Setup will use the global catalog ''.
[01/25/2016 22:08:54.0592] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ucanywhere,DC=net'.
[01/25/2016 22:08:54.0622] [0] No Exchange organization container was found for the organization. Message: 'Couldn't find the Enterprise Organization container.'.
[01/25/2016 22:08:54.0622] [0] For more information refer to http://go.microsoft.com/fwlink/p/?LinkId=257397.
[01/25/2016 22:08:54.0622] [0] Setup will search for an Exchange Server object for the local machine with name 'FE-EXCH-01'.
[01/25/2016 22:08:54.0699] [0] No Exchange Server with identity 'FE-EXCH-01' was found.
[01/25/2016 22:08:54.0714] [0] The following roles have been unpacked: 
[01/25/2016 22:08:54.0714] [0] The following datacenter roles are unpacked: 
[01/25/2016 22:08:54.0729] [0] The following roles are installed: 
[01/25/2016 22:08:54.0729] [0] The local server does not have any Exchange files installed.
[01/25/2016 22:08:54.0760] [0] Server Name=FE-EXCH-01
[01/25/2016 22:08:54.0806] [0] Setup will use the path 'D:\' for installing Exchange.
[01/25/2016 22:08:54.0821] [0] The installation mode is set to: 'DisasterRecovery'.
[01/25/2016 22:09:10.0115] [0] Exchange organization name is required for this mode.
[01/25/2016 22:09:10.0115] [0] Active Directory Initialization status : 'False'.
[01/25/2016 22:09:10.0115] [0] Schema Update Required Status : 'False'.
[01/25/2016 22:09:10.0115] [0] Organization Configuration Update Required Status : 'True'.
[01/25/2016 22:09:10.0115] [0] Domain Configuration Update Required Status : 'False'.
[01/25/2016 22:09:10.0238] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[01/25/2016 22:09:10.0299] [0] DisasterRecoveryModeDataHandler has 7 DataHandlers
[01/25/2016 22:09:10.0299] [0] RootDataHandler has 1 DataHandlers
[01/25/2016 22:09:10.0299] [0]      Languages
[01/25/2016 22:09:10.0345] [0] Validating options for the 0 requested roles
[01/25/2016 22:09:10.0421] [0] [ERROR] Can't specify installation mode because no Exchange Server is installed on this machine. Install Exchange Server.
[01/25/2016 22:09:10.0421] [0] [ERROR] Server is not found in Active Directory. Server must be present in Active Directory to recover.
[01/25/2016 22:09:10.0421] [0] CurrentResult console.ProcessRunInternal:90: 1
[01/25/2016 22:09:10.0452] [0] CurrentResult launcherbase.maincore:90: 1
[01/25/2016 22:09:10.0452] [0] CurrentResult console.startmain:52: 1
[01/25/2016 22:09:10.0467] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
[01/25/2016 22:09:10.0467] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[01/25/2016 22:09:10.0467] [0] CurrentResult main.run:235: 1
[01/25/2016 22:09:10.0467] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[01/25/2016 22:09:10.0467] [0] CurrentResult setupbase.maincore:396: 1
[01/25/2016 22:09:10.0467] [0] End of Setup
[01/25/2016 22:09:10.0467] [0] **********************************************

I have tried googling the the logs messages which arouse suspicion but I have't found anything which I'm confident which will work.

Any advice will be gratefully received.

Regards,

Rob 

Exchange 2013 to Exchange 2010 OWA Proxy Not Working :-( Something went wrong"

January 25, 2016, 5:17 am

≫ Next: Exchange 2013 CAS Server Windows NLB

≪ Previous: Exchange recovery fails

$

0

0

This redirect was working fine ... nothing was changed to break this.  Since it works out of the box, any ideas where I should be looking for issues? thanks. 

Exchange 2013 CAS Server Windows NLB

January 27, 2016, 4:30 am

≫ Next: DAG maintenance mode with passive copies

≪ Previous: Exchange 2013 to Exchange 2010 OWA Proxy Not Working :-( Something went wrong"

$

0

0

Hi.

I want to configure 2 new the Exchange 2013 CAS servers with Windows NLB.

But what is best practice regarding the use of Windows NLB?

My Network Experts says i cannot use unicast for NLB due to the current Network gear/configuration.

So then i want to know whats best practice regarding Exchange 2013 CAS Windows NLB with IGMP Multicast?

Do i need 2 Network adapters on each CAS server, and may both Network adapters register in dns and get enabled netbios setting?

Best Regards
Advizor

---

Advizor Hosting, Microsoft Partner

DAG maintenance mode with passive copies

January 27, 2016, 7:58 am

≫ Next: Custom Receive Connector 2013 - '550 5.7.1 Unable to relay'

≪ Previous: Exchange 2013 CAS Server Windows NLB

$

0

0

Hello everyone,  I had a question regarding the steps needed to take a DAG member offline for maintenance.  In our environment, we have 2 Exchange servers participating in a DAG, with 2 mailbox databases residing on each, with one active on one server, and the other database active on the other server.  See screenshot below.  To me it seems I would simply need to suspend the database on the server I will be performing maintenance on, and activate the copy on the other server.  Is this correct? Or do I need to follow step 6 in the 'Performing Maintenance on DAG Members' section of the whitepaper? I don't believe that would be necessary, since we have passive copies.

6.  To move all active databases currently hosted on the DAG member to other DAG members, runSet-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $True

Custom Receive Connector 2013 - '550 5.7.1 Unable to relay'

January 27, 2016, 10:17 am

≫ Next: Log Truncation Failure

≪ Previous: DAG maintenance mode with passive copies

$

0

0

I am using the VIP of my load balancer under the custom receive connector setting > scoping > Network Adapter Binding and the IP address of the sending matching under remote network settings. When the client send he gets ”unable to relay” 550.5.7.1

If I set the Network Adapter bindings to default then it works.

Any ideas? thanks

---

Log Truncation Failure

January 27, 2016, 4:19 pm

≫ Next: following error message : [ClientAccessServer=EXCHANGE,BackEndServer=exchange.domain.com,RequestId=58bfcb03-d4c8-4 2f6-b588-d08dc2b8c68c

≪ Previous: Custom Receive Connector 2013 - '550 5.7.1 Unable to relay'

$

0

0

I'm experiencing problems with log truncation failure on several databases of a 2 node DAG running Exchange 2013 CU10.  Each of the servers are virtual machines running an on esx host and the server operating system is 2012.

Backup Solution: Data Protection Manager.

DPM is completing the backup and reporting no failures, checkpoints for the databases are being updated, but logs are not being truncated.

Event logs from the Exchange server are showing two event id numbers in relation to VSS writers that are logged at the same time.  The event ID numbers are 2112 and 2024 with examples:

Event ID 2112:

The Microsoft Exchange Replication service VSS Writer instance [INSTANCE ID] failed with error code 80070015 when preparing for a backup of database 'MAILSTORE-00."

Event ID 2024:

The Microsoft Exchange Replication service VSS Writer (Instance [INSTANCE ID]) failed with error 80070015 when preparing for a backup.

The problem has occurred while the VSS writers were in a healthy state, but as of this posting one of the writers are currently not in a healthy state:

Writer name: 'Microsoft Exchange Writer'

   Writer Id: {WRITER ID}

   Writer Instance Id: {INSTANCE ID}

   State: [7] Failed

   Last error: Retryable error

 

I've been dealing with this for a bit now and I'm seeing a lot of mixed information.  Could anyone help me to further narrow down the issue or if you your have had experience with this problem please provide me with some additional information.

following error message : [ClientAccessServer=EXCHANGE,BackEndServer=exchange.domain.com,RequestId=58bfcb03-d4c8-4 2f6-b588-d08dc2b8c68c

January 20, 2016, 2:07 am

≫ Next: multiple internet high availability single server E2013

≪ Previous: Log Truncation Failure

$

0

0

Anyone had experienced this error on Exchange 2013 on Exchange powershell

VERBOSE: Connecting to Exchange.Domain.com
New-PSSession : [exchange.domain.com] Connecting to remote server exchange.domain.com failed with the
following error message : [ClientAccessServer=EXCHANGE,BackEndServer=exchange.domain.com,RequestId=58bfcb03-d4c8-4
2f6-b588-d08dc2b8c68c,TimeStamp=1/18/2016 6:47:22 AM]  For more information, see the about_Remote_Troubleshooting Help
topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed

multiple internet high availability single server E2013

January 28, 2016, 10:22 am

≫ Next: exchange 2013 mailbox points to ex2010 CAS Array

≪ Previous: following error message : [ClientAccessServer=EXCHANGE,BackEndServer=exchange.domain.com,RequestId=58bfcb03-d4c8-4 2f6-b588-d08dc2b8c68c

$

0

0

Hello,

i have an scenario with a single E2013 server and i need to have link resiliency, the question is what's the best way to configure this?.

The clients need to continue accessing the server using the same hostname(with a single cert)

On the SMTP side i have it covered as i can just add a new MX record and work with weights, and if the MX hostname isn't the same as the cert i don't really care mail will be delivered just the same falling back to smtp.(on DNS i just add the SPF to allow outgoing mail through other IPs)

The main problem is the OWA and outlook clients, since i have a sinlge hostname but multiple connections hwo do i deal with an outage?, do i need to buy a "HA" pack from a DNS provider that provides fast register change and monitoring(when main conn fails, it will redirect the dns hostname to the secondary ip)?

exchange 2013 mailbox points to ex2010 CAS Array

February 2, 2016, 9:56 am

≫ Next: Lag Copy's and DAG Maintenance

≪ Previous: multiple internet high availability single server E2013

$

0

0

Production. 

Exchange 2010 CAS array with nodes. with dag mailboxes.

2010 cas array called autodiscover.domain.local

Deployed first 1 ex2013 mbx and 1cas server in the environment.  configured everything. created a test mailbox on ex2013 mailbox server, fired up outook and it goes and connects to autodiscover.domain.local and cannot start outlook.

it should connect to new hardware based NLB name outlook.domain.local.  Using adsiedit I updated the ex2013 mailbox DB so it is not a part of autodiscover.domain.local.  

also ran the following on ex2013 cas:

Set-ClientAccessServer -Identity cas01 -AutodiscoverServiceInternalUri https://outlook.domain.local/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity "cas01\EWS (Default Web Site)" -InternalUrlhttps://outlook.domain.local/ews/exchange.asmx
Set-OABVirtualDirectory -Identity "cas01\oab (Default Web Site)" -InternalUrlhttps://outlook.domain.local/oab 

any thoughts???  thank u

Lag Copy's and DAG Maintenance

February 4, 2016, 12:17 pm

≫ Next: Test E-mail AutoConfiguration

≪ Previous: exchange 2013 mailbox points to ex2010 CAS Array

$

0

0

When we put our server into Maintenance mode, what will the LAG copy's do during this process? We are using the script to process putting the server into Maintenance mode but being new to LAg Copy's we do not want it to start to process the LAG into a active copy. Is there anything special we need to set or does it know based on the script not to start the process. Thank you!