http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-EABEAgAAQAAAAQECAQAAAAg~
So I'm about to do this, but the guide doesn't mention 2010 really, will the move affect any 2010 functionality? I will likely need months to migrate all users from 2010 to 2013 and am nowhere near ready configuring Exchange 2013 to start receiving emails (I publish Exchange in TMG), does that need to be configured prior to moving this mailbox as well?
Hey All,
Quick one on the Legacy Namespace;
I've created the nspace and added it in as a DNS entry and pointed this to the EX07 environment, I have now added to nspace into our SAN Cert for X13. I'll will then change the X7 URLs to be the same nspace as the Legacy.Domain.suffix. But how does the EX13 know to look for the legacy nspace do I need to set something on the X13 CAS?
Cheers,
Hello every one.
I have a problem to setup a lab asigment for school.
I have 2 Windows 2012 standard server
1e AD, DNS, IIS
2e Exchange 2013 SP1 64x
i prepared AD and installed al the features needed for AD and the Exchange server.
But when i run the readines check before i install Exchange 2013 i get to following warning
Warning:
A checked build of the operating system is installed. This can cause system instability issues including crashes, hangs, and other performance problems. It's highly recommended that the operating system be reinstalled with a non-checked build.
For more information, visit: http:// technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.OSCheckedBuild.aspx
I cant find out what to do, thear is no Boot.ini file in Windows server 2012, any one any idea's to solve this problem
Thanks for the help,
Greatings,
Hope you can help,
i have an existing Exchange server 2013 set up for multi-tenant Environment, i am looking to add an additional server (virtualised).
If i add a new Exchange server without the /hosted clause will it all just work as the setting are held in AD?
hi,
Recently we have migrated from exchange 2010 to 2013. now the outlook clients are not discover the new server. My domain in xyz.com and my mail domain is xyz.co.in
autodiscover works fine with autodiscover.xyz.com but not autodiscover.xyz.co.in
when I use Microsoft Connectivity Analyzer it fails because it search for
https://xyz.co.in/AutoDiscover/AutoDiscover.xml
https://xyz.provana.co.in/AutoDiscover/AutoDiscover.xml
how can I solve this issue.
Well, Typical Microsoft Errors... I have searched all over and can't seem the find the issue. I know and have confirmed that the Microsoft Identity Extensions are installed and are working. The MicrosoftIdentityExtensions.msi is also installed. I have passed all rerequisites and all looks good up until this point. My Topology was pushed out sucessfully and all seems good but I can't seem to figure out this issue. I am creating a Stand Alone Lync Server for the IM/Chat feature. I am running the Lync Server 2013 on Windows Server 2008 R2 and it is a VM with the undated VM tools. I have all patches and updates on the server.
Any help would be great.
My Error:
Microsoft Lync Server 2013, Front End Server installation requires that Microsoft Identity Extensions is already installed. Either use Setup.exe for installation or run MicrosoftIdentityExtensions.msi included with the product to install the redistributable.failure code 1603
Error returned while installing Server.msi(Feature_Server), code 1603. Please consult log at C:\Users\administrator.LTF\AppData\Local\Temp\2\Add-Server.msi-Feature_Server-[2014_04_29][11_32_57].log
Hi
Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13 and EXC10 ip adresses (Round Robin).
I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
get:
A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?
Hello,
get-mailboxdatabase "db1" | get-mailbox
shows all the users which are in that db1 mailbox database. However, the "Servername" is wrong for the majority of the users. Previously that environment had 2 exchange servers in DAG. At some point in time, DAG config and the environment got completely corrupt, the end result, out of 2 Exchange servers, MBX1 and MBX2, MBX2 survived and running all the databases. However as a result of the previous problems, the output of the above command points 90% of the users are located on MBX1, whereas 10% on MBX2. All of them are located on DB1.
I would like to fix the situation, for this I have installed new Exchange 2013 server, planning on moving all the mailboxes to the new server, format the other one and recreate, thus creating clean DAG config. However I can't migrate mailboxes to the new server, getting error: "StalledDueToReadUnknown" , which probably corresponds to the described situation.
Any suggestions as to how to proceed and resolve the issue? I don't really like the idea exporting everyone to PST and import them all to the new DB. Perhaps there's a more elegant solution?
When running "get-mailbox user | ft" for one of the problematic users, I see that the below values are pointing to the old server
ServerLegacyDNPerhaps there are more attributes to fix?
Thanks.
Memento Mori
Hi folks, I need to know how to migrate room and equipment mailboxes cross-forest from an Ex2010 forest to a Ex2013 forest. For the time being, the Ex2013 forest is just going to be a Resource Forest. We've got an ERP system (and other things) to plan for before we actually migrate the AD accounts/computers, etc. I've got the process down for normal mail users, but need some guidance on rooms and equipment.
When I tried running the Prepare-MoveRequest script for a 2010 Room, it created a disabled mail user in 2013. Will this convert to a room mailbox once we migrate the Room mailbox? If not, what's the correct way to do such a move?
There are only about 100 mailboxes, we're migrating over a two night period, so we aren't worried about a plan for any coexistence.
We are performing a server migration and after moving a group of pilot users from Exchange 2003 to Exchange 2007, they are reporting duplicate items (emails, calendar, contacts, etc.) in Outlook. What could be causing this to happen and how do we prevent it? What's the best way to fix the existing duplicates? The duplicates have sync'd to the server as they show up in Outlook Webmail as well.
Thank you
Hello,
i'have a single Exchange 2010(sp3) and i have just deployed a new Exchange 2013(sp1), mail flow from/to internet is working without problem, but when i try to send email from/to internal users located to 2010 server i have no success, no error, nothing.
What i can check on both server to understand what's wrong?
Thanks for help.
Hi,
we have 4 exchange 2010 servers, 2 mailbox and 2 hubcas. we are migration to 4 exchange 2013 servers, 2 mailbox and 2 hubcas.
exchange 2013 user can send and receive emails from/to internet without problems, but when i try to send email to internal users located to 2010 server i have no success.
i also can receive from exchange 2010, so the problem is only i cannot sent emails to exchange 2010 users.
is this a problem with receive connector of exchange 2010 or something else ???
I Have windows 2012 DC installed and This is a production server, I know that Its not recommended to install exchange server on the DC. I had to do it because of management instructions.
I have tried to install the exchange 2013 and received many errors at the time of installations and then finally I changed the path for installation to D drive. its installed successfully.
The issue is its not opening the OWA or ECP.
The owa virtual directory got deleted as part of troubleshooting to recreate it. but after that its not creating, I reset the iis and created the virtual drive for owa from the iis console but not through powershell and then i thought to install the SP1 so that it can be fixed.
At the time of installation client access front end service role ..it gives error
Error:
The following error was generated when "$error.Clear();
$FEOWAVdirIdentity = $RoleNetBIOSName + "\OWA (Default Web Site)";
$FEOWAVdir = get-OwaVirtualDirectory -Identity $FEOWAVdirIdentity -DomainController $RoleDomainController;
if ($FEOWAVdir -ne $null)
{
Set-OwaVirtualDirectory -Identity $FEOWAVdir.Identity -ExternalUrl $FEOWAVdir.ExternalUrl -InternalUrl $FEOWAVdir.InternalUrl -ExternalAuthenticationMethods $FEOWAVdir.ExternalAuthenticationMethods
-BasicAuthentication ([Convert]::ToBoolean($FEOWAVdir.BasicAuthentication)) -WindowsAuthentication ([Convert]::ToBoolean($FEOWAVdir.WindowsAuthentication)) -DigestAuthentication ([Convert]::ToBoolean($FEOWAVdir.DigestAuthentication)) -FormsAuthentication ([Convert]::ToBoolean($FEOWAVdir.FormsAuthentication))
-LiveIdAuthentication ([Convert]::ToBoolean($FEOWAVdir.LiveIdAuthentication)) -OAuthAuthentication ([Convert]::ToBoolean($FEOWAVdir.OAuthAuthentication));
}
" was run: "You must set a default domain if LogonFormat is set to UserName.".
Hello,
We recently migrated to Office365 but had an issue since we need more than 16 simultaneous connections to a single mailbox. Because of this, we need to deploy a local Exchange Server that will be used to host a single mailbox that requires up to 500 simultaneous connections for a Contact Center application. I'm looking for information on how to setup the local Exchange Server to basically create a local instance of a mailbox hosted on Office 365. So we can have our application open the numerous simultaneous connections to our local server which will then connection to Office 365 to send/receive email through the mailbox hosted on Office365.
Please let me know if you have any information or resources you can direct me toward.
Thanks,
Chris
So I'm trying to get my head around a coexistence implementation of Exchange 2010/2013, following the Exchange Server Deployment Assistant.
I would have thought I would use the same external hostnames for my Exchange 2013 server as my 2010 servers, to be used for the likes of Outlook Anywhere,but should I actually be using different hostnames to keep them separate?
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-EQBEAgAAQAAAAQECAQAAAAg%7e
Similarly I thought I'd just leave the Autodiscover the same for 2010 and 2013,is that correct approach?
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-EgBEAgAAQAAAAQECAQAAAAg%7e
If I update the 2010 Autodiscover hostnames to point to 2013, even though all my mailboxes are still on 2010, wont that affect 2010 functionality?Assuming the hostname isnt the same of course.
Anyone perhaps know of a better guide to follow to setup a 2010/2013 coexistence? Just with a bit more details and assurances in regards to each step compared to the Exchange Server Deployment Assistant?
Hi,
does anybody have any links to good sites that gives some pros/cons when it comes to the mailbox database sizes in exchange 2013? I've tried to google it - but hasn't found any good answers. I would like to know if I really need more than 5 mailbox databases or not on my exchange environment.
I have got this information from digicert http://www.digicert.com/internal-names.htm is there any way to ensure all clients works properly.
Should we have to change our internal domain names to external ones, this will be a problem and visible. It gives us insecured feeling.
Experts please throw your views.
Thanks!
Regards, Ganesh, MCTS, MCP, ITILV2 This posting is provided with no warranties and confers no rights. Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.
I have a customer who is using an externally hosted software package, which has the option to use SMTP details to send emails as the customer.
How do I go about setting up a Receive Connector that is secure but will allow this?
HI,
I have a situation where there are multiple accepted domains but it's required that when mail is accepted to one that a rule highlights or appends something to the subject.
Essencially I need mail sent to the "old" domain to stand out. A rule that can be set at server side, globally, would be useful.
I'll be using Exchange 2013 but would like a test solution for 2007 also if possible. A group policy option might be useful?
Thanks
Chris