Windows xp issues with exchange 2013

Like Like. Fixed the Early to say I agree this is confusing. We have a customer that get their mail stuck in the outbox after the upgrade for a while. They are running windows XP with office Yes they runned into the modern public folder issue. Although the indicator at the bottom right is saying that its connected. Have you seen this problem. Jason — Have you heard of anybody talk of their message tracking log formats changing with CU3? Specifically the file name of the hub transport tracking logs?

You are commenting using your WordPress. You are commenting using your Google account. Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.

That will encourage me - and others - to take time out to help you. Regards, Siva. What it seems happened which I recently discovered is in the "outlook anywhere" tab someone had accidentally saved a full-stop in the external address.

This is where the problem seems to have come from. I didn't think it would make that much of an issue seeing as all the users are internal and none use the external address. Sorry if I don't make much sense, I am very new to Exchange. Office Office Exchange Server.

Not an IT pro? Resources for IT Professionals. Thanks for the clarification. I'll try your solution and report if it fixes it or not. To continue this discussion, please ask a new question. Adam CodeTwo. Get answers from your peers along with millions of IT pros who visit Spiceworks.

I have seen a couple threads on the 'net but I wanted a little confirmation. Is this normal behaviour for this environment, or is there a workaround to fix it? Microsoft Corporation Exchange Server Microsoft Corporation Office Professional Plus Microsoft Windows XP Professional Popular Topics in Microsoft Exchange.

The reason was the certificates primary name was mail. In resolution I opened the Exchange Shell and ran this command. I got one more failed login when opening outlook. I closed and reopened again the second time without any error. Therefore I recommend to stick with basic authentication and use SSL. Especially for Windows XP clients running Outlook do not use the negotiate authentication feature. Note: It will take time until autodiscover and IIS pick up the new settings.

I really want to try this, but also worry it will mess up my Windows 7 clients. If somethign goes wrong, is there a way to undo that command? Yes you can. First run get-outlookprovider Then make a note of what the current value is. Then rerun the original command with the old values you made a note of earlier. Ran into the same problem on my LAB. Windows 7 computer with Outlook and newer could connect.