Looks like, for some reason, outlook is looking at the wrong mail server. Maybe because the main profile is 2007 but even when the 2nd profile is started with outlook its still wrong.
Generally when you migrate theres no need to re-do a users profile? Not sure why in this case there would be?
Its a Citrix thin client environment, which complicates things also. In a physical environment I am able to delete/recreate profiles - not so easy here.
I know this question may have been answered in a few different ways but want to see if anyone has done this before.
We have recently manually removed all the soft-deleted mailboxes from our Exchange 2010 server. There are still about 600 disconnected mailboxes that are in the databases due to a very long retention time. I know what some may be thinking but for this thread... it is what it is, lol. At any rate... We need to move all of these disconnected mailboxes to a new database in Exchange 2013.
So the plan at the moment is reconnect all of them and do a normal mailbox migration to the new server. Then disconnect them again.
The question in this post: Is there any other way to do it?
I appreciate it!
Hi,
I am having an issue with the migration of mailboxes from our Exchange 2010 server to our Exchange 2013 sever. I moved the mailbox from EX2010 to EX2013 using the EAC on the EX2013 server. The user moved was using Outlook 2010 to view and manage their mailbox with no issue before the move. When the user tries to open Outlook after the move they are getting the following message:
"Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)"
I have read through various posts and suggestions but so far nothing has helped. Our setup is:
Exchange 2013 installed on Windows Server 2012
Exchange 2010 installed on Windows Server 2008 R2 which is a virtual server running on the Exchange 2013 physical server
Our internal AD is different from our external DNS. We also host a copy of our external DNS records internally which point to internal IP addresses.
So far I have tried the following with no luck:
- Removed the .ost files and restarted Outlook
- Removed the mail profile and recreated
- Tried restarting the RPC Client Access Service on the Exchange 2013 server
- Created a new test user and added a mailbox to the Exchange 2013 server
- Tried to manually configure the Exchange settings for the Outlook client. When I did this it won't accept the FQDN of the Exchange 2013 server but when I enter the FQDN of the Exchange 2010 server it automatically changes it to the FQDN of the Exchange 2013
server. It looks like it knows the mailbox is on the Exchange 2013 server but then won't let me open it.
Can anyone help or point me in the right direction as I want to migrate these mailboxes asap so that I can retire the Exchange 2010 server.
Thanks
Peter Haase
Hi
A bit of a new-year challenge for anyone into Exchange server.
We are migrating from a Windows Small Business Server 2011 to Windows 2012R2 + Exchange 2013 on premise. Something I have done successfully for several clients over the past 2 years.
So I had a working WS2012R2 fully Windows updated as of last night, joined to the domain, Exchange prerequisites installed and all ready to install Exchange this morning.
This morning Exchange installed, it seemed happy enough with the install, we could access ECP web page happily and running powershell said that it was 'connected' to our new EX13 server. However when I run 'get-exchangeserver' only the Exchange 2010 server shows in the list, not the Exchange 13. Part of the problem with this is that powershell also didn't recognise the existence of the mailbox database, so trying to eg. move the edb path would fail. I forced it with 'configonly' or similar switch and manually moved the files, but I wasn't happy with the situation. Various attempts to repair and such didn't get very far until a force-delete of the PRogram files\Microsoft\Exchange Server folder
Eventually I ditched the new Exchange 2013 server install, reinstalled WS2012, re-install prerequisites and installed exchange in /m:recoverserver (and by the way /iacceptmicrosoftexchangeserverterms is a ridiculous switch to have to type so many times!). This time, following some advice I saw, I copied the install files to a local disk instead of installing Exchange from UNC. Same result, the server isn't listed and nor is the database in powershell, despite them both being listed and happy in the ECP.
As far as I can tell there are no network issues, AD is syncing and replicating happily between SBS11 and WS2012R2 (separate WS2012 to the Exchange install, obviously). I should also note that the download from the Action Pack site for Exchange SP1 wouldn't complete, so again following advice I found online I simply extracted the EX13 CU11 files and installed from there, IE not from an ISO download.
Anyone think of anything to try next?
Thanks
== Minor Update ==
Running get-exchangeserver -identity <myEx13Server> DOES return information, but still not showing in get-exchangeserver get-mailboxdatabase. I might have found an AD replication issue on one of my DCs but looking in ADSI Edit on that server, the Exchange13 server does show up under the administrative group, and also that server replicates without issue via AD Sites and Services. Thanks.
===== As a wise man once said to me - have a sense of proportion.
adsnow
Good afternoon,
I'm working towards finalizing my Exchange migration from 2010 to 2013; currently, we have been proxying between the two, but are gearing up to decommission the 2010 boxes. I've moved the majority of the users to 2013, and things have been working well. I have
a few questions about what else needs to be done and in what order.
1. Distribution Groups- I believe these are all set. They list ExchangeVersion 0.10 (14.0.100.0) when I do Get-DistributionGroup, but Set-DistributionGroup with the -ForceUpgrade parameter says it succeeded and no changes were made. I made a test group in the
2013 EAC and it lists the same version. Some confirmation would be nice.
2. Sharing and OWA Policy- It looks as though the 'Default Sharing Policy' is available on the 2013 CAS, using Get-SharingPolicy. It's ExchangeVersion is 0.10 (14.0.100.0), just like the Distribution Groups. The OWA policy I can find in the 2013 EAC,
as well as the 2010 management snap-in. How can I verify that when we turn off the 2010 boxes, these policies will not go away with it? Surely there is more to it than, 'It just works'? Is it a case of, as long as I can see it using the 2013 infrastructure,
it will work after decomissioning the 2010 boxes?
3. Am I missing anything else? I know we still have to configure the send/receive connecters.
Thanks for the help!
Sebulbasaur
Does anyone have any information on TLS 1.1/1.2 support for EWS? The deadline for PCI compliance is approaching fast and I can't find anything out about it.
I tested and it's still breaking EWS when you disable TLS 1.0.
Any information would be appreciated.
Thanks!
Hi- Single site, single domain. Migrating from 2010 single, stand-alone server to 2013, 3 dual-role VMs on Hyper-V, part of a DAG.
We've changed to a new namespace on the new installation. Most users are still on 2010. Since 2013 was introduced, some domains are not accepting email messages from users on the 2010 server.
"Last Error" messages in the Queue on 2010 refer to "Cannot find your reverse hostname" and "Reverse DNS Failure".
Doing a nslookup on the 2010 server of one of the domains comes back with the correct information.
I'm referencing a migration guide that is using the same namespace for the new installation, so I think I'm missing something.
Any help is greatly appreciated.
You should never, never doubt what nobody is sure about. -Willy Wonka
Hello Everyone,
I've been installing Exchange servers since Exchange 5.5. I'm now installing Exchange 2013 with SP1 that will coexist with one Exchange 2010 SP3 server. I'm installing it on 2012 R2 Enterprise Edition. There is a root domain and one child domain. The Exchange Server is in the child domain. Even though I've run the .\setup PrepareSchema, AD and domain and all were successful I still get the message below when running Exchange setup. If I look at what /preparedomain does it seems like it has done what is needed. I've run the /prepareschema, /preparead and /preparealldomains in the root domain & have even run /preparedomain over and over in the child domain. Like I said everytime I run these they are successful. Oh and my account belongs to all the right groups needed to run these. Any ideas would be appreciated!
The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DomainPrepRequired.aspx
Hello
I have newly installed windows server 2012 R2. No problem with that. Then i installed Exchange server 2013, set up Went ok.
The problem is that i cant log in at EAC. Wrong user or password?
Under the set up there were no show to put an admin user or password in.
Is there someone know whats the problem.
Hi,
Team,
I had moved all email address and contact address from exchange 2003 to exchange 2010. Now if i am trying to create new Email address policy in Exchange 2010 i am getting error message below is screen shot. Please help.
Team,
In my infrastructure we have two SMTP address showing for all users e.g.
1) ABC@cbs.com
2) XYZ@cbs.com
Primary is ABC@cbs.com. I want to remove secondary smtp address from all users. Please help me with the script and procedure
I tried to migrate PF from EX2007 to EX2013, but i ran into an error and made the
[PS] C:\Windows\system32>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server xyz) -CS
VData (Get-Content C:\pf\Foldertomailboxmap.csv -Encoding byte)
You cannot perform two types of Public Folder migration at the same time.
+ CategoryInfo : NotSpecified: (:) [New-PublicFolderMigrationRequest], MultiplePublicF...llowedException
+ FullyQualifiedErrorId : [Server=zxy,RequestId=20849fcf-14a4-4648-af8a-109451599fc2,TimeStamp=19.01.2016 09:45
:58] [FailureCategory=Cmdlet-MultiplePublicFolderMigrationTypesNotAllowedException] 4CE7226,Microsoft.Exchange.Man
agement.RecipientTasks.NewPublicFolderMigrationRequest
+ PSComputerName : zxy.domain.local
[PS] C:\Windows\system32>Get-PublicFolderMigrationRequest
[PS] C:\Windows\system32>
I would like to remove "old" Set-OrganizationConfig -PublicFolderMigrationComp
I removed and recreated Publicfolders in Exchange2013 and "Set-OrganizationConfig -PublicFolderMigrationComp
Hypocrit
------------------------------------------
Hi again,
Problem solved!!! Pending PublicfolderMigrationRequest are listed under:
CN=PublicFolderMailboxMigrationRequests,CN=Mailbox Replication,CN=Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=local
Just remove them with adsiedit and everything is good!!!
Hello,
I updated our Exchange servers over the weekend to CU11 and the mailbox C:\ drive is nearly full. I found some space (12 GB total now) quickly by deleting the CU11 installation files, but there is still a good 30 GB of extra data on the VM.
I also found some areas where I can cleanup log files and some temp files but it is only a few GB, so I was wondering if the following directory is the culprit:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Temp
Folder has 38.9 GB of data and accounts for roughly 33% of the entire C: drive. Seems to a likely suspect but I don't want to go deleting anything that is necessary.
Thanks
Chris
Dear All,
I presently i have one exchange server 2013 Cu9 it's working fine there is no problem i would like to implement another one exchange server 2013 CU10 when i try to prepare AD i got it error message
PrepareAD has either not been run or has not replicated to the domain controller used by Setup. Setup will attempt to use the Schema Master domain controller Main-Domain-Pr.KIMB.COM
[11/26/2015 05:46:47.0542] [0] The schema master domain controller is not available
[11/26/2015 05:46:47.0980] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Setup has determined that the schema master domain controller Main-Domain-Pr.KIMB.COM is not available or cannot be contacted. See the Exchange setup log for more information on this error.
How can i solve this issues please could you help me
Regards
Subash
MS Filtering Engine Update process was unsuccessful in contacting the Primary Update Path. Update Path http://forefrontdl.microsoft.com/server/scanengineupdate
How to fix this error or stop MS Filtering Engine Update becuase I use third party for scan virus ?
I following http://technet.microsoft.com/en-us/library/jj150526.aspx but error still appear on Event Viewer.
Currently at CU9 which is installed to D:
Ran CU11 update on our first archive server and it ran fine. On our second server, it appears to have failed part way through (its looking for scriptingagentconfig.xml file on C: drive).
Point being its ignored the install on D: drive and left it there but attempted to re-install to C: drive. So now I'm left with an install of CU9 on D: and a partial install on C: drive.
What to do now? If I use add/remove to remove the C: drive version there is going to be no installed version. I guess I could manually remove the D: drive version?
Fortunately, this was a (as of yet) unused archive mailbox server. I have reservations about doing this on one of our live mailbox servers and causing the same mess.
Problem is, it seems, even though the install process seems to detect its doing an upgrade, it can go wrong it seems. Ideally would be a way to specify the install directory to make absolutely sure...
Any ideas?
Hi,
I am planning to install exchange 2013 and coexistence with exchange 2010 , In my exchange 2010 my exchange organization name is "FirstOrganization" (no space between words )so while preparing AD for exchange 2013 , should i mention the same organization name or i can directly run PrepareAD command and that will not effect my coexistence.
Regards
Usman Ghani
Usman Ghani - MCITP Exchange 2010