First off, I want to say thank you to all the new signups, and the people who’ve emailed me with questions! We’ve had a lot of conversations lately. It’s great! Lync Server adoption is growing like crazy (not just on the blog too – we’re getting more & more consulting projects on it).

Today’s post centers on the Skype purchase. Yes, once again. Someone asked about it, honest!

Thing is, they asked me a very poignant question:
“What else do you think is in the cards for Skype at Microsoft? I’m thinking about Windows 8, mostly.”

GOOD question. And from just a little research, I determined that we’re not the only ones who’ve weighed in on it lately.

Skype’s Future at Microsoft: Ars Technica Speculates

Big-name tech news site Ars Technica posted on this the other day. Jon Brodkin speculated on “integration everywhere,” putting everything from Windows Phone to Xbox Live to Windows 8 on Skype’s potential-destination radar.

Jon has some very good points about how easily Skype could be integrated into the Microsoft software base. I think building it into Xbox Live and Windows desktop make a lot of sense. With that in mind, I’ll say this:
Adding Skype as a default option to Windows 8 is the smart play.

Picture this. You install Windows 8 around this time next year, on a dozen tablets for employees. Lync Server is already running on your back-end. The Skype client included in your Windows 8 detects each employee’s Lync credentials, auto-configures…and poof, your employees are able to call anyone.

I mean *anyone.* In the office or around the world. The VoIP in Skype and the Unified Communications in Lync, working together.

Pick up a Windows Phone and you’d have the same connectivity there. Same interface too. Sounds like a good future for Skype, doesn’t it?

Will Skype Grow, Shrink, or Vanish? Web Users Weigh In

That wasn’t the only speculation I came across though. Many Web users have their own questions. And their own concerns.

I’ve copied out a few of them below. And added my own thoughts. Some useful food for thought, for those of us involved in office communications.

“Do we have to use an integrated client?”
I suspect there will be several client options. A “basic” Skype client, Lync 2010 with Skype baked in, a Windows Phone app, etc.

“Skype on Windows Phone 7?”
As one commenter said on the Ars Technica piece, “Microsoft could easily roll its own telephony package.”  With the Skype technology and a Lync backend, they could indeed. That’s a bit more ambitious than I was thinking. It would be a very good pull for Windows Phone though!

“Skype allowed multiple logins before. Will we lose that?”
More than one person was interested in multiple logins. Since a seamless integration – not just with Lync, but also with Windows Phone and Xbox – makes sense, multiple logins is still a safe bet.

“Will Skype disappear into Lync and Windows Live Messenger?”
Unlikely. The Skype contact interface is too well-known to just throw it out. It’s more likely that Windows Live Messenger will take on most of Skype’s interface.
Lync less so, since it has its own interface. That will be more of an in-process integration; certain steps to use Lync may come to resemble Skype.

“Skype’s painfully inefficient. Anything Microsoft does will be an improvement.”
While that seems a little excessive, a lot of user complaints about Skype are that it’s slow. Bloated, memory hog, call it whatever you want.
Will that increase load time for Lync? Or other Windows integrations? Possibly. It IS a disparate code base. One possible method would be to re-develop segments of the code as they’re integrated into separate Microsoft platforms (one for Lync, one for Xbox, one for Windows 7, one for Windows 8…).

Hopefully Microsoft will release some additional plans soon. Now that the merger is approved, they’ll want to avoid wild speculation going on too long.

Since there’s already so much discussion, they’d better hurry!

I hope this sates your curiosity (for now). Next week I’ll discuss a Lync bug we came across in our latest implementation.

On Monday my boss handed me a new Jabra headset and said, “Here, we got a bunch of these in. Try it out. Let’s put a review up.”

Sure!

Image courtesy of Jabra.com.

Starting With a Headset Overview

I’m using a Jabra BIZ 620 USB mono headset (one headphone, for the right ear). The mic arm is adjustable, and moves up to 270 degrees.

In other words, up alongside your head when you want it out of the way.

The headset has an integrated call control knob on the cord (right).

The buttons are (from top to bottom):

• Answer Call
• Increase Volume
• Lower Volume
• End Call (Pressing this button when not in a call will mute your mic)

There’s also two LEDs on the call control. One green LED to indicate that the device is in use; one red LED to indicate that the headset is muted.

The BIZ 620 is a USB plug-and-play headset. No drivers are required. Just plug it in and you’re ready to talk.

Supports Windows 2000, XP, Vista, and Windows 7. Also support Mac OS 9.0.4 and up.

Putting it On

The call control knob is a little heavy, causes headset to tilt if it’s not adjusted. I had to keep the band fairly tight to balance out the weight on the cord. Once I did that, the headset was very comfortable.
The ear piece is well-padded, so it sits very lightly against the ear.

The mic is adjustable. Jabra recommends putting it about two finger-lengths away from your face.

I’ve had the headset on for about an hour now. No discomfort whatsoever. (In fact I stood up a moment ago, forgetting it was on!)

After I plugged the headset in, Lync automatically recognized it and switched my audio devices. (Note the headset icon in the lower-left corner.)

Right here!

That’s all the configuration I had to do. A test under Options/Audio Device reveals that the headset volume is set to about 40% by default. Just tap the “+” on the call control knob to raise it.

From here, it’s just a matter of clicking a contact (or entering a phone number) and hitting Enter.

Making Calls in Lync 2010

Rubber meets the road time!

I tested the headset on four calls: two to internal contacts, and two to outside clients.

I didn’t tell any of them I used the headset.

Both of the outside clients asked if I had a new phone. When asked why, they said I sounded much clearer. (I’d spoken with them before using my laptop’s built-in mic.)

It’s always better listening to voices through headphones than laptop speakers. The Jabra headset improved sound quality for both of us. No static, no pauses, no issues.

Final Verdict: Great Headset for Lync Users

The Jabra BIZ 620 USB is optimized for use with Lync Server. It’s one of Jabra’s Unified Communications products, made for their partnership with Microsoft. lines comes in mono (one headphone) and duo (two headphones) versions. USB and MS connectors available.

I really like how simple this headset makes things. There’s no setup, and no extra steps in Lync. Click to make a call, and this headset handles the rest.

The Jabra BIZ 620 USB headsets are available through several distributors and resellers. Jabra maintains a list on this page: Jabra BIZ 620 Series – Authorized Distributors and Resellers

Do you use a Jabra headset with Lync? Which model? How’s it working for you?

I’m not a Mac guy. One of our web designers is; he LOVES his Mac. And he does produce some really sharp images on it for us.

So I know that more & more companies use Macs in the office. If not for everyday computing, then at least for specialist jobs like graphics work, web development, video.

And like everyone else, Mac users will want to stay in contact with co-workers. When it came to Lync Server, this was difficult at first – Mac-based clients weren’t first priority.

But now that’s over with. Not only do we have a Lync client for the Mac, two clients for the iOS (iPhone/iPod Touch/iPad) are now available. Let’s take a look, hmm?

Microsoft Lync for Mac

Starting October 1st, Microsoft will ship the official Lync client for Mac.

(Credit to Mary Jo Foley for breaking the news.)

It’s got pretty much everything Lync for PC does: IM/Presence, voice and video, conferencing, desktop sharing, you name it. I don’t have a Mac to test this on, but the interface shots mirror Lync almost exactly.

You can use Lync for Mac with Lync Server 2010 and Lync Online (the Office 365 offering).

(Microsoft’s site says that “some voice capabilities require Lync Server 2010 and are not available with Lync Online.” Doesn’t give specifics though.)

Lync for Mac will be included with Office for Mac Standard 2011, via Volume Licensing.

Xync for iOS (iPhone, iPad) and Android

Credit to Tom Arbuthnot at the Lync’d Up blog for this one. He did a review of Xync on his iPad 2 last month.
(I borrowed the below screenshots from there.)

Xync’s website says the client supports Presence, Search, Audio/Video and PSTN Calls. The “Conferencing” link in their FAQ didn’t work, so I don’t know how much of the Conferencing role is supported yet.

Tom tested sign-in, IM, making calls and adding video. He noted one interesting caveat here: When in a video call to a Lync user, the iPad video looks fine. But the video on the Lync side doesn’t look so good. (You can see the difference in his screenshots.) Commenters also noted that the Xync client crashes on sign-in. Possibly an interface bug, or just a glitch.

Xync is available in the Android Market and the iPhone/iPad App Stores for $19.99. At its website you’ll find a FAQ, guides and how-to videos.

iDialog for iPhone

I couldn’t review Xync and ignore where Tom’s coming from, could I?

Tom works for Modality Systems, which ALSO has a Lync client for iPhone: iDialog. I mentioned it last year in my “How to Use OCS 2007 on Your Mobile” post. iDialog has since been updated for use with Lync Server as well.

The one caveat with iDialog is that it does not take Lync calls directly. From their site:

“…a user can control incoming phone calls to their OCS or Lync phone numbers. iDialog does this by alerting the user to the incoming call and providing the option to forward the call to their mobile phone, voice mail, or another device.”

However, you can reach contacts, IM, and change your presence status. The interface is nearly identical to Microsoft Lync, too.

iDialog is $9.99 in the iPhone App Store.

Never let it be said that, when it comes to Lync, Microsoft ignored the Mac users! In fact, I think the timetable for this release is faster than average – Microsoft doesn’t usually release a Mac software version this fast.

Maybe the third-party mobile apps have sped up timetables. Who knows. I’m glad the mobile apps exist; several good options for every mobile platform makes Lync adoption that much easier.

“If we move to Lync, can we use it on your iPhones?”
“What about my Droid?”

Yes. And yes.

Do you have Lync on your smartphone? What do you use?

It never fails. You blog about a topic, then you come across more information on it.

After last week’s post on Lync certs, a co-worker and I discussed the cert tests he just took (and passed, yay!). He mentioned that the Lync Resource Kit had helped him out. I took another look, and guess what? New stuff came out!

Follow-Up to Lync Certification: Updated Lync Resource Kit Chapters, and a Visual Aid

Two of the 19 available Lync Server Resource Kit Chapters were updated in late August. According to DrRez, they updated “Enterprise Voice” and “External User Access.”
The Enterprise Voice chapter added 8 pages on Call Admission Control (CAC). Given how important this call-routing technology is to Lync, all of us should read through it before the cert test.

DrRez also has a visual aid for us: a Protocol Workloads poster for Lync. It clarifies workload by Server Role: IM and Presence, A/V and Web Conferencing, Enterprise Voice, Application Sharing and Central Management.

The layout for each workload is very similar. Makes it easy to see how the roles can be installed side-by-side in the server room.

Follow-Up to Branch Appliance: Posts from InsideLync.com

One of the sites I check regularly is InsideLync.com, Curtis Johnstone’s blog. It’s a Lync-focused blog (like mine!) with lots of hands-on knowledge. Great resource.

This week’s check showed me two newer posts that relate to my post on Lync Branch Appliances a couple weeks ago.

A. Microsoft Lync Remote PowerShell Administration
Contains tips and a link on remote administration for Lync Servers (like a branch appliance). Pay attention to #3 and #4; if your certificates and your scripts aren’t cooperating, there’s only so much you can do remotely.

While you’re there, read this post on virtualization with Lync:

B. 10 Basics on Lync Server Virtualization
Just like the title says; virtualization basics for Lync. This WILL NOT help you with a branch appliance; as #2 points out, it’s the only server role that can’t be virtualized.

However, virtualization is something to keep in mind when you plan a branch appliance. Will a virtualized Server Role at the main office drop my branch appliance’s performance? Should I virtualize any additional branch servers? And so on.

Arm Yourself (With Knowledge!) Before the Exam

A final note: My co-worker also mentioned that 70-664 (Lync Server Configuring) was more difficult than 70-665 (Lync Server Administrator). So if you’re studying for these certs, spend a little extra time on the Administrator material!

Have you taken the Lync certification exams, or are you planning to? I’d like to hear about it. Please comment or email if you want to share your experience.

We’re at the end!

The end of the “20 Tasks” series, I mean, (Hah, I scared you! No, the blog’s not going anywhere.)

For the final entry in this series, let’s talk branch appliances.

Branch appliances are Lync Servers running at branch offices. They handle communications between the branch office and the main office, including phone calls, for up to 1,000 users.

(If you have more than 1,000 users at a branch site, you’ll need a Branch Server instead – slightly different installation.)

The main value of a branch appliance is Enterprise Voice. Namely, that branch offices can continue using Enterprise Voice – even if the link to the main office goes down.

If you’re in a position where you need to add a branch appliance, celebrate! It means things are going well!

And then, keep reading.

How to Deploy a Branch Appliance

Part 1: Prepare the Branch Site

We start preparation by adding a new branch appliance to Active Directory. Make sure the physical server is in place beforehand though!

1. Log on to Lync Server as an Enterprise Admins Group member.
2. Click Start, and then click Administrative Tools.
3. Click Active Directory Users and Computers.
4. On the Actions menu, click New –> Computer.
   In the New Object-Computer dialog box, type in a name for the Survivable Branch Appliance computer object (i.e., “OliveBranch1″).
5. Click Change.
6. In the Select User or Group dialog box, add the RTCUniversalSBATechnicians group and then click OK.
7. Click OK to save the Survivable Branch Appliance computer object.
8. Click Start, click Administrative Tools, and then click ADSI Edit.
9. In ADSI Edit, right-click the computer object that you created in the previous steps, and then click Properties.
10. In the attribute list, click servicePrincipalName, and then click Edit.
11. In the Value to add field, type HOST/. (without the brackets) is the FQDN we just set for the branch appliance. For example, “HOST/OliveBranch1.mysite.com”.
12. Click OK to save the servicePrincipalName attribute setting. Then click OK to save the computer object properties.
13. In Active Directory Users and Computers, right-click Users.
14. Click New –> User.
15. Enter information into the wizard to create a domain user account for a Survivable Branch Appliance technician. (They’ll be responsible for adding the physical device to the domain.)
16. In Active Directory Users and Computers, click Users, right-click the user object. Click Add to a group.
17. In Enter the object names to select, type RTCUniversalSBATechnicians, and then click OK.
18. If you want to add more technicians to this branch site, repeat Steps 12-15.

Part 2: Add the Branch Site to Lync Topology

Next up we’ll add the branch site to your Lync topology.

1. Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Topology Builder.
2. In the console tree, expand the central site, right-click Branch sites, and then click New Branch Site.
3. In the Define New Branch Site dialog box, click Name, and then type the name of the branch site.
4. If you want to, click Description and enter a description for the branch site (so you can distinguish later).
5. Click Next.
6. (Optional) In the next Define New Branch Site dialog box, do any of the following:
   • Click City, and then type the name of the city in which the branch site is located.
   • Click State/Region, and then type the name of the state or region in which the branch site is located.
   • Click Country Code, and then type the two-digit calling code for the country/region in which the branch site is located.
7. Click Next.
8. If you are using a Survivable Branch Appliance or Server at this site, make sure the Open the New Survivable Wizard when this wizard closes box is checked.
9. Click Finish, and then follow the directions in the wizard that opens. You’ll need the following information:
   • The new branch appliance’s FQDN
   • Which Edge Server this branch appliance will connect to
   • The FQDN or IP address for the gateway you’ll associate the branch appliance with
10. If you want to see what the wizard will want ahead of time, see this page: Define a Survivable Branch Appliance or Server.

Part 3: Determine What Voice Routing Method to Use

There are three options when it comes to routing method. A PSTN gateway, or SIP trunking with or without media bypass. I’ll link to TechNet posts on each for greater detail:

1. Define a PSTN Gateway at the branch site,
2. Configure Media Bypass on a SIP Trunk,
3. Or configure the SIP Trunk without Media Bypass.

As of yet we haven’t performed #2 for any clients. We have done 1 and 3. Neither is difficult. But be sure to test your branch appliance thoroughly, just in case!

After all this, your new branch appliance should be in place and running.

I’m not sure what next week’s post will be on. We’ve received a lot of questions (and Lync issues) lately, so the field is fertile. Do you have a question about Lync Server–or a problem? Email me, or leave a comment. I like digging for the answers.

Hope everyone in the US has a good Labor Day!

Live Meeting’s functionality was absorbed into Lync Server. Since Lync had Web Conferencing (and the Dial-In Conferencing service!) built in, it made sense to equip the software with Live Meeting’s anyone-can-join capability too.

With Live Meeting, people wanting to join a conference (as guests, outside your network) would join in by downloading the Live Meeting Client. In Lync Server, you have two new choices: Lync Attendee, or the Lync Web App.

Meeting Option #1: Lync Attendee

Lync Attendee is a downloadable client for external users to join Lync meetings. In other words, it operates just like the Live Meeting Client.

However, it doesn’t allow for Presence, or scheduling meetings on its own. (You need the full Lync client for those.) Attendees can enter a meeting as a Guest or as an Authenticated User, with their own corporate credentials.
Download Lync Attendee here.

Meeting Option #2: Lync Web App

The Lync Web App is a Silverlight-based app for people who don’t have Lync 2010. It enables remote connection as a guest – same functionality as Live Meeting, just in a Web-based app.

The Web App doesn’t allow for Presence either. But it *does* include IM. And all the collaboration features you’d find in Lync 2010 or Lync Attendee: PowerPoint presentations, the Whiteboard, polls, etc.

(Using these features may prompt attendees to download a plugin. Warn them beforehand.)

NextHop has a thorough run-down of the Lync Web App here.

So Which Should You Use for Meetings?

If you’re reasonably sure attendees are on newer computers, use the Lync Web App. Silverlight is newer technology; the latest systems will support it easily.

Also, use the Web App if you’re inviting people on Macs and/or smartphones.

Otherwise, go with Lync Attendee. It’s a good all-around client for meetings, and it’s easier to use than Live Meeting.

A Note About Conference Scheduling

Scheduling a web conference in Lync is pretty easy. Lync users can begin a meeting anytime (what’s called an “ad-hoc meeting”) by right-clicking on another contact.

However, when it comes to scheduling meetings, the Conferencing Add-In I mentioned will likely get more use. Being integrated into Outlook, it’s literally right there.

You’ll see a “New Online meeting” button (with the Lync logo) under Calendar. Click that and enter the meeting details.

This should clear up a little confusion. I’m sure there’s a lot more to discuss when it comes to meetings in Lync though.

Have you had trouble scheduling or attending one? Let’s hear about it!

In May I wrote about Microsoft’s Skype acquisition. I speculated a little on 4 ways Skype could affect Lync Server.

Microsoft gave us some answers at the WPC conference in late July. (Yes, I’m late to the party here. I was on vacation!)

Looks like my “all of the above” thought was on the right track. Lync will “thoroughly integrate” with Skype once the acquisition deal is final. We don’t have a lot of details beyond that. But the WPC announcements did shed more light on Microsoft’s goals.

See Steve Ballmer’s quote in the article:

“One of the great motivations in acquiring Skype is to enable the enterprise to have all the control it wants in communication and collaboration through Active Directory and Lync, and yet be able to connect people within enterprises to consumers, businesses and trading partners around the world. Lync … with Skype is a strategy that will allow the consumerization of IT to really proceed with full vim and vigor.”

Take another look at that last statement. (Not the ‘vim and vigor’ part, that’s just Ballmer trying to sound British.)

“Consumerization of IT.”

That makes me think. About the connectivity options available at different levels of business.

And my thinking makes me want to place a bet.

Bet on SMB Positioning for Lync

I’m betting the Skype-Lync integration will create a composite app that gives Lync functionality to the SMB level of business.

Lync’s highest adoption rate came from enterprises. They (for the most part) know what it can do.

But smaller businesses?

The SMB market is more familiar with Skype, not Lync. But there’s functionality they could use that Skype doesn’t have – UC connectivity with Office apps, for one.

I could be off. Heck, I could be restating an obvious development. But it still strikes me as a good bet to make. A blended Lync-Skype application would bring Lync capabilities to the small-business and mid-market business spheres.

Plus, it would make “Lync in the Cloud” easier to adopt.

Will the Positioning Hurt Current Skype Users?

Thousands of businesses already use Skype as a low-cost phone system. Does the Lync integration hurt them?

Maybe. Depending on how MS conducts the software integration, they might have to buy Lync Server (in some form) to use full UC capabilities. A composite app could be a middle-of-the-road…or a required upgrade.

It’s all speculation right now. We’ll have to see how right I am–eventually!

What do you think? Am I on-target with these integration speculations?

Late last year I posted on Office 365. More specifically: What does a Cloud Version of Lync Server (Hosted by Microsoft) Mean for the Market?

Including a version of Lync in Office 365 struck me as a good move. It means the demand is growing, and it provides a low-cost alternative to a full Lync Server setup.

Now that Office 365 has opened, it’s time to revisit the topic!

The Office 365 Advisors website recently posted a feature list comparing Lync Server, Lync Online and Office Communicator Online. (The list originates on the Office 365 Community site, but the Advisors post also comments on Lync Online pricing. And they made the list look cleaner.)

While this is a very thorough list, it is a feature-by-feature comparison. Let me extrapolate on what we’re reading. See if I can’t draw out some general guidelines on when it makes sense to use a full Lync Server. And when Lync Online would be a better choice.

When to Use Lync Online

Lync Online includes the features needed for IM & audio conferencing: The Attendee client, the Web app, interoperation with certified partners, conference scheduling and more. It does not include Group Chat, IM federation, PSTN calling (except for conferencing, via a third-party connector) or IP phone support.

This sort of package would appeal to an office where third-party connectivity isn’t necessary. Maybe the whole office already has smartphones, but they’re spending lots of money on conferencing systems. Lync Online makes sense as a cheaper alternative (per user), that also integrates into Outlook.

So when should you use Lync Online? When the focus is on conducting meetings and inter-office communication.

When to Use Lync Server

Obviously, Lync Server includes the features that aren’t in Lync Online. Full-service VoIP, PSTN calling, Call Admissions Control (CAC), interoperation with a PBX. All in. Of course this means you need a full server installation too. It’s a large investment, and it’s up-front (as compared to Lync Online’s per-user monthly pricing).

Lync Server is the better option if you need full communication options. Desk phones, calling (and receiving calls from) customers, and so on.

When should you opt for Lync Server? When the focus is on VoIP communication, especially calling out.

Honestly, Lync Online has more features than I thought Microsoft would include. Which is great – it’s a very affordable way to get into using the Lync platform.

Have you used Lync Online yet? How well did it work for you? Tell us your conference stories!

Last week I said I’d dedicate a post to the Lync How-To in the new Lync Adoption & Training Kit.

Having spent a little while fiddling with it, I’m glad I did. This tool deserves the focus!

The Lync How-To fulfills several functions at once, both out-of-box and with the customization options it presents. Use it as a training tool, a knowledge base, a FAQ, etc.

(Apologies for the screenshot quality; I’m not the designer on the team!)

There are two versions of the tool: One in Silverlight, one in HTML. I tried out the HTML version. (Bonus tip: The jqueryRolodex.html file will load in a browser directly. No need to upload it to a Web server first!)

As you see above, the tool’s set up with an expand-to-the-right menu style. This way you can see all the subcategories for any given topic. Quick, easy reference.

The categories are:

• Lync 2010 Presence and Instant Messaging
• Lync 2010 Voice and Video
• Lync 2010 Sharing and Collaboration
• Meetings and Conference Calls – Schedule
• Meetings and Conference Calls – Join
• Meetings and Conference Calls – Conduct
• Lync 2010 Group Chat
• Lync 2010 Attendant

On some pages, you’ll see a movie projector icon in the top right. When you do, it links to a how-to video from Microsoft on the current topic.

I’m pointing this out because it leads into a huge benefit of the How-To: You can customize ALL of the content in it.

Make the Lync How-To Fit Your Business (Instead of the Other Way Around)

The Lync How-To uses JavaScript, CSS and XML. So every part of it is customizable. Use these and you can:

1. Add your own information. Edit the content if you want, or add in company-branded images. Look in the Assets folder for each category’s images, scripts & videos.

2. Turn off categories you don’t use (or change the ones already there!). In the How-To tool, a file called Rolodex.xml lists all the category and content list information. If you aren’t using a certain Lync element (say, Archiving?), you can comment out the Archiving category in Rolodex.xml.

3. Use this as a reference for your own tutorials. Guide your users through steps in the How-To in order to educate them. For example, let’s say I wanted to train a group on how to:

• IM a co-worker
• Start a call in Lync between you two
• Invite a customer onto the call (even though they don’t have Lync)

I would point the group to these steps:

• Lync 2010 Presence and Instant Messaging –> Send an Instant Message
• Lync 2010 Voice and Video –> Add Voice to an Instant (Messaging Conversation)
• Lync 2010 Voice and Video –> Invite Others to a Call

A Step Above the Usual FAQ

This tool essentially brings a detailed Lync tutorial directly to your users. Instead of telling them to go search out some URL online, you can just hand them a shortcut.

The How-To even includes etiquette recommendations for IM conversations, calls and conferences! (I know I’ve had a few IM conversations where I wanted to smack someone with a dictionary…)

Download the Lync 2010 How-To in the Lync Adoption & Training Kit from Microsoft.

Have you tried this out yet? What customization would you add to it?

It’s a cold reality for IT: One short-circuit and all that work is down the tubes. Unless of course, you have a backup.

Server backups are nothing new for admins. So we’d better make sure Lync Server is included too.

NextHop offers an excellent white paper on this very topic: Backing Up and Restoring Lync Server 2010 – NextHop

Or, go straight to Microsoft Downloads for the white paper.

They’ve done a better job than I could hope to here. So I’ll post some things to remember from it (and our own observations) for today’s “20 Tasks” entry.

Backing Up/Restoring Lync Server: Things to Remember

1. Have a strategy in place. Consider how often you want to backup, where backups should be stored, what situations merit a restoration, where you’ll get replacement hardware if needed, when/how to test backups, and so on.
2. Make sure you’re backing up data AND settings.
3. Group Chat is NOT backed up with standard cmdlets.  See Backing Up the Group Chat Database, Compliance Database, and File Repository for that.
4. First backup priority is the Central Management Store database (Xds.mdf). It contains the Lync Server topology. Essential.
5. Include Active Directory Domain Services in this backup. AD DS has the user SIP URIs, contact objects for Response Group and Conferencing Attendant, authentication accounts, etc. Very important stuff.
6. The cmdlets for backing up Lync Server components:
   • Topology Data :: Export-CsConfiguration
   • Location information service/E-911 :: Export-CsLisConfiguration
   • Response Group configuration data :: Export-CsRgsConfiguration
   • Persistent user & Conference ID data :: Dbimpexp.exe (It’s in the Lync installation media)
7. Use SQL Server Management Studio to backup the Archiving and Monitoring databases.
8. A standard backup system (the white paper lists RoboCopy) will work for backing up the Lync Server file store.
9. The cmdlets for restoring Lync Server components:
   • Restore the Active Directory pointer to the Central Management store :: Set-CsConfigurationStoreLocation
   • Import topology, policies, and configuration into the Central Management Store :: Import-CsConfiguration
   • Republish the topology :: Publish-CsTopology
   • Enable the republished topology :: Enable-CsTopology
   • Restore location information/E-911 :: Import-CsLisConfiguration
   • Restore persistent users :: Dbimpexp.exe
   • Restore Response Group :: Get-CsApplicationContact (available on the Lync PowerShell blog) AND Import-CsRgsConfiguration
10. Don’t change any of the following between a backup and a restoration:
    • DNS configuration
    • DHCP configuration
    • Domain names
    • FQDNs
    • File store paths

    Restoration won’t work properly if you do.

11. Include Lync’s SQL databases in the nightly backups.

The white paper’s based on recovering from a failure in the Lync Server topology. Personally, I like the comfort that comes from having a good backup routine in place. But if “avoiding the panic of a horrible crash with no backups” is better motivation for you, then stick with that!

We’ve only got a few more posts left in this “20 Tasks” series. Anything I haven’t covered yet you’d like to know?