Hi All,

I recently inherited an environment that's had a handful of admins working on it, all of whom had varying competency levels and poor documentation habits (this story is pretty much a cliche by now, isn't it?). Personally, I have a few years of experience administering AD and Exchange in a DFL of 2008R2, but things were mostly set up correctly in that environment and I typically didn't have to dig in too deeply.  I'm working on some training to improve my knowledge, but at the moment I'm definitely still lacking in many areas.  I've been asked to install some shiny new 2012 servers, retired the old 2003 DC and 2008 DC, raise the domain functional level, and in general get our environment at my new employer up to date.

In the past, this environment was migrated from a 2003 Exchange server, possibly to a 2007 at some point, and now is running on a 2010SP3. One or both of the previous iterations of Exchange was running on the 2003 domain controller that until a week ago was the holder for all FSMO roles in the domain. I have the new DCs spun up, joined, and replicating.  I'm ready to remove the old 2003 DC. I decided to simply shut it down for a few days before doing anything more difficult to undo. When I shut it down to make sure things still work without it, Exchange breaks. I can fire it back up again and Exchange works. 

I have been told by other people in the organization that they remember a previous admin saying something about needing to keep some service routing through the old exchange server (the 2003 DC) to make it work, and if I run an organizational health report in the EMC, it comes up with 2 servers. The problem is that in server management, I only see the 2010 exchange server present, so I don't know what's relying on the 2003 machine. It sounds like the previous people also did a lot of messing with DNS that they didn't quite understand too, so it's possible this isn't even directly an Exchange issue. Since I'm seeing 2 servers reported when there should only be one however, that seems like a really good place to start.

Anyone have any ideas?

i got this error after  any idea ?

Get-MailUser "usertest" |New-MoveRequest -RemoteLegacy -TargetDatabase "test01" -baditemlimit 10 -RemoteGlobalCatalog $remoteGC -RemoteCredential $remoteCredentials -TargetDeliveryDomain $domainTarget

MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    ......
    Lid: 15000   dwParam: 0x6BA      Msg: EEInfo: prm[2]: Pointer val: 0x51C8A8C000000000
    Lid: 16280   dwParam: 0x6BA      Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x6BA      Msg: EEInfo: ProcessID: 19796
    Lid: 12696   dwParam: 0x6BA      Msg: EEInfo: Generation Time: 2015-01-14 20:21:54:210
    Lid: 10648   dwParam: 0x6BA      Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x6BA      Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x6BA      Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x6BA      Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x6BA      Msg: EEInfo: NumberOfParameters: 0
    Lid: 45169   StoreEc: 0x977
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52209   StoreEc: 0x977
    Lid: 56583
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : FBB4FBA6,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

Hi I am installing Exchange 2013 SP1 in a test environment. This server will coexist with an Exchange 2007 server.

Both the Exchange 2013 server and the 2007 server are standalone servers with all roles installed.  I understand that the mail flow has changed some in 2013.

On my current Exchange 2007 server, the Client and Default Connectors are disabled.  I then have two additional connectors that were created, the 1st receives incoming internet mail from our spam gateway, and the 2nd receives mail from a few select internal clients that send via SMTP (example: printers and copiers, server application alerts)

My question is regarding the setup of receive connectors on the new 2013 servers. I have already duplicated the 2 connectors that are on 2007. Which of the default receive connectorscan I disable on Exchange 2013?  thanks

Hi all,

I would need to setup an exchange 2013 in new data center and coexist with exchange 2010 (server room).

Hoping you guys can shed some lights on this. below is the existing exchange 2010 info

AD single forest Domain : ABC.local
Email STMP address : @temp.com
1 x Exchange 2010 server (CAS/HUB/Mailbox), 1 x Third Party Mail Gateway/SPAM (Data center)

Public DNS record
MX record : temp.com (using godaddy)
A record - mobile.silver.com (OWA/EAS) -using netregistry.net
A record - oa.silver.com (outlook anywhere) using netregistry.net

Internal DNS record

-A record for exchange server only

Virtual Direcotory (Exchange 2010)
Internal URL : server1.abc.local/owa
                     server1.abc.local/activesync
                     server1.abc.local/oab
                     server1.abc.local/EWS
                     server1.abc.local/Microsoft-Server-ActiveSync

External URL : mobile.silver.com/owa
                      mobile.silver.com/activesync
                      mobile.silver.com/oab
                      mobile.silver.com/EWS
                      mobile.silver.com/Microsoft-Server-ActiveSync

Outlook Anywhere
ExternalHostname : oa.silver.com
ClientAuthenticationMethod : Basic

Public SSL
Subject Alternative Name
-DNS Name=oa.silver.com
-DNS Name=abc.local
-DNS Name=mobile.silver.com

What I am planning to do on Exchange 2013 (new AD site)

1. Upgrade Exchange 2010 to SP3 with latest roll u

2. Install Exchange 2013(multi role) with SP1 and latest roll up (Install pre-requisites, Prepare schema/AD)

3. Obtain Public SSL (SAN- mail.temp.com, autodisover.temp.com),

4. Configure pinpoint DNS (mail.temp.com, autodiscover.temp.com)

5. Change all Internal & External Vdir to https://mail.temp.com/<owa,etc>

6. Import & configure public SSL on Exchange 2013

7. Configure autodiscover URI (SCP) to https://autodiscover.cscms.com/autodiscover/autodiscover.xml

8. Create internal DNS record mail.temp.com, autodiscover.temp.com pointing to new Exchange 2013

9. Create A record, CNAME for mail.temp.com, autodiscover.temp.com on public domain temp.com that pointing to new public IP address by new ISP

10. Migrating mailbox, external mail will flow to exchange 2010 to exchange 2013

11. Mail flow cutover

Please can help to review the 11 steps? maybe something important things are missing?

To coexist with 2010, question is

1. I would like to remain two different namespace (silver.com & mail.temp.com) for Exchange 2010 & 2013.

    Will the Proxy redirection works? Since they are in different site and different namespace

2. Remain -autodiscoverServiceInternalURI with no change on Exchange 2010? since no internal or external DNS record

3. Do I need to add/change any configurations on receive/send connector in order to send email between Exchange user

    2010 & 2013?

4. As you can see the above point no.9, new public ip address for exchange 2013 mail.temp.com and existing public IP address.

    Meaning Exchange users 2010 will connect to mobile.silver.com while exchange users 2013 will connect to mail.temp.com. they will run independently?

5. For external mail flow, when to cutover after moving all user to exchange 2013?

 6. During the coexistence, The external mail flow (inbound) go through Exchange 2010 then 2013?

     If yes, anything need to be changed on the connector?

Thanks in advance :)

Hi

Can any budy share me the best deployment guide of Exchange server 2013 with DAG implementation on Hyper 2012

Also the sizing of mailbox database..

Good day all.  We have installed Exchange 2013 into our single server 2010 environment.  After a successful install I am not able to log onto the 2013 EAC.  I know that since my mailbox is still on 2010 that I should not see EAC unless I use the

https://server/ecp/?ExchClientVer=15 but this does not work either.

I opened a case with MS on this and got a response but I am confused as to one part of the instructions.  I replied to the engineer but she is offline for a few hours and I wanted to drop the instructions here and see if you know what it is that she is stating. 

Question that I need answered:  Below, at step 4 she left a note "Please run above command with your production install directory script". What you think this line means?  Run this script from the provided scripts that came with 2010?  Grab the script from 2013 files and run it on the 2010 server?  or run this script on the 2013 server?

Thanks in advance!

Action Plan
=========
1.    Recreate the ECP virtual directories on exchange 2013 server with the following commands (Run as Administrator) on EMS:

Remove-EcpVirtualDirectory -Identity "Server2013\ecp (Default Web Site)”

New-EcpVirtualDirectory -Server Server2013 -InternalURL https://Server2013.domain.com/ecp

Set-ECPVirtualDirectory -Identity "Server2013\ecp (Default Web Site)” -AdminEnabled $True

2.    Recycle MSExchangeOwaAppPool under IIS, Application Pools.

3.    Ran "iisreset" on EMS.

4.    Ran the "UpdateCAS.ps1" powershell script from the Exchange install directory scripts subfolder. The command example is as follows:

C:\Program Files\Microsoft\Exchange Server\V15\Bin>.\UpdateCas.ps1

Note: Please run above command with your production install directory script.

5.    Open the IIS manager, find the Exchange Back End site, double-click Authentication on the right “/ecp Home” page. Point to Windows Authentication after launching Authentication windows. Right-click windows authentication, point to Providers. Make sure Negotiate and NTLM under Enabled Providers. You can refer to the related screenshot from my test environment as below:

6.    Then re-run "iisreset" EMS.
=========

Hi all!

I install Exchange Server 2013,but for some reasons I copy the installation files to a folder in my server, but spanish language not copy with that, after installation I try to select spanish language in my ECP an OWA but cant do that because spanish not exist in options...

please need help!!!

I am having an issue trying to move over my public folders from my 2010 server to my 2013 server.  It keeps on failing or not even starting the move. I am petty sure this coming down to1 folder I have called 'Helpful Websites' from previous versions of Exchange that has been moved over a few times. I can't delete the folder no matter what I try. I have owner access to the folder. This is the error I get trying to delete it. I don't need it and nothing is in the folder anymore.

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Action 'Remove' could not be performed on object 'HelpfulWebsites'.

HelpfulWebsites
Failed
Error:
Cannot delete the object '\XXXXXXXXXCorporateForms\HelpfulWebsites'. Please make sure that you specified the correct identity and that you have the correct permissions to delete it.

MapiExceptionPartialCompletion: Unable to delete folder. (hr=0x40680, ec=0)
Diagnostic context:
    Lid: 40487   EMSMDBMT.EcDoRpcExt2 called [length=61]
    Lid: 56871   EMSMDBMT.EcDoRpcExt2 returned [ec=0x0][length=173][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropDeleteFolder [29]
    Lid: 17082   ROP Error: 0x80070005
    Lid: 19297  
    Lid: 21921   StoreEc: 0x80070005
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropDeleteFolder [29]
    Lid: 4887    StoreEc: 0x80070005
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849  
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 24721  
    Lid: 20625   StoreEc: 0x80070005




--------------------------------------------------------
OK
--------------------------------------------------------

I can remove other folders without issue but I think if this one is gone I can migrate them over with no issue. My Public Folders are very small like 200MB is all.

Hi,

For some reason, my Exchange servers are no longer updating. Im getting error code 80072EFD.

I have googled this and found a few articles suggesting Time mismatch and a root certificate missing. This is not the case as I have checked both...

Any other ideas? This seems to have happened after I have applied CU5 on one of the servers.

Thanks in advance.

Hello,

In our environment, we used to have exchange 2003 but the server is crashed and not turning on. Also, we are not concerned about restoring its data.

I want to install Exchange 2013 but am not able to do so as the AD is still recognizing that there was an exchange 2003 version installed.

What is the best way to clean the active directory so that I can proceed with installing the exchange 2013? My current environment is based on Windows 2012.

Thank you

Goldenberg

ok, All I keep reading is how people keep on having issues moving public folders over and you get the most cryptic error that can mean anything. I don;t have mail enabled on any of the folders so I have no Alias's.  My public folders are not that large so I was just thinking of coping them to my mailbox since its only like 200MB and just deleting the whole PF database on my Exchange 2010 server and just make all new on my 2013 server. Has anyone done thin and had issues? I just don't want to make more problems. This one of the last steps to dump my 2010 server so I want this done. Here is the error if anyone knows of a fast solution. I removed all the spaces and non-characters so I am not sure why this is still showing.

RunspaceId                       : 8fd513de-9601-4770-8035-bef7a8ab46ed
Name                             : True
Status                           : Failed
StatusDetail                     : FailedOther
SyncStage                        : CreatingFolderHierarchy
Flags                            : IntraOrg, Pull, Suspend, SuspendWhenReadyToComplete
RequestStyle                     : IntraOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : True
SourceVersion                    : Version 14.3 (Build 174.0)
SourceDatabase                   : StaffPublic
SourceServer                     : HQEXCH1.staffing.local
BatchName                        :
OutlookAnywhereHostName          :
RemoteCredentialUsername         :
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            :
RemoteMailboxServerLegacyDN      :
BadItemLimit                     : 500
BadItemsEncountered              : 0
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {\}
QueuedTimestamp                  : 1/15/2015 10:32:50 AM
StartTimestamp                   : 1/15/2015 10:32:56 AM
LastUpdateTimestamp              : 1/15/2015 10:32:56 AM
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp               :
CompletionTimestamp              :
SuspendedTimestamp               :
OverallDuration                  : 00:00:06
TotalFinalizationDuration        :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration           :
TotalFailedDuration              : 00:00:00
TotalQueuedDuration              : 00:00:01
TotalInProgressDuration          : 00:00:05
TotalStalledDueToCIDuration      :
TotalStalledDueToHADuration      :
TotalStalledDueToReadThrottle    :
TotalStalledDueToWriteThrottle   :
TotalStalledDueToReadCpu         :
TotalStalledDueToWriteCpu        :
TotalStalledDueToReadUnknown     :
TotalStalledDueToWriteUnknown    :
TotalTransientFailureDuration    :
TotalIdleDuration                : 00:00:04
MRSServerName                    :
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 : 0 B (0 bytes)
BytesTransferredPerMinute        :
ItemsTransferred                 : 0
PercentComplete                  : 10
PositionInQueue                  :
PreventCompletion                : True
FailureCode                      : -2146233088
FailureType                      : DataValidationException
FailureSide                      : Target
Message                          : Error: Property expression "Staffing Network Corporate Forms" isn't valid. Valid
                                   values are: Strings formed with characters from A to Z (uppercase or lowercase),
                                   digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One
                                   or more periods may be embedded in an alias, but each period should be preceded and
                                   followed by at least one of the other characters. Unicode characters from U+00A1 to
                                   U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII
                                   string in the e-mail address, which is generated from such an alias.
FailureTimestamp                 : 1/15/2015 10:32:56 AM
IsValid                          : True
ValidationMessage                :
OrganizationId                   :
RequestGuid                      : 703a17ee-d88e-41ae-be43-d7382638e3c0
RequestQueue                     : IL-Corp
ExchangeGuid                     : 03a6c02d-19a4-404c-b00f-4de13a9145ab
Identity                         : 4e173ad7-aa2f-46e6-8528-792620337d93\703a17ee-d88e-41ae-be43-d7382638e3c0
DiagnosticInfo                   :
Report                           : 1/15/2015 10:32:50 AM [HQMAIL1] 'staffing.local/Users/Administrator' created
                                   request.
                                   1/15/2015 10:32:56 AM [HQMAIL1] The Microsoft Exchange Mailbox Replication service
                                   'HQMAIL1.staffing.local' (15.0.847.31 caps:03FF) is examining the request.
                                   1/15/2015 10:32:56 AM [HQMAIL1] Connected to target mailbox
                                   '03a6c02d-19a4-404c-b00f-4de13a9145ab', database 'IL-Corp', Mailbox server
                                   'HQMAIL1.staffing.local' Version 15.0 (Build 847.0), proxy server
                                   'HQMAIL1.staffing.local' 15.0.847.31 caps:1FFFCB07FFFF.
                                   1/15/2015 10:32:56 AM [HQMAIL1] Connected to source mailbox '', database
                                   'StaffPublic', Mailbox server 'HQEXCH1.staffing.local' Version 14.3 (Build 174.0).
                                   1/15/2015 10:32:56 AM [HQMAIL1] Request processing started.
                                   1/15/2015 10:32:56 AM [HQMAIL1] Cleared sync state for request
                                   00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                   1/15/2015 10:32:56 AM [HQMAIL1] Stage: CreatingFolderHierarchy. Percent complete:
                                   10.
                                   1/15/2015 10:32:56 AM [HQMAIL1] Initializing folder hierarchy from mailbox '': 47
                                   folders total.
                                   1/15/2015 10:32:56 AM [HQMAIL1] Folder creation progress: 0 folders created in
                                   mailbox '03a6c02d-19a4-404c-b00f-4de13a9145ab'.
                                   1/15/2015 10:32:56 AM [HQMAIL1] Fatal error DataValidationException has occurred.

ObjectState                      : New

Hi All ,

How to configure Exchange 2013 OWA with Single Sign On ?

Thanks .

Fabio Martins MCDST/MCSA Brasil!!!

Can I setup the Exchange Server in our depot and then bring it to our clients site and join it to active directory?

Can I set it up without extended the schema?

Thank you for your help!

Bonnie

Bonnie Whalon

Hi there,

Currently we have Exchange 2010 environment 3 MBX with CAS role and 1 CAS dedicated for External Client request. Also OutlookAnywhere is already enabled on Exchange 2010 CAS box's.

We are planning to install Exchange 2013 server in our environment and our plan is to have 3 MBX and 2 CAS dedicated.

Both the Exchange 2013 CAS will be also be responsible for internal Client and external Client request.

I plan to install 2013 MBX boxes in the environment and then both CAS 2013.

Now my question is how can i ensure that the client request internally and Externally are configured to received on Exchange 2013 CAS server. 

Where all should i make changes on CAS 2013 to achieve the same so that Mailbox which are on Exchange 2010 still connects through Exchange 2013 till i completely migrate the mailboxs form exchange 2010 to exchange 2013 box.

Hope i got my point clear what i am expecting :)

BR/Deepak

Hi all. I implemented Exchange 2013 in my current Exchnage 2010 environment, update this server to version 15.0 build 847.32. Build Exch2010 - 14.3 (build 123.4). Then i move mailbox from exch2010 to exch2013 this request all time "queued" and not migrate to exch2013:

PS C:\Windows\system32> Get-MoveRequestStatistics Scom

DisplayName                         StatusDetail              TotalMailboxSize                   TotalArchiveSize                  PercentComplete 
-----------                         ------------              ----------------                   ----------------                  --------------- 
scom                                Queued                    575.3 KB (589,056 bytes)                                             0

I restart services Microsoft Exchange Replication, Microsoft Exchange Search, Microsoft Exchange Search Host Controller, but no result(

Hi,

this is our Scenario:

Server:

2x Windows Server 2013 running Hyper-V 2013

Each Hyper-V Server runs one Exchange 2013 CU3 15.0.775.38 November 2013

Clients:

Windows 7, Office 2010

Windows Server Active Directory, DNS, DHCP

Task:

We want to upgrade our Exchange Server to the most recent Version.

Problem:

The last time i tried to upgrade the Server, i completly lost the Exchange Server AND (!) all Active Directory Users/Groups.
so actualy im realy scared to touch anything.

afaik the install process will be like: start setup ( which is pretty much a new exchange installation ),it will remove the installed instance, reinstall the new version.

Questions

if every install is like a fresh install, do i have to reconfig all my exchange server settings ?

should i shut down both exchange server for "backup" reasons or does the fresh installed server
"need" the 2.nd server online ?

do you have any clue why all AD Users/Groups etc where removed when the former installation failed and how
can i prevent that from happening again ?

do you have a step by step howto upgrade to the newest exchange server version and which version would you recommend as i can see there are some big problems with the most recent one ?

thx in advance.

Hi,

i am in the middle of an exchange migration from 2007 to 2013.

I have users that only use Outlook from Homeoffice over Outlook Anywhere (RCP over HTTPS).

I have the problem that after migrating mailboxes from 2007 to 2013 the users must reconfigure their outlook settings to have access. I thought outlook will recognize this itself.
Do the users need to reconfigure their settings or should outlook do that automaticly?

If it should works automaticly what could be the problem that it does not work for me.

Both Servers are available over https and outlook anywhere is also configured.

regards,

Frank

Hi,

i am in the middle of an exchange migration from 2007 to 2013.

The public folders are still on the exchange 2007 servers.

Users that are migratated to the new 2013 server does not have access to the public folders via OWA oder Outlook Anywhere.
I got only a error message that it is not possible at the moment.

What must i do that migrated users will also have access via OWA and Outlook Anywhere?!

Frank