March 4th, 2011 | Tags:

Two new Lync Server 2010 planning tools have been released to web:

Lync Server 2010 Capacity Calculator: an Excel spreadsheet used for calculating a user’s hardware requirements based on information about users and traffic.

Lync Server 2010 Stress and Performance Tool: This is to be used to prepare, define and validate performance targets of user scenarios offered by on-premises Lync Server 2010 deployment. LSS includes multiple modules and can simulate simultaneous users on one or more Lync Servers.

Source: here

February 22nd, 2011 | Tags:

Previously Communicator 2007 self-help documentation would need to be downloaded independently and made available to your end-users via a network share or embedded within your chosen Intranet platform, but did you know that with the Lync 2010 client help is always close to hand?

For easy access to videos and short how-to pictorials take the following steps.

1. Open your Lync client application (double-click the green Lync logo within your system tray). Then click Help and “Welcome to Lync” (see below)

2. You will then be presented with Lync client guides and video – how much easier could it be? (see below)

February 22nd, 2011 | Tags: ,

Looking for Lync Server 2010 Virtualisation best practice, if the answer is YES, then help is at hand. Microsoft have published an extremely helpful white paper to cover off this very subject.

Check out an excerpt taken from the TOC below:

1.1         What is Virtualization?.

1.2         Why Virtualize?.

2       Virtualization in Lync Server 2010.

2.1         Terminology.

2.2         Supported Functionality.

2.3         Hypervisors.

2.3.1          Validated Hypervisors.

2.3.2          Other Hypervisors.

2.3.3          Unsupported Hypervisors.

2.4         Guest Operating System Requirement.

2.5         Virtualized Lync Server Deployment General Considerations.

2.5.1          Mixing Physical and Virtual Servers Running Lync Server 2010.

2.5.2          Spreading Lync Server Workloads on Different VM Hosts.

2.5.3          High Availability through Virtualization.

2.5.4          Quick Migration and Live Migration Support.

2.5.5          Dynamic Memory Support.

Source: here

February 9th, 2011 | Tags: , ,

It’s refreshing to know that Microsoft heavily road test or “dog food” their products before they ship to their customers, what is even more impressive is how transparent they are on their challenges/successes. A quick reference guide detailing the story from a high-level can be downloaded via the Microsoft Download Center.

Excerpt below:

Results:

MSIT offers full IM/presence/conferencing to 160K users (the entire company).

MSIT has deployed:

  • EV to 80K users in 66 sites
  • Lync 2010 to 28K users. NSAT: 150+!

Keys to Success

  • Ensure that 100% of users at seven sites were on Lync and EV prior to decommissioning the PBXs.
  • Enforce a minimum client version by using the client version control (CVC) option.
  • Take advantage of volunteers instead of doing forced migrations. Volunteers rated the service about 50–80 points higher than users who were forced.
  • Provide a rich set of training resources.
  • Lync Attendee Client. The Lync Attendee client was slightly confusing to users and there were early problems installing the client due to locked-down desktops. The Lync Web Application has slightly different capabilities than the Lync Attendee Client, which also complicated matters. The Lync Attendee experience is much improved after making small changes to the client and after users have had more practice.
  • Firmware gateway upgrades and new SKUs took a while to put in place by OEMs, causing a delay in the schedule.
  • Delegation requires sufficient resources. MSIT invested in resources to help onboard the top people and their support teams to ensure a smooth experience.

Challenges:

  • Lync Attendee Client. The Lync Attendee client was slightly confusing to users and there were early problems installing the client due to locked-down desktops. The Lync Web Application has slightly different capabilities than the Lync Attendee Client, which also complicated matters. The Lync Attendee experience is much improved after making small changes to the client and after users have had more practice.
  • Firmware gateway upgrades and new SKUs took a while to put in place by OEMs, causing a delay in the schedule.
  • Delegation requires sufficient resources. MSIT invested in resources to help onboard the top people and their support teams to ensure a smooth experience.

What’s Next?

Period Goals
January
  • Maintain the current 28K users on Lync and 132K users on OCS 2007 R2
  • Complete all seven PBX site deployments
Feb—March
  • Migrate full Microsoft population to Lync 2010

Tools

MSIT uses the following tools.

Tool Description
QoE Records Office Communicator and UC Desk Phone voice quality
Call Detail Reporting (CDR) Shows the number of phone calls, IM, and Office Live Meeting sessions that take place for each user
Perfmon Gathers performance-monitoring metrics to monitor concurrent connections to the OCS pools
SCOM Used to raise alerts to the reporting and tracking system and to gather other general statistics from the pool
In-House Survey Tools Used to query end users for feedback on features and user satisfaction
Helpdesk Ticket-Tracking System Provides a rich set of backend metrics on ticket volumes

Source: here (currently unavailable – thanks Peter!) Now back online

February 8th, 2011 | Tags:

Good news! The Lync Server 2010 Planning Tool has now come out of beta, this tool is fantastic for those that are new to the concepts of Communications Server or Lync and not only assists in creating your design, but also outputs the necessary XML file that can be loaded into your Lync Server Topology Builder, giving you a head start.

Taken from the Microsoft Download Center:
The Microsoft Lync Server 2010, Planning Tool asks you a series of questions about your organization and the features that you are interested in. The planning tool will then use your answers to recommend a topology based on the tested Microsoft Lync Server 2010 user model.Your organization may have a different user model. If so, you should adjust the recommended topology as necessary to fit your organization’s needs.
What’s New in the Planning Tool for Lync Server 2010?

  • You can select virtualized server roles for your topology.
  • The Planning Tool offers more granular capacity guidance than in earlier releases.
  • You can customize individual branch site information.
  • The topology pages display site information, such as number of users and number of enabled users for various modalities.
  • The Planning Tool invites you to participate in the Customer Experience Improvement Program (CEIP), helping make the planning tool better.
  • You can view your edge network diagram and enter FQDNs and IP addresses and view the certificates, DNS settings, and firewall settings for your edge network in the central sites when using DNS Load Balancing or Hardware Load Balancing for Edge Servers. You can also import this information to Topology Builder. You can also export the diagram and the data to the Microsoft Visio drawing and diagramming software.
  • You can export your topology file to Topology Builder for a faster, easier Lync Server setup experience.
  • You can export the global topology, with its corresponding branch sites, as well as the number of concurrent calls connecting each central site, to the PSTN into Visio. The Visio output contains improved drawings for each of the site topologies.
  • The Planning Tool exports a list of the hardware for all sites, including branch sites, to a Microsoft Excel worksheet.
  • The Planning Tool accommodates more supported topologies for Enterprise Voice and dial-in conferencing.
  • Navigation between topologies and server information has been improved.
  • You can resize or maximize the Planning Tool window to better accommodate your screen resolution.
  • The Planning Tool provides a menu bar and a toolbar for available actions.
  • The Planning Tool incorporates new Microsoft Lync Server 2010 features and topology recommendations.
  • Users are now evenly distributed among the Front End pools.

Download: here

February 7th, 2011 | Tags:

Back in November a shiny new Windows Phone 7 (WP7) device came about my person. At the time I was a very comfortable iPhone 4 owner and like many I had become very used to the iOS chicklet-based interface and reliant upon a number of key applications available via the Apple App Store. I want to make a HUGE caveat at this point – I would not consider myself a typical smartphone user, those that are new to the smartphone eco-system probably won’t experience the same dependency symptoms or “iColdTurkey” that I experienced.

The net result, I was hesitant to make the switch – but I did it anyways. I knew that when I took part in this “mobile migration-a-thon” that I would be without certain functionality and I was prepared for this – or so I thought!

First, the positives:

WP7 IS a truly innovative smartphone platform, the interface is sublime and the “live tile” idea is a big favourite of mine, although more applications need to exploit this functionality. My handset is the LG Optimus 7 E900 and as with all hardware variants the UI is incredibly snappy!

The App Store Marketplace is growing at an alarming rate, 5000+ three months from launch (the holiday period was well placed in the middle of this timescale) – my understanding (from multiple sources) is that the Microsoft development toolkit is far superior to Apple’s iOS SDK, although I’m not a developer so this is not first-hand experience. I also noticed, with certain applications I purchased, that updates are far more frequent as a consequence of Microsoft’s relaxed approach to application approval. I even found myself suggesting certain “Reader 2.0” functionality, that was turned around by the developer and deployed inside of two weeks!

Now the not so positives:

For me this came down to the lack of certain functionality via the availability of particular applications, my “Top 10” (in no particular order) can be found below.

  • Jaadu RDP – for remote desktop
  • Skype – for Mobile VoIP
  • Bria – for mobile VoIP/SIP
  • Fring – for mobile VoIP
  • WhatsApp – for cross-device instant messaging
  • Cydia – for homebrew applications
  • Foursquare v.2.2.4 – the version 1.0 present on WP7 is still buggy and missing key capabilities (photos, comments, etc)
  • Kids’ stuff – Talking Carl, Super Why, Cooking Mama, MouthOff – the list goes on… (in general kids apps on WP7 are lacking and poor in quality at this stage)
  • Angry Birds – need I say more?
  • Tom Tom – I was quite literally “lost” without this *pardon the pun*

In most cases this comes down to platform maturity, although there are certain “APIs” that are still missing from the day one delivery, a well-documented one being “full sockets support” – at this time inbound and outbound traffic is limited to HTTP/HTTPS (ports 80 and 443). Most remote desktop, VoIP and messaging applications require access to ports outside of this range.

Regarding homebrew support, Microsoft seem to have a welcome fresh perspective on this, although this is yet to be confirmed.

In conclusion:

The bottom line here is that I’m a “techie” whom is already comfortable using a well-established platform (iOS), for those who are smartphone newcomers I would highly recommend you consider WP7.

Will my device hit eBay any time soon? No – I plan to go back to my WP7 device inside of 3-6 months, there are a number of key functions that need to be filled and I have no doubt in my mind that Microsoft will plug these in the near-term via patches or service packs.

Some reviewers have commented that Microsoft is “too late to the game”, I would disagree with this and have no doubt that Microsoft’s fresh perspective will make them a major player in the smartphone arena in forthcoming months/years.