Lync Server 2013 Unleashed has been… Unleashed!

I am super proud to announce that the new book I Co-Authored, Lync Server 2013 Unleashed is now available! This book is available on Amazon in ebook and good ol paperback! http://amzn.com/0672336154

The Microsoft NextHop blog provided an incredibly generous review of the book, which is available here: http://blogs.technet.com/b/nexthop/archive/2013/04/17/hot-off-the-presses-microsoft-lync-server-2013-unleashed.aspx

What I want to do in this post is provide an overview of the sections in the book, and how they will apply to readers of all types. When we started writing this book we wanted it to be the number one resource for Lync. This includes covering all aspects of a Lync journey, from early conception to detailed troubleshooting and advanced technical scenarios. I have broken the readers down into two broad categories, although I am sure there are many other scenarios out there.

Read more

Posted on by Randy Wintle in Uncategorized 1 Comment

Update to the Lync 2013 Centralized Logging Tool

As anyone who came to this blog probably realized, my Lync 2013 Centralized Logging UI quickly became outdated. Luckily, James from MyLyncLab.com has done a great job of bringing it back to life!

 

http://www.mylynclab.com/2013/04/lync-2013-centralised-logging-tool.html

 

Definitely check this out and support that project. He has done a great job of not only fixing my tool, but making it better. Thanks!

 

Posted on by Randy Wintle in Uncategorized Leave a comment

Locating the AlwaysOn Centralized Logging Files for Lync Server 2013

Lync centralized logging is a great new feature with Lync Server 2013. This feature also allows you to configure AlwaysOn logging, which will keep logging on, always J This is helpful in situations where an issue has been reported and you are not able to reproduce, or do not want to bother users to reproduce.

The commands for configuring centralized logging allow you to specify file locations, rollover time limits and sizes. However, these settings are only for when a user initiates a logging session. The AlwaysOn logging files are stored as part of the network service account, and in order to locate these ETL files, you must navigate to the following folder, by default:

%WINDIR%\ServiceProfiles\NetworkService\AppData\Local\Temp\Tracing Read more

Posted on by Randy Wintle in Uncategorized 1 Comment

My First Days with Surface

I consider myself to have a major bias towards Microsoft products. It is what I have made my living on ever since I started my career. I will say however, when the Surface was set to release, I was skeptical. My goal was to have a tablet that could be used for work and play, and to have said tablet be a replacement for my laptop when I travel for work. After testing the Surface in the Times Square store on launch night, and after a few days of use, I think I may have found my dream device. Read more

Posted on by Randy Wintle in Uncategorized 6 Comments

Lync Server 2013 Centralized Logging UI- Beta

Update 4/24/2013:

As anyone who came to this blog probably realized, my Lync 2013 Centralized Logging UI quickly became outdated. Luckily, James from MyLyncLab.com has done a great job of bringing it back to life!

 

http://www.mylynclab.com/2013/04/lync-2013-centralised-logging-tool.html

 

Definitely check this out and support that project. He has done a great job of not only fixing my tool, but making it better. Thanks!

_________________________________________________________________

All of this talk about Lync Server 2013 centralized logging has driven me to start a little side project. A powershell UI for the lync centralized logging. I am hopefully going to add a lot more features to this, but figured I would share the early beta to get some feedback.

For more details on lync centralized logging, see this link: http://blogs.technet.com/b/jenstr/archive/2012/08/01/using-centralized-logging-service-in-lync-server-2013-preview.aspx

Couple of things:

  1. Right now this must be run from a Lync 2013 Server
  2. This assumes that the default C:\Program Files was selected on install, if this is not where Lync is installed, you may have issues, and may need to adjust that file path.
  3. Right now it does not let you search specific text or components, I will be adding that functionality in the next rev.
Link to download is here:

If you have any suggestions, please let me know in the comments, thanks!

 

UPDATE: 9:30PM 8/2/2012- I just finished “Beta 2″ I re designed the UI. it can be found in the above link. Thanks!

UPDATE: 10:15PM 8/2/2012- I just finished “Beta 3″ I added filter options to Beta 3. Link is above!

 

UPDATE:  8/4/2012- I just finished “Beta 4″ I performed some cleanup and tweaks, as well as the ability to export your specific component logs as well.

Posted on by Randy Wintle in Uncategorized 11 Comments

An afternoon in NYC with Lync 2013- NYC Lync User Group

Quick announcement here:

See http://www.lyncusergroup.com for more details!

Meeting Details

August 16th 2012 2PM-5PM, an Afternoon in NYC with Lync 2013

The NYC Lync User Group will be conducting its next meeting on August 16th, 2012 at the Microsoft Manhattan Office!   This meeting will introduce everyone to Lync Server 2013. With all of the new features coming in Lync 2013, we will have plenty to talk about at this meeting. Food and Drink will be provided as well!

In addition to discussing Lync 2013, we will also have a special presentation from the Unify2 UC Adoption Team. “The switch from legacy telephony to unified communications is a high hurdle for many enterprises, and changing the way workers conduct meetings from in physical locations to online is an even steeper learning curve. Unify2 Adoption Services are designed to lay groundwork for increased user satisfaction and improved productivity, and to help our customers realize their ROI in a shorter timeframe.”

Agenda

Item

Time

Intros and Welcome 2:00PM-2:30PM
Lync 2013 – What is New (Overview) Speaker TBD 2:30PM-3:30PM
Lync 2013 Functionality Demo – Randy Wintle 3:45PM-4:00PM
Break 3:45PM-4:00PM
Driving UC Adoption in Your Enterprise- Unify2 UC Adoption Specialist 4:00PM-4:45PM
Sponsor Presentation- Jabra 4:45PM-5:00PM
Evaluation Surveys and Giveaways 5:00PM
Networking/Social Hour 5:00PM-6:00PM

 

Posted on by Randy Wintle in Uncategorized Leave a comment

New York Lync User Group June Meeting: Lync E9-1-1

I will be giving a presentation with 911 Enable and Audiocodes next week in NYC around E911. If you are deploying enterprise voice with Lync, you will want to be there to learn about how to properly deploy E911.

http://www.lyncusergroup.com

 

(Hint: There may also be a Lync meeting invite on Wednesday if people are not able to make it on-site)

 

Posted on by Randy Wintle in Uncategorized Leave a comment

Lync Push Notifications: 504 Timeout Error

I ran into an issue at a customer recently where push notifications for mobility were not working. Upon further investigation, the messages were receiving a 504 timeout with the Push Notification Clearing House (PNCH).

 

For reference, the push process interacts with the PNCH, and then on to the Apple or Microsoft Push Services. This happens through Lync Federation, through a Lync Edge Server.

clip_image001

When you are testing push notifications, Test-CSMCXPushNotification is the cmdlet to use. This will actually attempt to send a push message to the clearing house and report back any errors.

When using this cmdlet, use the following syntax: Test-CSMCXPushNotification – AcessEdgeFQDN <INTERNAL EDGE POOL>

In my case, the error below was displayed:

PS C:\Users\rwintle> Test-CsMcxPushNotification -AccessEdgeFqdn edgepool.contoso.com

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

At line:1 char:27

+ Test-CsMcxPushNotification <<<<  -AccessEdgeFqdn edgepool.contoso.com
+ CategoryInfo          : OperationStopped: (:) [Test-CsMcxPushNotificatio
n], FailureResponseException
+ FullyQualifiedErrorId : WorkflowNotCompleted,Microsoft.Rtc.Management.Sy
ntheticTransactions.TestMcxPushNotificationCmdlet

After some investigation, Microsoft has confirmed that the Federation SRV record is required for push notifications to work properly.

The PNCH will perform a look up on the SIP Domain for the Federation SRV record (_sipfederationtls._tcp.contoso.com). If this does not succeed, a 504 error will be thrown.

To fix this issue, you must configure that SRV record to point to your access edge server used for outbound Lync Push Federation Requests.

Posted on by Randy Wintle in Uncategorized 15 Comments

Lync Mobility Calculator (Alpha)

This calculator is alpha at best. I plan on hopefully fine tuning and adding more to this very soon.

 

What this does to date is calculate the memory you will require for your Lync FE servers to properly scale for Lync Mobility.

 

It requires you to enter your planned user bases (IOS/Windows Phone or Android/Nokia) and will output data based on the Microsoft Planning Formulas.

 

I do not take any credit for these formulas, I am simply putting them in a spreadsheet for easy access.

 

Let me know your thoughts in the comments, I will continue to update and hopefully make this a valuable tool!

Posted on by Randy Wintle in Uncategorized 2 Comments

Why Lync Mobile Call-Via-Work Makes Sense

 

 

Earlier this week, Microsoft released the Lync 2010 Mobile clients for all major platforms. (See more about that here http://lync.microsoft.com/en-us/Product/UserInterfaces/Pages/lync-2010-mobile.aspx)

With that release, a lot of people are talking about the lack of Voice over IP calling over 3G of Wifi in the product. Instead, Microsoft implemented a solution used for many years, referred to as “Call-Via Work”.

What is Call-Via-Work?

Call via work enables enterprises to deploy a consistently reliable enterprise voice solution to all mobile endpoints connecting to the Lync infrastructure. This functionality essentially bridges calls through the cell phone carrier network, and gives the appearance of a SIP call through your Lync identity.

This solution offers some great benefits:

  • A true “single number” solution, your identity is your work number. You can make or receive calls on this number from anydevice.
  • Battery friendly. This solution allows for users to actually utilize the tested and proven technology available on cell phones for years, reducing the impact on battery life when compared to a Voice over 3G, 4G or WiFi call.
  • Lync mobile users can call federated contacts.The call via work option allows users to make Lync calls to federated partners the same way it does to internal enterprise users, this is great because there is no gap in user capabilities from desktop to mobile.
  • I’ll say it again, Reliability! End users want a consistent experience, and do not want to be worried about the type of connection they are on when making a business call. Lets keep in mind, Lync is a business platform.

In some instances, VOIP makes sense, and lets face it, its kind of a popular technology right now. Everyone wants VOIP, not all end users know why they want it, but its just the new technology to use for most of them. However, it is important to understand that while it is a cool technology, with some potential for cost savings, a true enterprise grade solution cannot provide a reliable experience with VoIP on mobile devices, yet.

The potential savings that would be introduced through a VoIP solution deployed with Lync Mobile would definitely be eaten up by:

  • An overhaul of your Wireless Infrastructure. (If you want to deploy those fancy Cisco WAPs to support mobile VOIP, say good bye to any cost savings introduced by VOIP calling on your mobile)
  • Help Desk costs are a real problem in enterprise environments, these would definitely increase as users start having a poor experience when in an airport, or in a faux 4G area on an overloaded cell tower that provides limited bandwidth.
  • Costs for data vs cell minutes. Not many people know, but it isn’t always true that cell phone data is cheaper than cell phone minutes. Specifically when in roaming, and roaming international scenarios.In some instances, a roaming international 3G or 4G call could cost as much as 50 times more per minute than a roaming cell call…

So, to summarize:

Microsoft has done their research, they are not ignoring the fact that enabling mobile endpoints to communicate anywhere through their enterprise environment is important. What they are doing is deploying it properly! I would rather have a working, reliable solution, than have all the features in the world, that work half the time and provide me with a poor experience.

Posted on by Randy Wintle in Uncategorized 21 Comments
1 2 3 4 5 6 7 8   Next »