reredok
asked on
Exchange Server 2013 SP1 (KB3184736) Problem
Hello EE,
I've installed Security Update For Exchange Server 2013 SP1 (KB3184736) on a Windows 2012 R2 Server via Microsoft Windows Update (unfortunately a Domain Controller).
Outlook 2013 (with last Servicepack) can't connect to Exchange Server which have worked before MS Update. (always prompt for User-login)
OWA ist working without any Problems.
If I want to start Exchange 2013 - Powershell I got the message:
similar (translated from German Server)
In Connection of "FQDN-ofExchange-Server" occurs following Error: The Win-RM Client has return a http Status-code "307" from Remote-WS-Services.
I don't know where to start to isolate the Problem.
OWA, Exchange console via Webbrowser, IIS works properly.
Do you track with this KB3184736 Problem or have some tips for me?
Thanks in advance!
reredok
I've installed Security Update For Exchange Server 2013 SP1 (KB3184736) on a Windows 2012 R2 Server via Microsoft Windows Update (unfortunately a Domain Controller).
Outlook 2013 (with last Servicepack) can't connect to Exchange Server which have worked before MS Update. (always prompt for User-login)
OWA ist working without any Problems.
If I want to start Exchange 2013 - Powershell I got the message:
similar (translated from German Server)
In Connection of "FQDN-ofExchange-Server" occurs following Error: The Win-RM Client has return a http Status-code "307" from Remote-WS-Services.
I don't know where to start to isolate the Problem.
OWA, Exchange console via Webbrowser, IIS works properly.
Do you track with this KB3184736 Problem or have some tips for me?
Thanks in advance!
reredok
One option is to remove this KB and check again. I skipped this KB for my system. Microsoft is known for releasing bad patches. So, I wait minimum 3 months, before installing it. Or last option to give a call to MS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks for sharing work around.
ASKER
no other solution found