We recently changed our public IP addresses, and now mobile email apps no longer work while away from the network. I updated our external DNS host to include two new A records for mail and autodiscover, so outgoing and incoming emails are coming through fine within the network. 

We use Exchange 2010 and Windows Server 2012; both are behind a SonicWall firewall. I have updated the local DNS records and the firewall accordingly. The X1 (primary) and X2 (backup) interfaces reflect the new IP address info. I also created new public_mail and private_mail address objects. 

I used the Microsoft Remote Connectivity Analyzer and found that autodiscover is not working (pasted below). It looks like port 443 is not listening/opening. However, I am not sure why. It is configured to open. Any help is much appreciated. Please let me know if you need more information regarding the problem.

Thanks,

Kevin

 The Microsoft Connectivity Analyzer is attempting to test Autodiscover for k Testing Autodiscover 
failed.
Additional Details Elapsed Time: 5071 ms. Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method. Additional Details
Elapsed Time: 5071 ms.
Test Steps
Attempting to test potential Autodiscover URL https://westm                   
.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed.
Additional Details Elapsed Time: 3303 ms.
Test Steps
Attempting to resolve the host name westm                   .com in DNS. The host name resolved 
successfully.
Additional Details
IP addresses returned: 104. Elapsed Time: 38 ms.
by GoDaddy
Testing TCP port 443 on host westminstervillagein.com to ensure it's listening and open. The port 
was opened successfully.
Additional Details Elapsed Time: 162 ms.
Testing the SSL certificate to make sure it's valid. The certificate passed all validation 
requirements.
Additional Details Elapsed Time: 517 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server 
westm                   .com on p The Microsoft Connectivity Analyzer successfully obtained the 
remote SSL certificate.

Additional Details
Validating the certificate name.
The certificate name was validated successfully. Additional Details
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.

Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate 
CN=west                      .com. One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=DST Root CA 
X3, O=Digital Signatur Elapsed Time: 29 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows. Potential 
compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root 
Certificate Update functionality Update. Your certificate may not be trusted on Windows if the 
"Update Root Certificates" feature isn't enabled.
Elapsed Time: 1 ms.
Testing the certificate date to confirm the certificate is valid. Date validation passed. The 
certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 7/12/2019 8:26:20 PM, NotAfter = 10/10/2019 8:26:20 PM 
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication. Client certificate 
authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured. Elapsed Time: 1252 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs. Autodiscover 
settings weren't obtained when the Autodiscover POST request was sent.
Additional Details


7/28/2019                                                                                          
  Microsoft Remote Connectivity Analyzer
Elapsed Time: 1332 ms. Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL 
https://west.com:443/Autodiscover/Autodiscover.xml for user  one@westm.com.
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response. Additional 
Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
HTTP Response Headers:
Transfer-Encoding: chunked Connection: keep-alive Keep-Alive: timeout=20
Vary: Accept-Encoding,Accept-Encoding
Link: <https://westminstervillagein.com/wp-json/>; rel="https://api.w.org/" WPE-Backend: apache
Cache-Control: no-cache, must-revalidate, max-age=0 Content-Type: text/html; charset=UTF-8
Date: Sun, 28 Jul 2019 22:54:49 GMT
Expires: Wed, 11 Jan 1984 05:00:00 GMT Server: nginx
Elapsed Time: 1331 ms.
Attempting to test potential Autodiscover URL https://autodiscover.west                      
.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed.
Additional Details Elapsed Time: 1385 ms.
Test Steps
Attempting to resolve the host name autodiscover.westm                   .com in DNS. The host name 
resolved successfully.
Additional Details
IP addresses returned: 216.2 Elapsed Time: 26 ms.
Testing TCP port 443 on host autodiscover.westm                   .com to ensure it's listening and 
open. The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 1358 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to 
contact Autodiscover using the HTTP Redirect method failed.
Additional Details Elapsed Time: 367 ms.
Test Steps
Attempting to resolve the host name autodiscover.westm                  n.com in DNS. The host name 
resolved successfully.
Additional Details
IP addresses returned: 216.2 Elapsed Time: 12 ms.
Testing TCP port 80 on host autodiscover.westm                   .com to ensure it's listening and 
open. The port was opened successfully.
Additional Details Elapsed Time: 130 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.westm                   .com 
for an HTTP redirect to the Autodiscov The Microsoft Connectivity Analyzer failed to get an HTTP 
redirect response for Autodiscover.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body 
of the response: You do to view this directory or page.
HTTP Response Headers:
Content-Length: 58 Content-Type: text/html
Date: Sun, 28 Jul 2019 22:54:51 GMT
Server: Microsoft-IIS/8.5 X-Powered-By: ASP.NET Elapsed Time: 223 ms.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV 
redirect method. Additional Details
Elapsed Time: 9 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.westm                   .com in DNS. The 
Autodiscover SRV record wasn't found in DNS.
https://testconnectivity.microsoft.com/#&&6bcC5mCLIouoADw0Cig+2vSiG8pTcCTQJcd+stP++aHikM5dxPV+EL3774
yp3duvmVT5ySfoC5a991pnFqE…     2/3

7/28/2019                                                                                          
  Microsoft Remote Connectivity Analyzer
https://testconnectivity.microsoft.com/#&&6bcC5mCLIouoADw0Cig+2vSiG8pTcCTQJcd+stP++aHikM5dxPV+EL3774
yp3duvmVT5ySfoC5a991pnFqE…     3/3
Sta
Tell me more about this issue and how to resolve it Additional Details
Elapsed Time: 9 ms.
Checking if there is an autodiscover CNAME record in DNS for your domain 'west                      
.com' for Office 365. Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in 
Office 365, you can ignore this warning.
Tell me more about this issue and how to resolve it Additional Details
There is no Autodiscover CNAME record for your domain 'westmi                       m'.

Hi

I have exchange 2010

I'm trying to delete old ActiveSync Device to user (using EMC)but it say that it "cannot be found"

any idea?

I think that in the past I delete the device object from AD 

Hello all,

I was wondering what the logging file size estimation for a year would be for a 2016 Exchange server with 300 Mailboxes and around maybe 50 Messages per user a day. With high times being 8-4 With maybe 70 or so users being very active, I wouldn't say all 300 users send the 50 per day maybe just the 70 highly active. We have some users that may send twice a week, any who I am moving from Exchange 2010 fairly soon. With two servers in the DAG and 5 DB's in the server, my CIO wants to know if we could supply the server with the storage to hold our log files for a year. While the excel sheet that calculates is useful it only shows storage of logs per Server, DAG, Environment not per day, week, month, year total unless there is a field I am overlooking.

Thanks!  

Hi,

After a migration of Exchange 2010 to 2016, i have the following error:

[08/01/2019 10:46:46.0737] [1] Setup failed previously while performing the action Uninstall.  Looking for the failed task with ID ClientAccessOwaComponent___5effe7121e1740c083904cc189687464.
[08/01/2019 10:46:46.0737] [1] 71 tasks were found to execute.
[08/01/2019 10:46:46.0737] [1] Processing component 'OWA Configuration' (Installing/Removing Outlook Web App Component.).
[08/01/2019 10:46:46.0737] [1] Executing:
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          Start-SetupProcess -Name "$CommandAppCmd" -args "uninstall module exppw";
       
[08/01/2019 10:46:46.0799] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'MAIL15.domain.local', Preferred Global Catalog: 'MAIL15.domain.local', Preferred Domain Controllers: '{ MAIL15.domain.local }'
[08/01/2019 10:46:46.0799] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\System32\inetsrv\appcmd.exe' -Args:'uninstall module exppw'
[08/01/2019 10:46:46.0815] [2] Starting: C:\Windows\System32\inetsrv\appcmd.exe with arguments: uninstall module exppw
[08/01/2019 10:46:47.0298] [2] Process standard output: Failed to initialize command processor: Failed to initialize command object configuration. (HRESULT=c00ce558).

[08/01/2019 10:46:47.0298] [2] Process standard error:
[08/01/2019 10:46:47.0345] [2] [ERROR] Unexpected Error
[08/01/2019 10:46:47.0345] [2] [ERROR] Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [2] Ending processing Start-SetupProcess
[08/01/2019 10:46:47.0345] [1] The following 1 error(s) occurred during task execution:
[08/01/2019 10:46:47.0345] [1] 0.  ErrorRecord: Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [1] [ERROR] The following error was generated when "$error.Clear();
          $CommandAppCmd = join-path $env:SystemRoot System32\inetsrv\appcmd.exe;
          Start-SetupProcess -Name "$CommandAppCmd" -args "uninstall module exppw";
        " was run: "Process execution failed with exit code -1072896680.".
[08/01/2019 10:46:47.0345] [1] [ERROR] Process execution failed with exit code -1072896680.
[08/01/2019 10:46:47.0345] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponent___5effe7121e1740c083904cc189687464 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[08/01/2019 10:46:47.0345] [1] Setup is stopping now because of one or more critical errors.

I already those soltutions:

1. Go into IIS manager
2. go to the servername (Global configuration)
3. Go into Modules
4. Lookfor exppw - it might exist, just remove it :-)
5. Select "Configure NAtive Module"
6. In the dialog - select Register, type "exppw" as Name
7. Click the browse button for Path, and browse to f.ek. "c:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\Auth\" and Select exppw.dll
8. Press okey and okey - the exppw should be in the list Again, for Exchange Setup to remove :-)
9. re-run setup to uninstall Exchange 2010, and it should now run without problems.

And tried with another  file :C:\Windows\System32\inetsrv\config\applicationHost.config

Could you please give me some help?

Regards,

DB

Hi, it possible use powershell to get the space occupied by receveid emails between 2 dates?

Thaks

Hi,

We're moving mailboxes from an AD site to mailbox servers on another site and this will take about weeks of time.

OAW and OWA are published via TMG and point to a cas server in current site to all work well.

Normally when some users are moved to mailbox on new site with a new Non-Internet facing (better to say not published by TMG) they cannot connect from outside. As I said this will take about a month to move all the mailboxes so I'd like this:

When a user tries to connect from outside it will go to current CAS and mailbox server whose mailbox may be or may not be there. If there so .. serve and have fun but if his/her mailbox was not found on mailbox servers on that site (It may be moved) then I want the fallback from exchange side to proxy the OWA/OAW and ActiveSync requests to the CAS on the other site.

Is this possible?

Thanks in advance.

Hi All,

I have an issue regarding database mounting.

in my case, i have 2 mailbox servers (enterprise edition) and 1 CAS Server (Standard Edition).

when i create new data base e.g. DB01 it allows me to do that, but when i simply click to "mount this data base" it shows below error. please suggest what can i do?

Failed to mount database "DB1". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954) Diagnostic context: Lid: 65256 Lid: 10722 StoreEc: 0x8004060E Lid: 1494 ---- Remote Context Beg ---- Lid: 37952 dwParam: 0x4637086 Lid: 39576 StoreEc: 0x977 Lid: 35200 dwParam: 0x2E20 Lid: 58864 StoreEc: 0x8004060E Lid: 43248 StoreEc: 0x8004060E Lid: 35388 StoreEc: 0x8004060E Lid: 54336 dwParam: 0x4637096 Lid: 35200 dwParam: 0x2E20 Lid: 1750 ---- Remote Context End ---- Lid: 1047 StoreEc: 0x8004060E [Database: DB1, Server: .......

Appreciate yours prompt response 

Regards, Sarfraz Aslam

Hi there,

since a month, we have big trouble to sync shared calender. User-A makes an entrie in User-B calender, but User-B cant see it.

In OWA all looks fine. 

I have try this methodes:

- disable Cache Mode on all Clients

- run New-MailboxRepairRequest without no results

the it-environment are:

- Exchange 2010 up to date as a virtual maschine

- Outlook 2016 from O365 Pro

Greetings

Rico

Hi, 

Issue with adding forest to 2010 consol after MFA is enabled. 

Sorry for posting this in a Exchange 2013 forum, but i couldn't find anything related to 2010 :) Please do delete or move if this is the wrong place. 

After MFA was enabled the forest disappeared from the 2010 consol. Adding it give error message with authentication failure. 

I found that the Microsoft Exchange Online Powershell Module should solve this (In Exchange 2013 the module is downloaded from the server - hybrid page) 

Since this is an older Exchange version and older Powershell i am afraid that the Exchange Management Shell will stop working due to changing the authentication. 

Does anyone have any inputs or can advise ?

I have been told by one of our program suppliers that my exchange server is not configured correctly to accept mail from their program. I have no ideal what is wrong. I have sent a e-mail from the iseries to myself and this is what I see in the receive connector log  called iseries. I also send to a gmail account and they accept the mail. So i have tested it both externally and internally I say it works. 

2019-08-07T19:52:49.027Z,exchange\iseries,08D703E7C2BBB80E,0,192.168.3.12:25,192.168.3.101:30420,+,,

2019-08-07T19:52:49.027Z,exchange\iseries,08D703E7C2BBB80E,1,192.168.3.12:25,192.168.3.101:30420,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions

2019-08-07T19:52:49.027Z,exchange\iseries,08D703E7C2BBB80E,2,192.168.3.12:25,192.168.3.101:30420,>,"220 EXCHANGE.smokylakecounty.ab.ca Microsoft ESMTP MAIL Service ready at Wed, 7 Aug 2019 13:52:48 -0600",

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,3,192.168.3.12:25,192.168.3.101:30420,<,EHLO CNTYSMKL.SMOKYLAKECOUNTY.AB.CA,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,4,192.168.3.12:25,192.168.3.101:30420,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,5,192.168.3.12:25,192.168.3.101:30420,>,250-EXCHANGE.smokylakecounty.ab.ca Hello [192.168.3.101],

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,6,192.168.3.12:25,192.168.3.101:30420,>,250-SIZE 36700160,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,7,192.168.3.12:25,192.168.3.101:30420,>,250-PIPELINING,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,8,192.168.3.12:25,192.168.3.101:30420,>,250-DSN,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,9,192.168.3.12:25,192.168.3.101:30420,>,250-ENHANCEDSTATUSCODES,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,10,192.168.3.12:25,192.168.3.101:30420,>,250-8BITMIME,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,11,192.168.3.12:25,192.168.3.101:30420,>,250-BINARYMIME,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,12,192.168.3.12:25,192.168.3.101:30420,>,250 CHUNKING,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,13,192.168.3.12:25,192.168.3.101:30420,<,MAIL FROM:<BARB@CNTYSMKL.SMOKYLAKECOUNTY.AB.CA>,

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,14,192.168.3.12:25,192.168.3.101:30420,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,15,192.168.3.12:25,192.168.3.101:30420,*,08D703E7C2BBB80E;2019-08-07T19:52:49.027Z;1,receiving message

2019-08-07T19:52:49.043Z,exchange\iseries,08D703E7C2BBB80E,16,192.168.3.12:25,192.168.3.101:30420,>,250 2.1.0 Sender OK,

2019-08-07T19:52:49.058Z,exchange\iseries,08D703E7C2BBB80E,17,192.168.3.12:25,192.168.3.101:30420,<,RCPT TO:<brian@smokylakecounty.ab.ca>,

2019-08-07T19:52:49.058Z,exchange\iseries,08D703E7C2BBB80E,18,192.168.3.12:25,192.168.3.101:30420,>,250 2.1.5 Recipient OK,

2019-08-07T19:52:49.058Z,exchange\iseries,08D703E7C2BBB80E,19,192.168.3.12:25,192.168.3.101:30420,<,DATA,

2019-08-07T19:52:49.058Z,exchange\iseries,08D703E7C2BBB80E,20,192.168.3.12:25,192.168.3.101:30420,>,354 Start mail input; end with <CRLF>.<CRLF>,

2019-08-07T19:52:49.058Z,exchange\iseries,08D703E7C2BBB80E,21,192.168.3.12:25,192.168.3.101:30420,*,,Proxy destination(s) obtained from OnProxyInboundMessage event

2019-08-07T19:52:49.933Z,exchange\iseries,08D703E7C2BBB80E,22,192.168.3.12:25,192.168.3.101:30420,>,"250 2.6.0 <1290816752.1565206223527.JavaMail.qspljob@CNTYSMKL.SMOKYLAKECOUNTY.AB.CA> [InternalId=227384158584923, Hostname=exchange.smokylakecounty.ab.ca] Queued mail for delivery",

Exchange 2010 SP3 UR4 (yes, SP3 UR4!) single-server using EOP as its smarthost.

This server has a problem...it fails to install UR's, which is why it's still on UR4. So we're in the process of migrating to a new single-server EX2010 SP3 UR29 so we can then set up hybrid Exchange and migrate to Office 365 before end-of-support.

There's no EX2010-to-EX2010 migration guidance that I could find. I was referred on another thread here to https://docs.microsoft.com/en-us/exchange/checklist-upgrade-from-exchange-2010-exchange-2013-help, and instructed to do the EX2013-side tasks using EX2010 MMC/PowerShell equivalents and I'd be fine.

So I got as far as step 14, Configure service connection point, which sends youhere--

https://docs.microsoft.com/en-us/exchange/exchange-2013-client-access-server-configuration-exchange-2013-help

--matching config of the old EX2010 throughout, and users started reporting that outbound emails sent in the last 2 hours (a bit after I started configuring the new EX2010) were not being received.

I remembered then that the perimeter firewall blocks outbound SMTP for all internal IPs except that of the mail server. So I modified that rule to add the IP of the new EX2010 to the allow list, thinking it would solve the problem. I'm not sure that it didn't, honestly, but it was late in the day and I couldn't take any chances because I wouldn't be there next day, so I shut down the new EX2010. A test message sent after the shutdown was delivered timely. I expected a flood of outbound messages queued during the outage to be delivered, possibly after a short delay...but they were not. They all arrived in a rush almost 3.5 hours later, and 5.5 hours after they were sent.

Message Tracking Logs on the old EX2010 show they were sent off to EOP as they were received by the server (i.e, up to 5.5 hours after they were sent) and all about the same time that I received them, so that starts to sound like a CAS problem. EOP message traces show "There was a delay of 195 minutes prior to being received by Office 365," but shows no delays after receipt and before sending on to my server (on O365, and also no delay in the O365 trace). The delay for the particular message was actually longer than 195 seconds/3.6 hours...it was about 5.5 hours. So I don't understand that, either.

The new EX2010 has been shut down ever since, and there have been no further mail flow problems during that time.

But I don't really understand what happened, or if the firewall rule blocking outbound SMTP explains all the symptoms--

• The firewall blocked outbound SMTP for about 2 hours.
• There might have been outbound emails numbering in the low 100s queued--I should have looked at the queues at the time but I didn't--but with a 30Mbps upstream, the queues should have cleared fairly quickly...minutes, not hours. As it was, 8 or 10 queued emails for my external mailbox were delivered within 2 minutes of each other.
• Nothing I know of would have prevented the old mail server from sending messages at any time, but nothing went out. App logs on the old EX2010 showed nothing unusual.

Ultimately, I'll boot up the new server after hours and do some mail flow tests. Before doing that though, if possible, I'd like to understand what happened so I have some idea if this was just caused by the outbound firewall rule, and therefore likely to be resolved at this time.

Is there a way to speed the process of having "Manage Full Access Permission" take effect? That is, when I add an Exchange user to the "Manage Full Access Permission" list on the Exchange 2010 server, it can take five to 10 minutes before the newly-managed mailbox appears in the folder list for the user granted the full access permission to the mailbox.

I am not sure if this is even primarily an Outlook question or an Exchange question.

We are in upgradation process from Exchange 2010 to Exchange 2013, after the installation of Exchange 2013 in an organization, there are 02 default Offline address book available in Exchange 2010 EMC where Default Offline Address Book 2010 (Exch2013) is default. Due to this existing outlook 2010 users not able to see new users in GAL that are created in Exchange 2010. Till that upgradation, i want to use my Default Offline Address Book 2010 as default.

After click on "set as default" on exchange 2010 address book, it gives an error that property "IsDefault" is read only

Regards,

Regards, Sarfraz Aslam

On Exchange 2013. when we do anything using EMC. It shows below mentioned error. Also same error while using cmdlt

Active Directory operation failed. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150BB9, problem 4003 (INSUFF_ACCESS_RIGHTS), data

All rights on user and OUs have already been checked. User has the following rights

Administrators

Domains Admins

Domain Users

Enterprise Admins

Exchange Organisation Administration

Early response is highly appreciated 

Hi,

while setting up outlook for some clients, their mailboxes had been in a Database Say DB1

So outlook has set this as the exchange server

Now they are moved to another Database in another site with another CAS server, So, the CAS server for the databases was updated using set-mailboxdatabase -rpcclientaccessarray to the new CAS.

But thus setting is not reflected (changed, updated anything ) in clients outlook. How this should be handled?

Recreating outlook profile is a baaad idea cause there are too many of them.

And BTW, how and where in outlook 2016 we can see or change exchange server settings?

In outlook 2010 it can be seen in email accounts and can be changed there. In 2013 seen there but no change possible and in 2016 I cannot even find where and what is the server set let alone changing it. It just displays username.

Regards

Hi All,

I have one mailbox database for 2 nodes: Mail2, Mail3 in DAG.

Now, mail2 is die. I only use one Mail3 to work. And, how i can remove mail2 out of mailboxdatabase copies ?

I would like to use one Mailbox database for mail3.

Thanks,

Tony

Dears,

We've Exchange 2010 in our environment. We've set multiple SMTP domains on our Exchange. Issue is with only domain, when users try to set Autoreply for Out of office, it gives an error " Your autoreply replies setting cannot be displayed, server is currently unavailable".

Appreciate your assistance to fix this issue.

Regards,

Ammar