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

Migrating public folders 2007 to 2013

$
0
0

I am currently migrating public folders from Exchange 2007 to 2013.  The first Sync of the batch job has completed.  In the 2013 ECS, I am seeing the following: 

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.

Also, the 2013 EAC does not show any public folders.   How can I verify the folders will be available when I completed the migration.   I thought the folders were viable in the EAC during the migration, but I may be mistaken.

Please advise.



Recovered and Retired Exchange 2010 Server Listed as Provisioned

$
0
0

I'm trying to clean up an Exchange 2010 > 2013 migration. The 2010 servers were physically removed and trashed without uninstalling Exchange after the migration was considered complete. There were still a ton of references to 2010 servers and databases so I was tasked with cleaning it up.

I followed steps to recover the servers by creating VMs with same OS and name as the old 2010s. I ran the recover install on the mailbox database server and then retired it without rebooting (this may have been a mistake?). It appears that deleting the databases and uninstalling Exchange from the mailbox database server worked as its databases no longer appear in the 2013 ECP.

But the mailbox database server is still listed in the 2013 ECP as a "provisioned server". I have since run the 2010 setup on the server with the /RemoveProvisionedServer switch and it says it completed but it remains in the 2013 ECP. I have also run the 2013 setup on an existing 2013 server with the /RemoveProvisionedServer switch but it fails with an error which I'm not entirely sure about:

[10/18/2019 01:02:45.0234] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
[10/18/2019 01:02:45.0234] [0] **********************************************
[10/18/2019 01:02:45.0234] [0] Local time zone:
[10/18/2019 01:02:45.0234] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[10/18/2019 01:02:45.0250] [0] Setup version: 15.0.847.32.
[10/18/2019 01:02:45.0250] [0] Logged on user: DOMAIN\administrator.
[10/18/2019 01:02:45.0281] [0] Command Line Parameter Name='removeprovisionedserver', Value='SRV-2010MBDB'.
[10/18/2019 01:02:45.0281] [0] Command Line Parameter Name='sourcedir', Value='F:\'.
[10/18/2019 01:02:45.0516] [0] RuntimeAssembly was started with the following command: '/removeprovisionedserver:SRV-2010MBDB.DOMAIN.LOCAL /sourcedir:F:"'.
[10/18/2019 01:02:45.0516] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[10/18/2019 01:02:45.0516] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[10/18/2019 01:02:45.0516] [0] Copying Files...
[10/18/2019 01:02:45.0531] [0] Starting copy from F:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[10/18/2019 01:02:47.0844] [0] Finished copy from F:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[10/18/2019 01:02:47.0844] [0] File copy complete. Setup will now collect additional information needed for installation.
[10/18/2019 01:02:47.0860] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[10/18/2019 01:02:49.0891] [0] Setup is choosing the domain controller to use
[10/18/2019 01:02:50.0063] [0] The MSExchangeADTopology has a persisted domain controller: SRV-DC2.DOMAIN.LOCAL
[10/18/2019 01:02:50.0094] [0] [ERROR] Exception has been thrown by the target of an invocation.
[10/18/2019 01:02:50.0094] [0] [ERROR] Method not found: 'Boolean Microsoft.Exchange.Data.Mime.MimeAddressParser.IsValidDomain(System.String, Int32, Boolean)'.
[10/18/2019 01:02:50.0094] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
[10/18/2019 01:02:50.0094] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[10/18/2019 01:02:50.0094] [0] CurrentResult main.run:235: 1
[10/18/2019 01:02:50.0094] [0] CurrentResult setupbase.maincore:396: 1
[10/18/2019 01:02:50.0094] [0] End of Setup

I still have the Frontend/CAS server to recover and then retire.



Exchange 2013 Server - Virtual Directories Settings in EAC/ECP

$
0
0

I removed our OWA and ECP virtual directories from Default Web Site to remove access from the outside world. Then created a new Website, assigned to a 2nd IP on the server's NIC. I added both OWA and ECP to the new site. We can access email from the new URL internally.

I can login to Exchange Admin Center and manage everything EXCEPT when I go into Servers - Virtual Directories. The Virtual Directories that were not changed work as designed. The 2 I changed I click on then the window pops open with a 500.19 error in that small window.

I need to correct that problem. I have found many articles about not being able to login to EAC this is not that. It's just the two directories management windows.

Exchange 2013 (Build 1473.3) on Server 2012r2

Thanks


Kevin Skinner

Upgrading to TLS1.2 with CU23 ON EXCHANGE 2013 WIN2012 R2

$
0
0
Hi Everyone,

Please, need some advise i am planning to upgrade MS EXCH 2013 to TLS 1.2 running on win2012 r2, now to do so i need Install CU19 in production for TLS 1.2 support, but CU19 is not available CU23, looking at the user guide for TLS1.2 i have it says be ready to upgrade to CU20 after its release if you need to disable TLS 1.0 and TLS 1.1. Has anyone recently upgraded TLS1.2, can i upgrade to CU23?
Does that mean TLS1.0 and TLS1.2 will get disable automatically?
Thanks

Nas 

Exchange Server 2013 Licensing after Hybrid deployment.

$
0
0

Hello Team!

One of my customers migrated from Exchange 2010 to Office 365 via Hybrid Deployment with Directory Synchronization and decided after complete descomission of Exchange Infraestructure (keeping DirSync alive) to install a new Exchange Server 2013 server in another site, just to manage the Active Directory user attributes.

The installation worked fine, no Exchange Forest was created, he created Remote mailboxes to manage user objects and life goes on...

The question: Is the licensing of this new Exchange 2013 Server really necessary, since he has only 2 admin mailboxes to access the console, and the system/arbitration mailboxes?

Thanks and regards to all community!


Set-OrganizationConfig -DomainController Fails (Attribute Not Legal For Class)

$
0
0

While installing the Mailbox Role I get the below error installing Mailbox Service. I cannot find any logs that point to the object that needs to be updated or what attribute it is.

Is the source code for this command viewable to see what Attribute is trying to be updated and on what object?

Prepare Schema and PrepareAD both ran successfully. CAS Role is already installed.

Error:
The following error was generated when "$error.Clear();
          $count=0;
          $ExchangeServers = Get-ExchangeServer -DomainController $RoleDomainController;

          $minVersion = New-Object -typeName Version -argumentlist "8.0.642.0";

          foreach ($server in  $ExchangeServers)
          {
            $currentVersion = [Version]$server.AdminDisplayVersion;
            if (($currentVersion -ge $minVersion) -and ($server.IsMailboxServer -eq $true))
            {
              $count++;
            }
          }

          if ($count -eq 1)
          {
            Set-OrganizationConfig -DomainController $RoleDomainController;
          }
        " was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on DOMAINCONTROLLER. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
Active directory response: 0000207D: UpdErr: DSID-031517D5, problem 6002 (OBJ_CLASS_VIOLATION), data 1376259
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: An object class violation occurred.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOrganizationConfig.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

HCW: could not converting string to DateTimeOffset

$
0
0

Hi,

running thr HCW I get this error: "Could not convert string to DateTimeOffset: 0001-01-01T00:00:00. Path '[0].LastDirSyncTime' line 1, position 104"

the log reports

2019.09.06 08:30:56.214 *ERROR* 10430 [Client=UX, ExecuteHighlandsServiceRequest=DirSync, Thread=17]
                                      Newtonsoft.Json.JsonReaderException: Could not convert string to DateTimeOffset: 0001-01-01T00:00:00. Path '[0].LastDirSyncTime', line 1, position 104.
                                         at Newtonsoft.Json.JsonReader.ReadDateTimeOffsetString(String s)

Any idea? :(

thanks


Cannot Add Mailbox Permissions in a Hybrid environment From OnPrem to O365 (Users do not show up in search)

$
0
0

Hi There,

We Cannot browse/add mailbox delegation to users in Office 365 from On Premise Hybrid Environment (It does work the other way around however from Office365 to on premise users)

Essentially, if we open the ECP, navigate on the Enterprise Tab (Not Office 365 Tab) and double click a user with a local mailbox on premise 2013, and then goto 'Mailbox Delegation' we cannot see any hybrid users in Office 365 to add delegation to.

It does work the other way around (In Office 365 ECP we can add on premise users as permissions)

Any ideas on what could be wrong?

Cheers

Snook


The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed

$
0
0

Hello Everyone,

I've been installing Exchange servers since Exchange 5.5. I'm now installing Exchange 2013 with SP1 that will coexist with one Exchange 2010 SP3 server. I'm installing it on 2012 R2 Enterprise Edition. There is a root domain and one child domain. The Exchange Server is in the child domain.  Even though I've run the .\setup PrepareSchema, AD and domain and all were successful I still get the message below when running Exchange setup. If I look at what /preparedomain does it seems like it has done what is needed. I've run the /prepareschema, /preparead and /preparealldomains in the root domain & have even run /preparedomain over and over in the child domain. Like I said everytime I run these they are successful. Oh and my account belongs to all the right groups needed to run these. Any ideas would be appreciated!

The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DomainPrepRequired.aspx


Update from Exchange 2013 SP1 to CU8 error

$
0
0

hi,

i've got problem when update to cu8.

the file 'c:\program files\microsoft\exchange server\v15\transportroles\agents\hygiene\asdat.msi' is not a valid installation package for the product microsoft exchange 2007 standard anti-spam filter updates. try to find the installation package 'asdat.msi' in a folder from which you can install microsoft exchange 2007 standard anti-spam filter updates.

please help me..

Exchange SP3 download link

$
0
0

Hello,

we need to update from exhange 2007 to 2013, but we have exchange 2007 with SP2.

First we nned to update to SP3, but i can't find any working link for download.

In Windows catalog i see only rollups, but i can't find package with update from SP2 to SP3.

Can You send me naz link or package name in microsoft catalog?

Thx,

Petr

on-premises mailboxes cannot receive emails from 365 Hybrid deployment

$
0
0

Hi

I have an exchange 2013 and I tried to set up a hybrid environment with Exchange 2013 for Office 365. After the hybrid wizard, on-premise mailboxes cannot receive emails from users Office365.

this is the error

the message keep in pending

Motivo: [{LED=450 4.7.320 Certificate validation failed};{MSG=UntrustedRoot};{FQDN=owa.mydominio.com};{IP=77.240.116.238};{LRT=5/9/2016 9:09:56 PM}]. OutboundProxyTargetIP: 77.240.116.238. OutboundProxyTargetHostName: owa.mydominio.com

regards

Shared Calendar prompts for credentials

$
0
0

A full hybrid was recently set up on exchange 2013. When some mailboxes were moved to the cloud after the hybrid was set up, there was an issue of viewing free / busy information for the user that was moved to O365. MS support asked that the autodiscover be pointed to O365 instead of on-prem (only a couple of users in O365 and rest are on premise). When that was done the free / busy was visible for the user in cloud. However, right after the move some users that had the mapped the cloud user's calendar to their outlook received an error that the admin had made some changes which required restart of outlook. Thereafter, it has been prompting them for credential whenever they try to access their calendar (which also contains the mapped calendar of the cloud user). Also, one of the users on premise that have the cloud user's calendar mapped is not able to view the on-premise users calendars anymore. The user had a few users' calendar listed under shared whose contents were visible. However, that is not the case anymore.

Any insight would be appreciated! 

 

Exchange Server 2007 SP3 download link

$
0
0

Hello All, 

I am with upgrading E2007 to 2016 and as a first step I have to install E2013 in the organization. My current Exchange 2007 is SP2 level so I need update it to SP3 before moving forward. 

All MS links to SP3 are dead, I spent a few hours trying to find one, but no happy. 

Could you please help me with sharing the link where I can download Exchange 2007 with SP3 or SP3 separately?

Thank you in advance. 


Exchange Online migration with ExpressRoute

$
0
0

Hi,

I know ExpressRoute is not recommended (but is supported) by Microsoft for Office 365 traffic and utilising internet links is the preferred method.

We have a customer who already has an ExpressRoute configured and ready to go. My concern is that they have this configured for egress but not ingress (as they certainly don't have Autodiscover, MRS, Web services etc) configured.

There seems to be limited documentation on how this works but I am correct in thinking for Autodiscover, EWS etc we add those records into Public DNS and map it to an external IP address and Express Route will have specific routes advertised for those endpoints and external users would use the standard internet routes? 

Would there be any issue why egress traffic could go via ExpressRoute and ingress traffic traverse the internet?

Any advice greatly appreciated. We really don't want them going down the ExpressRoute method but we are having our hand forced here.


the subscription for the migration user couldn't be loaded

$
0
0

For every user that I migrate from EX2010 to EX2013 I get error:

the subscription for the migration user couldn't be loaded

but move request suceededs at the end.


bostjanc

Upgrading Exchange 2013 CU8 to CU23

$
0
0

Hello,

Good Day!!!

We have 2 Exchange 2013 CU8 member of the DAG, our company requires us to use TLS 1.2 in the Exchange.

Accordingly TLS 1.2 supports starting from CU19 above and the available to download in Microsoft is CU23.

I am looking for detailed steps on how to Upgrade to CU23 and how to enable TLS 1.2.

Your HELP and Support will be very much appreciated.

Thanks very much.

OS Updates for a server running Exchange

$
0
0

All,


I'm looking for a step-by-step/best practices guide on how to install Windows Server updates (i.e., window server security and servicing stack updates) that has Exchange 2010 installed.  I'm not looking to update Exchange, but just the server OS. 

I inherited this Windows Server 2008 that has a year's worth of OS updates waiting to install (which will require multiple reboots) and I'm worried about hosing the mail database.  Is the process simply stopping/disabling the Exchange services first, install all of the Windows Server OS updates, reboot, and then bring Exchange back online?

Thanks,

Dave  


Exchange 2010 to Exchange 2013

$
0
0

I have Exchange 2010 SP3 with all mailboxes.  I installed Exchange 2013 RU23 on new hardware.  I was curious what the EAC would look like so started it and logged.  Looks like O365 admin center.  When I went to recipients and mailboxes all of our mailboxes were listed.  Again being curious I logged into OWA on the Exchange 2013 and all my mail was there.  I hadn't started a migration batch yet.  Is this normal?  

Thank you,

Wade


Wade Harris

Migrating an Exchange 2013 to Exchange 2019

$
0
0
We have an Exchange organization that excepts email for 4 domains. We are starting to migrate one of the domains to it's own forest. We have migrated a couple of test users and all seems ok except, old emails involving the migrated users. During the migration an X500 address is created on the new mailbox in the new forest but how are emails routed to that address from the original Forest/Domain? When replying to an old email an NDR is generated there is a legacyDN address but how can that be routed to the new Forest/Domain? 
Viewing all 7129 articles
Browse latest View live


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