I recently configured coexistence between exchange 2007 and 2013.

I have moved some users to 2013 and they are fine.

I recently moved "BESADMIN" account to exchange 2013 while trying to integrate exchange 2013 with BES. The integration is suspended for now and I am trying to move the mailbox back to 2007. From ECP it completes successfully but running get-mailbox cmdlt shows that the mailbox is still in 2013.

I have also tried using management shell but it fails at 95%

I will appreciate all the help I can get here ..

~Richard

..forever is just a minute away*

Hi,

I am just finishing migrating from SBS2011 with Exchange 2010 to Server 2012 Standard with Exchange 2013.

The problem I am having is when I run the New-MigrationBatch script on the 2012 server to begin migration of public folders from the SBS2011 Server.

I have followed this https://technet.microsoft.com/en-GB/library/jj150486(v=exchg.150).aspx 

I run this cmdlet New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server sbserver) -CSVData (Get-Content C:\PFMigration\folder-to-mailbox.csv -Encoding Byte) -NotificationEmails

I then get this error 

A parameter cannot be found that matches parameter name 'SourcePublicFolderDatabase'.
    + CategoryInfo          : InvalidArgument: (:) [New-MigrationBatch], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-MigrationBatch
    + PSComputerName        : server2.domain.local

I have tried changing this to direct public folder database name but I still get errors.

Can anybody shed any light as to what I am doing wrong here?

Thanks in advance

I'm just looking at a server that needs quite a lot of updates. What is the recommended strategy?

Exchange CU9 then .Net 4.5.2 or .Net first then CU9? What about the other general Windows Updates?

Thanks

Nick

I just performed a fresh install of Exchange 2013 w/ SP1 on Windows 2012 Standard R2 which is also a domain controller in an organization that already has an Exchange 2010 server (on a separate server). When I launch the Exchange Management Shell and attempt to run "Get-ExchangeServer" I get the error "The term 'Get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file, or operable program..." I see that \\HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.SnapIn is loading the module name "D:\Program Files\Microsoft\Exchange\bin\Microsoft.Exchange.PowerShell.Configuration.dll" (which is the correct path to that file).

I've restarted the server twice and have the same issue. Also tried doing an unattended install of just the Managment Tools since using the setup GUI didn't give me the option of uninstalling and reinstalling the Management Tools since the checkbox is greyed out. I searched the ExchangeSetup log for errors and didn't find any.

How do I get the Exchange Management Shell to register the Exchange Powershell commands? Do I need to uninstall Exchange and Re-Install?

Hi

I have a Windows 2008 r2 VM server and I have noticed that if I shut down the server (deallocated) when I come to restart it I can not connect to it using remote desktop. To resolve this I have to delete the remote destop endpoint and recreate it using the same public and private ports - it then works fine. This only happens to the 2008 R2 server, all my other Windows 2012 server never have this issue - does anyone know why this might be happening?

Thanks

Simon

Hi, sorry if this subject is a bit perplexing. and if it's been answered before.

Migrating 2007 - 2013. Most mailboxes fine- slow but fine. Moved a few hundred now, more to come!

The odd mailbox- for various reasons- failed. Literally just a handful so far. So... I try to move them again, and the move completes with 0 mailboxes moved. No errors, it just hasn't moved the mailbox(es). Any idea what could be going wrong? Target database: xxx. Status: Completed. Synced Mailboxes: 0, Finalized mailboxes: 0, Failed mailboxes: 0.

There's no rhyme nor reason to this that I can see- it's almost like there's a flag set which says this mailbox can't be moved.

Any ideas gratefully received! I've just got these few causing problems on our old WS2K3/EX2007 boxes now (along with public folders), need to meet next Tuesdays deadline :)

I have a new install of Server 2012R2 and Exchange 2013 (no edge server roll installed and nothing else installed on this machine). We are failing our PCI compliance testing with the following failures:

I have disabled the reg key for SSL 3.0 server, and I am still failing the POODLE vuln.  Can anyone help me with getting past these issues?

Hello all,

I am planning an Migration from EX2010 to EX2013 by installing the EX2013 parallel to EX2010. During that planning i have red a lot of public folder migration (e.g. http://technet.microsoft.com/en-us/library/jj150486.aspx) - but after all I am a bit confused.

When reading above mentiones technet article I understand the following:

- When using the method describes it is a kind of an one way copy. Is this right?

- When using this method users on EX2010 as well as users on Ex2013 can access andcreate public folders. Is this right?

- But there is no kind of syncronisation between Public Folders hosted on EX2010 and EX2013. Is this right? So there will be an inconsitence between PF hosted on EX2010 and EX2013?

I have the issue that the user migration will take about a month or more. How can I solve the issue of getting inconsitences?

Please execuse my bad English.

Thanks in advance

Lars

Hi All ,

How to configure Exchange 2013 OWA with Single Sign On ?

Thanks .

Hi all,

I'm having problems with users syncing their Android 5.0.x devices with our Exchange server. This article (https://code.google.com/p/android/issues/detail?id=79389) suggests disabling TLS 1.2 would fix the issue, however, I can't find the option in EAC that would allow me to do this.

Where would I find this option, or is it only possible via the Shell? If so, what command would I use to do this (and subsequently re-enable)?

Thanks :)

Hi all,

I'm getting following message logged in the event viewer every 30 sec:

The Software Protection service entered the running state.

Log Name:      System
Source:        Service Control Manager
Date:          08/07/2015 22:49:20
Event ID:      7036
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A

We use a KMS, so I have tried a reactivation via slmgr.vbs /ato (which succeeds, but doesn't stop this).

I've also tried to activate via the UI, but canceling before key entry as suggested here (https://social.technet.microsoft.com/Forums/en-US/c1107e3b-e3eb-4c12-be35-b7ffaa50c787/the-software-protection-service-entered-the-running-state)

I have tried to enable the scheduled task "SvcRestartTask" in Scheduled Tasks (Microsoft > Windows > SoftwareProtectionPlatform). This runs and terminates without error, but this event keeps being logged.

What can I do to sort this? Anyone have any ideas?

Thanks :)

Hello Support team ,

Since moving  hybrid configuration  from Exchange 2010 to Exchange 2013 we are experiencing issues moving student mailboxes to the 0ffice 365 .

Please see below.

Test-MigrationServerAvailability -ExchangeRemoteMove -Autodiscover -EmailAddress username@student

.domain.com -Credentials $Cred

RunspaceId         : 003f5db1-fd81-4a52-9acd-e232f329e6f6

Result             : Failed

Message            : AutoDiscover failed with a configuration error: The migration service failed to detect the

                     migration endpoint using the Autodiscover service. Consider using the Exchange Remote

                     Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues.

ConnectionSettings :

SupportsCutover    : False

ErrorDetail        : internal error:Microsoft.Exchange.Migration.AutoDiscoverFailedConfigurationErrorException:

                     AutoDiscover failed with a configuration error: The migration service failed to detect the

                     migration endpoint using the Autodiscover service. Consider using the Exchange Remote

                     Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues.

                        at Microsoft.Exchange.Migration.DataAccessLayer.MigrationEndpointBase.InitializeFromAutoDiscove

                     r(SmtpAddress emailAddress, PSCredential credentials)

                        at Microsoft.Exchange.Management.Migration.TestMigrationServerAvailability.InternalProcessExcha

                     ngeRemoteMoveAutoDiscover()

IsValid            : True

Identity           :

ObjectState        : New

From the connectivity analyser, I see the following.

It firstly successfully found the IP address:

Attempting to resolve the host name autodiscover.student.saintaug.nsw.edu.au in DNS.

The host name resolved successfully.

IP addresses returned:

Testing TCP port 443 on host autodiscover.student.saintaug.nsw.edu.au to ensure it's listening and open.

The port was opened successfully.

Testing the SSL certificate to make sure it's valid:

The certificate passed all validation requirements.

Remote Certificate Subject: CN=*.,

The certificate name was validated successfully.

The host name that was found, autodiscover.student.saintaug.nsw.edu.au, is a wildcard certificate match for common name *.

The certificate is trusted and all certificates are present in the chain.

However, some error on this: Client certificate authentication couldn't be determined because an unexpected failure occurred. WinHttpSendRequest failed with error 12175.

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover. student.domain.com:443/Autodiscover/Autodiscover.xml for user user@.student.domain.com

Exception details: Message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. Type: System.Net.WebException Stack trace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() Exception details: Message: The remote certificate is invalid according to the validation procedure. Type: System.Security.Authentication.AuthenticationException Stack trace: at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async)

Are you able to assist.

Thank you

I have succesfully migrated an exchange 2010 environment to an exchange 2013 server.

Now I am finding in my logs this message:

SMTP rejected a (P1) mail from 'HealthMailboxb91a20da4d8649a68abbb80cb44c9d83@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailboxb91a20da4d8649a68abbb80cb44c9d83'. The Active Directory lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError

What I checked:

- This healthmailbox has in the AD the permission to 'send as' for SELF
- I have noticed that the UPN is set as "...@<my domain>.be" (which we use for standard emailadresses), I have changed this to "...@<my domain>.local" but after a few minutes it automatically restores itself (?) to the previous value..

Any help on this matter? I have read I can delete the entry from the AD and restart  the exch monitor service but I'm not sure if this won't break anything as this is the only server running all services.

Please see if anyone can help me with following.

I have installed 2 windows 2012 server(1 AD + 1Exchange2013) in my existing SBS2011 with Exchange 2010 Environment. Having 2 problems,
1. When configuring outlook i have to type old exchange server name then it resolves to new server name, if i type new server name it does not configure outlook.
2. i have moved 2 mailboxes to new server sending and receiving email are fine. but when i go to global address book it says connection to Microsoft exchange unavailable.
Any help would be appreciated.

Thanks

We started a migration batch containing 17 users  5 of them got migrated and the rest was stuck on syncing and they were syncing for about one week and a half we stopped the batch and deleted it. Now when we try to continue moving the other users they stuck on syncing with no email getting migrated whatsoever what can we do in order to transfer these user to the new server without having problems.

Hi,

Is there any option to move the Recoverable Items > Purges folder to Journal mail box. As it's not getting moved to Journal mail box like the other mail items. The content of this folder is the Lync chat archives.

Is there an option to move only particular folder to Journal mail box?

Is there any option to move conversation history content automatically to Journal mailbox or any other mail box?

Exchange expertise - Appreciate your help

Hello,

We are in the process of migrating from an Exchange 2003 server to an Exchange 2013 SP1 server. The EXCH2003 server is in a separate domain environment than the new EXCH2013 server. We plan to export all mail from the EXCH2003 server and import to the EXCH2013 server.

At this time we are seeing an issue with the new EXCH2013 SP1 server. When we test creating a new profile in Outlook 2010 SP2 on a client machine we receive the following errors:

1) The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

- also -

2) The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

We are able to access OWA both internally and externally and can login under multiple user accounts. Also while logged into OWA, mail flow is working, able to send and receive.

We installed and configured a new SSL trusted certificate on the Exchange 2013 SP1 server as well.

At this time our main issue is with Outlook 2010 SP2 and Exchange 2013 SP1 not communicating with each other properly.

Please let us know what other information is needed to help resolve this issue.

Thank you,

Jason Ringholz

Regards, Jason

Hi all,

not sure how I did it previously, but I am able to generate a usable certificate from my local CA server, which is standalone (not enterprise ver.).

I was trying to request for a new certificate for my exchange server currently but its mentioning not valid.

Is CA Standalone version not meant for Exchange servers? Due to parent/child domain we are not able to create enterprise CA in child domain, and we have no access to parent domain, using my AD account.

Thanks and Regards,

Low

Please help me

I met this error message by reinstalling Exchange 2013 SP1

Best regards,

Michael

Michael Phan

Hi,

I was wondering if anyone can advise me the correct way to go about deploying a second exchange 2010 server on a network.

Server A lives on a separate subnet than the new Server B will be.  I will be deploying the CAS, Mailbox and HUB roles, but i need to utilize the same webmail address for both servers some how.

I heard load balancing may be the way to go but I have also researched there may be other ways such as silent redirection but I don't know enough about them.

Server B will relieve pressure from Server A, also mailboxes will be transferred.  I would also like the auto discover configured for both servers so outlook finds the correct  mailbox on the appropriate server.  Please note we do not want a DAG even though i am fully aware its High Availability.

Any advice would be great or any Blogs/Posts I can read up on :)