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

Help

$
0
0

Hi we are in the process of migrating exchange 2007 to exchange 2013. For exchange 2013 we have setup DAG with two mailbox servers. Alss have two CAs servers. We are using f5 for load balancing. SSL' are offloaded at the Exchange servers. All our outlook client connect to owa.company.com. Even ActiveSync, outlook web access and OA all point to owa.company.com.

Created a VIP in F5 to load balance CAS servers. In DNS owa is pointing to VIP. Also I have created another DNS entry for autodiscover which is also pointing to same VIP. Please advise if this isa correct configuration. Or do I need to crfeate separate VIP for autodiscover? Do I need to offload the SSL at F5? Please advise.


Exchange 2013 failed CU1 to CU5 update. Trying to get CU1 working again

$
0
0

Hello all,

Currently running a single server installation of Exchange 2013 CU1 on Server 2008 R2.

Checked prerequisites for updating to CU5 and all looked good.

Launched the CU5 install via GUI, not command prompt, which from what I remember when I installed CU1 using the GUI didn't work very well.

Anyway, CU5 failed telling me I have to uninstall CU1. Checked a couple forums and found the same answer.

Tried to uninstall CU1 via Programs and Features, but that failed because it couldn't find a file. Also tried Change and that errors out saying the installation failed and to run setup from an installation media location.

So, I enabled the services that where disabled by either the CU5 install or the CU1 uninstall and started chasing and correcting errors. I've got it to the point that where it looks like everything is working, but I can't send or receive. I'm trying to find an error message somewhere, but I'm not having any luck finding any.

I've tried to use the Queue Viewer and suspend the queue, but nothing shows up in the queue. I've looked at send and receive connectors and they look OK.

I've been up all night and I'm at a loss right now and could really use some help getting this train back on the tracks.

Thank you,

Dennis


Mailbox Role: Mailbox Service Error when installing CU5 from 2013 Sp1

$
0
0

I was on Exchange 2013 Sp1 and was installing CU5 and got this error:

Error:
The following error was generated when "$error.Clear(); 
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
          {
          if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
          $dispname = "Microsoft Exchange";
          $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
          if ( $mbxs.length -eq 0)
          {
          $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispname )
          {
          set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;

          # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
          # This can be remove after BUG(O15#2555914) is fixed.
          if ($sysMbx.RetentionPolicy -eq $null )
          {
          $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
          set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
          }
          }
          else
          {
          write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
          }
          }
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.".

Error:
The following error was generated when "$error.Clear(); 
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
          {
          if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          {
          $sysMbx = $null;
          $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
          $dispname = "Microsoft Exchange";
          $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
          if ( $mbxs.length -eq 0)
          {
          $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          {
          $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          {
          $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
          }
          }
          }
          else
          {
          if ($mbxs[0].DisplayName -ne $dispname )
          {
          set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
          }
          $sysMbx = $mbxs[0];
          }

          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          {
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;

          # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
          # This can be remove after BUG(O15#2555914) is fixed.
          if ($sysMbx.RetentionPolicy -eq $null )
          {
          $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
          set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
          }
          }
          else
          {
          Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
          }
          }
          else
          {
          write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
          }
          }
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow)
   at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.Validate(TDataObject dataObject)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

What would be the best way to Uninstall Exchange 2013

$
0
0

In my setup, I already have a exchange 2007 server and we are planning to migrate to exchange 2013.

On my first attempt to install exchange 2013 I had several issues and finally created a new server and managed to install exchange 2013 on it usingSetup /m:RecoverServer.

Since the first attempt of exchange 2013 installation had issues we want to uninstall exchange 2013 completely from our organization and start from scratch.

What would be the best way to uninstall this particular exchange 2013 completely so that it will also remove all the objects it has created within Active Directory?

Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

$
0
0

We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them. 

With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.

For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.

In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.

I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.

I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.

So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.

In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.

Questions are, Is this the right way to migrate all the users to Exchange 2013?

Will it affect the operation of existing Exchange 2007 server?

Migration from Exchange 2010 to Exchange 2013 Local outlook clients Certificate problem

$
0
0

Hello everyone

I have installed Exchange 2013 in 2010 environment that have 2500 users. Configured everything and migrated 4 users for test without an issue.

Internally and Externally everything working perfectly including Autodiscover, redirection..etc however on Outlook 2010/2013 clients users either on 2010 or 2013 keep getting Certificate warning with local FQDN of the Second exchange 2013 CAS is not included in the Public wildcard certificate which is associated with the IIS,SMTP services on both CAS 1 and 2 for exchange 2013.

The interesting thing is that the mail, autodiscover is configured on local dns to point to first CAS01 but the certificate error message is coming from the second one CAS02.. I don't know how.

Regardless of the Error Outlook clients connect without any issue but still it's very annoying for the customer.

When I delete and recreate a new profile. Users don't get the warning anymore.

I have 2 CAS and 2 Mailboxes on Exchange 2013. 1 CAS,HT and 1 Mailbox server on Exchange 2010. Their Local DC is not compliant name space with the external domain.

Local DC is domain.local.

I have setup and configured all the Internal Webservices on CAS1,2 on Exchange 2013 to match the External one in order for the server not to require local FQDN.

Is there any way to get rid of this error without deleting and re-creating all the users's profiles ??

I would appreciate your comments.

Thanks


Mohammed JH


POP3 to Exchange Server Migration

$
0
0

Hey guys i've got a question. So i have a client who is using a hosted solution and accessing mail through pop and would like move Exchange 2013. I'm trying to come up with a way to get this done in a staged manner. they already have an internal AD infrastructure setup.

So here's my idea:

  1. create a public sub domain example temp.domain.com with mx record of course.
  2. add sub domain as alias to all accounts user@temp.domain.com
  3. set the default domain (domain.com) as internal relay
  4. set sub domain as authoritative
  5. Connect users outlook to Exchange
  6. setup forwarding on the POP account to forward to user@temp.domain.com
  7. Disconnect POP account and import pst to exchange mailbox.
  8. Switch MX once all mailboxes are moved

Does my plan sound plausible? if not, any suggestions would be greatly appreciated.

Thanks.

Autodiscover SSL cert not good for External Users

$
0
0

External Users are getting ssl cert issue with the autodiscover, everything works ok for them but when they open Outlook it asks them to accept the cert each time.

Our Webmail and everything else is  webmail.domaincorp.com  yet our email is just domain.com. When cert is presented its presenting the autodiscover.domainCorp.com cert instead of autodiscover.domain.com ... how can I fix that?


Exchange 2010 Migration to 2013 Coexistence url's

$
0
0

Hello,

What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.

So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

Exchange Server 2013: Database Increasing double

$
0
0
Dear All,

I just migration from MS exchange server 2003 to MS Exchange Server 2013. I have problem with database size are increase double.

the old database size only 400GB in MS Exchange server 2003.

After migration to MS Exchange server 2013, the size are increase to 800GB of .edb.

Any idea?


Khemarin333@hotmail.com

Bug in ABP based segregation at distribution group level

$
0
0

We have Exchange 2013 based hosted exchange platform, tenants are segregated via ABP with custom attribute1 as a filter. users, distribution groups etc. are properly segregated as expected.

when a user login to owa\ecp and navigate to Options->Groups, they can see the distribution groups it is member of and the distribution group for whom he is defined as manager, with in the same tenants. All good as expected.

but now when you click on join button, it open up a windows which exposes all the security groups and distribution groups from all the tenants on this platform. it clearly says the ABP is not taking care of segregation at this level and expose ALL Groups Address list to all the tenants bypassing the ABP segregation. Is their any hack exist for this issue? 
 



Can not recreate exchange 2010 sp3 systemmailbox in a organizationconfig version 15449 ,FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042

$
0
0

My exchange server version is 2010SP3,Then I setup a exchange 2013 RTM in my domain.

a few weeks later iI uninstall the exchang 2013,I found all the system mailbox did not work 

I want to Preparead AD but system told me my exchange organizationconfig is too high,how to do ?

OWA problem Exchange 2013 coexistence with 2010

$
0
0

Hi all,

I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying to access OWA with a mailbox that is still on 2010 it fails with the following error:

:-(
something went wrong
A problem occurred while you were trying to use your mailbox.
X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
X-OWA-Version: 15.0.913.21
X-FEServer: <name of 2013 server>
X-BEServer: <name of 2013 server>

Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.

Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments. This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?

Any help is greatly appreciated!

Best regards
Daniel


Accepted Domain Question - what should be the default?

$
0
0

We have just installed EXCH 2013. Our Root Domain Name is internal.companyname.com and it was already listed as the default domain. We added our email domain as companyname.com and want to accept external emails on behalf of it. We do want send/receive internal emails among AD users.  Which should be the default?

Email Address policy -Which one to choose?


Removing Public Folders after migration from Exchange 2007 to Exchange 2013

$
0
0

Recently we migrated from Exchange 2007 to Exchange 2013.  We did not migrate Public Folders and are retiring them from Exchange altogether.  I shut Exchange 2007 off for a couple of weeks to ensure 2013 functions properly and it does so we're ready to decommission Exchange 2007.  I was able to remove all the mailbox databases without a glitch.  Using the EMC I click to remove the Public Folder database from Exchange 2007 and get the following message:

Error: The public folder database "server\storage group - Public Folders\ Public Folder Database" contains folder replicas.  Before deleting the public folder database, remove the folders or move the replicas to another public folder database.

Any help appreciated.

Exchange 2013 CAS functionality in coexistence with Exchange 2010 CAS

$
0
0

Hi,

I am planning to migrate Exchange 2010 to Exchange 2013 for 15000 users. We have a pool of 6 CAS 2010 servers added in a single CAS array. So my question is if we introduce a new CAS 2013 server in same site then will it affect CAS traffic anyway ? If we point our HLB to all CAS servers including CAS 2010 and CAS 2013 so will the CAS 2010 servers wil take traffic or is it only CAS 2013 servers who will take traffic. We will be putting same URLs in CAS 2013 same as CAS 2010. I have read lot of MS articles and all say that CAS 2013 should be enabled for CAS traffic and it will proxy request to CAS 2010. But I am not sure if we will face any CAS traffic issue whenever we will introduce CAS 2013 servers in same site and traffic will be pointed to CAS 2010 and CAS 2013 both. Is it possible to add CAS 2013 in Exchange 2010 CAS array ? Please guide. Thanks in advance.

Popup Window Lag Opening OWA 2013

$
0
0

Hello,

I have an issue regarding the OWA 2013.

When I want to open a message in a popup in OWA 2013, randomly and suddenly, the icon "Starting" freezes and I have to wait 90 seconds to get access to the message.

When I launch the debug mode just as well with IE and Firefox, I'm seeing that request taking almost 90 seconds to complete

GET /owa/userspecificresourceinjector.ashx

Has anyone else faced that issue ?

My setup is one server HUB+CAS Echange 2013 Version 15.0 (Build 847.32)

Thanks for you time and your help,

PYD.


Access Control Entry Issue after Installing Lync 2013 into the Forest

$
0
0

I am having an issue after deploying Lync 2013 into the same Forest/Domain where Exchange 2013 is deployed. Lync 2013 and Exchange 2013 both work fine, however, when I am in the Exchange 2013 Admin Center and I edit either a Group or a Resource, I receive the following warning:

warning
The object has been corrupted, and it's in an inconsistent state. The following validation errors happened:

The access control entry defines the ObjectType 'd819615a-3b9b-4738-b47e-f1bd8ee3aea4' that can't be resolved..

The access control entry defines the ObjectType 'e2d6986b-2c7f-4cda-9851-d5b5f3fb6706' that can't be resolved..

The access control entry defines the ObjectType '9b51a1ef-79b7-4ae5-9ac8-d14c47daca46' that can't be resolved..

Has anyone run into this or have any suggestions on how to resolve this issue?

I appreciate any assistance.

Thank You,

ExchangeKiller

Failed CU5 update, need help recovering

$
0
0

I went to install the CU5 update today and it fails on the step Mailbox role: transport service.

Error:
The following error was generated when "$error.Clear(); 
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\MFP". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:
The following error was generated when "$error.Clear(); 
          $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
          foreach($connector in $connectors) { if($connector.MaxLocalHopCount -gt 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 } };" was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.ReceiveConnectorRoleConflictException: The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MAIL\Client Frontend MAIL". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnector.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

When I try to re-run the setup, it fails at the same spot. I can't use the ECP nor the Shell to remove the Receive Connector (it is just a receive connector for the MFP).

Is there any way to remove this receive connector with Powershell not working?

(It looks like this is the problem: http://exchangemaster.wordpress.com/2014/01/24/incorrectly-adding-new-receive-connector-breaks-exchange-2013-transport/ but since I can't get a shell to run in this failed upgrade state I can't take the recommended fix nor just remove the connector.)
Viewing all 7008 articles
Browse latest View live


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