Migrating a customer to Exchange 2013 from SBS 2008.
Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
The customer only has a single external IP address...
So what do I do for this external DNS of legacy.customer.com?
I was attemping to apply CU 5 to my Exchange 2013 Mailbox Server and I get the following when it get to step Mailbox Role: Mailbox Service. I have tried to delete the Federation, Discovery, and System/Exch accounts and change the to contacts, no dice, Disable them again, Delete them, Recreate, run PopulateSchema, AllDomain, etc... To no available. I cannot roll back as there is no uninstall I have been able to find out of CU5 once it has been started, it just keeps forcing me to click next to continue. I have tried run as administration. I'm coming up on uninstall exchange mailbox server, then reinstall and apply cu 5. I've taken 18 hours on this of which I could have done that easily within that time.
Any other thoughts you can provide would be awesome. Thanks in advance.
The following
Error:
The following error was generated when "$error.Clear();
if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
{
$arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
{
$mbxname = $arbUsers[0].name;
$mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
{
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
{
enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
}
}
}
}
" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on clddcpgc01.cld.co.fairfax.va.us. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1709429824
---> System.DirectoryServices.Protocols.DirectoryOperationException: An object class violation occurred.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
Adam Macaulay
Hello,
I have an internal domain.lan
An ssl certificate was ordered/installed for mail.domain.com/autodiscover.domain.com
The autodiscoverinternalurl was set to the external mail.ipcotrading.com and an internal DNS zone was created to map to the internal server to work with the ssl certificate.
The autodiscover.domain.com was added to the external DNS zone.
When we try to setup an email account for a mobile device it gives me an error for the certificate, the certificate shows for the actual domain.com website (which is hosted in another external IP address other that the pointing mail.domain.com IP)
The Exchange connectivity test shows everything is ok except for the first autodiscover test as follows:
***Attempting to test potential Autodiscover URL domain.com/autodiscover/autodiscover.xml
Testing of this potential Autodiscover URL failed. ***
I dont understand why it is trying to validate with the website certificate and not with the SSL one.
I dont get it what am i missing or what is wrong.
Spent a lot of time trying to figure it out without luck. :(
Thanks for any help
Hi everyone,
I have been built my home lab with Exchange server. I can receive emails from outside, but I cannot send emails to outside. When I send email to domain email address, everything is ok.
Help me please. I cannot find any lab guide that can help me to check what is wrong with my "outside" configuration.
Hi ,
I am installing Exchange 2013 (2 x CAS + 2 x Mailbox) with Microsoft NLB. I am installing Blackberry Express 5.0.4 with RPC /HTTP. But, it failed to create MAPI profile and asked me to enter credentials but it failed.
Exchange Server name is resolved to one of the DAG members mailbox and I edited host file with Front End CAS pool IP with
mailbox server name which was resolved by Blackberry.
Please advise.
ZAW
I was trying to uninstall exchange 2013 and in that process I disabled two default mailboxes created by Exchange 2013.
Reason to uninstall was because my CAS was missing, re ran setup and installed CAS but now want to enable the disabled default mailboxes.
But now cannot even mount the database.
I get the following error while mounting the database.
Couldn't mount the database that you specified. Specified database: Mailbox Database 0424069483; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionDatabaseError: Unable to mount database. (hr=0x80004005, ec=1108) Diagnostic context: Lid: 65256 Lid: 10722 StoreEc: 0x454 Lid: 1494 ---- Remote Context Beg ---- Lid: 45120 dwParam: 0x435BE7B2 Lid: 57728 dwParam: 0x435BE83F Lid: 46144 dwParam: 0x435BE89C Lid: 34880 dwParam: 0x435BE89C Lid: 34760 StoreEc: 0xFFFFFB4A Lid: 46144 dwParam: 0x435BEC65 Lid: 34880 dwParam: 0x435BEC65 Lid: 54472 StoreEc: 0x1388 Lid: 42184 StoreEc: 0x454 Lid: 1750 ---- Remote Context End ---- Lid: 1047 StoreEc: 0x454 [Database: Mailbox Database 0424069483, Server: xyz.com].
Please help - I had disabled the mailboxes on 12th of last month so still have few days to enable it before it gets deleted permanently.
Hello,
My apologies first if this would be better asked in another forum but this one seems to fit best. I am running Exchange 2013 on Windows Server 2008 R2 Standard and am experiencing an issue after logging in to ECP and OWA. After entering my credentials (all credentials experience the same issue) I am redirected to a 404 error for both \ecp and \owa. The odd thing is that Re-entering the url completes the login. How do I fix the appearent lack of the login.aspx? If my description isn't sufficient please let me know.
Thanks.
We have a CAS server (mail1, 10.1.0.26) and Mailbox server (mbx1, 10.1.0.25). When I ran the update on the mailbox server, it failed with the following errors (see below). The update completed successfully on the CAS server. It appears I have a problem with receive connectors. I really could use some help please. Thank you. -Glen
Here are the results of the Get-ReceiveConnector PS script:
Identity
Bindings Enabled
--------
-------- -------
MBX1\Default MBX1 {0.0.0.0:25}
True
MBX1\Client Proxy MBX1 {10.1.255.26:25, 0.0.0.0:465} True
MAIL1\Default Frontend MAIL1 {0.0.0.0:25}
True
MAIL1\Outbound Proxy Frontend MAIL1 {0.0.0.0:717} True
MAIL1\Client Frontend MAIL1 {0.0.0.0:587} True
Here are snippets of the failure results:
The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Client Proxy MBX1". A receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at lease one of these settings.
The values that you specified for the bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "MBX1\Default MBX1". A receive connector must have a unique combination of a local IP address & port bindings and remote IP address ranges. Change at lease one of these settings.
I have 3 new exchange 2013 physical servers, all 3 return this BPA critical error, see below - doesn't make sense.
Hi!
So I have been browsing through a lot of Exchange Server documentation, guides and best practice but I have not found (or misunderstanding) the CAS placement for my situation.
We are currently in the process of upgrading to Exchange server 2013. As we have an Exchange 2003 only deployment, we will first need to move to Exchange 2010 and get rid of all the Exchange 2003 servers and then move on to Exchange 2013. We have a single domain with 21 AD sites. 8 of these sites (Vessels at Sea) are connected by vSat the other 13 of these sites a remote offices with a more stable connection than vSat.
We want to have a MBX server at every site and what I get from the available documentation on the internet I will also need a HUB server per AD site. What I am not sure about is, do I also need a CAS server per site? What I get from this excerpt:"A new service was introduced with Exchange Server 2010 to allow these MAPI connections to be handled by the Client Access server. The RPC Client Access service provides data access through a single, common path of the Client Access server, with the exception of public folder requests, which are still made directly to the Mailbox server. This change applies business logic to clients more consistently, and provides a better client experience when failover occurs." (ref Understanding RPC Client Access.), is that I also need a CAS server per site.
Can somebody give me any definite insights in this one?
To summarize the question:
In a multi site AD with a MBX server per site, do I also need a CAS server per site?
Your help is much appreciated!
Regards,
Erik
Hi all, In order to get more free space in my Exchange Server 2010, I was thinking to delete a database after move all mailboxes that are in this database to office 365.
Is this a good idea?Because deleting logs is not enough for me, I need more free space. Which impact I will have if I do it after move all mailbox from this database to cloud?
Thanks so much!
I'm currently migrating AD Forest/Org A with mixed E2K3 (SP2) & E2K7 (SP1) into Separate AD Forest/Org B with E2013 SP1. Most all MBs are still on 2K3. SMTP Domain will not change so this will be a 'shared namespace' scenario. Note that the new AD/Exch is a greenfield and trusts have been created/validated and DNS resolution via 2ndary zones on each side is working.
I’ve searched/dug reviewed and found all of the 2003-2013 KBs for handling the shared namespace but I think my scenario is not ‘standard’ because of the mixed source environment (maybe…)
SOURCE:
4 E2K3 servers – not true FE/BE config.
2 E2K7 Servers (1 CAS, 1 MBX)
TARGET:
2 2013 CAS Servers – DNS Round Robin
4 2013 MBX Servers
Mail flow from 2013 to source org MBs (both 2K3 & 2K7) works fine via 'accepted domain', send connectors, etc. However, my problem is with flow from 2K3/2K7 into 2013 target org. When I reply back to the 2013 MB (or send to another known good in 2013), I get the 5.1.1 ‘e-mail account does not exist…’ NDR.
I've modded the 2003 default recipient policy to make the shared namespace nonauthoritative for source org, assigned another domain as authoritative, & created the SMTP connector to 2013 for the shared domain namespace. I also reset the shared namespace as the Primary SMTP in the default recipient policy due to the requirement that all new & existing users continue to be able to send/receive with our internet domain.
However, despite the org-level changes in 2K3, in 2K7 the shared namespace still shows up as authoritative. Next, when I change the shared domain in 2K7 from authoritative to internal relay, the queues start filling up (either via the SMTP connector to 2013 or the outgoing internet queue). Changing things back in 2K7 to authoritative allows the queues to empty out and mail to be delivered again. Also, when I change the domain setting back in 2K7, the domain settings on the 2K3 recipient policies are reset back to authoritative as well!
How do I handle this mixed/inconsistent configuration in my source/legacy environment? Recipient policies have not been upgraded in the legacy environment to E2K7 yet, BTW. Do I need to change things in both 2K3/7, or only manage things from one side? If so, what and/or which one? Since mail is being sent from 2013 into 2K3 (per the send connector) and arriving in both 2K3 & 2K7 mailboxes, is this even the issue? I’m not sure where to go with this.
Thanks
John
Our Exchange 2010 Organization has Exchange servers deployed at multiple sites, AU, NZ and UK.
We recently deployed a Exchange 2013 CAS/MBX server in AU site. Our OWA was cutover from the AU EX2010 CAS server to this EX2013 box. The OWA is still published as MAIL.CONTOSO.COM. The EX2013 server does not hold any mailboxes.
After the cutover, we notice users with mailboxes on remote site Exchange 2010 servers are having problem to connect through Outlook Anywhere. OWA and ActiveSync work perfectly for those uses through MAIL.CONTOSO.COM which is hosted at AU site. However, AU mailbox Users does not have this problem. They can use Outlook Anywhere without any issues. Note their mailboxes are hosted on EX2010 server still.
I tried with TestExchangeConnectivity site and get RPC Proxy Ping failed error for NZ and UK mailbox users. In the mean time, on the Ex2013 server I see event source MSExchange Front End Proxy HTTP event 3005, it basic warns EX2013 has marked NZ and UK remote site EX2010 server as Unhealthy due to exception.
I then confirmed and tested with our network team that ports 6000-6005 and 443 between AU and NZ UK sites. There is no package been blocked or dropped and I can telnet to 6001 from AU EX2013 server to NZ and UK EX2010 servers fine.
I then notice people were mentioning about manually setting EXCH and EXPR value to msstd:mail.contoso.com as mentioned in this post http://social.technet.microsoft.com/Forums/exchange/en-US/728be9b1-4415-4df6-a997-5ecb9ded9a63/rpc-proxy-cant-be-pinged-20132010-coexistence-with-outlook-anywhere?forum=exchangesvrgeneral
But I suspect this is not relate to my case, as RPC Proxy works perfectly between the AU EX2013 and EX2010 server.
Any suggestions?
This should be a relatively simple question. I've just set up the DAG on my new Exchange 2013 deployment, it spans two servers, MB1 and MB2. Both are dual-horned, on both a replicator subnet and the LAN. I notice that the 2013 DAG is automatically setup by default, so I want to make sure it's been setup optimally. I'm going by this article:
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
My main concern is it looks like I should be seeing two DAG networks set up, as per this:
| Name | Subnets | Interfaces | MAPI access enabled | Replication enabled |
|---|---|---|---|---|
MapiDagNetwork | 192.168.0.0/24 192.168.1.0/24 | EX1 (192.168.0.15) EX2 (192.168.1.15) | True | True |
ReplicationDagNetwork01 | 10.0.0.0/24 10.0.1.0/24 | EX1 (10.0.0.15) EX2 (10.0.1.15) | False | True |
But I'm only seeing a MapiDagNetwork in my list of DAG Networks. Did it fail to install the ReplicationDagNetwork? If so, what's the best way to go about fixing it? Seems preferable to keep the automatic setup.
----------- Ron E Biggs Network Administrator Entertainment Studios
Hi all.
I'm a bit lost, it's my first exchange 2013 install and my first coexistence scenario. So I need help.
I've got an existing Exchange 2007 SP3 CU 12 organization, with 3 servers :
- Server38 and Server39 as Mailbox Server, CCR Cluster, virtual node isServer40
- Server41 as CAS Server.
I want to migrate everything to Exchagne 2013 SP1 on Windows 2012 R2. I have 2 servers :
- Server12 and Server13 are Multirole servers, CAS ans MBX. I have configured a DAG. It's working.
To provide HA on CAS service, I put this in order : http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Clearly, I want my CAS Server to be accessed with mail.domain.com instead of Server12.domain.com or Server13.domain.com
So I configure Outlook Anywhere like this : "Set-OutlookAnywhere -InternalHostname mail.domain.com -InternalClientsRequireSsl $false"
Now, I don't really imagine how I can use this platform during coexistence.
I want to set users on my new servers, but autodiscover is configured in DNS to point Server41.
Users can access to their mails via OWA and Outlook.
How can I configure autodiscover? Must I change autodiscover record in DNS to point to new servers or should I let it on Server41?
How will Outlook work when I migrate one user to the new servers? Will I have to change config?
Thanks
Hi Guys
Im planning to deploy a new domain Win 2012 and an Exchange server 2013, but I have doubts about the name for my domain, because of the SSL certificate.
Should I keep the domain.local convention name, domain.com or a subdomain like internal.domain.com convention.
I have this doubt because the SSL certificate cannot have the internal name for the autodiscovery.
Regards
i installed the certificate from my exchange 2010 server and it was accepted as valid. it gave an error like in this link http://www.hsuconsulting.com/wildcard-ssl-certificate-exchange-2013-imap-and-pop-error/
but it was accepted as valid.
i changed ECP to connect as webmail.domain.com externally but no other changes. Now i get "The security certificate presented by this website was issued for a different website's address." whenever i try to open ECP.