We are implementing a pilot of Microsoft Lync 2010 and we've been running in to a few little quirks.
We are using a Dialogic DMG VoIP gateway to interface with our legacy telephony equipment to receive calls from the PSTN.
Here is the current quirk that was encountered: any call that originated from the PSTN to a Lync user that was placed on hold would disconnect after exactly 90 seconds. The following information was observed in a Lync trace of the call:
WCF Web Services, IIS, Kerberos, and Delegation problems are maddening!
Sometimes you implement something exactly as you have in the past, but due to some unforeseen circumstance it doesn't work as you expect. We've seen issues like this when implementing WCF web services on IIS 6.
Some things you can check are:
- Have you setup the proper service principal names for the service account running the application pool?
- Is the service account setup to run the application pool that is running the web service trusted for delegation?
Well we had an interesting problem this week. For some reason all of a sudden, users with Outlook 2010 started to have the application crash when they tried to open the application. Outlook would open fine in safe mode and if the user re-created their mail profile everything would work fine - until they rebooted.
After a reboot Outlook would again crash with an APPCRASH error with the culprit being olmapi32.dll.
It seems that radio buttons on forms displayed/rendered with SharePoint 2007 Infopath Forms Services are not working properly.
We have some internal custom forms on our SharePoint 2007 farm that are provided via InfoPath Forms Services. After I upgraded to the recently release Internet Explorer 9 Beta I could no longer select a radio button displayed on an InfoPath Form Services form.
Guess we'll need to file a bug on this one.
The Bottom Line: make sure your Exchange security solution/anti-virus is operating properly. Details below.
Here's an oddball issue we had this morning.
Have you been pulling your hair out trying to get a Windows Server 2008 R2 virtual machine deployed from a vCenter template to join a Windows Active Directory domain? Fear not, the solution is at hand and is realtively simple.
After reading the following thread on the VMware Communities site:
http://communities.vmware.com/thread/251925
I found out that one needs to use the FQDN of the AD domain and NOT the NetBIOS name of the domain, and also the user principal name for a user with proper permissions to join computers to the domain.
A friend of mine uses Samba and winbind on his CentOS Linux boxes for user and group information and Kerberos for authentication. He upgraded his domain controllers recently to Windows Server 2008 R2 and suddenly his winbind authentication broke.
