Setup a simple sales funnel with exchange 2013 public folders and outlook 2010 -2013

BCM for Outlook is big and has too many choices. What we want is a combination of contacts and tasks within a public folder so we can see what others are doing. If possible I want
to make a connection between an contact and a task. The task should have some extra fields like branches responsible organization members status etc. Does anyone have a simple solution which is easy to implement in a small organization of 10 people?

Hello,
First of all thank you for your answer. The Outlook version I'm using is 14.0.7113.5005 and the Exchange versuin is CU3. As I'm testing it on XP client it is probably the issue in the PS. I'll try it with Win7 client probably tomorrow. I wonder if there
exists any kind of workaround for XP clients.
Thank you in advance,
Peter

Similar Messages

Accounts made in o365 can't access legacy public folders - Migrated through 2010/2013 Hybrid can access

We've added two 2013 hybrid servers to our existing 2010 environment. Added the CAS role to all 2010 mailbox servers per ( https://technet.microsoft.com/en-us/library/dn249373%28v=exchg.150%29.aspx ) and currently have public folders (located on our
2010 mailbox servers) working in Outlook client for users whose mailboxes have been migrated from on-prem 2010 to o365. The problem is when we create a new user in o365, that user CAN see that we have public folders via Outlook client, but when we expand
the public folder list a credential window pops up and will not accept any set of credentials (even those of working hybrid migrated accounts).
We are following this method when creating new o365 accounts:
1) Make a user in AD
2) Dirsync the user
3) License the user for exchange
4) Run on on-prem mailbox server via Exchange Management Shell: Enable-RemoteMailbox "[email protected]" -RemoteRoutingAddress "[email protected]"
5) In o365 Remote Exchange Powershell run: Get-Mailbox -identity "[email protected]" |fl Identity,ExchangeGUID
6) Copy ExchangeGUID
7) Back on on-prem mailbox server via Exchange Management Shell: Set-RemoteMailbox "[email protected]" -ExchangeGUID <paste GUID here>
8) Dirsync the user again
I've compared two Remote User Mailboxes, ones that were migrated via Hybrid, and ones that were created in o365 and the settings look identical outside of the attribute "RemoteRecipientType" is set to Migrated vs ProvisionMailbox. I'm not
sure what else the difference in these accounts could possibly be that would be causing this credential failure.
Any thoughts would be appreciated.

Hi,
Please do the following steps to create an Exchange Online mailbox in your Hybrid environment:
Method 1: Create a remote mailbox for an existing user.
If you already have created a user in Active Directory, and the user has already been synced to online with license, we can give that user a mailbox in Exchange Online by using the Exchange Management Shell cmdlet Enable-RemoteMailbox on
your on-premise Exchange server:
Get-User “User1” | Enable-RemoteMailbox
Then the mailbox is enabled with an Exchange Online mailbox. We can check the mailbox by running the following command in On-premise Exchange server:
Get-RemoteMailbox “Test1” | FL *address*
Method 2: Directly create a new remote mailbox.
1. Create the remote mailbox in On-premise Exchange server by running:
$Credentials = Get-Credential
New-RemoteMailbox -Name "Test2" -Password $Credentials.Password -UserPrincipalName
[email protected]
2. Launch dirsync and assign a license to the newly created user with Office 365 account.
Then Test2 can sign in, using his on premises credentials, and open his online mailbox.
For more information about the remote mailbox, please refer to:
http://blogs.technet.com/b/ilvancri/archive/2011/08/24/exchange-online-exchange-on-premises-shared-namespace-how-about-mail-routing.aspx
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]
Winnie Liang
TechNet Community Support

Merging existing 2013 Public Folders and 2010 Public Folders from different organization.

Following recent acquisition of another company we faced the following situation:
Company A has Exchange 2013 Organization up and running and already using new Public Folders migrated from 2010 when we upgraded.
Company B has Exchange 2010 Organization with their own PF infrastructure.
When it comes to migration, there's already public folder mailbox which was created when first migration occured.
I cant figure next steps to merge those PF infrastructures at the moment, as removing public folder mailbox prior migration is not an option, since we already have big amount of data in 2013 Organization.
Have anyone done similiar task and if so, how did you overcome this limitation?

You're looking at a third-party product. MigrationWiz does public folders. There are other cloud-based migration solutions, but I don't know whether they support public folder migrations.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Migrate Exchange 2003 Public folders and OAB to Office365?

Hi guys,
I am trying to migrate exchange 2003 public folders to office 365. I have read various documentation however they were either out of date or half-solutions.
The company stored OAB's in each public folder as well, how do I go about migrating these lists into office 365? Will it just "work" if I migrate the public folders across?
Thanks,
Alex

Hi,
If you are migrating from inhouse 2003 to office 365, then the best options for you are-
1. Either you can go for the manaul process. You can create PST files and can upload them to mailboxes through office 365 account.
Kindly refer the below mentioned link for the same
http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx
2. Or you can go for any 3rd party tool using the same you can migrate your public folders to office 365. This is required when you need to avoid the risks associated and need to keep your environment up and running even while migration process. Respond
back for third party tool suggestions.

Never ending story: Exchange and Outlook 2010/2013 - Read receipts (reading confirmation) implementation is buggy

OK, I try it again (for the fifth time or so), maybe anywhere in the big microsoft world there is ONE support engineer that is able to recognize a bug and hand it over to the development????
In several cases the read receipt does not contain the sending time of the original message, instead it contains (quite senseless) the time when the receipt itself has been sent.
The only information in the read receipt is the subject of the original mail which may be identical in longer mailthreads to several (dozends of) mails. So in this implementation you are not able to find out to which message a read receipt really relates.
So we cannot prove at all if a single mail in a thread has been read or not. The printout of such a receipt does not have any information that can be used in a meeting or discussion.
Since this situation obviously lasts for several years I'd like to ask
how I can get a working read-receipt-functionality for professional eMail-handling???
It seems that the problem does not lie in the content of the MDN sent by the Exchange server.
If I look into a copy of such a sent MDN with Thunderbird, it tells me for example, that my mail, sent on 15th Juli 2013 14:43:47 (UTC+1) has been read on 15th Juli 2013 14:50:08, which is correct.
But in combination with Outlook I get the same MDN displayed like follows:
Your message at... subject... sent Monday, 15. Juli 2013 14:51:30 (UTC+01:00)... has been read on Monday, 15. Juli 2013 14:51:16 (UTC+01:00) (Text translated from German to English)
So Outlook exchanges the timestamps and falsifies the content of the MDN.
This does only appear in combination with an Exchange server. If I work with a POP3 account and Outlook and send a message to an Exchange 2010 mailbox the correct timestamps are displayed within the returned MDN-message.
All involved systems are set to German (DE-de), the timezone on all systems is UTC+1
Here a small table with my tests
I've used Outlook on all Clients, 2010 and 2013.
Sender: sends initial mail and gets the Reading Confirmation
Receiver: gets the initial mail and sends the MDN
Sender     |     Receiver     |     MDN Display
POP3        |     Exchange   |     correct
Exchange |     Exchange   |     fail (displays wrong "sent"-time)
POP3        |     POP3         |     correct
Exchange |     POP3         |     fail (displays wrong "sent"-time)
It is obvious this cannot be a "feature". This is different behaviour depending on the senders Account type and one of this two scenarios must be a bug.
Could you help me further on this, please?

Almost no - the MS-Support here in this website was completely overchallenged to even understand this issue. I've tried several times to address this in this forum with no success. The "supporters" here had only one target - to quickly get this
"complicated" case off their desks.
The Office 365 support was much more competent and able to understand the problem. They escalated this to the development team (which lasted about 3 months, dozends of telephone calls and about 20 hours working time, which I had to donate to Microsoft freely)
and located the Problem in Exchange Server.
The result was that they promised to fix it in Exchange Server 2013, but there will be no Bugfix in Exchange 2010. I am waiting for the fulfilment of this promise since over 6 months.
Microsoft seems not to have any problem to leave their (professional and very expensive) Exchange software in a buggy state.
My conclusion: If Exchange 2010 runs out of maintenance I'll switch to Linux and Zarafa Server. The Zarafa guys are able to understand and fix their bugs and I do not have to donate thousands of Euros in working time only to get them understanding their
own bugs.
PS: You need only to press F1 in Office, especially in Access in the German language variant and you get an impressing lesson how desolate Microsoft is working today. Pressing F1 in Access 97 or XP lets you know, how much better they were some years ago.
An impressive deep fall down to the ground.
Regards, Conny

Problems with Win 7 64-bit and Outlook 2010 with iCloud setup

I have an iPhone 4, iPAD2, Windows Vista Desktop (home) and Windows 7 64-bit laptop (work) and I'm trying to sync Outlook 2010 on my laptop with Calendars and Contacts. iCloud works great on the iPhone, iPAD and Home Dekstop....but...
When installing iCloud on my Laptop, the software gives me the following error when trying to setup the system:
Your setup couldn't be started because the iCloud serverstopped responding.
Error: 0x80040108: Server Did Not Accept HTTP Request(HTTP 400)!
What is interesting is that it is sending all of my calendar event contacts email invites from my @me.com account but fails to install on my laptop.

Tony,
Were you ever able to fix this error? If so, please let me know what you have done. I have had the same issue with the iPhone 4 and the iPhone 4S.

Sync Outlook contacts and calendar with iTunes between iPhone 4 and Outlook 2010 (32bits) USB only manually, not automatically.

Hello guys,
After disabeling and enabeling the option automatic sync iPods, iPhones and iPad in iTunes (settings > devices), my iPhone 4 is only syncing manually and not automatically as before the option change.
With manually sync I mean connecting the usb cable and pushing the synchronisation button in iTunes. I reinstalled Outlook (Office 2010 32bit) and iTunes but it did not solve the problem and it's still only manually syncing. I also renewed the Windows Profile. Is there an option I missed in iTunes or Outlook? In Outlook is the iTunes Outlook Addin present and enabled....
How can I solve this problem?
Thanks, William

Hi, could you specify what you did. It appears that nothing on my iPhone syncs any more. I have an iMac and iPhone 4 running the latest system updates. Thanks!

Migrating from Exchange 2007 to Exchange 2013 Public Folders coexistence

Hi all, I'm migrating from Exchange 2007 SP3 to Exchange 2013 SP1.
I have an Exchange 2007 server (Client Access, Hub Transport and Mailbox Server) in Site A, mailboxes and Publics Folders
In another Site in Site B, I have already installed (Client Access and Mailbox Server) Exchange 2013 server.
I am migrating test users, the fact is that users who migrated to Exchange Server 2013 Public folders do not see.
How I can make the migrated users from viewing the Exchange 2007 Public Folders duration coexistence?
Is there a "how to" to migrate Public Folders from Exchange 2007 to Exchange 2013?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

How do I grey out outlook 2010 & 2013 Signature Options

Hello,
I know by using the administrative templates for outlook 2003/2007 that you can disable, or grey out the ability to make changes to your signature. Our company is looking to deploy a template signature, and we want to have the ability to disable users from
changing their signatures. We are using Office 365 for e-mail and outlook 2010/2013. Obviously if the user wants to edit their signature to each e-mail they write (manually) we can't control that.
What I am looking for is a way through group policy, local registry settings or something else that will allow us to disable users from changing signature settings. The only setting similar to this for the ADM Templates for 2010+ is to completely disable
signatures, which we obviously do not want.
Please let me know if you have any other ideas/suggestions.
Thank you!

You can disable many commands using DisabledCmdBarItemsList - this is in the GPO under Outlook > disable Items in user interface > custom
HKEY_CURRENT_USER\Software\Policies\Microsoft\office\15.0\outlook\DisabledCmdBarItemsList
String name: TCID1 (where 1 is incremented for each command you want disabled)
The value for the Insert Signature command on the ribbon in forms is 5608 but I didn't see any other signature commands on the list - and it doesn't disable the right click, choose signature command. A spreadsheet with the command id's is here - http://www.microsoft.com/en-us/download/confirmation.aspx?id=6627
http://www.slipstick.com/how-to-outlook/group-policy-disable-commands/
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Exchange AutoDiscover not working correctly in 2010/2013 environment

Here's my setup:
Mixed environment transitioning:
Exchange 2010 running on Server 2008 in a VM
Exchange 2013 running on Server 2012 in a VM
I have split dns so that autodiscover.domain.com points to my 2013 server internally and my 2010 server externally. When setting up new profiles in outlook internally, autodiscover seems to work fine. However, when I try moving the public autodiscover.domain.com
DNS record over to the 2013, things stop working (like auto profile setup).
I know that the 2013 server is reachable from the outside because mail.domain.com will to go owa and ecp without a problem. I can log in to both without an issue.
If I point public DNS back to my 2010 server, then all is well again with outlook anywhere and mobile connectivity.
I'm not really sure what needs to be tweaked for the 2013 server to be ready to take over the day to day communications so that I can decommission my 2010 server.
Here are the results of the connectivity analyzer:
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for me.
Testing Autodiscover failed.
Additional Details
Elapsed Time: 1774 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: 1773 ms.
Test Steps
Attempting to test potential Autodiscover URL https://domain.com:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 489 ms.
Test Steps
Attempting to resolve the host name domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 98.129.228.152
Elapsed Time: 165 ms.
Testing TCP port 443 on host domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 97 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 225 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server domain.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US, Issuer: CN=Equifax Secure Global eBusiness CA-1, O=Equifax Secure Inc., C=US.
Elapsed Time: 170 ms.
Validating the certificate name.
Certificate name validation failed.
Tell me more about this issue and how to resolve it
Additional Details
Host name domain.com doesn't match any name found on the server certificate CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US.
Elapsed Time: 1 ms.
Attempting to test potential Autodiscover URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 1009 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: x.x.x.x
Elapsed Time: 70 ms.
Testing TCP port 443 on host autodiscover.domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 189 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 300 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.domain.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated, Issuer: CN=PositiveSSL CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.
Elapsed Time: 220 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name autodiscover.domain.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 1 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE.
Elapsed Time: 34 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 5 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 5/19/2014 12:00:00 AM, NotAfter = 5/18/2016 11:59:59 PM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 276 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Additional Details
Elapsed Time: 172 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Sat, 19 Jul 2014 03:44:42 GMT
Server: Microsoft-HTTPAPI/2.0
Elapsed Time: 171 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Elapsed Time: 207 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: x.x.x.x
Elapsed Time: 15 ms.
Testing TCP port 80 on host autodiscover.domain.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 76 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
Additional Details
An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: HTTP Response Headers:
X-FEServer: SMSE2013
Content-Length: 0
Date: Sat, 19 Jul 2014 03:44:42 GMT
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Elapsed Time: 115 ms.
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
Elapsed Time: 39 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.domain.com in DNS.
The Autodiscover SRV record wasn't found in DNS.
Tell me more about this issue and how to resolve it
Additional Details
Elapsed Time: 39 ms.
Checking if there is an autodiscover CNAME record in DNS for your domain 'domain.com' for Office 365.
Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning.
Tell me more about this issue and how to resolve it
Additional Details
There is no Autodiscover CNAME record for your domain 'domain.com'.
Elapsed Time: 28 ms.
I just double checked my SSL cert and it has the three typical entries:
DNS Name=mail.domain.com
DNS Name=AutoDiscover.domian.com
DNS Name=domain.com
I have assembled the output for the following commands
HERE
Get-OutlookProvider | fl
Get-OutlookAnywhere | fl
Get-ActiveSyncVirtualDirectory | fl
Get-AutodiscoverVirtualDirectory | fl
Get-EcpVirtualDirectory | fl
Get-OabVirtualDirectory | fl
Get-OwaVirtualDirectory | fl
Get-PowerShellVirtualDirectory | fl
Get-WebServicesVirtualDirectory | fl
Text
I have gone through the Exchange Server Deployment Assistant. Almost everything was as it should have been. I made some changes in the "Enable and configure Outlook Anywhere" and "Configure
service connection point."
I have switched external DNS over to my 2013 server, and the connectivity test is still failing. It is also not proxying the 2010 mailboxes through 2013 as it should (according to the Deployment Assistant).
I have a 2010 test account and a 2013 test account. Both work fine in their respective WebMail's, but the 2010 mailbox will not pull up through the 2013 WebMail.
Just for the heck of it, I have checked my SonicWall and it is configured the same for the 2010 host and the 2013 host. I knew that ports 80 and 443 were passing on both hosts anyway because the port 80 redirect works and https webmail works
on both hosts.
If I try to access the xml file directly on both hosts:
https://mail.domain.com/Autodiscover/Autodiscover.xml (2013)
https://webmail.domain.com/Autodiscover/Autodiscover.xml
(2010)
I do get an xml response from both of them after authenticating like this:
<Autodiscover>
<Response>
<Error Time="18:17:41.0173284" Id="2526055628">
ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Sooo...I'm stuck.

Update since my last post.
I have all mailboxes migrated off of 2010 and onto 2013. I'm ready to turn 2010 off as soon as I can figure out this autodiscover problem and get mail flow going in and out of the 2013 server instead of the 2010 one.
Brian, I had a http redirect enabled in 2013. I disabled that redirect and checked for any others. There is currently no redirect in place anywhere under the default web site (the root site now goes to an IIS 8 page). AutoDiscover is still
failing according to the Exchange Connectivity site.
When I switch autodiscover.domain.com over to the 2013 server I still get failures:
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Additional Details
Elapsed Time: 146 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Mon, 11 Aug 2014 16:50:27 GMT
Server: Microsoft-HTTPAPI/2.0
Elapsed Time: 145 ms.
If I try to hit the xml manually, I get the expected 600 error after providing a username and password. Should IIS be prompting for credentials when hitting the path for AutoDiscover.xml directly?
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response>
<Error Time="10:53:38.3228589" Id="36607859">
<ErrorCode>600</ErrorCode>
<Message>Invalid
Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
If I switch autodiscover.domain.com back over to my 2010 server the test passes:
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
Additional Details
Elapsed Time: 444 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user [email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006">
<Culture>en:us</Culture>
<User>
<DisplayName>Exchange 2013. Test</DisplayName>
<EMailAddress>[email protected]</EMailAddress>
</User>
<Action>
<Settings>
<Server>
<Type>MobileSync</Type>
<Name>https://mail.domain.com/Microsoft-Server-ActiveSync</Name>
</Server>
</Settings>
</Action>
</Response>
</Autodiscover>HTTP Response Headers:
Persistent-Auth: true
Content-Length: 736
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Mon, 11 Aug 2014 17:08:12 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Elapsed Time: 444 ms.
One interesting thing to note, is that <Url>https://mail.domain.com/Microsoft-Server-ActiveSync</Url>
is my 2013 server, not my 2010 server

Outlook 2010/2013 not able to connect to Exchange 2013

Hi, I'm the midst of co-exist between Exchange 2010/2013. I have issues where none of internal users that migrated to Exchange 2013 not able to connect via Outlook 2010/2013. OWA is running fine without issue. Using MCA, the issue due to port is blocked
but I have verified that firewall on Exchange 2013 server is turn off all.
    1. Exchange 2010/2013 cert is using public CA cert.
    2. Both outlook anywhere external URL for Exchange2010/2013 is set to outlook.domain.com. internal pointing to server.domain.com. while autodiscover is set to autodiscover.domain.com.
   3. user mailbox in exchange 2010 do not have any issue
while if I try to logon, the error look like below:
Cannot open your default e-mail forlders. You must connect to microsoft exchange with the current profile before you can synchronuze your folder with your outlook data file (.ost).
what else should I check ?
many thanks.

Hello,
What server does “outlook.domain.com” and “autodiscover.domain.com” point to, Exchange 2013 FE or 2010 CAS?
You can also do a Outlook Test Email AutoConfiguration by the following steps:
a. While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray and then select “Test Email Autoconfiguration”.
b. Confirm that your email address is in the address field, uncheck “Use Guessmart” and “secure Guessmart authentication” boxes. Then click the “Test” button.
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

Exchange 2013 public folders are sending read receipts for items viewed in public folders

We have Exchange 2013 with public folders. These public folders are used for a large amount of shared contacts. When a user goes into the public folders and double clicks on a contact to view it, Exchange dispatches a read receipt to all users
that are configured as publishing editors to notify them that a certain contact was read. How do I disable this option?

hi again dear.. :)
"At first, I would like to say the
read Receipt is not sent out by the device, it is sent out by the Exchange server. This is how it works and what happens:
1.
E-mail with request for send
receipt is received on the Exchange server;
2.
E-mail is synchronized with Windows Mobile based device using Exchange
ActiveSync;
3.
When e-mail is
read on Windows Mobile based device the read status is synchronized back to the Exchange server;
4.
The Exchange server creates and sends out the
Read Receipt when receiving the Read status update from the device;
The above is how this is implemented and there is no functionality which allows preventing this from occurring on the Mobile device.
It seems that there is an alternative method to disable RR using transport rules. However, it will at the risk of the filtering out other messages
with the same subject.
Towards the third party mobile clients that support RR and DR, you might consider using Flexmail 4.11. It’s impossible to deactivate ActiveSync
RRs in Exchange server 2007/2010."
also
One way to stop read receipts being triggered through client side configuration on the mobile is to use the option "Don't Mark Read on server".
I have tested this successfully using this option in the TouchDown mail client on Android.
Not sure if the standard or other mail clients do support this option, TouchDown certainly does and it works.
The side effect obviously is, that the read status isn't synced back to Exchange anymore:"
hope now i r clear... one way or the other... you need to send a feed back or define a transport rule... but that again may create problem with the same subject :)
Regards Shah. MCITP, MCMA, MCTS No claims (try at your own risk)

Connection Office365 Exchange - Outlook 2010/2013 (Desktop)

I have an Office365 account with Exchange function, connected with my personal domain. This works perfect for almost a year now, but since a few days, Outlook (desktop) can't connect to my ExchangeMail/Office365 anymore. Some details:
I can reach my mail via the Web App
My iPhone receives my email; no problems here
The password has not been changed
I've tried to connect with Outlook2010 on Windows7 and with Outlook2013 on Windows8; both can't connect
Profile removed and re-added: no result
As during creating/editing the profile in the ConfigurationScreen/Email, as in Outlook (2010 & 2013) itself, the login window pops up and can't connect (and because of that, Outlook automatically close).
In short: what is the problem here and -more important- how can I fix this?
Many Thanks,
Ewoud
PS: Apologies if this question has been asked in the wrong forum.

Hi,
Please check the problematic users' Outlook settings by the following steps:
1. Click File > Account Settings > Account Settings > Change > More settings.
2. In Security tab, make sure "Encrypt data between Microsoft Outlook and Microsoft Exchange" option is checked, "Always prompt for logon credentials" is unchecked.
3. Change the logon network security to Negotiate Authentication, and Apply > OK to set it.
Restart Outlook to have a try. If the issue persists, please
re-create Outlook profile to check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support
Thank you for the response.
I did as you suggested and the problem persists

Exchange 2013 Public folders unavailable intermittedly using MAPI HTTP

We have a problem with Public folders not being available both in Outlook 2013 and OWA.Any ideas in troubleshooting the issue will be appreciated.Thanks.

Hi,
Is there any error message when you try to access public folders in Outlook 2013?
If there is, please post here for further analysis.
In Exchange 2013 CU1, the ability to open public folders in OWA is added. You need to add public folders from Favorites.
Please use the get-mailbox | fl defaultpublicfoldermailbox to check the default public folder mailbox in Exchange 2013.
Please navigate to the following path to check the msExchHomePublicMDB attribute if the value is not set.
Open ADSI Edit -> Configuration -> CN=Configuration, DC=domain, DC=com -> CN=Services -> CN=Microsoft Exchange -> CN=<Organization Name> -> CN=Administrative Groups -> CN=Exchange Administrative Group (FYDIBOHF23SPDLT) -> CN=Databases
-> Select the mailbox database and right click on it, choose Properties.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 Public Folders Array Dimensions Have Exceeded Supported Range

Hello,
I have another odd issue for public folders on Exchange 2013. I am working with an environment with a bit over 3000 Public Folders and we are having some issues where some users are not able to access the public folder. When I try to change the permissions
to those folders I get the error of:
"Array Dimensions Have Exceeded Supported Range"
The environment is a 2 Node DAG with all components installed on each server. The latest Roll Up has been in stalled on both servers as well.
Thanks in Advance
Joe

Update the thread if you find the resolution...
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Setup a simple sales funnel with exchange 2013 public folders and outlook 2010 -2013

Similar Messages

Maybe you are looking for