Calander Sharing Permission is not effective between Exchange 2007 & Exchange 2013 User

When a Exchange 2013 mailbox user share a calander with user in Exchange 2007 with OWNER permission, but Exchange 2007 user cannot modify or view full details of Exchange 2013 user calander.
And same behavior from Exch2007 user sharing calander with Exch2013 user.
In both scnarioes we can view only free/busy information. Cannot see full details of the meetings, cannot edit/modify. But permissions are set correctly.
Getting Yes or No prompt window with message "You dont have permission to view the calander, Do you want to as User A to share his or her calander with you?"
We are in Co exsistance with Exch2007 and Exch2013 CU3.

Hi,
Does the issue happen to all users? What about Exchange 2007 users share calendar with Exch2007 users?
Please double check whether calendar permissions are configured properly. If possible, we can remove the permission in Outlook then re-add it back later to check whether it works.
Thanks,
Winnie Liang
TechNet Community Support

Similar Messages

OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.

hi ALL
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
2 cas Servers
first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
please support
thanks

Hi,
According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
If I have misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
Please run following command to double check the database status:
Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
for further troubleshooting.
Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
Best Regards,
Allen Wang

Mail flow problem between Exchange 2013 and 2010

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 ???

one more thing, when i open exchange queue i got this error:
451 5.7.3 cannot achieve exchange server authentication. attempted failover to another host but that did not succeed. either there are no alternate hosts, or delivery fail
For this error refer to the following article:
http://support.microsoft.com/kb/979175
Thanks, MikeV MCSE 2012

Exchange 2013 users cannot open public folders on exchange 2010

Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
client version is outlook 2013
outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
outlook any where external host name field is blank (we need to keep outlook any where disable for external)
outlook anywhere internal authentication is set to NTLM and Client require SSL to false
I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggest

Hello,
Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
If the user has no permission to see the public folder, please check the permission.
=============================================================
1. Open ADSIEDIT.
2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
Administrative Group ->CN=Databases ->CN= PF Database.
3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Differences between SharePoint 2007 and 2013 security options?

Hi,
We just did a test upgrade from Sharepoint 2007 to Sharepoint 2013 by copying over the content database. One thing we are noticing is that users who had permissions to upload to a document library no longer have that option in 2013. Is there a difference
between the 2007 and 2013 "contribute" permission?
What can I do to fix this issue?
thanks,
Sherazad

their is no difference between 2007 & 2013 for Contribute premission.
Contribute having the same rights in 2007 and 2010.
Read permissions, plus:
Add Items
Edit Items
Delete Items
Delete Versions
Browse Directories
Edit Personal User Information
Manage Personal Views
Add/Remove Personal Web Parts
Update Personal Web Parts
You can further check here:
SP 2013: http://technet.microsoft.com/en-us/library/cc721640.aspx
Moss 2007: http://technet.microsoft.com/en-us/library/cc721640(v=office.12).aspx
May be you edit the Contribute permission level, make sure its on its default.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Exchange 2013 wil NOT send email, same problem as every other exchange 2013 user, typical everything.

I have a brand new dell server 2 netwrok cards. One WAN one LAN connected, each with its respective DNS server added to the card. In OWA the sent email shows in drafts, in outlook it shows in sent items, the user NEVER gets it, internally or externally.
i get all mail from the internet, exactly as expected no problem, all tests show this is working everything checks out fine, server runs great, full blown domain controller with exchange 2013 added. ONLY problem after the 9th install, is still the same, exchange
will NOT send email, everything else works perfectly event log looks great. I do see the DNS error where a DNS server on that network card is not responding crap, which is not true, internet works, al pages everything, NO firewall Bare connect while i get
it to work. I HAVE been over the forums for the last week, tried all done all. i am an MSCE, was an MCSE instructor for 10+ years, Exchange Administrator, Exchange instructor for years, so yea, i am not some newb who has no clue, this DOES NOT WORK. it
came at the CU1 level right out of the box, so i did not install and break it myself Microsoft is now selling this broken. Where do i go what do i do here. Like i said, every other aspect is in perfect order, Just email not sent, not showing in exchange tracking
logs, and that DNS error on the event log, and YES i made the send connector, and the 3 setting it asks, not like that could be wrong, i mean seriously you put in very little info, any wrong entry would be obvious to even a child. SO walk me through what is
going worng, as soon as this server sends an email, i am done building this domain, Please Help here.

Performing Outbound SMTP Test
The outbound SMTP test was successful.
Additional Details
Elapsed Time: 18739 ms.
Test Steps
Attempting reverse DNS lookup for IP address xxx.xxx.xxx.148.
The Microsoft Connectivity Analyzer successfully resolved IP address xxx.xxx.xxx.148 via reverse DNS lookup.
Additional Details
The Microsoft Connectivity Analyzer resolved IP address xxx.xxx.xxx.148 to host wsip-xxx.xxx.xxx.148.ri.ri.cox.net.
Elapsed Time: 187 ms.
Performing Real-Time Black Hole List (RBL) Test
Your IP address wasn't found on any of the block lists selected.
Additional Details
Elapsed Time: 18453 ms.
Test Steps
Checking Block List "SpamHaus Block List (SBL)"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 1050 ms.
Checking Block List "SpamHaus Exploits Block List (XBL)"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 27 ms.
Checking Block List "SpamHaus Policy Block List (PBL)"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 60 ms.
Checking Block List "SpamCop Block List"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 90 ms.
Checking Block List "NJABL.ORG Block List"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 8161 ms.
Checking Block List "SORBS Block List"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 119 ms.
Checking Block List "MSRBL Combined Block List"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 61 ms.
Checking Block List "UCEPROTECT Level 1 Block List"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148 wasn't found on RBL.
Elapsed Time: 63 ms.
Checking Block List "AHBL Block List"
The address isn't on the block list.
Additional Details
IP address xxx.xxx.xxx.148wasn't found on RBL.
Elapsed Time: 8818 ms.
Performing Sender ID validation.
Sender ID validation was performed successfully.
Additional Details
Elapsed Time: 97 ms.
Test Steps
Attempting to find the SPF record using a DNS TEXT record query.
The Microsoft Connectivity Analyzer wasn't able to find the SPF record.
Additional Details
No records were found.
Elapsed Time: 97 ms.

External Mail Flow not coming into Exchange 2013 Server

We just finished migrating from Exchange 2007 to Exchange 2013 and when I disable a certain receive connector on Exchange 2007 we stop receiving external emails. I have reviewed all of the Exchange 2013 Receive Connectors and everything looks to be fine
but the server does not get mail flow. If anyone could assist with this issue that would be great.
Thanks,
Ryan

Hi,
According to your description, all your inbound mails cannot be received in your Exchange 2013 server after you disable a receive connector in your Exchange 2007 server. If I misunderstand your meaning, please feel free to let me know.
If yes, since your MX record has been configured properly for your Exchange 2013 server, we can begin with checking the A record for the Exchange 2013 server and confirm if all external mails cannot come in your organization. And we can depend on the following
troubleshooting to narrow down the mail flow issue:
1. Check the NDR information if there is NDR.
2. Check Telnet to test the mail flow:
http://technet.microsoft.com/en-us/library/bb123686(v=exchg.150).aspx
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

RBL not working on Exchange 2013 Edge Transport

Single multi-role server with a couple of mailboxes, recently added an Edge Transport server. After configuring the Edge Subscribtion I added sen.spamhaus.org as a RBL Provider:
Add-IPBlockListProvider -Name Spamhaus -LookupDomain zen.spamhaus.org
This is not working. A lot of spam is still entering Exchange and the http://www.crynwr.com/spam/ test failed.
Both servers run Exchange 2013 CU5.
Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

Hi,
Yes, the command is specific for provider SpamHaus.
http://tweaks.com/windows/40003/cut-down-on-spam-with-ip-block-list-providers-rbl/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Have you added the additional parameters in the command and did it work?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

SME 7.1 not working with Exchange 2013 SP1 CU6

Hello, i tried upgrading to SME 7.1 on our Exchange 2013 SP1 CU6, but when trying to configure the Exchange Server in the SME management console using the configuration wizard, it gave an error before the LUN mapping page, saying "Failed to get Exchange information for server" and "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.". I upgraded Snapdrive to 7.1, verfied all credentials according to the manuals, re-installed and rebooted multiple times (registry and filesystem cleaned, even tried to rename the existing SnapInfo directory, ...), stopped all other services on the server but without any change... Every time when trying to run the configuration wizard, the debug log shows no errors, lists all Exchange information and ends with the following lines:[11/18 12:51:58 155] Exit CSmeCDOExm::GetExchangeStructureInternal 0x0
[11/18 12:51:58 155] Exit CNtapSnapMgr::GetExchangeStructure: 0x0
[11/18 12:51:58 233] Enter CSmeServerBase::~CSmeServerBase ...
[11/18 12:51:58 248] m_ptrSnapShot released
[11/18 12:51:58 248] m_pISnapShot4 released
[11/18 12:51:58 248] m_pISnapShot5 released
[11/18 12:51:58 248] m_pISnapShot6 released
[11/18 12:51:58 248] m_pISnapShot7 released
[11/18 12:51:58 248] m_pISnapShot8 released
[11/18 12:51:58 248] m_pISnapShot9 released I ended up uninstalling SME 7.1 and re-installed SME 7.0 which is working. Exchange Server: ESXi 5.5 VM, Windows Server 2012 R2 (with current patches), Exchange 2013 SP1 CU6 - no DAG, single server installation (in co-existence with Exchange 2010), 4 iSCSI LUNs created with Snapdrive (1x Log, 3x Store), System drive and Exchange installation drive on vmdk Disks (via ESXi -> NFS store on the same NetApp)NetApp: FAS 2240-2 with Data ONTAP 8.1.4P1 7-mode (with complete license bundle) Anyone else got this problem or even better - a solution?

We could not reproduce the error with the upgrade workflow.Looking at the error and the relevant function, we could force the problem in following conditions: -SME is configured or ran at the DAG level-one of the following services is stopped or not responding on one nodes of the DAG Snapdrive Service, Snapmanager Service, Snapdrive Storage Management Service,Snapdrive Management Service. Would be good if we could get the output of following powershell cmdlet before and after the upgrade: Get-Service –ComputerName Node1, Node2, Node3 –name Snap*, SDMGMT*, SWSvc Best regards,Dan

Outlook clients on Windows XP not connecting to Exchange 2013

Previously outlook on XP machines were working fine with a SAN certificate having the mail.company.com as common name. Since we're moving to Exchange Hybrid we reissued the certificate and made company.com as the common name after that change all Outlook
on XP machines are not able to connect to the Exchange 2013. It is always asking for password. Outlook clients on windows 7 and 8 have no problem.
I wanted to run the below commands but I'm worried that it may break the connections of the Windows 7 and 8 machines:
Set-OutlookProvider
EXCH -CertPrincipalName msstd:mail.XXX.com
Set-OutlookProvider
EXPR -CertPrincipalName msstd:mail.XXX.com
Is it safe to run the commands or I should just reissue again the certificate and make the mail.company.com as the common name? Will there be any issues with Exchange 2013 hybrid if I do this?

I just reissued the certificate and all Outlook on windows xp are working now.

POP3 is not working in Exchange 2013

Hi,
Facing Wiered issue in Exchange 2013, POP3 is not working ... When configuring POP3 in outlook it failed to authenticate.
unknown user name or bad password. [Error=ProxyNotAuthenticated Proxy=ZAJNBEXC03.cws.sasol.com:1995:SSL]"
Amit

Credentials are correct
Here is the output ..... pls. let me know if this is correct
[PS] C:\Windows\system32>Get-PopSettings |fl
RunspaceId                        : ecc593c8-067e-4d9d-aca1-c121295b8499
Name                              : 1
ProtocolName                      : POP3
MaxCommandSize                    : 512
MessageRetrievalSortOrder         : Ascending
UnencryptedOrTLSBindings          : {[::]:110, 0.0.0.0:110}
SSLBindings                       : {[::]:995, 0.0.0.0:995}
InternalConnectionSettings        : {ZAJNBEXC02.cws.sasol.com:995:SSL, ZAJNBEXC02.cws.sasol.com:110:TLS}
ExternalConnectionSettings        : {ZAJNBEXC02.cws.sasol.com:995:SSL}
X509CertificateName               : mail.sasol.com
Banner                            : The Microsoft Exchange POP3 service is ready on ZAJNBEXC02.
LoginType                         : PlainTextLogin
AuthenticatedConnectionTimeout    : 00:30:00
PreAuthenticatedConnectionTimeout : 00:01:00
MaxConnections                    : 2147483647
MaxConnectionFromSingleIP         : 2147483647
MaxConnectionsPerUser             : 16
MessageRetrievalMimeFormat        : BestBodyFormat
ProxyTargetPort                   : 1995
CalendarItemRetrievalOption       : iCalendar
OwaServerUrl                      :
EnableExactRFC822Size             : False
LiveIdBasicAuthReplacement        : False
SuppressReadReceipt               : False
ProtocolLogEnabled                : True
EnforceCertificateErrors          : False
LogFileLocation                   : D:\Program Files\Microsoft\Exchange Server\V15\Logging\Pop3
LogFileRollOverSettings           : Daily
LogPerFileSizeQuota               : 0 B (0 bytes)
ExtendedProtectionPolicy          : None
EnableGSSAPIAndNTLMAuth           : True
Server                            : ZAJNBEXC02
AdminDisplayName                  :
ExchangeVersion                   : 0.10 (14.0.100.0)
DistinguishedName                 : CN=1,CN=POP3,CN=Protocols,CN=ZAJNBEXC02,CN=Servers,CN=Exchange Administrative
                                    Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Sasol,CN=Microsoft
                                    Exchange,CN=Services,CN=Configuration,DC=cws,DC=sasol,DC=com
Identity                          : ZAJNBEXC02\1
Guid                              : 4c5d5409-1b4a-4127-a4cd-11b064156322
ObjectCategory                    : cws.sasol.com/Configuration/Schema/ms-Exch-Protocol-Cfg-POP-Server
ObjectClass                       : {top, protocolCfg, protocolCfgPOP, protocolCfgPOPServer}
WhenChanged                       : 2015-02-24 08:57:41 AM
WhenCreated                       : 2014-12-08 11:25:29 AM
WhenChangedUTC                    : 2015-02-24 06:57:41 AM
WhenCreatedUTC                    : 2014-12-08 09:25:29 AM
OrganizationId                    :
OriginatingServer                 : ZAJNBWCWSFGC001.cws.sasol.com
IsValid                           : True
ObjectState                       : Unchanged
==================================================================
In my case I have 4 DAG and each having 3 server. .. I am POP test and it is failing with below error
RunspaceId                  : 75d8800c-3f32-4750-8fe1-940133eaf6e8
LocalSite                   : AFR-BYN
SecureAccess                : True
VirtualDirectoryName        :
Url                         :
UrlType                     : Unknown
Port                        : 0
ConnectionType              : Plaintext
ClientAccessServerShortName : ZAJNBEXC01
LocalSiteShortName          : AFR-BYN
ClientAccessServer          : ZAJNBEXC01.cws.sasol.com
Scenario                    : Create a MailboxSession object.
ScenarioDescription         : Creating MailboxSession object to access the mailbox [[email protected]].
PerformanceCounterName      :
Result                      : Failure
Error                       : Unable to create MailboxSession object to access the mailbox [[email protected]].
                              Detailed error information:
                              [Microsoft.Exchange.Data.Storage.WrongServerException]: The user and the mailbox are
in different Active Directory sites. Inner error [Microsoft.Mapi.Ma
UserName                    : migrationtest3
StartTime                   : 2015-02-24 10:58:51 AM
Latency                     : -00:00:00.0010000
EventType                   : Error
LatencyInMillisecondsString :
Identity                    :
IsValid                     : True
ObjectState                 : New
Amit

Redirect emails in OWA and Outlook 2010 not working in Exchange 2013

I have an new install of Exchange 2013 with all updates.
When I setup an inbox rule to redirect messages to another contact it is not working.
When I used Outlook 2010 and ran the rule manually I received this error:
"the redirect action is not currently supported with run rules now"
It seems that I didn't setup up something correctly in Exchange 2013 or a feature is not turned on. Please assist.
In the EM console when I setup forwarding that is working. Its the inbox rule redirect not working.

Hi,
From your description, I recommend you use the following cmdlet to ensure that the DeliverToMailboxAndForward parameter is set to $True.
Get-Mailbox <identity> | fl DeliverToMailboxandForward
If this parameter is false, you can use the Set-Mailbox cmdlet to set it and check the result.
Hope this can be helpful to you.
Best regards,
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]
Amy Wang
TechNet Community Support

Throttling policy not working on Exchange 2013 CU6

Hi,
We have a test throttling policy to restrict a mailbox to send at most 2 messages
per minute in our live Exchange 2013 CU6 enviroment. It was associated to a test mailbox. We have separated installed 2 mailboxe and 2 cas server roles in our enviroment. I have checked latest CU-s (7 & 8) but these are
not fixing any related bugs.
We tried lots of workaround (see below list) and solutions to fix this but it is still not working with outlook MAPI and OWA client.
Throttling policy not working
smtp service restart
RPC Client Acces service restart
The policy details:
Get-ThrottlingPolicy low_rate_limit |fl *limit*
MessageRateLimit : 2
RecipientRateLimit : 1000
Get-mailbox [email protected] | fl ThrottlingPolicy
ThrottlingPolicy : low_rate_limit
Do you have any idea what is the problem?
Thank you in advance.
br,
Zoltan

Hi Zoltan,
Base on my research, you need to configure the MessageRateLimit parameter on receive connector also.
The MessageRateLimit parameter specifies the maximum number of messages that can be sent by a single client IP address per minute. The default value for a Receive connector configured in the Transport service on a Mailbox server is
unlimited. The default value for a Receive connector configured on an Edge server is 600 messages per minute. The valid input range for this parameter is 1 to 2147483647. To remove the message rate limit on a Receive connector, enter a value of
unlimited.
https://technet.microsoft.com/en-us/library/bb125140(v=exchg.150).aspx
Best regards,
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]
Niko Cheng
TechNet Community Support

AutoReplyState is Enabled. But still OOF is not working on exchange 2013

Hi All,
We have exchange 2013 installed. How can I make our OOF (Out of Office) reply works?
Thanks in advance.
Jake

Hi Sneff,
Sorry, but I can't find anything on my event viewer that is "MSExchangeMailboxAssistants". Do i need to start the "Microsoft Account Sign-in Assistant" in services?
Checking oof with
https://testconnectivity.microsoft.com/. I got lots of "x". Please give some advice :
Exchange Web Services synchronization, notification, availability, and Automatic Replies.
Not all tests of Exchange Web Services tasks completed.
Additional Details
Elapsed Time: 42852 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for blank.com.ph.
Testing Autodiscover failed.
Additional Details
Elapsed Time: 42852 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Additional Details
Elapsed Time: 42852 ms.
Test Steps
Attempting to test potential Autodiscover URL https://blank.com.ph:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Test Steps
Attempting to test potential Autodiscover URL https://autodiscover.blank.com.ph:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 21299 ms.
Test Steps
Attempting to resolve the host name autodiscover.blank.com.ph in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host autodiscover.blank.com.ph to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_ctl01_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Test Steps
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Additional Details
Test Steps
Checking if there is an autodiscover CNAME record in DNS for your domain 'blank.com.ph' for Office 365.
Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl04_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
There is no Autodiscover CNAME record for your domain 'blank.com.ph'.
Elapsed Time: 24 ms.
Thanks
Jake

Lync integration not working after Exchange 2013 SP1 is installed...

Hi,
I have two Exchange 2013 servers running and everything is fine, almost.
The problem is that on the first server we had OWA with Lync integration working before installing SP1, but after the installation of SP1, it doesn't Work any more.
The second server was installed with SP1 from the start, but we can't get the Lync integration to Work on this one either..
When we log in to OWA, it just starts to sign in but then says "there was a problem signing in, if this continues please contact your helpdesk"
I have checked the Exchange server for events, and i can see the event ID 112 everytime i recycle the Application Pool, so there are some connection between Exchange and Lync..
Have any of you Guys seen or experienced any thing like this?
Thanks in advance.
Regards
Kenneth

Hi,
I recommend that you refer to the following article to troubleshoot the issue:
Troubleshooting tips for Exchange 2013 OWA IM Integration to Lync 2013
This post describes how to configure Exchange 2013 OWA to have IM integration to Lync 2013. Here I would like to give some troubleshooting tips in case you can't get the integration to work.
In addition, here is a similar thread for your reference:
Lync 2013 with Exchange 2013 SP1 OWA integration failed
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Calander Sharing Permission is not effective between Exchange 2007 & Exchange 2013 User

Similar Messages

Maybe you are looking for