Hi All,

We have on on-prem. Exchange server 2013 server, with DAG configured on the same. when we assigning POP and IMAP services on wildcard certificate it showing below error.

"This certificate with thumbprint ********* and subject '*.yourdomain.com' cannot used for POP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-POPSettings to set X509CertificateName to the FQDN of the service."

due to this we are facing certificate error popups at client end where we have configured POP and Imap a/c.

Please help us to resolve this issue.

Regards, Prashant

I have an Exchange 2013 installation started with SP1 that I have kept updated installing the Cumulative Updates when they were released.

I have observed that after each CU installation the C: free space (Exchange is installed on C:) was less then before. So I searched in the Exchange install directory and I have found a lot of sub-directories named with an Exchange build number, expecially under the ClientAccess install dir and the OWA subdir.

For instance, under C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa I have many folders named "15.0.995.28", "15.0.995.32", "15.0.1044.21", "15.0.1044.27", "15.0.1076.2", "15.0.1076.10".

The C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem directory has the same subfolders and is consuming a lot of disk space.

As I could understand, the CU setup should remove the older files but it seems that it does not and keeps older version in these directories. I have tried installing a fresh Exchange 2013 CU8 on a new server and these directories are not present.

The question is: is that correct?

And: can I safely delete the older versions folders?

Thanks

dmg

1. What is the tool for migration from existing IBM Domino to Exchange ?  Any idea the time to migrate the existing email server with 500GB  (in hours) ? 

2. Are we still able to send email to our members/staffs from our portal which using SMTP TLS ? 

3. Do we allow to create the Group email address by admin and is there any charges ? e.g  technicalsupport@domain.com (which consists of engineer@domain.com, support@domain.com, tech@domain.com) 

4. Can single user with 2 domain ? Do you charges 2 user id or 1 user id ? e.g john@domain.com and john@domainallias.com 

5. Some email account already archived their IBM Domino email (.nsf) to local PC, do we able to put back to exchange or any tool to convert to exchange for them to view back the existing archive email ? 

Is there any 3rd party service that help us to migrate domino to exchange? Can introduce to us?

Hi all,

Do i need to rerun the HCW each time I remove an on premise server or can I do it when I am down to the lat one?

as ever, thanks for your help

SIAH

Hello!

A few months ago we configured an on premise Exchange 2019 server and then migrated our mailboxes to a 2013 instance(2013 also on premise).

Our 2013 server has been physically powered off for three months. I would like to understand the steps i need to officially decommission it, remove any connections, and uninstall it. My goal would be to then raise the functional level of our domain to 2016 version.

Can somebody please help me understand what the steps are to decommission this 2013 instance?

thanks!

current exch version:

I'm updating to CU23, and it fails Mailbox Role - Below is the error. And Below that is the snip's from the setuplogs.

Strangely this server doesn't even have an F:

I've been googling this, and not finding the answer. Any help would be appreciated.

Error:
The following error was generated when "$error.Clear(); 
	buildToBuildUpgrade-ExsetdataAtom -AtomName SystemAttendant -DomainController $RoleDomainController" was run: "Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685616' and message 'The file or directory is corrupted and unreadable.'.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
   at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.BuildToBuildUpgradeAtom(AtomID atomID)
   at Microsoft.Exchange.Management.Deployment.BuildToBuildUpgradeExsetdataAtom.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

[11/25/2019 22:13:09.0610] [2] Entering ScSetVersionOnAddressTypeObj
[11/25/2019 22:13:10.0157] [2]  ScFindFileInDirTree (f:\15.00.1497\sources\dev\admin\src\libs\base\basemisc.cxx:1347)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2]  ScFindFileInDirTree (f:\15.00.1497\sources\dev\admin\src\libs\base\basemisc.cxx:1347)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2]  ScFindFileInDirTree (f:\15.00.1497\sources\dev\admin\src\libs\base\basemisc.cxx:1347)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2]  ScFindFileInDirTree (f:\15.00.1497\sources\dev\admin\src\libs\base\basemisc.cxx:1347)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2]  ScSetVersionOnAddressTypeObj (f:\15.00.1497\sources\dev\admin\src\libs\exsetup\dsmisc.cxx:1008)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2] Leaving ScSetVersionOnAddressTypeObj
[11/25/2019 22:13:10.0157] [2]  CAtomSystemAttendant::ScSetAddressTypes (f:\15.00.1497\sources\dev\admin\src\udog\exsetdata\components\server\a_systemattendant.cxx:246)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2]  CAtomSystemAttendant::ScReinstall (f:\15.00.1497\sources\dev\admin\src\udog\exsetdata\components\server\a_systemattendant.cxx:317)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2] mode = 'Reinstall' (61955) CBaseAtom::ScSetup (f:\15.00.1497\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:537)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2]  ScSetupAtom (f:\15.00.1497\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:877)
           Error code 0XC0070570 (1392): The file or directory is corrupted and unreadable.
[11/25/2019 22:13:10.0157] [2] Leaving ScSetupAtom
[11/25/2019 22:13:10.0157] [2] [ERROR] An error occurred with error code '3221685616' and message 'The file or directory is corrupted and unreadable.'.
[11/25/2019 22:13:10.0157] [2] [ERROR] An error occurred with error code '3221685616' and message 'The file or directory is corrupted and unreadable.'.
[11/25/2019 22:13:10.0157] [1] The following 1 error(s) occurred during task execution:
[11/25/2019 22:13:10.0157] [1] 0.  ErrorRecord: An error occurred with error code '3221685616' and message 'The file or directory is corrupted and unreadable.'.
[11/25/2019 22:13:10.0157] [1] 0.  ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685616' and message 'The file or directory is corrupted and unreadable.'.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)

Good afternoon,

I've got my exchange all working well for our business, however some users keep having pop ups appear looking to get them to log into there email. When they enter there active directory logins it will carry on popping up but give them access to there emails, so at present they just ignore it. The other issue is they get pop up its not accepted, but they click need password and it connects them to exchange.

I have tried flushing out there credential manager to see if that solves the problem, but not had any luck. Following that most staff are on a mix between of versions between Office 2013 and 2016 86x. 

The old exchange is still in the environment at present and not decommissioned but i am worried now if it becomes decommissioned will this break further mailboxes? All staff have been migrated to the new exchange on a new edb. I believe it could be due to conflicting with the old exchange but to my knowledge everything is now pointing to the new exchange. 

Are there any checks I can do in order to further investigate this? The exchange setup is in split brain DNS, with outlook anywhere setup, and using DNS shared internal and external "remote.Businessname.co.uk". 

Any help would be greatly appreciated. 

Many Thanks,

Steven Parsons

We are moving mailboxes from Exchange 2010 to Exchange 2013. We have a long running mailbox migration that we need to pause during working hours so it doesn't affect users. When I resume it, nothing appears to happen. It did work, but for the last couple of days it has not made any progress. We have other migrations we are treating in this way and they work fine. I have tried restarting the MRS service on the two servers involved in the move. We normally stop the batch through the EAC, but I have tried resuming the request through PowerShell and that does not appear to help either. Below is a snippet of the log sowing the activity for the last two days.

I have 1 Exchange 2013 server which is being replaced with 2016 CU12. After successfully completing the installation wizard I tried to login to the ECP but I get HTTP 500 error. I can login to the 2013 ECP and see the new server.

I've reset the virtual directories and reset forms authentication but that does have any affect on it.

I recently updated to the CU 23 update, and mail is flowing correctly, but users cannot update their out of office from Outlook 2013 internally, and you see a Mailtips error when sending a new message.

When I connect to my ECP, browse to recipients, mailboxes, and try to add a new user I see the following in a yellow bar to the right side of any highlighted user:

If I click the +, User Mailbox, and browse I get the same error.

Several commands in Exchange Console give the following error (including trying to add a user in the console)

VERBOSE: Connecting to EMAIL.SERVER.local.
VERBOSE: Connected to EMAIL.SERVER.local.
[PS] C:\Windows\system32>get-mailbox -arbitration
WARNING: An unexpected error has occurred and a Watson dump is being generated: Method not found:
'Microsoft.Exchange.VariantConfiguration.IFeature ADSettingsIni.get_DisplayNameMustContainReadableCharacter()'.
Method not found: 'Microsoft.Exchange.VariantConfiguration.IFeature
ADSettingsIni.get_DisplayNameMustContainReadableCharacter()'.
    + CategoryInfo          : NotSpecified: (:) [Get-Mailbox], MissingMethodException
    + FullyQualifiedErrorId : System.MissingMethodException,Microsoft.Exchange.Management.RecipientTasks.GetMailbox
    + PSComputerName        : email.SERVER.local

[PS] C:\Windows\system32>

Hi, 

We are in the middle of a migration from Exchange 2010 to 2013, and they are currently coexisting on the network. We are currently migrating mailbox in batch of 15-20 users and for the first 100 or so, everything was fine, but we encountered an issue and after a few days of troubleshooting, decided to ask for help. So here’s the issue :

Only some user cannot open total control mailbox. Every time the user open their Outlook for the first time, Outlook ask for their credentials for the additional mailbox, and in some cases, the credential windows won’t disappear. The user can send and receive message from his own account, but if the user wants to access the Full Access mailbox added through the EMC mailbox delegation, this message shows up : “Cannot expand the folder. The set of folders cannot be opened. Microsoft exchange is not available. Either there are network problems or the exchange computer is down for maintenance.” . The user can have access to the calendar and the contacts of the attached mailbox but the inbox is unavailable.

Here’s our configuration and what we’ve actually tried to solve this issue :

General configuration :

• All Exchange 2013’s internal and external virtual directory are in the same format : https://ourserverfqdn/ExchangeDirectoryPathofTheVirtualDirectoryORServiceLikeCAS
• Those addresses are different from Exchange 2010
• We have Autodiscover DNS records for both of our Exchange server
• DNS also have the server’s FQDN
• Our users use Office Pro 2010 with the latest updates
• All the mailbox transfers from one Database to the other are clear (no errors)

What we’ve tried up to this point :

• Remove and add back the rights with the ECP
• Tried to remove the access and add them back using PowerShell
• Delete the Outlook profile and create a new one
• Adding the Outlook account directly with the credential in the account parameters
• Adding the Outlook account in the profile advanced settings
• Uninstalling Office, then reinstalling it
• Replacing the actual computer
  • This “solution” actually works, with exactly the same specs and Office Pro 2010 updated (only works sometime. All other times, we need to replace Office 2010 with Office 2013 on the new computer). But replacing every user computer with this issue is only a way to avoid the actual issue.
• Uninstalling Office 2010 and go with Office 2013
  • This “solution” actually works as well (only sometimes. All other times we need to replace the computer itself), but we do not have enough licence to move every user to this version (due to an program we use, every user with access to it must be on the same Excel/Word/Outlook versions, or else it won’t work, which represents, well, all our users) and to avoid the issue once again.

So as of now, as a temporary measure, users with 1 or 2 Full Access mailbox, have access through the webpage, but some of them have multiple (over 5), and this temporary measure isn’t very effective.

Is there something we missed, or any configuration we could try to resolve this issue ?

Thanks

Hello,

i´m migrating our exchange 2010 standalone server to exchange 2013 (two servers with mailbox and cas role and dag).

Last week i found the get-healthreport command. So i execute this command on both server to check if my installations are correct.

But i found on both server that the network Healthset is unhealthy. Also i found in the Microsoft eventviewer this error.

receive side scaling should be activated

So i ask Dr. Google but i found nothing to fix my problem. I tried to disable netsh int tcp set global chimney=disabled

and netsh int tcp set global rss=disabled  and enabled SR-IOV for the virtual network card.

But nothing helped.

Both servers run as vm on a hyer-v host. The server and hyper-v host run with Windows 2012R2.

So, have somebody an idea?

Matias

I migrated public folders to Exchange Online. So far everything worked.
When doing the post-Tasks and cleaning up the Exchange 2013 server I ran into an issue.

I tried to delete the public folder mailbox and recieved the following error:

"No active public folder mailboxes were found. This happens when no public folder mailboxes are provisioned or they are provisioned in 'HoldForMigration' mode. If you're not currently performing a migration, create a public folder mailbox."

How can I delete the the public folder mailbox?

Some values from the get-organozationConfig (onPremise) which may be helpful

Thanks

Hi,

I'm in the middle of preparing AD and extending the schema for an Exchange server 2013 installation and I'm getting the bellow error. My question are, what type of key do I have to create, on which server(the one I'm using to prepare the organization) and what value should I add? Is this even supported?

Event ID:     2866

Task Category: Security

Level:        Error

Keywords:     Classic

User:         <redacted>

Computer:     <domain controller>

Description:

While logging audit events for the following object, the directory service reached the maximum number of audit events that could be cached in memory at any given time. As a result of reaching this limit, the operation was aborted.

Maximum number of audit events that can be cached: 17000

Distinguished name of object:

CN=View-Only Configuration,CN=Roles,CN=RBAC,CN=<company>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain>,DC=ca

Generally this occurs if there are a large number of changes being performed on attributes that require auditing. An example of such an operation could be deleting the membership of a large group, where the ‘member’ attribute is being audited.

Additional Data From the Audit Event Attribute name or old distinguished name:

msExchRoleEntries

Attribute value or new distinguished name:

c,Get-PublicFolderClientPermission.

Microsoft.Exchange.Management.PowerShell.E2010,Debug,DomainController,ErrorAction,

ErrorVariable,Identity,OutBuffer,OutVariable,Server,User,Verbose,WarningAction,WarningVariable

User Action

(1) Check that an excessive number of object creation, modification, move, rename or undelete operations are not being performed.

(2) Check that an excessive amount of auditing is not enabled. For example, confirm that auditing is not configured for more attributes than is necessary.

(3) If necessary, increase the size of the audit queue by increasing the ‘Maximum Audit Queue Size’ registry parameter.

Thank you.

Hi,

Currently we have 3 exchange servers in our environment.

• Exchange Server 2007 – Server Inaccessible
• Exchange Server 2010 – CAS, MBX & HT Roles Installed.
• Exchange Server 2013 – CU 6 Standard Evolution version installed which is expired.. Exchange Control Panel web console is not accessible. Exchange Management Shell is accessible

All arbitration mailboxes are on mailbox database of exchange server 2013 and all users mailbox databases are on exchange server 2010. Send connector and the and public MX record is pointing to the exchange server 2010.

Exchange web console is not opening for exchange 2013 but Management shell is accessible. 

So here now we are planning to install Exchange Hybrid setup to migration mailboxes to the Office 365 but before that we would like to decommission exchange server 2007 and exchange server 2013 first.

So here my question is can we migration arbitration mailboxes back to the exchange 2010 than uninstall 2013. Or if we uninstall exchange 2013 directly than It will migration arbitration mailboxes to the exchange 2010.

Or Can we install exchange 2016 in the environment on new server and migrate arbitration mailboxes on them than uninstall 2013?

Please advice in this situation.

If you are facing any kind of difficulty with converting EDB file to PST format, then you can make use of third party tool EdbMails for the successful conversion of EDB to PST. This is one of the instant solutions for all Exchange database recovery issues with ease.

EdbMails EDB to PST tool functions admirably with most of the versions of Exchange and Outlook. You are allowed to download the demo version of the tool to use all the features extensively and export 30 items from each and every folder of all mailboxes of Exchange to Outlook PST. This will give you an idea of how powerful EdbMails is.

Deleted mailboxes are still retained in the Exchange Server database until it’s permanently deleted by an Exchange administrator or until the mailbox retention period expires. Using EdbMails you can recover deleted Exchange Server mailboxes and permanently deleted emails from Exchange EDB files.

Also, it works for:

• Handling a severely corrupt Exchange server file.
• Recovers permanently deleted Exchange mailboxes.
• Helps to repair and restore Exchange mailboxes.
• Removes Exchange errors & viruses safely.
• Resolves secondary corruption like Index corruption, database page, etc.
• Maintains the original folder structure intact.

It supports all the Exchange server versions such as 2019, 2016, 2013, 2010, 2007, 2003 and you can save EDB data in EML, MHT, and HTML formats.

For more information visit EdbMails official website.

To know more : edbmails in google.

Hi to all and sorry for my English,

*****************************************************************

$createTenantRoot = ($RoleIsDatacenter -or $RoleIsPartnerHosted);
          $createMsoSyncRoot = $RoleIsDatacenter;

          #$RoleDatacenterIsManagementForest is set only in Datacenter deployment; interpret its absense as $false
          [bool]$isManagementForest = ($RoleDatacenterIsManagementForest -eq $true);

          if ($RolePrepareAllDomains)
          {
              initialize-DomainPermissions -AllDomains:$true -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$cre
ateMsoSyncRoot -IsManagementForest:$isManagementForest;
          }
          elseif ($RoleDomain -ne $null)
          {
              initialize-DomainPermissions -Domain $RoleDomain -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$c
reateMsoSyncRoot -IsManagementForest:$isManagementForest;
          }
          else
          {
              initialize-DomainPermissions -CreateTenantRoot:$createTenantRoot -CreateMsoSyncRoot:$createMsoSyncRoot -Is
ManagementForest:$isManagementForest;
          }
        ": "Microsoft.Exchange.Management.Tasks.EnumerateRightsFailedException: Rilevato l'errore 0x6BE durante l'enumer
azione dei criteri di gruppo per l'account S-1-5-21-3562906010-3634392973-2603855403-2111.
   in Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object ta
rget, String helpUrl)
   in Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.AddSaclRight(ADDomain dom, SecurityIdentifier exsS
id)
   in Microsoft.Exchange.Management.Tasks.InitializeDomainPermissions.InternalProcessRecord()
   in Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   in Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePip
elineIfFailed)".

*****************************************************************

where S-1-5-21-3562906010-3634392973-2603855403-2111correspond to "<domain>\Exchange Servers".

Error can be reproduced running 

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

then "Preparing Organization" fail.

Using domain administrator account and everything work fine even the installation fail.

Where is my mistake?

Thanks in advance for any help

Best regards.

Massimo

Hello All,

On-Premise Active Directory

Forest - Single

Domain - Single

UPN Suffixes - 6

On-premise Exchange Server 2013 Standard.

Single server host combined role of Mailbox and CAS.

Accepted domains - 6

Users are in 6 different Organizational Unit according to the Accepted domain.

Now, we are planning to migrate to office 365 E3 license. To isolate the Administrative console for each accepted domain we have decided to go with multiple tenancy (i.e.) 6 Office 365 Tenant.

With the current setup, is it possible to use a Single Azure AD connect sync for the 6 tenants in office 365? If not, could you please recommend the best practices. 

Thanks in Advance!!!

Rajakumar