Revert Back Exchange 2013 to Exchange 2010

Dear All,
I migrated Exchange 2010 to Exchange 2013 but was facing lot of issues on Windows XP clients with Office 2007 SP3 with November update. XP clients machine were continuously prompted user name and password and some times windows 7 with Office 2007 SP3 with
November update were also behaved like this. I googled alot but couldn't find any solutions.
Lastly decided to revert back to Exchange 2010, every thing went fine but again hurdles started on IMAP/POP3 clients that are not able to send email external domain but able to receive emails from external domains.
The other issue is in Exchange 2013 made some contacts which was deleted in Exchange 2013 but those contacts are now in GAL but couldn't find where these contacts are sit in and how to remove.
Kindly someone guide on those issues and specially on XP machine prompted username and password as I have to again migrate the users from Exchange 2010 to Exchange 2013.
Thanks,

here is the reply of error message
Delivery has failed to these recipients or groups:
Abc123 (Contact in Exchange 2010)
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: server.local.net
IMCEAEX-_O=FIRST+20ORGANIZATION_OU=First+20Administrative+20Group_cn=Recipients_cn=abc123.domain.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Original message headers:
Received: from server.local.net ([fe80::e07c:d3fe:2aeb]) by
server.local.net ([fe80::e07c:3ded:2aeb%11]) with mapi id 14.000;
Fri, 6 Feb 2015 17:57:09 +0500
Content-Type: application/ms-tnef; name="mail.mail.net"
Content-Transfer-Encoding: binary

Similar Messages

Install a temporary Exchange 2010 in an existing environment

I have an existing production environment with 3 Exchange 2010 servers in a DAG configuration working well.I would now like to verify the backups by restoring databases to a new Exchange 2010 server which I will only keep for a limited time.When installing Exchange 2010 I get "You must be member of the 'Organization Management' role group or 'Enterprise Admin' to continue"I assume this is because I need some specific permissions in Active Directory I don't normally have. I could very well use a different account which I'm fairly sure has these permissions, but I want to make sure I'm not introducing instability in our production environment by adding a fourth Exchange 2010 server which will then be deleted again.I have no intention of configuring the fourth server as a DAG member, but I'm not really an Exchange person and I'm looking...
This topic first appeared in the Spiceworks Community

Hi FriendzKnight
II,
Try to perform exchange 2010 recovery using the recovery switch. Build new exchange 2010 server and restore the exchange 2010 from the backup using recovery switch.
This will work to get back exchange 2010 in your existing exchange 2013 enivornment
Exchange Queries

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Exchange 2010-2013 Migration - Outlook Client gets "Your administrator has made a change..."

So we're migrating from an Exchange 2010 environment to Exchange 2013. We use a single namespace ("exchange.contoso.com") for both internal and external clients.
In testing, we have taken a few machines running outlook 2013 and 2010, and edited their hosts file such that "exchange.contoso.com" points toward the new exchange 2013 environment, rather than the 2010 environment for our users. So far so good,
they can connect, no issues.
However, when we move a mailbox to the 2013 environment, the outlook client comes back with "Your Exchange Administrator has made a change which requires you to restart outlook". This error affects both Outlook 2013 and 2010. We do have public
folders in place in exchange 2010, but we have not yet migrated them to 2013 (because the user's still are on 2010).
Repairing the profile is no help, and recreating the profile does not work either. Any thoughts?

Hi ,'
On you first post you have said you have put host file entries for the namespace "exchange.contoso.com"
in few of the client machines .
what about for autodiscover namespace did you have put any host entries for that .If not please put that
too in the host file of the client machines and then check by moving anyone of the mailbox from exchange 2010 to exchange 2013 .
Same time please check this blog especially on the end of the page .
http://blogs.msdn.com/b/aljackie/archive/2013/11/14/outlook-and-rpc-end-point-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook.aspx
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Outlook 2010, 2013 on new 2010 exchange server get windows security popup for password

We recently migrated exchange 2003 on 2003 server to Server 2008R2 and Exchange 2010 SP3. The installation had multiple problems and we resorted to Microsoft technical support for the server resolution. On the server level it seems to function
as expected. Our problem is with outlook 2010 and 2013. Some of these outlook 2010 installs existed prior to the exchange 2010 upgrade and worked as expected prior to the upgrade
Now with new machines (never been connected to our Domain) and some existing windows 7 machines with outlook 2010 and 2013, we get a windows security popup requesting the password.
We have spent a couple of weeks reading blogs, how two's and guaranteed fixes that don't fix. The best we can do is start outlook, get the folders to sync and shortly thereafter it will request the password. You can enter the password and
it comes right back requesting the password. You can cancel the request and you will get needs password in the area where it shows connected to exchange server and then will not prompt for another password until you need an update from the server
or you try to send and email. The email will not send until provide a password and immediately press send. Once in the outbox it will require the password again to send and then cancel the popup and repeat the process again.
Outlook test, turn off discovery, remove all credentials do not help. Outlook anywhere turned off. So far nothing seems to help.
Does anybody have a solution to my dilemma?

Hi,
Please check the problematic users' Outlook settings by the following steps:
1. Click File > Account Settings > Account Settings > Change > More settings.
2. In Security tab, make sure "Encrypt data between Microsoft Outlook and Microsoft Exchange" option is checked, "Always prompt for logon credentials" is unchecked.
3. Change the logon network security to Negotiate Authentication, and Apply > OK to set it.
Restart Outlook to have a try. If the issue persists, please
re-create Outlook profile to check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support
Thank you for the response.
I did as you suggested and the problem persists

Help needed with buggy Outlook 2013 and Exchange 2010 trashing profiles

Hi All,
I have a customer who has eschewed MOLP and buys all their Office OEM from Dell. So as a result they are starting to have more and more office 2013 be deployed. They have a SBS 2011 server with Exchange 2010 and it is patched to the latest
rollups and service packs. (SP3, RU2) Their Outlook 2010 and earlier clients are just peachy on this. But the Outlook 2013 clients are having problems.
What is going on is that periodically I'll get a complaint from a user that their Outlook 2013 is randomly crashing. In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default
and going back into Outlook 2013 and letting it rebuild the cached data on the PC. This seems to happen a few times a month with random users on the network.
I told the customer it was probably people not logging out of Outlook 2013 at night and their machines being power spiked but I think that's highly unlikely since it doesen't happen to the Outlook 2010 clients.
I don't know if any Microsoft developers read this but if you do, please take it back to your bug database. Any other suggestions would be appreciated (other than scotch Outlook 2013 - while I'd appreciate that, my customer wouldn't)

In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default and going back into Outlook 2013 and letting it rebuild the cached data on the PC.
The Outlook 2013 crash problem would be fix after you re-create a new profile and re-sync the data from Exchange, right?
When we meet the same problem in next time, I suggest we run the Outlook Product Stability Diagnostic tool to isolate known causes of crashes in Outlook. The Outlook Product Stability Diagnostic also creates a diagnostic report outlining the data it collected
and recommendations on possible steps you can take to reduce or eliminate Outlook stability issues.
Please click the following link to run the Outlook Product Stability Diagnostic tool in the Microsoft Fix it Center Pro portal:
Outlook Product Stability Diagnostic:
https://wc.ficp.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2764035
Other troubleshoot steps for Outlook 2013, please refer to the link below.
Let me know the result.
http://support.microsoft.com/kb/2632425/en-us
Tony Chen
TechNet Community Support

Introduce an "passive" Exchange 2013 in Exchange 2010 environment without user or administration impact.

Hi
We wish to introduce an Exchange 2013 server in our existing Exchange 2010 environment.
The Exchange 2013 server is only needed for migration purposes where we wish to leverage the new features of the migration-batch functionality.
It’s important that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, right now, since the customer wish to stay on 2010.
Can you guys come up with anything to be aware of?
Oblivious we disable the Autodiscover SCP for the Exchange 2013 server, so that the clients will not hit this server. Nor will we point any URLs to the Exchange 2013
I can see that a new “Default Offline Address Book (Exch2013)” is created and set as default when EX2013 is installed. We will change this back to the default EX2010.
The server will properly take part in the Shadow Redundancy feature, and is doesn’t seem to be possible to exclude the server or avoid, unless disabling Shadow Reduncancy.
I can only come up with these 3 things that will have a "direct" impact on the environment, but any input will be highly appreciated!
BR,
Martin

Hi,
I agree with Li Zhen’s suggestion. If you don’t migrate from Exchange 2010 to Exchange 2013, we can disable add services in Exchange 2013 and don’t use it any more.
If you want that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, please keep the published server to pointed to Exchange 2010. Then the original configuration in Exchange 2010
would not be changed to the new configuration in Exchange 2013.
If you want to use Exchange 2013, then we can point the published server to Exchange 2013 and configure the virtual directories in Exchange 2013. Though all mailboxes are still located in Exchange 2010, all external requests would be proxy or redirected
from CAS 2013 TO CAS 2010 automatically.
For more information about Client Connectivity in an Exchange 2013 Coexistence Environment, please refer to:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Regards,
Winnie Liang
TechNet Community Support

Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

I currently have an Exchange 2010 server with all the roles installed. Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error. When I installed Exchange 2013, I got an error saying I
had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left. There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group. This deletion caused my access
to my public folders to get messed up. I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA. I also get this error when
trying to access either Default or System Public Folders. "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
-server 'ExchangeServer' "
My Public Folder Database exists and is mounted. Any help is appreciated.

Hi Belinda,
Thank you for responding. Yes you do understand my problem correctly. One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA. I followed these steps in the below article:
http://blog.bruteforcetech.com/archives/766
After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
Here are the results to your requests:
et-PublicFolder -Recurse | Format-List Name
Name : IPM_SUBTREE
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
[PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
Name : NON_IPM_SUBTREE
Name : EFORMS REGISTRY
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

Outlook 2013 / Exchange 2010 constantly prompting for password

I as well as many users keep getting prompted for User/pass in outlook. This usually happens when I go from LAN to WIFI or from office to home. For example, If I close my laptop (not shut down) and head home then log back in and connect to my
VPN I usually get prompted for my user/pass for outlook. I type the correct user/pass but it does not accept and immeadiatly prompts for me to re enter. If I close down Outlook and re open the issue is fixed however this is not fixing this issue
and the owner of the company is receiving this error as well. I would like to find a solution so that either it does not prompt and automatically updates once it is reconnected with the network via VPN.
Any suggestions?
Thank you

I as well as many users keep getting prompted for User/pass in outlook. This usually happens when I go from LAN to WIFI or from office to home. For example, If I close my laptop (not shut down) and head home then log back in and connect to my
VPN I usually get prompted for my user/pass for outlook. I type the correct user/pass but it does not accept and immeadiatly prompts for me to re enter. If I close down Outlook and re open the issue is fixed however this is not fixing this issue
and the owner of the company is receiving this error as well. I would like to find a solution so that either it does not prompt and automatically updates once it is reconnected with the network via VPN.
Any suggestions?
Thank you
Outlook is simply not good at that with the existing protocols in Exchange 2010. Exchange 2013 uses MAPI over HTTP which may make that experience better.
Switching networks with Outlook open is typically not a good user experience.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010-2013 co-existence - need for OWA/ActiveSync legacy namespace?

Hi all
Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?
Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user
was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.
So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.
What did I overlook or not understand, or am I making migration more complex than needed?
Thanks for reading and best regards
/Maurice
PS: here were some of my pre-post readings:
Exchange 2003-2013 co-existence, even better
Exchange 2003-2013 co-existence,
Exchange 2010-2013 co-existence slides,
Upgrading ActiveSync to Exchange 2010,

Hi
Is that because External URL on Internet facing CAS servers were set to Blank，and Users are not able to get Updated URL
Please try to Add the External URL and made sure that all the required configurations are set Appropriately.
Also I suggest posting on Exchange ActiveSync Forum as well
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

Exchange 2010 - 2013 random auth.owa error

Hello,
I have an odd situation where we are preparing 2 exchange 2013 servers to migrate 2010 servers to
so currently:
2x Exchange 2010 (with dag)
2x Exchange 2013 (with dag).
Now it's behaving extremely odd when it comes to ECP for the 2013 servers.
randomly it works and doesn't work.
i generally try it from localhost on both 2013 servers, and individual server ip's from lets say 4 or 5 places.
all same login, and admin user is inside mailbox db DAG cluster.
now the problem:
it randomly pops up auth.owa error 500
when i say random i truly mean random, sometimes everything 100% works, i am able to login 100% from all servers.
then i check back lets say 2 hours later.. some obtain auth.owa errors while others work.
What i tried:
- I rebuild OWA (first with reset, then with remove and re-add method) on both 2013 servers.
- removed killbit file from 2013's
- rebuild exchange 2013's (just exchange it self).
- checked heartbeat monitor boxes and removed the null values.
It's safe to say i am kind of lost on what to try next.
i am also mistefied why it randomly works, i know it's internally loadbalanced, but shutting down 1 of the 2013 servers did not get rid of this strange behavior.
is it possible that the exchange 2010 servers play a part in this issue?
Any ideas, any help is very much welcome!.
Regards,
Marco
Key4ce - IT professionals: www.key4ce.eu

Hi,
Please check whether the Microsoft Forms Based Authentication service is running on all Exchange servers.
Similar thread for your reference:
https://social.technet.microsoft.com/Forums/exchange/en-US/8cf6886f-a96f-44f1-88ee-bd3a42349fa9/owa-brings-up-logon-screen-but-after-login-gives-http-500-internal-server-error
Also check the authentication configuration on CAS.
Get-OwaVirtualDirectory -Server <server name> | fl *auth*
Set-OwaVirtualDirectory -Identity " server name \owa (Default Web Site)" -FormsAuthentication $true
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

Latency leads to full system Failure in Exchange 2010 - Resolved in 2013?

My work encountered a bug - and for no lack of trying - I could not find any bug submission for Ex2010 anymore. Since Most programming relies on the foundation of the past - if replication service was implemented the same in 2013 than it could leave
to a full system failure.
The issue is something happened in REPLICATION service in such a fashion that it accepted a connection, and in the programming it set a variable to a LARGE NUMBER (fail closed) to replace for "Copy Queue
length" in the ball park of 922 quadrillion.
The service never updates this value because of its quasi-state and some timeout occurs and now the GOOD servers think their copy is ludicrously behind. This causes the GOOD servers to attempt to fail-over - as they believe their copy from the BAD
server has failed or perhaps another check fails...
[6 DAG pieces on 3 servers, 4 pieces per server]
In my scenario Server 3 holds:
1 part of server 2 <= Tells server 2 you're bad - don't fail over
1 part of server 1. <= Tells server 1 you're bad - don't fail over
2 parts its own <= "good" - though dead replication service
As I do not know if this exploitable by simply placing a listener in place of replication service to accept and do not respond to connections - I do not know. However, there is a "bug" or flaw in my opinion to allow 1 bad server to superceed
two good servers based on a partial service crash. Simply stopping replication service on Server 3 allowed Server 1 / 2 to take over with out issue - I then restarted replication service and no issue since.
Since i wasted an hour looking where to submit this - this forum will hopefully do - I am very much a white hat - but I am dislike the non-simple way before me to disclose said information to the creator. I want my hour back for their non-intuitive
process, or maybe the simply don't care about Exchange 2010.
- Dan

Please note "LATENCY" in my topic is not network but inter-process on a single host, and is used as saying a timeout occurs without value.

Addition of Exchange 2013 server to Exchange 2010 organization broke Exchange

This is somewhat of an emergency, since Exchange is down completely for us right now.
I just migrated from SBS2003 to Exchange 2010 on Windows 2012 over last weekend. Everything is now stable, and SBS2003 is shut down. Now I am attempting to migrate from Exchange 2010 to Exchange 2013.
The plan was this:
Install Exchange 2013 on another server (Windows 2008R2)
Wait until everything is replicated
Remove the Exchange 2010 server from the organization
Uninstall Exchange 2010
Install Exchange 2013 on the Windows 2012 server
Wait until everything is replicated
Remove Exchange 2013 from the Windows 2008R2 server
But here is what actually happened:
Installed all Exchange 2013 prerequisites on the Windows 2008R2 server
Began Exchange 2013 server setup on the Windows 2008R2 server. Included both Mailbox & CAS roles
At step 11 of 15 (not sure what that was, though), received this error message:
Error: The following error was generated when "$error.Clear();
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
" was run: "The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.".
And setup halted. I ran the netsh command via the command prompt, and it correctly said something about four rules being created or updated (not sure of exact verbiage). Now, when I try to restart setup, it says it is in the middle and will try to complete
but stays at 0%. But here is the most immediate issue:
Now I cannot access e-mail from any workstations (says Exchange server is unavailable)
Opening EMC on the Exchange 2010 server: I get as far as Microsoft Exchange -> Microsoft Exchange On-Premises and get this error:
The attempt to connect to http://[Exchange 2010 FQDN]/PowerShell using "Kerberos authentication failed: Processing data from remote server [Exchange 2010 FQDN] failed with the following error message:
Couldn't find Enterprise Organizaiton container. (Note that it refers to the local server as remote server)
I get an event 7031 on the Exchange 2010 server: The Microsoft Exchange Service Host service terminated unexpectedly
Opening the Exchange Management Shell on the Exchange 2010 server yields the same message regarding "Couldn't find the Enterprise Organization container..."
It also says, "Connecting to [Exchange 2013 server FQDN], then says connected to that server. Opening EMS on the Exchange 2013 server seems to connect correctly to the Exchange 2013 server, but there is no EM Console available there.
At this point, I am lost. I will continue to research this online but may have to call Microsoft soon, since we are entirely down at the moment. Any help is much appreciated!

All of the above, I believe. And E2003 is on the DC (and functioning just fine); E2012 on a member server (this is a very small environment--they have only the DC, a DB2 database server, and a lightly-used and old terminal server). I just spent 12 hours
on the phone with MS support on this issue, and it has now come down to this: the Exchange 2013 installation will not run to completion. It has failed repeatedly at a few points today, all related to the shell being unable to access Windows EXEs or environment
variables with variations on this error:
"...not recognized as the name of a cmdlet, function, script file, or operable program..." for each of these:
netsh (windows exe)
sc.exe (windows exe)
hostname (windows command that returns workstation name)
These all work from the command prompt. I am currently stuck on sc.exe failing on each attempt to install Exchange 2013 or Exchange 2013 SP1. Nor can I just remove it--it insists on attempting to proceed with installation even with the manual command-line
argument to remove it instead.
At this point, I am awaiting a night call back from Microsoft support, since the technician that worked on it with me for 12 hours today had to go home.

Archive Mailbox Duplicated - Exchange 2010/Outlook 2013

Hi,
I have enabled archive mailboxes for a number of users in an Exchange 2010 environment no problem.
There is one user though, that is seeing two online archives:
Online Archive - <Firstname> <Surname>
Online Archive - <email address>
Both are replicas of the other.
Any ideas how to get rid of the duplicate?

I just encountered the same issue. This has been going on for months with my mailbox and no one else's.
I can't tell you how many outlook profiles I created in attempt to fix this.
Originally I was running Outlook 2010 when the issue happened. In my case I had one archived named "Online Archive." The second one was named "Personal Archive." If I expanded either one, I could see the contents in it without issue, but
I couldn't expand the other. I didn't save the error message, but something about being unable to access it.
Once I started using 2013, both archives changed to be called "Online Archive," and were able to be expanded simultaneously. Any changes made in one were immediately reflected in the other. But it still left me with the duplicate archives.
I had reset my password using AD Users and Computers a number of times, but it was always set to the same password. This went on for probably 4 months. Finally I reset my password via ctrl+alt+del. I closed outlook, made sure outlook.exe
wasn't running, opened it back up, and the duplicate archive is GONE!
I even reset the password back to the original one via AD Users and Computers and the duplicate archive has not come back.
Excellent detective skills walshyno_1. But I really want to know why this happens. How is it even possible that creating a different password would remove the duplicate Exchange archive view in Outlook?

OWA still lands at Exchange 2010 for users migrated from Exchange 2010 to 2013

I never had any issues with OWA redirection for a few users that I migrated from Exchange 2010-2013 initially. For users that I am migrating in the past few days, the OWA 2013 is landing on Exchange 2010 despite the mailbox being successfully migrated to
Exchange 2013.
Troubleshooting:
1. I have restarted the IIS Services
2. I have restarted MSExchangeOWAAppPool.
3. I have also checked the homeMDB attribute of the 2013 migrated user with the Exchange 2013 database.
I would really appreciate if anyone could share their experiences on similar issues.

I have checked it, the migration status is completed. In regard to the namespaces, both CAS 2010 and 2013 are set to mail.domain.com; CAS 2013 is the internet facing. I have also checked the internal access for OWA, it's the same scenario. Migrating them
back to 2010 and 2013 won't resolve the issue in my case, because the issue persists for every new user that I am migrating.
I recently found the following when I login with a user who is not effected and then logout:
1. Login in back with the affected user without closing the browser or clearing the cache, it lands at CAS 2013 OWA.
2. However, I get the below listed error message when I logout.
Your request couldn't be completed.
Click here to continue working.
This may have occurred for security reasons or because your session timed out.

Revert Back Exchange 2013 to Exchange 2010

Similar Messages

Maybe you are looking for