OK, maybe this is a goofy question

I am currently working a migration from Exchange 2007 to Exchange 2013.  I've just finished a simple install (ClientAccess, Mailbox only) changed my internal autodiscover URI and then rebooted.

If I remember correct when I migrated from Exch 2003 to Exch 2007, the server moved itself into the Exchange OU within ADUC.  Is it a big deal if I just move the server myself?  OR should setup have moved it automatically?

Thanks

I had to bring up the public folder database for the moved resources to work again.  We do not use public folders any longer so we did not do any type of public folder migration.  Do I need to do this for the resources to work?

After succesfull moving mailboxes from Exchange 2010 to Exchange 2013 (single all role servers in same Forest/AD) error messages are displayed in the eventviewer:

source: MSExchange Management Application
id: 5000

I do have installed a valid 3rd party certificate, all works well on both servers (2010 and 2013). How to fix this before I migrate all other mailboxes from 2010 to 2013?

Thnx Remco

Hello all,

i've started the installation of a new Exchange 2013 with SP1 in a Windows 2012 R2 environment. New AD, no Exchange previously installed. Exchange ISO fromVolume Licensing Service Center (Filename: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118.iso)

All the prerequisites are ok, installed also the “Unified Communications Managed API (UCMA) 4.0″ as requested.

Setup.exe i've started with "run as administrator" and all went well, until Step 11 of 15 (Mailbox role:Mailbox service).

Setup stopped and gives an error:

The following error was generated when "$error.Clear(); 

         Install-MsiPackage `

           -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi")) `

           -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `

           -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-nb-NO.msilog"))

       " was run: "Installing product F:\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'The cabinet file 'EngineInstanceData.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.'.".

Exchange ECP is not working (HTTP Error 404.0 - Not Found), EMS (Shell) is working - if i try a get-mailboxserver it gives me the correct servername.

Exchange Services are running:

Running MSExchangeADTop... Microsoft Exchange Active Directory...
Running MSExchangeAntis... Microsoft Exchange Anti-spam Update
Running MSExchangeDelivery Microsoft Exchange Mailbox Transpor...
Running MSExchangeDiagn... Microsoft Exchange Diagnostics
Running MSExchangeEdgeSync Microsoft Exchange EdgeSync
Running MSExchangeHM Microsoft Exchange Health Manager
Stopped MSExchangeIMAP4BE Microsoft Exchange IMAP4 Backend
Running MSExchangeIS Microsoft Exchange Information Store
Running MSExchangeMailb... Microsoft Exchange Mailbox Replication
Running MSExchangeMigra... Microsoft Exchange Migration Workflow
Stopped MSExchangePOP3BE Microsoft Exchange POP3 Backend
Running MSExchangeRPC Microsoft Exchange RPC Client Access
Running MSExchangeServi... Microsoft Exchange Service Host
Running MSExchangeSubmi... Microsoft Exchange Mailbox Transpor...
Running MSExchangeTrans... Microsoft Exchange Transport
Running MSExchangeTrans... Microsoft Exchange Transport Log Se...
Running MSExchangeUM Microsoft Exchange Unified Messaging

So, how to proceed ? Try to download a new ISO for Exchange 2013 incl. SP1 and run the setup again ? 

What happens to the existing  (corrupt) installation of the exchange which is not working ?

Thanks for your help

Bruno

Hello Community

    With Outlook 2007 you can create a link that when clicked Exchange Server appears but how
do you make "New Message/Send to" appear and the user's email address of your choice appear automatically by default?

    Thank you
    Shabeaut

Greenfield installation of Exchange 2013 CU5 on a Windows Server 2012 R2 VM. Getting alot of eventlog errors, so im a bit hesitant before deploying this in production.

Security log is getting swamped with eventid 4625:

An account failed to log on.

Subject:
 Security ID:  SYSTEM
 Account Name:  EXCH01$
 Account Domain:  AD
 Logon ID:  0x3E7

Logon Type:   3

Account For Which Logon Failed:
 Security ID:  NULL SID
 Account Name: 
 Account Domain: 

Failure Information:
 Failure Reason:  Account currently disabled.
 Status:   0xC000006E
 Sub Status:  0xC0000072

Process Information:
 Caller Process ID: 0x1048
 Caller Process Name: C:\Windows\System32\inetsrv\w3wp.exe

Network Information:
 Workstation Name: EXCH01
 Source Network Address: -
 Source Port:  -

Detailed Authentication Information:
 Logon Process:  Authz  
 Authentication Package: Kerberos
 Transited Services: -
 Package Name (NTLM only): -
 Key Length:  0

Also getting the same error on :
Caller Process Name: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxAssistants.exe

Tried recreating the healthmonitoring mailboxes, but didn´t solve the problem.
This happens without ANY clients connecting to the server, so its a local issue on the server.

I am building an Exchange 2013 environment to co-exist with my existing Exchange 2010 server and to migrate users over. I think I have everything correct but just wanted to get a sanity check.

Our environment is fairly simple, we have an Exchange 2010 server that hosts all the roles, it has ActiveSync enabled for mobile devices, internal clients (Outlook 2007 and up) are domain joined, we have a few external clients connecting to Exchange via Outlook over the public internet.

Currently we do not use Split DNS, our internal clients resolve to mail-server.domain.com and we have a Enterprise Certificate Authority that issues a certificate that our clients trust.

Externally (and mobile) access the Exchange server via webmail.domian.com and the certificate is a 3rd party SSL (GoDaddy).

Moving forward with Exchange 2013 i'd like to use Split DNS and use webmail.domain.com for both internal and external and use the 3rd party SSL for both internal and external (inc. mobile) clients just to keep things simple and not have to worry about different CA SSLs and different DNS for internal/external clients.

Is there any issues with the above plan? Using 3rd party SSL for internal/external clients and moving away from using our Enterprise CA SSL for internal clients and sticking to webmail.domain.com for both? As I understand Microsoft suggest using Split DNS for Exchange deployments.
Because I am changing this to Split DNS will there be any interruption to my internal clients when they do Autodiscover?

Also attached is a picture of my current Exchange configuration and also the configuration in the Lab with the current Exchange 2010 (mail-server) and exchange 2013 (new-server) configuration for all the various virtual directories and their authentication.

http://s22.postimg.org/qaggl1fwv/cfg.png

This outlines where I am trying to go with this, does anyone see any issues with it? I am shooting to not break autodiscover and any exchange services to end users, trying to make the upgrade/migration "seamless".

Thank you

I am starting my transition to Exchange 2013 and I have a few questions. 

First, I am installing my mailbox servers. The management want a phased rollout and install the CAS servers next month. Are the mailbox servers OK to run on their own until then?

Second, I have some new and old namespaces, and I want to know how I configure these.

Old names:

internal webmail : https://webmail.domain.com.owa

activesync: webmail.domain.com

internal autodiscover: autodiscover.domain.com

CAS Array name: mapi.domain.com (MXserver10 and MXserver11)

We also have a DR with:

DRactivesync: DRwebmail.domain.com

We want to use the following names in our environment. Is it still wise to have different names for our DR activesync?

We are not using a CAS Array. We will be running exchange.domain.com as a CNAME to both serverCAS01 and serverCAS02

EAS: email.domain.com

DR EAS DRemail.domain.com

Am I missing something? Please help! How do I go about setting these names so that all mail for my 2010 servers gets routed through Exchange 213, and so that there is no disruption when i set these things up.

Hi,

I am running with Exchange 2010 SP1 in DAG & CAS/HUB in cluster mode. need to upgrade to SP3. few things need to know

1. Schema upgrade will be done I as read in the article. can this create any issue? what is the best measure to safeguard any problems of schema upgrade. Do we do this along with exchange setup or we should run schema upgrade prior to install exchange 2010 SP3?

2. Any impact on active sync, outlook anywhere & HUB connectors side post SP3?

3. Do we need to take any exchange related backups as we are running mailbox, CAS/HUB servers in redundant mode?

Please share your experiences.

Regards,

VIpin

We are running Exchange 2010.  For our e-mail addresses we use the formatfirstname.lastname@domain name.    This works fine until we get a username with a number after it.

E.g. 1st John Doe ->  jdoe - > John.Doe@happy.com

       2nd John Doe -> jdoe1 -?  John.Doe1@happy.com

       3rd  John Doe - > jdoe2 -> John.Doe2@happy.com

Is there any way to configure the e-mail addresses in Exhange so that the correct e-mail address is associated with the account when the exchange mailbox is created.  Currently we have to manually fix any account that do exactly matchfirstname.lastname@happy.com 

Windows Server 2013; Exchange Server 2013 with Cumulative Update 1

Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with

[xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.  See the Exchange setup log for more information on this error.
[xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
[xxx] [0] [ERROR] The supplied credential is invalid.

(Crosses - XXX - replace original values.)

I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely conincidental:

The Security System could not establish a secured connection with the server ldap/xxx.xxx/xxx.xxx@XXX.XXX. No authentication protocol was available.

Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

When I log on as Administrator to either .../ecp or .../owa, authenticaion, I believe, succeeds but then I get HTTP 500.

When I do this on another server hosting the Exchange server for the same Organisation, I succeed - can get into both the mailbox and the Exchange server ECP interface. Unlike the first server, this Exchange server does not host any mailboxes but otherwise has identical Exchange roles installed.

When I log on as another non-administrator user to the first server that hosts mailboxes, I again succeed.

The problem seems to relate the administrative interface that the first server somehow fails to display but what could be the reason for that?

Thank you.

Hello,

I am migrating all on-premise exchange 2010 SP3 to Exchange 2013 SP1. I am testing mailbox migrations, each mailbox that gets moved to 2013 the user keeps getting prompted for credentials. I have read several posts in the forums yet none which solve my problem. Can someone point me in the right direction. All 2013 setting are currently at default.

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

Hello,

I would like to install Exchange 2013 into my existing Exchange 2010 / Office 365 environment but I do not want to introduce it into "production" until I had a play with it and configured it the way I want to before I allow it to accept connections and proxy to EXCH2010 for clients connecting up.

My understanding is until I update the AD SCP to point to new server and my internal/external DNS, the new EXCH2013 installation will not be detected by clients.

I also need to make sure the EXCH2013 will not modify any settings on my existing EXCH2010 (such as virtual directory URLs, etc..)

Is this correct?

Hi guys,

I'm hoping for a bit of assistance. I have stepped into an environment where there is one production Exchange 2010 server and one Exchange 2013 server. The Exchange 2013 server is in a unrecoverable state however it contains the domain administrators mailbox and therefore I cannot remove it manually. As it was a vm, I took it offline, created an identical server (name, os version(Windows 2008 R2 with latest updates), ip address etc.), installed all the prerequisite components and then ran setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms. Everything runs through successfully until it gets to the Mailbox role: Transport service where it fails with "Unable to set shared config DC.". After some searching on Google, it suggests that ipv6 is disabled on the DC. We have two DC's in our environment and both have ipv6 enabled as does the exchange server. If I try to re-run the installation for the role alone, i.e. Setup /mode:install /IAcceptExchangeServerLicenseTerms /role:HubTransport, it fails with "The machine is not configured for installing "BridgeheadRole" Datacenter Role." 

Any help would be greatly appreciated. 

Hi,

When user changing their password in email ,alert msg should go to their mobile, is it possible .In our organisation customer asking the above requirements

I am trying to migrate our public folders over to Exchange Online after having successfully executed a cutover migration.

I am following this guide: http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx

I submitted the migration request 11 hours ago. It has since then had the status "queued" and PercentComplete at 0. Is this normal or healthy?

This is how I submitted the request in a remote powershell session on my own laptop connected to Office 365:

$source_credential = Get-Credential xx\xx
$source_remoteMailboxLegacyDN = "/o=xx/ou=Exchange Administrative Group (xx)/cn=Recipients/cn=xx"
$source_remotePublicFolderServerLegacyFQDN = "/o=xx/ou=Exchange Administrative Group (xx)/cn=Configuration/cn=Servers/cn=EXCHANGE"
$source_OutlookAnywhereExternalHostName = "mail.xx.com"

New-PublicFolderMigrationRequest -OutlookAnywhereHostName: $source_OutlookAnywhereExternalHostName -CSVData (Get-Content FolderToMailboxMapPath.csv -Encoding Byte) -RemoteCredential: $source_credential -RemoteMailboxLegacyDN: $source_remoteMailboxLegacyDN -RemoteMailboxServerLegacyDN: $source_remotePublicFolderServerLegacyFQDN -AuthenticationMethod Basic

I get status like this:

Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | Format-List

RunspaceId                       : [guid]
Name                             : PublicFolderMigration
Status                           : Queued
StatusDetail                     : Queued
SyncStage                        : None
Flags                            : CrossOrg, Pull, SuspendWhenReadyToComplete
RequestStyle                     : CrossOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : False
SourceVersion                    : Version 14.3 (Build 195.0)
SourceDatabase                   :
SourceServer                     : exchange
BatchName                        :
OutlookAnywhereHostName          : mail.xx.com
RemoteCredentialUsername         : xx
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            : /o=xx/ou=Exchange Administrative Group (xx)/cn=Recipients/cn=xx
RemoteMailboxServerLegacyDN      : /o=xx/ou=Exchange Administrative Group (xx)/cn=Configuration/cn=Servers/cn=EXCHANGE
BadItemLimit                     : 0
BadItemsEncountered              : 0
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {<FolderToMailboxMapping><FolderName>\</FolderName><MailboxGuid>d9aae95d-0e27-40bd-aae9-cde8047a18e2</MailboxGuid></FolderToMailboxMapping>}
QueuedTimestamp                  : 17-07-2014 20:48:37
StartTimestamp                   :
LastUpdateTimestamp              : 17-07-2014 20:49:01
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp               :
CompletionTimestamp              :
SuspendedTimestamp               :
OverallDuration                  : 11:30:40
TotalFinalizationDuration        :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration           :
TotalFailedDuration              :
TotalQueuedDuration              : 11:30:40
TotalInProgressDuration          :
TotalStalledDueToCIDuration      :
TotalStalledDueToHADuration      :
TotalStalledDueToReadThrottle    :
TotalStalledDueToWriteThrottle   :
TotalStalledDueToReadCpu         :
TotalStalledDueToWriteCpu        :
TotalStalledDueToReadUnknown     :
TotalStalledDueToWriteUnknown    :
TotalTransientFailureDuration    :
TotalIdleDuration                :
MRSServerName                    :
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 :
BytesTransferredPerMinute        :
ItemsTransferred                 :
PercentComplete                  : 0
PositionInQueue                  : 1/1 (Position/Queue Length)
PreventCompletion                : True
FailureCode                      :
FailureType                      :
FailureSide                      :
Message                          :
FailureTimestamp                 :
IsValid                          : True
ValidationMessage                :
OrganizationId                   : EURPR01A002.prod.outlook.com/Microsoft Exchange Hosted Organizations/xx.onmicrosoft.com - EURPR01A002.prod.outlook.com/ConfigurationUnits/xx.onmicrosoft.com/Configuration                                  
RequestGuid                      : [guid]
RequestQueue                     : EURPR01DG002-db020
ExchangeGuid                     : [guid]
Identity                         : xx.onmicrosoft.com\[guid]
DiagnosticInfo                   :
Report                           : 17-07-2014 18:48:36 [xx] 'EURPR01A002.prod.outlook.com/Microsoft Exchange Hosted Organizations/xx.onmicrosoft.com/xx' created request.
ObjectState                      : New

Also posted to Office 365 forum since both are involved: http://community.office365.com/en-us/f/156/p/252752/776437.aspx#776437

i've add all user in AD to mailbox exchange 2013 except one user,when I add this user mailbox from existing user in AD, it's show error bellow :

Active Directory operation failed on domain-1.corporate.com. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150BC1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

when I create as new user for this one user with same account in AD, it's show error:

The value "xxx@corporate.com" of property "UserPrincipalName" is used by another recipient object "". Please specify a unique value.

i've does below :

*E:\ExchangeSvr2013>setup.exe /preparead /IAcceptExchangeServerLicenseTerms

*Use ADSIEdit to re-enable inheritance on on the object in AD

Any suggest for this problem?

Thank You