Lync - EWS not deployed on Configuration Tab

Lync was not able to find EWS, althoght Outlook and Exchange autodiscovery seems to be ok.

You will see EWS not deployed in Lync 2010 client configuratiob tab. You can using this with Ctrl+Right click  on Lync sign on the taskbar.

The problem can fixed by modifying the Autodiscover-Webconfig (you find the web.config under %ProgramFiles%\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover\web.config).

Open the Config-File with notepad.exe and adding the following line under <handlers>...


<add name="AutodiscoverSVCHandler" path="*.svc" verb="POST" type="System.ServiceModel.Activation.HttpHandler, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="integratedMode,runtimeVersionv2.0" />

You can see the full config in the following PrintScrn...

Restart the Lync-Client and reopen the configuration tab. You can see under "EWS Information" Status that it now runs.
Location: Bern, Schweiz

Comments

Post a Comment

Popular posts from this blog

How to fix the check box on RDWeb 2012 for use private computer

Image
It is hard when you use the RDWeb interface internally only and you must activated the checkbox " I am using a private computer that complies with my organization's security policy. " each time. Do you want to activated the checkbox by default, you must make the following points. Go to C:\Windows\Web\RDWeb\Pages\en-US or other language Open the file "Default.aspx" with admin rights Go to line 32 with the content " public bool bShowPublicCheckBox = false, bPrivateMode = false, bRTL = false; " Change the value from bPrivateMode from false to true Save Example:  public bool bShowPublicCheckBox = false, bPrivateMode = true, bRTL = false;
Read more

SCCM 2012 Software Center returned error code 0x0041013 (-2147217389)

After an update from SCCM 2007 client to SCCM 2012 client, there is sometimes show the error "Loading Software Center returned error code 0x80041013 (-2147217389)." in Software Center. This even though the client was successfully installed. I think this error is because not all parts of the old SCCM clients have been properly removed. You can fix this issue with the following steps: Open registry Go to  HKEY_CLASSES_ROOT\CLSID\{555B0C3E-41BB-4B8A-A8AE-8A9BEE761BDF}\InProcServer32 Check the value for Default is C:\WINDOWS\CCM\ccmcisdk.dll (if not, change the value) Go to  HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{555B0C3E-41BB-4B8A-A8AE-8A9BEE761BDF}\InProcServer32 Delete the value in Default (value is C:\Windows\SysWOW64\CCM\dcmsdk.dll) You can launch the software center again and you can see the applications without the error message.
Read more

How to publish the remote desktop session servers to RDWeb under RDS 2012

You can find the setting for publishing the Remote Desktop Session Server Desktop under: Server Manager Remote Desktop Services Collections CollectionName Tasks Edit Properties General tab But you can not change this setting in this wizard! Under Windows Server 2012 RDS you can only publish Desktops or RemoteApps, but not both. :-( If you would like to bypass this limitation for session collections only, you may consider changing the following registry value on your Remote Desktop Connection Broker (RDCB): Open the Registry-Editor Go to the following path:  HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\CentralPublishedResources\PublishedFarms\<collection>\RemoteDesktops\<collection> Open the REG_DWORD " ShowInPortal " Change the value data from 0 to 1 After this change you can see the desktop in RDWeb. :-)
Read more