Hi,
For some reason, my Exchange servers are no longer updating. Im getting error code 80072EFD.
I have googled this and found a few articles suggesting Time mismatch and a root certificate missing. This is not the case as I have checked both...
Any other ideas? This seems to have happened after I have applied CU5 on one of the servers.
Thanks in advance.
Hello,
I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
Any advice on performing this migration without issues?
Thanks
HI,
I am installing the first ADFS server on an existing Windows 2012R2 Domain Controller. The domain is Forest and Domain Functional level 2003.
Using this Guide: http://www.schmarr.com/Blog/Post/12/Installing-Windows-2012-R2-Server-ADFS-Service-
Created a group managed service account like so:http://www.schmarr.com/Blog/Post/7/Group-Managed-Service-Accounts
I have a commercial certificate with the correct name, using local Wid Database om the domaincontroller
When I install the ADFS role, I get an error at the end of the installation: "Login failed. The login from an untrusted domain and cannot be used with Windows authentication"
I tried on 2 Domaincontrollers, recreated managed serviceaccount, but the error remains. I don't see any errors in the eventlog.
Hi,
i am in the middle of an exchange migration from 2007 to 2013.
The public folders are still on the exchange 2007 servers.
Users that are migratated to the new 2013 server does not have access to the public folders via OWA oder Outlook Anywhere.
I got only a error message that it is not possible at the moment.
What must i do that migrated users will also have access via OWA and Outlook Anywhere?!
Frank
When trying to open EMS on all CAS Servers, an error is received -
"The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again."
Most people have solved this by going into the bindings of the Exchange Back End site in IIS and assigning a certificate. There is already a certificate assigned, so that is not the problem. We are using a wildcard certificate, but I don't think that is the problem because I have reassigned the default self signed cert as well as creating a new certificate with the FQDN of the server as the CN and it produces the same results.
I am able to "fix" the error by changing the path of "PowerShell" under the Default Web Site in IIS from "C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\PowerShell" to "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell", but that is not a good solution as I am sure it can cause other problems.
We are running Exchange 2013 CU5. We have four CAS servers spanning two sites (two in each site) and they are all running Server 2008 R2 Standard. All four CAS servers are having the problem. This is an environment I inherited, so I can't say when the error started happening (after initial installation, applying an update, etc.).
Any help is greatly appreciated!
hi guys
i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will move old one at the end .
my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ??
thank you
Indunil
Hi,
We are in process of migrating from Exchange 2007 to Exchange 2013 Servers.
To meet the migration requirements we have changed the standard single name SSL certificate with UCC Certificate having multiple SAN values using the exchange 2013 EAC wizard. Later on we applied the same certificate to both Exchange 2013 and 2007 CAS servers.
Outlook Anywhere was enabled since long on exchange 2007 servers and was working fine till we made the certificate change. After we make the change of certificate given were the error message we started encountering:
Another change which we noticed were of Domain Controllers names in the same AD site as exchange getting added to VALID PORTS key under given HASH:
HKLM\Software\Microsoft\RPC\RPCProxy
As per my understanding Valid ports entry is populated with all the mailbox servers in organization only until unless we define DC there, which we never did until now. I can also see values for Exchange 2013 mailbox server there.
And now since Valid ports entry contains reference for domain controller i have to made following registry entry on my domain controllers to make it work :
On the Global Catalog servers: a REG_MULTI_SZ entry needs to be created on each GC named NSPI interface protocol sequences at HKLM\System\CCS\Services\NTDS\Parameters\ and the value set to ncacn_http:6004
I have tried modifying the Valid Ports entry manually and removing the domain controllers reference from there but then my Outlook Anywhere doesn't work anymore. Yes i know that RPCConfigurator again populate the entry every 15 minutes and i can turn it off,i have tried that but no luck.
Result of the above change now my CAS is directly speaking for my domain controllers which earlier mailbox server was doing through DSPROXY.
Can anyone suggest me what is happening wrong here...given are the environment details:
2 CAS +HUB Exchange 2007 SP3 RU13 server on windows 2003 R2
Exchange 2007 Mailbox Server SP3 RU13 SCC on Windows 2003 R2
Exchange 2013 CU5 CAS + Mailbox Server on Windows 2012 R2
Windows 2003 AD with mix of 2008R2 DC.
Regards,
Vishal Malhan
Hello,
I have a very interesting problem Exchange 2013 installation step on Hyper-V.
I have 2 server. I installed on server Server 2012 R2 Standart. And then installed hyper-v role for both server.
I created virtual machine for first server and this virtual machine domain controller.
And then I created virtual machine for second server and this virtual machine Exchange 2013.
I installed all prequisites and exchange 2013 finished successfuly. When I opened https://server/ecp it give me http 500 internal error. I checked almost all forums but any recommendation didn't solve my problem.
And then I removed hyper-v role and installed vmware v11. and installed same applications like above.
Very interesting finished installation and opened ecp console. eveythink seen to good.!
Actualy I find problem.
There is exchange feature installation command on microsoft exchange prequisite. When ruunning this command installing two program on program and feature name is "c++ redistrubutable x64 and x32"
I must uninstall this programs before install unified communication api 4.0.
I cannot see on hyper-v when running this feature.
But I can see on vmware this features on programs and feature.
This is very absurt.
Anybody have an idea for this
Thank you for your clarify.
I'm aware there is a Group Policy admin template available to force Outlook to request only NTLM or basic authentication, however, I'd like to disable Outlook Anonymous NTLM on the server side in our Exchange 2013 SP1 on-premises installation.
Is there a method to disable Anonymous NTLM for Outlook client connections for the cas or organization? I've tried the "Set-OutlookAnywhere" InternalClientAuthenticationMethod and ExternalClientAuthentcationMethod but Outlook is still able to connect with Anonymous Authentication selected for the logon network security.
Thanks
John Lowery
I am trying to figure out what server settings need to change in order for my outlook clients to have a better chance of success connecting to their mailbox. our internal domain name is something.local and our email domain is somethingdifferent.com.
here is what happens when I try to configure an outlook client offsite (w/out vpn).
outlook asks for their name, email address and password. users can generallyget that right and it moves to the next step and it brings up a box with their email address as their username. users assume that is correct but their password doesn't work because they should be clicking 'other user' and change the username from 'email address' to internaldomain\theirusername. it brings that up 2 or 3 times before it's successful.
so, what I would like to know is, what setting(s) should I be looking for that would make that first credentials box pop up with internaldomain\firstpartofemailaddress instead of their email address.
phones do the same thing, it starts out asking for just email address and password as if that is all you 'should' need but it comes in partially successful but they still have to fix the username to internaldomain\username. and the server address comes in something.com but it always has to be changed to mail.something.com before it'll work. I'd like to see if there is a way that it could already know the correct server address.
I figure that since both outlook and phones start by asking only email address and password, there should be some combination of settings that would allow valid credentials at step1 to be enough to connect.
Exchange 2013 mail server and both of my domain controllers are server 2003.
Thanks, Tony McPherson
Exchange 2013 is up and running (still in test mode) and I can process mail with POP, IMAP, Outlook Anywhere, and activesync (with my cellphone and tablet). Event logs are pretty normal except for the ProbeResult log. I see errors in there for ActiveSync, IMAP and POP and some others. I ran the get-serverhealth cmdlet and then followed the instructions in the knowledgebase articles to reset stuff in IIS. I am at a loss what else to do. Everything seems to be working fine but I see those errors. (Maybe I shouldn't have looked in that log :)
Any suggestions? Thanks,
Lou
Hello all,
I have installed Exchange 2013 (CAS Role) on a Windows 2008 R2 server. All the requirements where passed.
After installing and the reboot, I am unable to start the Exchange Toolbox. It gives the following error:
Unhandled Exception in Managed Code Snap-in
FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}
Exception type: System.Runtime.Serialization.SerializationException
Exception stack trace:
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
Any help is appreciated and with kind regards,
Willem-Jan
It all began last night when I tried to install CU3. The uninstall of CU1 has been problematic to say the least
Today the CU1 update almost completed then stopped with a dialogue box as shown below
When I point the dialogue box to the Install CD for Exchange 2013 (the only source I know of) it says its not a valid source
I have tried downloading CU1, and KB2874216 and reinstalling but each reports the other needs to be removed first
Background - Ex2010 / 2 Datacenters / 1 DAG / 1 client site in a different region where users are accessing 2010 via the Internet (even though they have a local office where a server can be deployed)<o:p></o:p>
Planning to deploy 2013 to take advantage of forcing proxy option for OA/OWA/ActiveSync etc. due to network architecture/limitations in one region (read as internal corp network has much
better latency/bandwidth as opposed to
users connecting via Internet directly to the main datacenters)<o:p></o:p>
We have users in one region (CN) where we want to force users to use a local CAS (no mailbox servers there) and have that CAS proxy (on internal network) to the mailbox servers. We plan to do
this via 2013 cas and having them to proxy to 2010
mailbox servers and eventually proxy to 2013 mailbox servers.<o:p></o:p>
Questions:<o:p></o:p>
Can we deploy single namespace with a local cas server in the region - have smart dns or local hosts file in that region to point to the local region CAS server with no mailboxes / it will proxy to 2013/10 ?<o:p></o:p>
If we deploy region specific name space (ex. cn.infra.com) with no mailboxes in that region
and all mailboxes are in the main datacenter in a different region (and different AD Site and with a different name space like na.infra.com) / How can we force users to use that region specific name space with no mailbox servers
in that AD site? / Is there any way we can force name space based on their user attributes as opposed to autodiscover doing the <GUID>@infra.com logic ?<o:p></o:p>
TIA
Prakash
Hi,
I am currently migrating Exchange 2007 to 2013 but have run into a strange problem trying to connect from Outlook 2007 or 2010 (haven’t tried 2013). I have spent 3 days trying to solve this now and its driving me crazy now, any advice would be greatly appreciated.
Outlook autodiscover process finds the mailbox but then prompts for a login and then all logins fail even when the correct credientials are definitely being used and the account is not then being locked out. The GUID of the mailbox shown by Outlook is correct.
can connect to the mailbox fine using OWA.
This is the same for Mailboxes created on Exchange 2013 or migrated to it
I am currently just trying to test Outlook connectivity as I will be swiching all external DNS records to point to EX2013 next week so at the moment all external records point to 2007 whilst all internal DNS records point to 2013.
I am using a wildcard certificate and it has been installed on both servers.
One thing I have noticed is that the ‘Exchangeversion’ is the same on each server which seems like it must be a mistake.
Below is the output from get-outlookanywhere | fl
RunspaceId : 9cff00a7-eb02-4c88-b379-b351c6f8a3f2
ServerName : EX2007
SSLOffloading : True
ExternalHostname : webmail.domain.org.uk
InternalHostname : ex2013.domain.org.uk
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://ex2007.domain.org.uk/W3SVC/1/ROOT/Rpc
Path : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 8.3 (Build 83.6)
Server : EX2007
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EX2007,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=domain,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=org,DC=uk
Identity : EX2007\Rpc (Default Web Site)
Guid : d482b79a-9b23-4edd-92d7-8e500faea8fa
ObjectCategory : domain.org.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 20/01/2015 17:02:08
WhenCreated : 01/05/2013 11:51:05
WhenChangedUTC : 20/01/2015 17:02:08
WhenCreatedUTC : 01/05/2013 10:51:05
OrganizationId :
OriginatingServer : DC2.domain.org.uk
IsValid : True
ObjectState : Changed
RunspaceId : 9cff00a7-eb02-4c88-b379-b351c6f8a3f2
ServerName : EX2013
SSLOffloading : True
ExternalHostname : webmail.domain.org.uk
InternalHostname : ex2013.domain.org.uk
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
MetabasePath : IIS://ex2013.domain.org.uk/W3SVC/1/ROOT/Rpc
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 847.32)
Server : EX2013
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EX2013,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=domain,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=org,DC=uk
Identity : EX2013\Rpc (Default Web Site)
Guid : c6293197-0f44-4927-b37a-66bc38742502
ObjectCategory : domain.org.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 20/01/2015 17:02:08
WhenCreated : 18/12/2014 13:27:50
WhenChangedUTC : 20/01/2015 17:02:08
WhenCreatedUTC : 18/12/2014 13:27:50
OrganizationId :
OriginatingServer : DC2.domain.org.uk
IsValid : True
ObjectState : Changed
And below is the result of get-outlookprovider | fl (Which also shows the wrong version)
RunspaceId : 3e64b3bb-31e8-48a1-946d-45df22a1d679
CertPrincipalName :
Server :
TTL : 1
OutlookProviderFlags : None
RequiredClientVersions :
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : EXCH
DistinguishedName : CN=EXCH,CN=Outlook,CN=AutoDiscover,CN=Client Access,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=org,DC=uk
Identity : EXCH
Guid : 27fbd0f4-7207-4abf-be6d-cd96b8b30a4f
ObjectCategory : domain.org.uk/Configuration/Schema/ms-Exch-Auto-Discover-Config
ObjectClass : {top, msExchAutoDiscoverConfig}
WhenChanged : 16/07/2010 17:29:11
WhenCreated : 10/07/2008 09:59:43
WhenChangedUTC : 16/07/2010 16:29:11
WhenCreatedUTC : 10/07/2008 08:59:43
OrganizationId :
OriginatingServer : DC2.domain.org.uk
IsValid : True
ObjectState : Unchanged
RunspaceId : 3e64b3bb-31e8-48a1-946d-45df22a1d679
CertPrincipalName : msstd:webmail.domain.org.uk
Server :
TTL : 1
OutlookProviderFlags : None
RequiredClientVersions :
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : EXPR
DistinguishedName : CN=EXPR,CN=Outlook,CN=AutoDiscover,CN=Client Access,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=org,DC=uk
Identity : EXPR
Guid : ce360167-4cb9-4743-9bb6-76638906ca2b
ObjectCategory : domain.org.uk/Configuration/Schema/ms-Exch-Auto-Discover-Config
ObjectClass : {top, msExchAutoDiscoverConfig}
WhenChanged : 21/01/2015 10:42:07
WhenCreated : 10/07/2008 09:59:43
WhenChangedUTC : 21/01/2015 10:42:07
WhenCreatedUTC : 10/07/2008 08:59:43
OrganizationId :
OriginatingServer : DC2.domain.org.uk
IsValid : True
ObjectState : Unchanged
RunspaceId : 3e64b3bb-31e8-48a1-946d-45df22a1d679
CertPrincipalName :
Server :
TTL : 1
OutlookProviderFlags : None
RequiredClientVersions :
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : WEB
DistinguishedName : CN=WEB,CN=Outlook,CN=AutoDiscover,CN=Client Access,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=org,DC=uk
Identity : WEB
Guid : 5a27fb7b-619c-4da4-9782-3b4bedf775f1
ObjectCategory : domain.org.uk/Configuration/Schema/ms-Exch-Auto-Discover-Config
ObjectClass : {top, msExchAutoDiscoverConfig}
WhenChanged : 16/07/2010 17:29:11
WhenCreated : 10/07/2008 09:59:43
WhenChangedUTC : 16/07/2010 16:29:11
WhenCreatedUTC : 10/07/2008 08:59:43
OrganizationId :
OriginatingServer : DC2.domain.org.uk
IsValid : True
ObjectState : Unchanged
And this is the output of get-exchangeserver
RunspaceId : 3e64b3bb-31e8-48a1-946d-45df22a1d679
Name : EX2007
DataPath : C:\Program Files\Microsoft\Exchange Server\Mailbox
Domain : domain.org.uk
Edition : Standard
ExchangeLegacyDN : /o=DOMAIN/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX2007
ExchangeLegacyServerRole : 0
Fqdn : EX2007.domain.org.uk
CustomerFeedbackEnabled :
InternetWebProxy :
IsHubTransportServer : True
IsClientAccessServer : True
IsExchange2007OrLater : True
IsEdgeServer : False
IsMailboxServer : True
IsE14OrLater : False
IsE15OrLater : False
IsProvisionedServer : False
IsUnifiedMessagingServer : False
IsFrontendTransportServer : False
NetworkAddress : {ncacn_vns_spp:EX2007, netbios:EX2007, ncacn_np:EX2007, ncacn_spx:EX2007,
ncacn_ip_tcp:EX2007.domain.org.uk, ncalrpc:EX2007}
OrganizationalUnit : domain.org.uk/EX2007
AdminDisplayVersion : Version 8.3 (Build 83.6)
Site : domain.org.uk/Configuration/Sites/Default-First-Site-Name
ServerRole : Mailbox, ClientAccess, HubTransport
ErrorReportingEnabled :
StaticDomainControllers : {}
StaticGlobalCatalogs : {}
StaticConfigDomainController :
StaticExcludedDomainControllers : {}
MonitoringGroup :
WorkloadManagementPolicy :
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainController :
ProductID : 90559-047-0000007-05612
IsExchangeTrialEdition : False
IsExpiredExchangeTrialEdition : False
MailboxProvisioningAttributes :
RemainingTrialPeriod : 00:00:00
Identity : EX2007
IsValid : True
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=EX2007,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=org,DC=uk
Guid : f2d1cf56-93c8-4afb-83fa-2149dfe4f30f
ObjectCategory : domain.org.uk/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 05/12/2014 20:05:14
WhenCreated : 10/07/2008 09:53:59
WhenChangedUTC : 05/12/2014 20:05:14
WhenCreatedUTC : 10/07/2008 08:53:59
OrganizationId :
OriginatingServer : DC2.domain.org.uk
ObjectState : Unchanged
RunspaceId : 3e64b3bb-31e8-48a1-946d-45df22a1d679
Name : EX2013
DataPath : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox
Domain : domain.org.uk
Edition : Enterprise
ExchangeLegacyDN : /o=DOMAIN/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX2013
ExchangeLegacyServerRole : 0
Fqdn : EX2013.domain.org.uk
CustomerFeedbackEnabled : True
InternetWebProxy :
IsHubTransportServer : True
IsClientAccessServer : True
IsExchange2007OrLater : True
IsEdgeServer : False
IsMailboxServer : True
IsE14OrLater : True
IsE15OrLater : True
IsProvisionedServer : False
IsUnifiedMessagingServer : True
IsFrontendTransportServer : True
NetworkAddress : {ncacn_vns_spp:EX2013, netbios:EX2013, ncacn_np:EX2013, ncacn_spx:EX2013,
ncacn_ip_tcp:EX2013.domain.org.uk, ncalrpc:EX2013}
OrganizationalUnit : domain.org.uk/EX2013
AdminDisplayVersion : Version 15.0 (Build 847.32)
Site : domain.org.uk/Configuration/Sites/Default-First-Site-Name
ServerRole : Mailbox, ClientAccess
ErrorReportingEnabled :
StaticDomainControllers : {}
StaticGlobalCatalogs : {}
StaticConfigDomainController :
StaticExcludedDomainControllers : {}
MonitoringGroup :
WorkloadManagementPolicy : DefaultWorkloadManagementPolicy_15.0.825.0
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainController :
ProductID : 02064-004-0073083-02862
IsExchangeTrialEdition : False
IsExpiredExchangeTrialEdition : False
MailboxProvisioningAttributes :
RemainingTrialPeriod : 00:00:00
Identity : EX2013
IsValid : True
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=EX2013,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=org,DC=uk
Guid : 0acae8de-041c-4a31-8ea8-0b690fdb5e6c
ObjectCategory : domain.org.uk/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 07/01/2015 11:39:59
WhenCreated : 18/12/2014 13:10:28
WhenChangedUTC : 07/01/2015 11:39:59
WhenCreatedUTC : 18/12/2014 13:10:28
OrganizationId :
OriginatingServer : DC2.domain.org.uk
ObjectState : Unchanged
So any ideas?
Hi I am installing Exchange 2013 SP1 in a test environment. This server will coexist with an Exchange 2007 server.
Both the Exchange 2013 server and the 2007 server are standalone servers with all roles installed. I understand that the mail flow has changed some in 2013.
On my current Exchange 2007 server, the Client and Default Connectors are disabled. I then have two additional connectors that were created, the 1st receives incoming internet mail from our spam gateway, and the 2nd receives mail from a few select internal clients that send via SMTP (example: printers and copiers, server application alerts)
My question is regarding the setup of receive connectors on the new 2013 servers. I have already duplicated the 2 connectors that are on 2007. Which of the default receive connectorscan I disable on Exchange 2013? thanks
Yesterday we decided to pull the trigger on migrating to exchange 2013 from 2010. We changed the autodiscover URI's to mail.domain.com and we also changed the DNS records to as follows:
mail.domain.com -> 2013 cas
mailhub1.domain.com -> 2010 cas
mailhub2.domain.com -> 2013 cas
Ive pushed every single URL I can find through mail.domain.com. We had a few odd issues but were able to work through them. Now we are about 10 hours into troubleshooting without making any headway. Here is where we currently stand:
Exchange 2010 User - Works on everything - Web, Mac Mail, Outlook (inside and outside), mobile clients
Migrated and New Exchange 2013 User - Works on Web, Mac Mail, Mobile. Does not work on outlook inside or out.
For outlook we receive the following error:
Microsoft Outlook --------------------------- There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site mail.domain.com. Outlook is unable to connect to the proxy server. (Error Code 0) --------------------------- OK ---------------------------The certificate is perfectly fine from what I can tell. The main domain on it is "mail.domain.com" with "autodiscover.", "mailhub1.", "mailhub2.", and "domain.com" in the Subject Alternate Name.
What on earth could I be missing here? It works on exchange 2010 but not on 2013 which is the exact opposite of what I was expecting.
I'm writing up the process for us to migrate from Exchange 2007, to 2013. It looks like I need to add my Exchange 2013 HT servers to the SourceTransportServers property for each Send connector. When I finish up the migration and decommission my legacy servers, will that clean up the SourceTransportServers property, or do I need to go back in and do it manually?
Thanks.
We are in the process of 2003 to 2010 Exchange upgrade so that they coexist in the same environment what I don’t seem to be able to find is as follows.
Question can users still access the old 2003 OWA web page after the upgrade integration of 2010 so we don’t have to configure all mobile devices in one hit, or do all users now have to use the new 2010 OWA webpage? In a nutshell will both OWA servers work side by side?