Comments for Bibble-IT.com

Comment on Sharepoint, Reporting services and Kerberos authentication by Mikhail

Mikhail — Fri, 03 Feb 2012 16:07:21 +0000

There is HarePoint Analytics for SharePoint: the essential web-analytics solution for SharePoint-based sites and portals. More 50 reports, wide customisation, great features.
Homepage: http://www.harepoint.com/Products/HarePointAnalyticsForSharePoint/Default.aspx

Comment on Configuring Lync Mobility – Part 2 by Jameel

Jameel — Fri, 03 Feb 2012 05:39:43 +0000

After running the commands that create the IIS directories, I did receive both success messages, log file shows all success, but the directories are not there….Your thoughts?

Comment on Overview of Lync Mobile for Windows Phone 7 by Overview of Lync Mobile for Windows Phone 7 | Bibble-IT.com « JC’s Blog-O-Gibberish

Sat, 28 Jan 2012 14:18:12 +0000

[...] Overview of Lync Mobile for Windows Phone 7 | Bibble-IT.com Posted on January 28, 2012 by johnacook http://www.bibble-it.com/2011/12/12/overview-of-lync-mobile-for-windows-phone-7 [...]

Comment on Configuring Lync Mobility – Part 4 by Troy

Troy — Fri, 27 Jan 2012 22:07:24 +0000

Here was our problem:

PS C:\Users\xxxxxxx> Get-CsAllowedDomain

Identity : push.lync.com
Domain : push.lync.com
ProxyFqdn : lyncedge.xxxxxx.com
Comment :
MarkForMonitoring : False

ProxyFQDN should be empty (null).

Solution:

PS C:\Users\xxxxxxx> Set-CsAllowedDomain -Identity push.lync.com -proxyfqdn $null
PS C:\Users\xxxxxxx> Get-CsAllowedDomain

Identity : push.lync.com
Domain : push.lync.com
ProxyFqdn :
Comment :
MarkForMonitoring : False

Comment on Configuring Lync Mobility – Part 4 by Troy

Troy — Fri, 27 Jan 2012 17:44:58 +0000

We’ve made some head way, but our issue continues.

While running wireshark, the Test-CsFederatedPartner command successfully made a TLS handshake with Microsoft, and beyond that I couldn’t see any of the data (obviously). Then our command fails, and our push notifications still don’t work.

Perhaps we’re to the point of calling MS, as I seem to have exhausted Google lol.

Comment on Configuring Lync Mobility – Part 4 by Warren

Warren — Fri, 27 Jan 2012 16:57:50 +0000

I’d suggest installing a packet sniffer on to your edge box (I used Microsoft Network Monitor 3.4 as this step was recommended to be through Microsoft support).

Run a packet scan while executing your Test-CsFederatedPartner cmdlet and then trawl through the logs.

The problem that I had with the lack of SRV stuck out like a sore thumb, and although yours is obviously something different, hopefully your problem will become clear too.

Comment on Configuring Lync Mobility – Part 4 by Troy

Troy — Fri, 27 Jan 2012 14:58:59 +0000

Hey Ben,

Thanks for the reply. We went ahead and put a cheap single name certificate on the internal interface just to try something out, but it did not solve our issues.

We are not federated with any other organisations. At the moment, _sipfederationtls points to sip.ourdomain.com:5061 with a weight/priority of 1.

We’re at a loss on this one.

Comment on 70-680 Section 1 Module 1 by kc burger

kc burger — Fri, 27 Jan 2012 14:47:40 +0000

Using Microsoft IT Academy online course which we have subscribed to. This is much better and to the point. Thank you for this.

Comment on Configuring Lync Mobility – Part 4 by Ben Lee

Ben Lee — Fri, 27 Jan 2012 12:40:57 +0000

Hello,
The SAN cert wont need the internal name so that doesn’t sound like your issue. Have you been able to federate with any other organisations at all before?

Ben

Comment on Configuring Lync Mobility – Part 4 by Troy

Troy — Thu, 26 Jan 2012 20:57:25 +0000

We are getting the following error:

Test-CsFederatedPartner : A 504 (Server time-out) response was received from the network and the operation failed. See the exception details for more information.

Our phones can connect, our certificates are valid, and all external edge applications appear to work perfectly. DNS is not an issue (we’ve setup ALL possible DNS records required by Lync). The only name missing from our SAN certificate is the INTERNAL name of our edge server/pool, is this our issue? We are also using an internal CA certificate for “Edge Internal”.

Any help would be greatly appreciated!!!!