OWA functionality in Exchange 2007 coexistance with 2013

I have conexistance environment with Exchange 2007 and Exchange 2013. Out of about 1200 users we have 25 test users in the 2013 environment. The problem we are seeing is when a 2013 mailbox has "Full Access" to a 2007 mailbox and tries to connect
to that mailbox through OWA 2013 the connection always fail. I can attach the mailbox in Outlook with no problems but cannot open that mailbox through OWA 2013. Any thought?

See if this helps. It's not an exact match for your versions, but I think it's what you need to look at.
http://support.microsoft.com/kb/981541
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

Exchange 2007 EXCDO 8206 error in Exchange 2007 SP2 with Rollup 4

Dear sir,
    We have a problem on Exchange 2007 Server. When user use OWA to access web mail calendar, server event log will show EXCDO error 8206:
Calendaring agent failed with error code 0x8000ffff while saving appointment
Type: Error
Event ID: 8207
Category: General.
     Moreover server becomes working in very slow web mail response during any user click web mail calendar.   Server performance return back after error message appeared in event log.
It doesn't has problem if using Outlook to access mailbox calendar.
Any suggestion to fix it ?
Joe

Hi Joe,
We are also finding the same issue with getting that EXCDO error. The problem stemmed when users noticed some previously accepted appointments disappeared (As I suspect you discovered with your users).
The workaround has been to get the user to accept the appointment again by going into deleted items, this seems to add the appointment as it should have the first time.
We have done the following but it didn't fix the problem:
Disabled extra SEP features on the clients - No Change
Disabled non-essential Outlook add-ons - No Change
Removed BES Express and CDO MAPI From Exchange server - No Change
Disabled MS Defender on Exchange - No Change
Fixed any Public folder errors - No Change
Disable Window services WSS and UNC sharing feature in Active Sync - No Change
Also ensured Autoupdate and auto process was enabled for affected users - No Change
I'm going to try the reg change mentioned in this thread but other than the built in MS Defender we don't have anti-virus on our mail server.
At first we thought it was Active Sync as it only seem to impact those with a A/S device, but now it's intermittent for other users using Outlook.  We are currently using Exchange 2007 SP3 with RU13. We are looking at trying an update
to RU14 but I am doubtful it will fix the problem. Did you have any luck finding a solution?
Thank you in Advance.

Exchange 2007 Environment with BlackBerry Enterprise Server 5

Hi,
I am planning to migrate Exchange 2007 to 2013 DAG with BlackBerry Enterprise Server 5. For BlackBerry Users, How can I configure to work with Exchange 2013? Because Exchange 2007 works with MAPI for BES but 2013 with RPC/HTTPS.
Do I need to set up new BlackBerry Server? Please advise
Regards,
Zaw Tun Naing
ZAW

Have a look in the Blackberry
KB33413.
As stated in this blog this seems to be an "all or nothing for BB mailboxes". So if you plan to migrate slowly it would be the best to install
another BB Server.

Connect to Exchange 2007 Mailboxes with Exchange 2013 Management shell

Hello,
I was wondering if it is possible to use the Exchange 2013 Management Shell with the older version of Exchange 2007. When I run the console now it give me an error saying no exchange servers are available in the Active Directory site. When I use Exchange
management shell for 2007 the errors do not appear. Wondering if the management shell is backwards compatible.
Thanks,

No. your management shell MUST be the same roll-up version of exchange. I have applied updates and learned the hard way to block all updates that go beyond the server version you are
running.
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-bui...
To this end, you can use the same installation media that was used to install your Exchange server "Provided you are hosting your own", just install the management console instead of the whole thing,

Restoring Exchange 2007 mailstore to 2013 server

We got hit with a nasty malware infection and want to rebuild our network from the ground up, moving to a VM environment in server 2012 and starting over from scratch. Scorched earth.
We currently have an exchange 2007 SP3 server. Is it possible to restore our 2007 mail store directly to the 2013 server? We want to avoid connecting our old network/domain to the new one at all costs.
If direct restore isn't possible, what steps would be needed to restore the mail store and retain all user mailboxes?
Thanks for any advise.

A direct restore is definitely not possible - it's not even possible from Exchange 2007 to Exchange 2010. Your best option would be to restart your old systems and export your mailboxes to PSTs. It's not pretty, but it's going to be a lot easier
than any other solution I can think of. Especially since your old and new Exchange organizations are probably going to have the same organization name ...

Exchange 2007 SP1 with GoDaddy Cert - iPhone cannot verify cert

Hi Everyone,
My school has just moved to Exchange 2007 and I'm trying to connect my iPhone to it. We haven't changed any settings on the Exchange server really that relates to ActiveSync (at least as far as I can tell). We're using a GoDaddy wilcard SSL cert with the site for OWA and (I hope) ActiveSync.
From what I can see, Apple has included all of the GoDaddy Intermediate and Root certs in OS 3. I have manually installed these certs again on my iPhone (the one I'm testing with) by emailing them to myself. This hasn't helped with the issue...
When trying to add the Exchange account on the iPhone I'm getting an "Unable to Verify Certificate" error. The error makes no mention of autodiscovery (which it should be using), so I'm not sure if it has anything to do with that. I'm really not sure what to do at this point since we're all new to Exchange, and I only have used my iPhone through Exchange with Google in the past.
Thanks,
-MRCUR

Ever hear anything back on this? I too have an iPhone (3G) and would like to connect it to a GoDaddy Exchange server. No luck so far.

Symantec Mail Security with Exchange 2007 (Emails with Attachment missing)

HI, i need help here
I have Win 2008 with Exchange 2007 and Symantec Mail Security. Symantec was working fine until the license expired but it was still fine until yesterday, we realize that we cannot receive email with attachment. after stopping the symantec services, mail
flow went back to normal. We then remove the program from the control panel.
Then i found that i cant retrieve or find those emails that was sent to us during a period of ard 6 hours. i tried looking the the Symantec quarantine folder but it is not there.
Can someone point to me where should i look for the missing mails? When i do a mail flow troubleshoot i can see the logs that it is sent to the mailbox, but from users's outlook inbox, there is no email ??
Much Appreciated

Symantec's support group should be able to tell you what happened.
--- Rich Matheisen MCSE&I, Exchange MVP

Upgraded to Exchange 2007 - Problems with opening attachments in e-mail Treo700wx

We upgraded our server at work to Exchange 2007. Ever since then, there have been multiple problems, on of which I am not able to open pdf files, excel or word files on my handheld 700wx. Anyone else have this problem. Talked with Verizon, they suggested downloading a new version of the pdf viewer. That didn't work. Looking for any suggestions.
Post relates to: Treo 700w (Verizon)

Hello!
Since your company is now using 2007, good chance you will need a Windows Mobile 6 and up phone. Please install this update to get your phone to windows mobile 6.0:
http://kb.palm.com/wps/portal/kb/common/article/10133_en.html
Be sure to follow the instructions on the page.

MS Exchange 2007 integration with ECC 6.0

Hello Experts,
   We have ECC 6.0 and MS Exchange 2007. We need to integrate ECC 6 and MS Exchange .
   Mails sent from MS Exchange should be received in ECC 6.
   What is the method to do this ?
   Mails sent from MS Exchange to ECC 6.0 should be available in SAPGUI Inbox..
   MS Exchange supports MAPI format and ECC Mail Inbox supports SMTP . So how should it be integrated ?
regards,
Pravash Raikar

Hi!
Check the SAP Best Practices documents
http://help.sap.com/bp_crmv12007/CRM_DE/HTML/index.htm
There have a look at
C71: CRM Connectivity
B09: CRM Customizing Replication
regarding the connection and replication
rollo

Exchange 2010 coexist with exchange 2013

Hi All ,
Planning to have a coexistence scenario in my environment which is mentioned below
Exchange 2010 - ambiguous url in place - OA enabled
For mapi/rpc traffic - mail.domain.in - exchange 2010
For https traffic - mail.domain.in - exchange 2010
mail.domain.in will get resolved in to cas array in exchange 2010 .
After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
Note :
On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
exchange server via exchange 2013 server.
question : I would like to know above mentioned scenario is possible or not ?
On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
All of you tell me your valuable suggestions.
Regards
S.Nithyanandham

Hi,
Going Straight to the point... and answering your question...
The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
As per Exchange Team...
In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
their DNS cache expires after the shared FQDN is moved to CAS 2013.
As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
fix existing Outlook clients with the old value in the server field.
So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
Outlook 2013: 15.0.4420.1017 (RTM or later)
I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx>
Hope it can help you!
Cheers,
Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

Exchange 2007 Sending with Second Email Address (trying to use Send As)

I support a company who just bought another company. I'm trying to bring a couple of users' old email addresses in to Exchange and have it work with their old and new addresses. They can receive mail under old and new accounts just fine. Sending
under the old address is the problem. They still need to send under the old address for existing contracts.
My first attempt was to create a distribution group, give it the user's old email address, and then give the user "send as" rights for the group using the Exchange Management Shell. I ended up with the same error I'll detail below.
My next (and current) attempt was to set up a shadow user in AD with the old email address and then give the user "send as" rights to the shadow mailbox. I assigned the "send as" permission by right-clicking on the mailbox and choosing
"Manage Send As Permission" and then adding the real user to the list. In Outlook, I clicked From and then choose the shadow user account from the Global Address Book. This added the address to the From drop down box.
This works, once... Every time I restart the Information Store service, I can get one email to send out successfully. Here is the error I get on every other attempt. Notice it says "send on behalf" in the error. Maybe I'm not
setting it up correctly in Outlook? I didn't make Outlook screenshots but you'll find my AD and Exchange setup screenshots below.
Thanks for the help.
(also posted at http://forums.msexchange.org/m_1800602162/mpage_1/key_/tm.htm#1800602162)
***ERROR START***
Delivery has failed to these recipients or distribution lists:
Tripp Beasley
You are not allowed to send this message because you are trying to send on behalf of another sender without permission to do so. Please verify that you are sending on behalf of the correct sender, or ask your system administrator to help you get the required
permission.
Diagnostic information for administrators:
Generating server:
[email protected]
#MSEXCH:MSExchangeIS:/DC=local/DC=XXXXXXXXXX:XXXXXXXXXX[578:0x000004DC:0x0000001D] #SMTP#
***ERROR END***

open the list of previous recipients and select the ones you need by holding the command button. then press "add to address book".

Getting error -2147221219 when trying to execute OpenMsgStore function on Exchange 2007 Server

Hello,
I am getting error -2147221219 when trying to execute OpenMsgStore API on Exchange Server 2007. I have created the Public Folder also on the same server. Also, I have installed the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 on the server. Please do let me know if our previous MAPI / CDO applications would work for Exchange Server 2007 in this environment?
Also, while executing the Microsoft Exchange MAPI editor when I click on Session -> Logon and Display Store Table I see Err:0x8004010F=MAPI_E_NOT_FOUND in the row type column. The MAPI initialization is successful and in the Display Name I get Public Folders and Mailbox - Administrator. Please let me know how to I make work the MAPI Editor.
Thanks for your time and cooperation !!
Thanks & Regards,
Neel

Answers in social.msdn.microsoft.com/Forums/en-US/3a2e9489-6137-42fb-95d1-bebcfe2ea138 may solve your problem.
PR_PROFILE_CONNECT_FLAGS = 0 will also work.

Mail Crashing when adding exchange 2007 account with SL

I tried adding my work exchange to my mail which I currently have gmail and mobileme configured. I enter my info and credentials, accept the certificate (unsigned), and mail crashes immediately.
I tried moving out the plist and /Library/Mail folded to start from scratch, but I get the same result.
This did work with my exchange account on another machine (my Mac Pro) with the last beta. I have not had a chance to upgrade it yet. Anyone else have similar problems? Any other ideas to try?

I was able to figure out a work around. In order to get out of the automatic discovery of my mail server information, I started over at the new account wizard and put in a bogus email domain. Since the wizard did not recognize it, it prompted me to enter the server type and the rest of the settings. Once I entered them manually I was able to add the account. Hopefully there will be a forthcoming permanent fix somewhere down the road.

Adding a new FFL 2012 trusted domain to a Exchange 2007 domain with a FFL 2003 domain

My organization has decided to create a new forrest and domain. We will be creating a two way trust between the current 2003 forrest & domain and the new 2012 forrest & domain. For now, only a few of our users will
log into the new domain, but we still want them to be able to access their email in the 2003 domain and have their emails come from the 2003 domain. There are no Exchange servers in the new domain, users will just authenticate to the
new domain.
Besides creating the accepted domain policy and new email policy, is there anything else that will be required?
Thanks in advance
MikeV
Thanks, MikeV MCSE 2012

In Exchange 2003 there is no "accepted domain policy" or "email policy", just recipient policy. And you only need to do that if you're adding a new e-mail domain. Further, in many cases you can probably just modify the existing policy.
A one-way trust with the server domain trusting the account domain is all that should be necessary. You will have to grant full mailbox rights and send as rights on each mailbox to the corresponding user account.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
We added the trust, but Exchange doesn't see the new domain. I've tried both the EMC and powershell (add-mailboxpermission useralias -user"newdomain\alias" accessrights-fullaccess) error says "user or group not found please make sure you
have typed it correctly"
What else needs to be done for Exchange to see the new domain and users?
Thanks, MikeV MCSE 2012

Outlook can't connect with Exchange 2013 after migration from Exchange 2007

<style type="text/css">P { margin-bottom: 0.21cm; }</style>
Hello,
recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
To try to resolve it we've done:
- Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
- Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
- In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
- Check Outlook Anywhere block: we've cheked.
Currently server state:
- Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
unless the mailbox. After a restart it can't start.
-The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
We continue to try to resolve the problem.
Thanks to all in advance!
Testing RPC / HTTP connectivity.
Error in testing RPC / HTTP.
additional Details
Elapsed time: 24295 ms.
Test steps
Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
Error in automatic detection test .
additional Details
Elapsed time: 24294 ms.
Test steps
Attempting each method of contacting the Autodiscover service .
Failed to properly contact the Autodiscover service using all methods.
additional Details
Elapsed time: 24294 ms.
Test steps
Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 1509 ms.
Test steps
Attempting to resolve the host name in DNS empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 80.36.252.194
Elapsed time: 507 ms.
Testing TCP port 443 on the host to ensure empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 464 ms.
Testing the SSL certificate to make sure it is valid.
The SSL certificate is not exceeded one or more certificate validation checks .
additional Details
Elapsed time: 537 ms.
Test steps
Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
additional Details
Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
Elapsed time: 454 ms.
Validating the certificate name .
The certificate name was validated successfully .
additional Details
Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
Elapsed time: 1 ms.
Is validating the trusted certificate .
Validation Error trusted certificate.
Test steps
Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = mail.empresa.com .
Could not build a certificate chain for the certificate.
Tell me more about this issue and how to resolve
additional Details
The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
Elapsed time: 31 ms.
Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 21723 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 498 ms.
Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
The specified port is blocked , not listening or does not generate the expected response .
Tell me more about this issue and how to resolve
additional Details
Network Error communicating with the remote host.
Elapsed time: 21224 ms.
Attempting to contact the Autodiscover service with the HTTP redirect method .
Error when trying to contact the Autodiscover HTTP redirect method .
additional Details
Elapsed time: 606 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 14 ms .
Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 202 ms.
Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
additional Details
Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
Elapsed time: 388 ms.
Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
additional Details
Elapsed time: 186 ms.
Test steps
Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
Not the Autodiscover SRV record in DNS found .
Tell me more about this issue and how to resolve
additional Details
Elapsed time: 186 ms.
Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
Tell me more about this issue and how to resolve
additional Details
No Autodiscover CNAME record for your domain ' empresa.com ' .
Elapsed time: 268 ms.
jspt

Hello,
We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
$AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
Name                                 : EXCHANGE13
Fqdn                                 : EXCHANGE13.domain.local
ClientAccessArray                    :
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : EXCHANGE13
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
AlternateServiceAccountConfiguration :
IsOutOfService                       : False
WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
Identity                             : EXCHANGE13
IsValid                              : True
ExchangeVersion                      : 0.1 (8.0.535.0)
DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                       (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=First Organization,CN=Microsoft
                                       Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
WhenChanged                          : 09/03/2014 12:46:07
WhenCreated                          : 08/03/2014 19:15:54
WhenChangedUTC                       : 09/03/2014 11:46:07
WhenCreatedUTC                       : 08/03/2014 18:15:54
OrganizationId                       :
OriginatingServer                    : severdc.domain.local
ObjectState                          : Unchanged
I hope this stuff can help you.
Thanks!!
jspt

OWA functionality in Exchange 2007 coexistance with 2013

Similar Messages

Maybe you are looking for