We will be replacing our SBS2003 server with new (very beefy) hardware. We will use Windows 2012R2 as DC and ultimately Exchange 2013 (after installing 2010 first). Even though not recommended, we will install Exchange on the DC, as we have a tight budget
and won't require DAG. We have less than 15 users in AD & we plan to change the server name, so we can recreate the AD from scratch, so we realize this is not a true "migration".
If we change the server name on the new server, does this affect the import of Exchange mailboxes into 2010 as long as the usernames & email addresses are exactly the same?
Anything else to be aware of if changing the server name with regards to Exchange?
There were actually three PSTs that returned this error, but one of them imported fine when I retried. The other two fail so consistently that it seems like a user mailbox issue and not a PST issue (although this isn't 100% definitive). I came
to that conclusion after the following discoveries:
1) Performing a repair on these PSTs using SCANPST.EXE did not resolve the issue
2) Larger PSTs have imported fine (even to the same user mailbox)
3) Splitting these PSTs makes no difference (each is an archive, and I manually dragged the Inbox and Sent folders to separate newly created PSTs, when those failed the same way, I archived just a small portion of the data from those split PSTs into a new archive
PST, importing it also failed)
I also tried the following commands, and still got the same error when trying to import the same PSTs again afterwards:
Searching the net (and this forum) didn't turn up anything at all for me. Can anyone tell me what I should do next / how I should troubleshoot and/or fix this problem?
I have used a hybrid configuration for a while but have recently finished moving all mailboxes to 365 and I have also removed the Dir Sync so the authority point is 365, all DNS records point to 365 and mail flow is all directly to 365.
I have 2 on premise exchange servers that are doing nothing,
What are the steps to remove the hybrid configuration and remove these exchange servers from the domain?
hi, i have windows server 2008 r2 on hyper-V server 2012 R2.
when i was install microsoft exchane 2013 in step 3 i see the follwing error:
please help me. tanx
Error:
The following error was generated when "$error.Clear(); if ($RoleProductPlatform -eq "amd64") { $useAttachMode = $false; $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer"; $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1"; $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data"; $dataFolderPath = $fastDefaultDataFolderPath;
if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath)) { $useAttachMode = $true; } else { if ($RoleIsDatacenter -eq $true) { $preferredDataFolderPathRoot = "D:\"; if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot)) { $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData"; if ([System.IO.Directory]::Exists($dataFolderPath)) { $useAttachMode = $true; } } } }
if ($useAttachMode -eq $true) { &$command -action a -dataFolder $dataFolderPath -silent; } else { try { &$command -action i -dataFolder $dataFolderPath -silent; } catch { $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message; Write-ExchangeSetupLog -Error $errorMsg; &$command -action u -silent; try { if ([System.IO.Directory]::Exists($dataFolderPath)) { [System.IO.Directory]::Delete($dataFolderPath, $true); } } catch { $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message; Write-ExchangeSetupLog -Error $deleteErrorMsg; } } } } " was run: "Couldn’t attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesn’t contain old nodes belonging to the system 'Fsis'.".
Warning:
An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear(); if ($RoleProductPlatform -eq "amd64") { $useAttachMode = $false; $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer"; $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1"; $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data"; $dataFolderPath = $fastDefaultDataFolderPath;
if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath)) { $useAttachMode = $true; } else { if ($RoleIsDatacenter -eq $true) { $preferredDataFolderPathRoot = "D:\"; if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot)) { $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData"; if ([System.IO.Directory]::Exists($dataFolderPath)) { $useAttachMode = $true; } } } }
if ($useAttachMode -eq $true) { &$command -action a -dataFolder $dataFolderPath -silent; } else { try { &$command -action i -dataFolder $dataFolderPath -silent; } catch { $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message; Write-ExchangeSetupLog -Error $errorMsg; &$command -action u -silent; try { if ([System.IO.Directory]::Exists($dataFolderPath)) { [System.IO.Directory]::Delete($dataFolderPath, $true); } } catch { $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message; Write-ExchangeSetupLog -Error $deleteErrorMsg; } } } } " was run: "Couldn’t attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesn’t contain old nodes belonging to the system 'Fsis'.".
I have one Exchange 2013 RTM (CAS+MBX) server in organization and I wanna get HA by implementing additional Exchange 2013 server and create DAG.
Before installing new Exchange server I have a question about installing version that differ than existing one -can I install Exchange 2013 SP1 as additional server in infrastructure where Exchange 2013 RTM exists?
I imagine the following scenario:
install new Exchange 2013 SP1 server near existing Exchange 2013 RTM server
move all mailboxes from Exchange 2013 RTM server to Exchange 2013 SP1 server
add new server into CAS publishing farm on ARR
update or reinstall existing Exchange 2013 RTM to Exchange 2013 SP1
We have installed the certificate on all of our Exchange 2013 servers (5 combined CAS/Mailbox servers) that we are using on our F5 load balancer.
The problem is, if we have more than just one server active in the load balancing pool, you can't login via Outlook web. It looks like it's going to log you in. but then immediately kicks you back to the login screen. If we just have one server
in the load balancing pool, you can login and everything works as it should.
We have a case open with F5, but they seem to think they have only seen this problem when the SSL certificate doesn't match across all of the nodes. but in our case it does. I have escalated the case to see if they can troubleshoot more.
but is there something more I need to do besides what is in the article above? We have all of our URLs set correctly on all nodes.
I tried bypassing the load balancer and trying to use DNS round robin as a test, but HTTP headers confirmed I was only getting kept on one node once I attempted to login.
We are using F5 load balancers and setting up the configuration via the latest version of their Exchange iApp template.
Question 1: I have an Windows Server 2012 that is running Exchange 2010 that I would like to upgrade to Server 2012 R2. Is there any potential issues with this going forward?
Question 2: Upgrading my domain controllers from Server 2012 to Server 2012 R2, will this cause any potential problems?
I am
currently designing the new Excahnge 2013 environment that I am looking to deploy by the end of the month. And I have come up with two designs on what could be deployed. The first being an active/passive design with a single namespace across two sites.
One site being the primary site and the other being the secondary DR site in a single DAG. Now this is a common design and similar setups are documented in detail online on many blogs and such.
Where my trouble is with the second design I have come up with which is an active/active model using a multi namespace across the same two sites utilizing two DAGs. The idea here being the first
site is the corporate head office which would only contain those users. While the second site would contain everyone else not based out of the head office. The goal being to cut out internal users from connecting all of the way into the primary site when they
are external to it.
Now the way in which the network is setup between the two sites. Accessing the internet from the primary site requires you to go through the secondary. So for the second design my idea would
be for external Outlook, OWA and ActiveSync connections would connect into the secondary site for it to then proxy over to the primary. Now I am used to how Excahnge 2010 did its proxying and if the ExternalUrl property was blank is knew to proxy to the other
site. Is that still the case with Excahnge 2013 or it does not care at all and I can just populate both the internal/external url properties for all of the CAS servers at the primary site?
Now assuming I do populate both the internal/external url property in Excahnge 2013 for the primary site. And for this example I am going to use mail01.domainname.com for the primary site and
mail02.domainname.com for the second. To get Outlook, OWA and ActiveSync to connect for users of the primary site externally would it be as simple as having that external internet DNS entry for mail01.domainname.com point to the same IP as mail02.domainname.com
would be? With mail02.domainname.com pointing to a externally accessible load balancer for the second site.
Now applying the above logic and assuming as long as you hit a CAS server. And it will find your mailbox for you does that mean I can could also use the same namespace in both locations for
say OWA and ActiveSync? So the idea being we want to keep using webmail.domainname.com for OWA access. So if I set that URL for both the primary and secondary site as long as I hit a CAS server in the secondary site. It will be able to connect over to the
mailbox in the primary site for OWA?
I am little new to exchange and trying to learn it on my on as I i'll be getting new assignments for it in coming weeks. Hence I tried to configure a little exchange 2010 infrastructure in my lab environment.
I have configured a DC and have installed server with exchange 2010 HUB and CAS server role and another server with Mailbox server role. Have used Windows server 2008 r2 as a base operating system for the servers.
Now my problem post installation of the server roles is that I am unable to send email using owa(which work well) as when tried to send, the email automatically gets stored in the drafts folder where as when tried to use the MS Outlook 2010 the email shows
up under send items but the receiver never receives the email.
I am unable to google search this issue as I am unable to find the correct word to search it over the web.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com. Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013 Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013.
ISSUE
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.
I'm configuring outlook for the first use on a new machine, this was how I did:
1. Opened Mail in control panel.
2. Filled everything in the configuration dialog with my name, email address, password, the configuration went through 1. Establish Network Connections2. Retrieve the server settings of the mailbox. and suspended at 3. Logon to the server. It just keep pulling
up the credential dialog.
I tried to my account on my colleague's machine, it worked well. and I also tried to configure my colleague's account in outlook client in my machine, also worked, I even tried to configure my account in my own machine at home, it worked. I don't know what
the problem is, I even tried a couple of methods to add missing keys in registry table, still not working.
I have update Exchange server 2013 CU1 to SP1 (CAS Role). After upgrade mail cannot flow. all the mail are stuck.
CAS server use to mail flow outside and receive from outside. but The problem is this CAS server mail flow not work after upgrade exchange server 2013 CU1 to SP1.
I am importing PSTs that I got out of Exchange 2003 server in to Exchange 2013 SP1
Some of the import jobs are failing with the following error
FailureCode : -2146233088
FailureType : TooManyMissingItemsPermanentException
Message : Error: This mailbox exceeded the maximum number of corrupt or missing items that were specified for this request.
How can I increase the limit for corrupt or missing items ?
Hopping I would be able to restart the request with
Our organization is in the process of planning/designing our on-premise Exchange 2013 infrastructure. Currently we have an existing Exchange 2010/2007 coexist environment deployed as a resource forest. My question is it possible to deploy the new Exchange
2013 environment in another resource forest? So we would sort of have the following layout:
Image may be NSFW. Clik here to view.
The reason why we want to create a greenfield environment for the 2013 is because we still need to keep the 2010/2007 environment for restores and litigation reasons. We also just want to start off with a fresh install so we do not break any legacy applications
still relaying or utilizing the 2010/2007 forest.
Another question - if the model above is possible. How would GAL sync work? Would we need to do federated trust between the two Exchange organization?
I am currently trying to migrate our public folders to the new server, but it is going very slowly, and it fails after working for some time.
In my report for the migration I keep getting these errors:
1/17/2014 9:42:27 AM [WINSRV01] Transient error ResourceUnhealthyException has occurred. The system will retry (14/60).
1/17/2014 9:42:35 AM [WINSRV01] The move is currently stalled due to 'Remote Resource' lagging behind on resource 'Resource 'CiRetryQueueSize(New Mailbox Database)' is unhealthy and shouldn't be accessed.'.
My contentindexretryqueuesize is currently about 7000.
I started an the upgrade on our Exchange 2013 Standard server last night. It was previously on CU3 and I'm updating it to SP1.
It's been 13 hours and it's still only on step 14 of 18.
Our server meets the minimum hardware requirements for Exchange 2013, although we are on the very low end for RAM (8 GB).
Do others have similar experiences? How long did it take you to install SP1?
Besides having a test environment or running high availability does anybody have tips for how to speed up this process?
EDIT: After reviewing the logs (see my first response below) I see that the Set-LocalPermissions cmdlet is taking over an hour to run each time it's called. Any idea why that would be?
