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

EX2013 SSL Outlook Client Issues - Internal and External Names are Different

$
0
0

I have just migtated from exchange 2007 to exchange 2013 sp1. Internal Domain name abcd.local and External Domain name 1234.com. I have purchased a new SSL Cert from Go Daddy with mail.1234.com and autodiscover.1234.com. Everything is working fine except my internal Outlook clients. They receive an SSL error because the names don't match which i totally understand. I have tried adding an autodiscover SRV record to DNS that points to mail.1234.com and changed the internal and external virtual directories to the external url. Neither of these have helped.

So the question is how do i get the internal outlook clients to work without the SSL error?

Thanks.


Exchange 2013 CU6 update cannot pass preresquites?

$
0
0

When I go to update our Exchange 2013 server to CU6 (from CU5) I get the following error:

I was doing something with the Tasks, which cannot be scheduled anymore. How do I fix this?

Thanks

Error:
The following error was generated when "$error.Clear();  
          try
          {
            $Target = $env:COMPUTERNAME
            try
            { 
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue 
            } 
            catch 
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.  Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive.  Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
          }
          catch 
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.  Setup can not continue.";
            throw;
          }" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   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.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   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();  
          try
          {
            $Target = $env:COMPUTERNAME
            try
            { 
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue 
            } 
            catch 
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.  Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive.  Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
          }
          catch 
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.  Setup can not continue.";
            throw;
          }" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   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.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   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();  
          try
          {
            $Target = $env:COMPUTERNAME
            try
            { 
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue 
            } 
            catch 
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.  Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive.  Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
          }
          catch 
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.  Setup can not continue.";
            throw;
          }" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   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.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Installing Exchange 2013 - Domain/forest prep

$
0
0

Hi guys

I've just installed the first Exchange 2013 server in our forest.

The server was installed in the root domain of the forest.
We have several child domains in the forest. These contains our users.
I haven't done any prepping in these domains.
The painful question is: Should I have done that? And if so, can it be done post installation of Exchange 2013?

My own test account is located in one of these child domains, and so far I haven't experienced any problems with this account using OWA.

Just want to make sure that I'm not set up for failure later in the migration.

Best Regards
Klaus Ringe Nielsen


Best regards Klaus Ringe Nielsen

Cross Domain migration

$
0
0

Hi,

I would like to know best practice for Cross forest Migration from Exchange 2010 to Exchange 2013... Here is the scenario:-
1. There are two forest abc.xyz.com & efg.xyz.com.
2. abc domain having Exchange 2010 is running.
3.Efg domain having user accounts and users login to laptop using this domain.
4. I have to install Exchange 2013 in Efg domain and migrate mailboxes from Exchange 2010 servers. This includes public folder, GAL Sync & Free /busy.

Please suggest me best practice to achieve goal ... Pls. send details on

Thanks in Advance !!
Amit kumar

MS Exchange 2010 Sp3 Ent Migration to Exchange 2013

$
0
0

Hello,

We currently have 2 Exchange 2010 SP3 servers in 1 DAG. Both servers host CAS, Mailbox and Hub Role.

I want to introduce a 3<sup>rd</sup> Exchange 2013 Server and slowly move users onto a new DAG I build in Exchange 2013.

Can I create a 3<sup>rd</sup> Exchange 2013 Server with CAS and Mailbox Server Role and make the 3<sup>rd</sup> Exchange server (2013) a member of the existing (2010) CAS array then slowly perform local move requests for users mailboxes from my Exchange 2010 DAG to the Exchange 2013 DAG without any disruption to my outlook, OWA and AS clients?

Exchange 2010 (Windows 2008 R2)

Exchange 2013 (Windows 2012 R2 DataCenter)

Error when updating Client Access Front End Service to Exchange 2013 Update 6

$
0
0

When updating to Exchange 2013 Update 6 we received the following error at the Step 11 of 13: Client Access role: Client Access Front End service step: 

Error:
The following error was generated when "$error.Clear(); 
          $fe = get-ActiveSyncVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController -ErrorAction SilentlyContinue;

          if ($fe -eq $null)
          {
            new-ActiveSyncVirtualDirectory -DomainController $RoleDomainController -Role ClientAccess;
          }
          else
          {
            update-ActiveSyncVirtualDirectory $fe -DomainController $RoleDomainController -InstallIsapiFilter $true
          }
        " was run: "System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter' required by parameter 'Identity'. Specified method is not supported. ---> System.NotSupportedException: Specified method is not supported.
   at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

Problem was that if you have more than one ActiveSyncVirtualDirectory, the installer for Update 6 fails because it's not expecting an array of virtual directories to be returned. Solution is to remove the "extra" virtual directory, perform the installation, and then re-add the virtual directory. 

None of the other types of virtual directories are susceptible to this, only ActiveSync. 


installing Exchange 2013 cu6

$
0
0

Upgrading Exchange 2013 CU6 (no updates applied to original)

This is a simple server for 25 users, no DAG or clustering etc

Do I simply backup Existing DC & Exchange VM's and run setup?

everything is now work so I don't want to mess it up!)

or are there any services etc I need to stop ?


ChrisS

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.)

Exchange 2013 Cu6 fails to install

$
0
0

When I attempt to install CU6 on Exchange 2013 I get this error message and cannot continue, occurs after reboot as well and trying to re-run setup.  Any ideas how to fix?

Thanks,

Setup Error 2nd time 5 of 9 after restart

Error:
The following error was generated when "$error.Clear(); 
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          {
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          {
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          {
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          }

          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          {
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
          {
            trap [Exception]
            {
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            }
            
            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
          }
          }
          }
          }
        " was run: "Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "Domain.local/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed.

   at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)
   at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
   at System.Security.Principal.NTAccount.Translate(Type targetType)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   --- End of inner exception stack trace ---
   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.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxPermissionTaskBase.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Configure "New user mailbox" Identity Parameters to change the "Display name" format.

$
0
0

Good morning,

I was referred from http://community.office365.com/en-us/f/158/t/261575.aspx and was hoping you would be able to assist me with the inquiry below.  Thank you!

When creating a new user mailbox, the Display name defaults to "First name, Initials, and Last name" (as confirmed by http://technet.microsoft.com/en-us/library/jj991919(v=exchg.150).aspx).  More specifically, the default is "First name, SPACE, Initial(s), PERIOD, Last name".  Our Exchange 2010 environment is presently configured to format new mailbox display names to "Last name, SPACE, First name, SPACE, Initial".  We are in the process of testing Exchange 2013 for migration from Exchange 2010 with existing mailboxes of 5,000+ and need to configure Exchange 2013 to default the display name utilizing the same format as established through Exchange 2010.  How can this be accomplished?

Seth

Exchange 2010: Redirect Logging folder

$
0
0

I need to redirect the E:\Exchange\V14\Logging folder to L:\Logging.  Will the mklink be able to redirect the folder?

mklink /j E:\Exchange\V14\Logging folder  L:\Logging

Is there a better option?

Readiness Checks fail with "The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

$
0
0

There's another thread about this issue but the accepted answer actually has nothing at all to do with the original problem/question so that's a bit deceptive.

Anyway, when trying to install Exchange 2013 SP1 (on 2012 R2 Datacentre) the installation reaches the Configuring Prerequisites part of the Readiness Checks and then fails out with the message:

The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception.

I honestly can't find any way around this issue and the only mentions I've seen resulted in people reinstalling Windows which obviously isn't really a resolution to the problem.

Is there any known fix for this issue?

Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception.

Exchange CA recovery

$
0
0

i lost one of my CA 2013 servers

installed  new server with same name and config upon unning Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

but getting this message

e:\>Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms

Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Management tools
Client Access role: Client Access Front End service
Client Access role: Front End Transport service

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Prerequisite Analysis                                     FAILED
    Exchange Server version Version 15.0 (Build 995.29) or later must be used t
o perform a recovery of this server.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.DrMinVersionCheck.aspx


The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Our environment has Exchange 2013 On-line with CU6

 

EXCHANGE 2013 AD Topology Service crashes when a single DC goes offline

$
0
0

We have a single 2013 multi-role Exchange server in our environment.  I have noticed that whenever a single DC goes offline I lose connectivity to Exchange. When I look at the services on the Exchange server i see that  EXCHANGE 2013 AD Topology Service has crashed. The specific server that causes this is a DC / GC in a different site. It holds the domain naming master role.  There is a DC/GC in the same site as the Exchange server. The domain is at 2008r2 functional level. Please let me know if there is anything else I have omitted  about my environment that is pertinent to answering this question.

Thank you

Jim


NSF to PST! Require Information

$
0
0

Upgraded Lotus Notes version into newer 8.5 it has complex functionalities. These functions are not easily graspable and it takes long time to understand, I decide to export my data into another (MS Outlook) platform, is it possible, I want new updates about conversion in cost-effective manner. And if yes then suggests me the way?

OWA 2012 login "almost there..."

$
0
0
Hi guys,
I'm facing a weird problem about OWA 2013. It's just one user who can't log into his owa. He can access his mailbox through Outlook though.
when he entres his credentials, the page remain on "almost there..." forever. Other users on same computer can log into their mailbox without any problem.

what's the reason and what shoud I do to fix it?

thanks in advanced

Certificate Management in Exchange 2013

$
0
0

Hi There,

I need clarification on Exchange 2013 certificates.... In my proposed Solution there are 12 physical Exchange 2013 dual role Mailbox + CAS.

Question:-

1. Shall i go for SAN based certificate of individual certificate as i have Exchange 2010 running in Exisitng environment?

Individual Certificate means ( Owa, Autodiscover & Legecy)

2. I can set Certificates on all CAS servers using single certificate.? Do i need to purchase 12 Certificates or Single certificate would work?

 Thanks,

Amit kumar


Amit

Upgrade advices...

$
0
0

Hello Friends,

We had been running Exchange 2013 CU2 without issue for some time. Patch CU3 was released, and recommended by Microsoft. The upgrade to CU3 failed, and we immediately called Microsoft Support. We were unable to run Exchange in its current state, we could not uninstall the patch as it had already upgraded our Active Directly Schema making Exchange 2013 CU2 incompatible, and we were unable to get the patching process to complete.

Microsoft Support worked on this issue for three days and nights, before finally getting everything working again and email started flowing once more. However, our Exchange server has never been the same. We immediately noticed strange issues that we have not been able to resolve, such as email delivery delays, an empty mail database that does nothing, yet cannot be removed, and other issues.

Service pack 1 arrived for Exchange 2013 over six months ago. However, we’ve been afraid to update our suspect Exchange server. This update performs yet another schema update, and we are afraid things may break once again.

We thought we might build another Exchange 2013 Server CU3, move all of the mailboxes to it, take down the old server, and then upgrade the new server to Service Pack 1. But, we’re not sure that this process is the best way to go about achieving healthy email functionality,  or if it will even work at all. We cannot afford any more email downtime.

Any reccomendations?

Thanks,

Stephen Barash

Adding second domain in Exchange 2013

$
0
0

Dear all, 

I am migrating our mail server from Exchange 2007 to 2013. Untill now not many problems encountered, I have set up a 2 members DAG for redundancy and most of Exchange functions and services are working like a charm (except sharing schedule's when you work with Outlook 2007 on the Exchange 2013 server).

Now comes the challenge: Our company has bought another company. They have their own domain. We need to migrate all their mailboxes to our mailserver, with as little downtime as possible. Their mail addresses needs to be kept the same, but they will work in our mail server. 

I wonder if someone has experience on doing this? How can I connect the mailboxes to our domain, keeping the old known address to clients. This company delivers very critical services to diverse clients, and every 5 minutes downtime is actually too much, and changing addresses is not possible. Can someone help me with this? 

All help will be appreciated! 

Regards, 

Cornelius 

Viewing all 7008 articles
Browse latest View live


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