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,

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

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

Currently our exchange 2013 is setup for incoming & outgoing mail for abc.org. How can I setup a new domain 123.org?

I will need for 123.org to be primary, but if someone sends to abc.org we will still receive those emails.

Hello,

We currently are running Exch2013 CU5 in coexistance with Exch 2007.  We are almost done migrating all users off 2007, and hopefully will be able to decom them soon (unless something comes up forcing us to keep them).  We want to upgrade to cu6 or cu7.  The only complaint we have with cu5 is iOS syncs outlook notes.  if updated on the iOS device, the note is unreadable in outlook.  this will be a big deal for alot of our users.

Anyways, CU6 has document issues (and fixes) for coexistance with 2007.  at this time would it be advised to jump straight to cu7 or are their any issues that would make the upgrade to CU6 a better idea at this point?

let me know if any other info would be helpful.  Thanks.

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.

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

I'm trying to set up Exchange 2013.

There are two errors - not sure which one is fatal (perhaps both)

Eror 1: Setup encountered a problem while validating the state of Active Directory: The Active Directory organization configuration version (15870) is higher than Setup's version(15844). Therefore, PrepareAD can't be executed. See the Exchange setup log for more information on this error.

Error 2: Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group

The 2nd error surprises me because I've logged in with an account that has access to pretty much everything. I tried a second account, same result. Perhaps it has something to do with the process running as administrator.

Additional info: this is the 2nd time I have set up an Exchange 2013 server on the domain. This is probably why we have the version issue. I scrubbed the first server because it corrupted.

I have tried:

1. Installing from the dvd
2. Setup /PrepareAD /IAcceptExchangeServerLicenseTerms (on both the Exchange machine and the domain controller)
3. Deleting all the Exch containers in active directory (but not deleted entries from the schema)

Anyone help?

Roger

I am working on a on premise Exchange 2010 to 2013 migration (mailboxes are migrated) with a large public folder database (176GB).  The old server had a 5MB limit on PF attachment sizes, however, some older folders and some newer ones did not have a limit applied and has 15MB+ attachments.

After following the TechNet article to migration PF folders (have done this many times in the past without issues), the PF migration fails.  I have included the output from Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | FL below.  I have verified all connectors are set over 30MB, the attachment size limit on the old public folder has now been removed and set to unlimited (after the PF migration started).

I would like to know if there is a way to increase the attachment sizes on the PF migration.  I have found there are limits when moving to O365, but can't seem to find too much information on premise.

All attachments need to be moved.  I do not want to set the largeitemlimit and not migrate these attachments.

1/15/2015 5:13:00 PM [NH-CBGEX01] A large item was encountered: Item (IPM.Note)
Subject:"Re: Phoebe Berks - Delivery #2 - Scheme B cam 1", Size: 7.039 MB
(7,380,412 bytes), Folder:"06096 Phoebe Berks Cottages"
1/15/2015 5:13:10 PM [NH-CBGEX01] A large item was encountered: Item (IPM.Note)
Subject:"FW: Revised Switchgear Layout", Size: 14.17 MB (14,856,345 bytes),
Folder:"07100 CIA Utility Relocation"
1/15/2015 5:13:15 PM [NH-CBGEX01] A large item was encountered: Item (IPM.Note)
Subject:"RE: Revised Switchgear Layout", Size: 14.17 MB (14,857,325 bytes),
Folder:"07100 CIA Utility Relocation"
1/15/2015 5:13:15 PM [NH-CBGEX01] Stage: CopyingMessages. Percent complete: 43.
1/15/2015 5:13:15 PM [NH-CBGEX01] Copy progress: 156035/183221 messages, 44.95 GB
(48,263,255,527 bytes)/172.5 GB (185,234,779,443 bytes), 130/2389 folders completed.
1/15/2015 5:13:16 PM [NH-CBGEX01] Fatal error TooManyLargeItemsPermanentException
has occurred.

What can be done to increase the attachment limit on the on premise Exchange or force the migration to copy these large items?  Again removing them or manually migrating them is not really an option.

My Exchange 2013 setup reported the error below. Just wondering if someone has experienced this and how easy it was to fix.

Roger

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

I installed Exchange 2013 on 2 brand new Server 2012 virtual machines, one with the mailbox role and another with the CAS roles. The installation completed without errors but I cannot log on to the ECP (or OWA for that matter). As I enter my user/pass, the password field goes blank and a number of event log entries are added (see below).

I'm using the default administrator account (also Enterprise Admin, Domain Admin and member of the Organization Management security groups). I mail-enabled the account with enable-mailuser + enable-mailbox. I can execute Exchange Powershell cmdlets when logged on with this account, so security looks good.

The problem is OWA/ECP which consistenly logs the following errors when I attempt to access the OWA:

---------------------------------------------------------------------

I have spent hours wading through log files and posts, and cannot get my head around this one. 

While trying to install Exchange 2013, it gives an error that sp3 needs to be applied to exchange 2010.  There are no exchange 2010 servers on the network, the one the existed on a mail server was formatted along with the server. I have tried removing all the orphaned objects in AD without success. I have tried ADSI EDIT there are no containers containing exchange. How do i get exchage out of AD in order to proceed with the installation of exchange 2013.

I set up the first Exchange 2013 Server and issued a cert from our internal CA server on Windows Server 2012 R2. Everything worked with no errors and no cert warnings when accessing OWA (followed steps at: http://exchangeserverpro.com/create-ssl-certificate-request-exchange-2013/ and the related pages that one links to). That cert include the computer name of the first server and all the external names (mail.domain.com, autodiscover.domain.com, etc.)

However, when I added a second server and created a DAG (for redundancy and failover protection), I wasn't sure what to do about the cert. I just exported the cert from the first and imported it into the second, but I now get bad certificate errors on various devices, even though the DAG's name points to the first server. One thing I know I may have done wrong is left the name of the second server out of the certificate. I can correct that easily enough and produce a second certificate, but I'd like to know that's all that's needed before taking this step.

Should I just repeat the original process, but include the name of the second server on the certificate and issue one cert for both, or do I need to produce a second certificate just for the second server, and use that along side the existing cert issued to the first.

I am quite ignorant about this, so as much details as you could give me would be very much appreciated. Or, if you need any additional details from me to be able to help, just let me know and I'll be happy to provide as much info as I can gather.

Thanks,
Colin

Colin

The basic symptom is this: The PF migration appears to work perfectly but when trying to assign a user to test the new folders it still attempts to connect to the old folders even though the users's DefaultPublicFolderMailbox is set to the new server. Connection status in Outlook still shows a connection to the 2007 server.

I'm using the TechNet PF migration article: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

This is a single server migration from 2007 SP3 UR10 to 2013 CU5 Standard. The migration of mailboxes is complete with no errors and I'm trying to move the 100mb in public folders over to the 2013 server. Using several guides but once I've had problems I've switched to using the "standard" TechNet article as follows. I am creating only one PF mailbox since there are 10 folders and 100mb in data roughly. My Mailboxmap.csv file shows only the following:

"TargetMailbox","FolderPath"
"PFRoot","\"

The entire PF migration steps work flawlessly with no errors that I can see at all. I've rolled back and ran this process a half dozen times now to see if I've missed something.

I'm stuck on Step 8: Item #2 testing the migration from the test user in Outlook.

I've assigned the DefaultPublicFolderMailbox properties as that Item #2 shows me to do and if I use Get-Mailbox (test user) | Select DefaultPublicFolderMailbox command I see the new PFRoot mailbox listed as the default. However, the test user can't access the public folders at all. If I look in EAC I still see no public folders listed at all. If I use this guide:

http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part2.html

It shows after setting "Set-Mailbox PFRoot -PublicFolder -IsExcludedFromServingHierarchy $False" I should be able to see the public folders in EAC. However, I can see the PF mailbox (PFRoot) but no public folders at all in EAC.

Where do I go from here? Even though I have no errors I don't want to complete the migration because the test isn't working.

Jeremy Regehr

Hi Everyone,

I'm trying to migrate mailboxes from 2010 -> 2013 and I've com across an odd error.

I've put my skip limit to 5(for bad files), however this error seems to appear regardless. I'm not a Jets DB expert, but not being able to find a row seems quite serious. Any ideas?

Data migrated: 1004 MB (1,052,931,906 bytes) 
Migration rate: 0 B (0 bytes) 
Error: MigrationPermanentException: Error: MapiExceptionJetErrorPageNotInitialized: Unable to find table row. (hr=0x80004005, ec=-1019) Diagnostic context: ...... Lid: 52176 ClientVersion: 15.0.516.30 Lid: 50032 ServerVersion: 14.3.123.2 Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropGetContentsTable [5] Lid: 27962 ROP: ropSetColumns [18] Lid: 17082 ROP Error: 0xFFFFFC05 Lid: 27489 Lid: 21921 StoreEc: 0xFFFFFC05 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 1238 Remote Context Overflow Lid: 8756 StoreEc: 0xFFFFFC05 Lid: 58765 StoreEc: 0xFFFFFC05 Lid: 48425 StoreEc: 0xFFFFFC05 Lid: 6995 StoreEc: 0xFFFFFC05 PropTag: 0x67B50102 Lid: 4819 StoreEc: 0xFFFFFC05 Lid: 17692 Lid: 5587 StoreEc: 0xFFFFFC05 PropTag: 0xC1A84B0 Lid: 13300 StoreEc: 0xFFFFFC05 Lid: 21097 Lid: 39027 dwParam: 0x6BD Lid: 8756 StoreEc: 0xFFFFFC05 Lid: 58765 StoreEc: 0xFFFFFC05 Lid: 48425 StoreEc: 0xFFFFFC05 Lid: 5459 StoreEc: 0xFFFFFC05 PropTag: 0xC1A84B0 Lid: 6483 StoreEc: 0xFFFFFC05 PropTag: 0xC1A84B0 Lid: 59073 StoreEc: 0xFFFFFC05 Lid: 28220 Lid: 52321 StoreEc: 0xFFFFFC05 Lid: 46177 dwParam: 0xBFE629 Lid: 35937 StoreEc: 0xFFFFFC05 Lid: 44129 dwParam: 0x1183C6F Lid: 60513 StoreEc: 0xFFFFFC05 Lid: 48225 Lid: 9253 StoreEc: 0xFFFFFC05 Lid: 28104 Lid: 13861 StoreEc: 0xFFFFFC05 Lid: 27265 StoreEc: 0xFFFFFC05 Lid: 1750 ---- Remote Context End ---- Lid: 27962 ROP: ropFindRow [79] Lid: 17082 ROP Error: 0xFFFFFC05 Lid: 23649 Lid: 21921 StoreEc: 0xFFFFFC05 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropFindRow [79] Lid: 40685 StoreEc: 0xFFFFFC05 Lid: 28720 Lid: 11621 StoreEc: 0xFFFFFC05 Lid: 56781 StoreEc: 0xFFFFFC05 Lid: 21484 Lid: 23788 StoreEc: 0xFFFFFC05 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0xFFFFFC05 Lid: 29726 Lid: 18462 StoreEc: 0xFFFFFC05 

Hello,

I have been trying to troubleshoot why PST Capture 2.0 will not show all of the mailboxes from my Office 365 environment (Exchange Online). 

I am using a global administrator (Who is allowed for the Organization Management role)  in the connection settings and have used the following for the server settings:

smtp.office365.com

smtp.outlook.com

outlook.office365.com

pod#####.outlook.com

however when I used the pod url I was able to view all 50+ mailboxes for about 10 seconds before it only showed roughly 10 mailboxes.  However because the pod url changes it is not reliable. Is there anyway for me to force PST Capture to show all of the mailboxes that it finds?