Hi,

I just setup an Exchange 2013 server and am experiencing the following issue. I am able to access OWA without any issue. From OWA I am able to send and receive emails. I was able to setup my exchange account on my iphone without any issue but the messages in my inbox are not downloading to my phone and when I try to send an email from my phone, I get an error  message starting "cannot send mail, the message was rejected by the server."

I verified external URL. I ran the Get-ActiveSyncVirtualDirectory commend and was only given the internalUrl. I tried to create a new external virtual directory but was informed that the directory already existed. I tried to set the directory using power shell but got an error that the object 'servername\Microsoft-Server-ActiveSync' could not be found.

I will appreciate any help you can provide.

Everything else works except for ActiveSync.

Thanks,

Emmett

Hi team,

How to prevent users from changing calendar permission in outlook. When user open calendar option in Outlook he should either he should able to view the calendar sharing tab or he should not able to make modification in calendar permission by assigning permission to others.

Dear All,

I plan to cutover migration exchange on-premises to exchange online with single-sign-on.

http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx

In Step 2: It need to Convert on-premises mailboxes to mail-enabled users. it has only instruction guide for exchange server 2003 and 2007. it didn't have for exchange server 2010 or 2013.

Could you guide what is the best solution to convert mailbox in exchange server 2010?

BR,

Khemarin

Khemarin333@hotmail.com

We have to migrate Mailbox in a Cross Forest environment (from Exchange 2007 SP3-RU10 to Exchange 2013).For Account coesistence we already migrate Users/Group via ADMT, excluding Exchange Attribute.

The steps are:

• Enable-MailUser
• Prepare-MoveRequest.Ps1
• New-MoveRequest.

Before to Upgrade to CU6, the migrations steps described above worked fine (Exchange Server 2013 SP1 (alias CU4))

After ugrading we alway get the following error running New-MoveRequest:

New-MoveRequest -Identity "02909" -Remotelegacy -RemoteCredential $RemoteCredentials

-TargetDeliverydomain "old.mycompany.com" -TargetDatabase MBOX2A -RemoteGlobalCatalog "odl_dc.mycompany.local"

–DomainController “new_dc.newdomain.int”-verbose

New-MoveRequest -Identity "user200" -Remotelegacy -RemoteCredential $RemoteCredentials

-TargetDeliverydomain "new.mycompany.com" -TargetDatabase MBOX2A

-RemoteGlobalCatalog "old_dc.mycompany.local" -verbose

Recipient '4309a8a0-9edf-4ad1-991b-89d8d75a1c28' isn't a mailbox.

+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemotePermanentException

+ FullyQualifiedErrorId : [Server=mailbox1,RequestId=f3bd2350-a9dc-49d1-8cf6-f5564a47bd26,

      TimeStamp=17/11/2014 01:45:59]

      [FailureCategory=Cmdlet-RemotePermanentException]

            17FEEA0A,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

   + PSComputerName       : mailcas1.newdomain.int

I have found the below article which is the exact issue that I am having.

https://support.software.dell.com/migration-manager-for-exchange/kb/133684

Is there anyway to get HotFix on this problem. I cannot wait two months fo CU7.

In addition downgrade (e.g. Uninstall CU6 and re-installa SP1) is quite complicate and hard.

Dear Sir

I Trying to upgrade my exchange server 2013 to CU6 but I got this error so I want to go back to previous version before update

and this is the massage that I got in upgrade installation

Error:
The following error was generated when "$error.Clear();
          $maxWait = New-TimeSpan -Minutes 8
          $timeout = Get-Date;
          $timeout = $timeout.Add($maxWait);
          $currTime = Get-Date;
          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)
          {
            $setSharedCDCErrors = @();
            try
            {
              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)
              {
                break;
              }
              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
            }
            catch
            {
              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
            Start-Sleep -Seconds 30;
            $currTime = Get-Date;
          }

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "System.Exception: Unable to set shared config DC.
   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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Please is there any solution because it is very argent issue 

Best Regards

Rawa Zangana

I have exchange 2013 installed on win 2012 r2.

One day a technician came to install a * certificate and then we cannot access the management console.

When we connect we put the username and pass and nothing happens.

So I installed exchange on a virtual server with the 2 roles and finally managed to access the management console but unfortunately only for 2 day.

I think we have an authentication problem in the IIS.

Help please

Hi

I am working on fixing Exchange 2007 being host on business server

Due to errors made by 3rd party contractor we had to change static IP address given by ISP.

deleivery error email stated

Could not deliver message to the following recipient(s):

Failed Recipient: grahame@??????????????.com.au

Reason: Remote host said: 601 Attempted to send the message to the following ip's:

      220.233.92.164

   -- The header and top 20 lines of the message follows --

This is old static IP address

C:\Windows\system32>nslookup
Default Server: 
Address: 

> set type=mx
> ??????????????.com.au
Server: 
Address: 

Non-authoritative answer:
accurateroadrepairs.com.au      MX preference = 0, mail exchanger = mail.accurateroadrepairs.com.au

??????????????????.com.au      nameserver = ns22.myownserver.net
??????????????????.com.au      nameserver = ns21.myownserver.net
mail.??????????????????.com.au internet address = 220.233.92.164

Question : where does nslookup obtain this ip address from?

is this no cache'd somewhere on the net and just waiting for a refreshed. (just like waiting for refresh to a change in the nameservers)

or is getting it from our srever- because I cannot  find host or mx records for this IP

Not receiving external emails - doing I need to simple need to wait for the internet to catch to our IP change?

or is their something else I did to do.

Running Cisco Modem/Router  with Nat active

Firewall checked and not blocking

and we are running a postmaster catch all on exchange.

Yours gratefully and thanking you in advance

Grahame Wheatley

I have multiple users using shared mailboxes under Exchange Server 2013. I have a single user the receives the send receive error listed using Outlook 2013. I've seen multiple threads on this problem. Basically deleting the users outlook profile and letting it rebuild. No luck...

The users primary mailbox sends and receives fine. However, when sending from another mailbox, it fails. Here is what I've done:

Win7, Office 2013 SP1

1) Converted the standard mailboxes that are being shared to Exchange Shared Mailboxes.

2) Added the appropriate permissions under delegation through the Exchange console.

3) Deleted the users Outlook profile.

4) Renamed c:\users\USERNAME\appdata\microsoft\outlook to outlook.old.

5) Rebooted

6) Created a new user profile when launching Outlook.

7) Allowed the users email to sync

8) Added a shared mailbox to the users profile.

9) Sent a message and it sticks in the outbox.

10) Built a new machine.

11) logged in as the user

12) Built the Outlook profile with the same user

13) let the client sync email to the primary mailbox

14) added the second mailbox and let it sync

15) attempted to send from the second mailbox, and receive the error and the message sticks in the second mailbox outbox.

New machine, same user. Is there an Exchange Server mailbox repair function? I'm making a career out of the issue. I configure my Win 8 machine/Outlook 2013 with the same mailboxes, and it works fine. I am able to send and receive from 5 different mailboxes.

please help!!

I have a domain installed on windows server 2012 R2 with function level 2008 R2 and when i try to install "as a administrator" Update for exchange 2013 CU6 or CU5  DC restart and am facing this error :

I already prepare AD and Schema before start install 

Please Advice Thanks

Hi,

I tried to install Exchange 2013 as a second Exchange Server, first Exchange Server ist a Ex2007. While Setup, I got the "otherWellKnownObjects"-error. I found some posts and the solution could be delete the CN=Microsoft Exchange in ADSIEdit.

Before I proceed, I need to know if this container is used by Ex2007 so it would cause Ex2007 problems?

THANKS!

Daniel

If there's a chance to edit / clean the key in ADSIEdit, please tell me. If I try to, I got an error message like "No Editor registered for that data type"

I know there isn't a migration path for Exchange 2003 but has anyone tried any type of work around?  I'm thinking about moving one of my customers users mailboxes to PST files and them importing them into Exchange 2013 on a 2012 server.  Has anyone had any experience doing this?  Below are the details of what I have and what I was thinking about doing:

Small Network - approx. 10 users

Server 2003 Sp3 standalone AD DC with Exchange 2003

Would like to move straight to Server 2012 with Exchange 2013

If I export the mailboxes and uninstall Exchange from the 2003 server will Server 2012 join the domain and upgrade the existing AD schema (forest and domain)?  If it would, could I then install Exchange 2013 on that server, create the mailboxes for the users and import the PST files?

Just wondering if anyone has tried this, or something similar.  They don't have an extra server to move everything to 2010 first so it's either a workaround or move them to Exchange 2010 (which Microsoft has quit selling).  I'm sure this will put a lot of small business VARs in a bad situation. 

(Just as a side note) Is it true that Dell and HP have quit selling Windows 7 Pro? My vendor still sells it and will for 18 more months.

Good afternoon, all!

My company is starting a migration from dovecot on Linux using OpenLDAP to Microsoft Exchange using Active Directory.  We have fewer than 10 employees,  want to self-host and want a secure design that won't break the bank.  I originally thought to have the mailbox server running on one of the two domain controllers and the client access running on a separate server in the DMZ.  I've started to re-think this in favor of two independent servers.

Is there a design document out there on options for where to place which server in different scenarios? I see lots of information about large enterprise installations but nothing much for the small but secure installation.  Management is set on having Exchange in-house, so hosted Exchange, no matter how much "more better" that would be, is not an option.

May thanks for looking into this!

Gregg

Had this occur, then stop occurring, now reoccurring. I can't find any mention of it so either a bug or something wrong with our setup I guess. Really annoying because at this point I have only 145 mailboxes to move, being able to view the mailboxes by database, select those on the old and run the migration via the web interface is the simplest way to achieve this and it's just not working.

1. Select a group of mailboxes
2. Select migrate to another mailbox
3. Give batch a name
4. Start batch
5. Batch initially shows the 145 mailboxes ready to go
6. Refresh the Migration page shows then the number suddenly at 0
7. Job just completes.

What am I missing here?

Excuse the weird picture but can't attach more than 2 images...

I have Exchange 2013 installed on the only domain controller.

When I go to put Exchange 2013 into maintenance mode from the Exchange Management Shell using the command:

Set-ServerComponentState server.domain.local -Component ServerWideOffline -State Inactive -Requester Maintenance

I get the following error:

"Set-ServerComponentState : The term 'Set-ServerComponentState' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Set-ServerComponentState server.domain.local -Component ServerWideOffline -State ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Set-ServerComponentState:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException"

How do I put this Exchange server into maintenance mode?

I am trying to put Exchange into maintenance mode as the CU6 Cumulative Update is failing with the below error:

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 isnot an ExchangeServer.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 Inactivewhile setup is running."

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

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            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 isnot an ExchangeServer.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 Inactivewhile setup is running."

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

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            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 isnot an ExchangeServer.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 Inactivewhile setup is running."

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

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            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)"."

Dear All,

I'm planning to do the migration from Lotus Domino 8.5.3 to exchange server 2010 or 2013.

I had go through the link http://technet.microsoft.com/en-us/library/bb124294(v=exchg.65).aspx

and Microsoft have a tool named: Exchange Server Migration Wizard.

Can I use to do the migration? or Do you recommend another tools?

BR,

Khemarin SET

Khemarin333@hotmail.com

Hi!

I have a design implementation question. We are a small firm with 80 AD users, 100 mailboxes, DB store is 200 gigs and all on Exchange 2007 (Virtualized connecting to a SAN), but growing rapidly. Also, we currently have two sites in Chicago and New York(Exchange 2007 server in NY). We would like to upgrade from 2007(all roles installed on a VM server ESX 5.5 server) to 2013. Should we virtualized the Exchange 2013 or should they be physical servers? Also, since the servers will be in separate sites will I need a Load Balancer in both location? Also, should I split up the roles since we have two locations running the both roles on both servers. For example below:

1 Chicago server-CAS/Mailbox Role
1 New York server-CAS/Mailbox Role

Should I have the Chicago users connect to the Chicago Server? And the New York users pointed to the New York Server? Currently everyone connects to the mail sever in NY. Any advice or comments would be appreciated.

Thanks!

Hi,

I just setup an Exchange 2013 server and am experiencing the following issue. I am able to access OWA without any issue. From OWA I am able to send and receive emails. I was able to setup my exchange account on my iphone without any issue but the messages in my inbox are not downloading to my phone and when I try to send an email from my phone, I get an error  message starting "cannot send mail, the message was rejected by the server."

I verified external URL. I ran the Get-ActiveSyncVirtualDirectory commend and was only given the internalUrl. I tried to create a new external virtual directory but was informed that the directory already existed. I tried to set the directory using power shell but got an error that the object 'servername\Microsoft-Server-ActiveSync' could not be found.

I will appreciate any help you can provide.

Everything else works except for ActiveSync.

Thanks,

Emmett

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:

I now realize this was a bad idea.  As I'm sure you can guess, it corrupted the databases.  Luckily it's on a new install and there's only a couple test mailboxes in the database.  I've tried the repair instructions, but can't get them to work.

Running "eseutil -r e01" from the log folder returns an error that it might be a lossy operation, and suggests running the soft recovery with the -a argument.  Running "eseutil -r e01 -a" returns the same error.

Any ideas?  I'm thinking about just nuking the databases, and starting from scratch.  Aside from deleting the arbitration mailboxes and running ADprep to recreate them, is there any trick to doing this?

I am getting ready to apply CU6 to my Exchange 2013 environment ( currently CU4, SP1 ). I have a primary and a secondary site with the same number of CAS and Mailbox servers. Secondary site setup for resilience.

I know that Microsoft supports updating one half of a DAG environemt, following with the other after a soak period.

I am hoping to get some real world feedback on update practices.
- Update all servers same night?
- Update Primary one night and secondary next night? ( just a little easier on the tired techs )
- update primary site, leaving secondary site as fall back in case of issues?
How many days do you leave in the soak period? 1 day, 1 week?

What have you found to be reasonable and practical?

Thanks!
Tom