There’s so much information in the new Lync 2010 Training Package that I had to dedicate another post to it.

As promised, a second comparison of its training lists. As this package is geared toward training users on the Lync 2010 client, we’re talking about the Help Desk list today.

Training List 2: Help Desk

Last post I pointed out that each of the training packages is based off a “standard set” of materials. FAQs, Quick Reference cards, introductory How-To videos, and Self-Paced Training.

With Help Desk, we see how Microsoft adapts the training package for different roles. Specifically, 2 more resources included above this standard (1 new, 1 at higher priority).

A. The addition of “Help Desk Troubleshooting,” a 110-page reference document for common Lync client problems.You’ll find guidelines for everything from “(Sharing) Participants See a Black Window” to “Agent Unable to See Some Response Groups.”

The Troubleshooting document alone makes this worthwhile. It’s a great keep-on-hand reference. Our Support department has already used it to help a client. (I may pull some how-to’s for future posts in fact.)

B. The Instructor-Led Training mentions go from “Optional” to “Strongly Recommended.” Often the only difference between training lists is what priority each material element is assigned. However, because the Help Desk will field most of the (initial) support calls, it’s important they be fully informed on Lync’s capabilities.

If you want to see what’s available for Instructor-Led Training, look here. There are four courses (registration required, but free):

1. Introducing Microsoft Lync
2. Best Practices for Microsoft Lync Conferencing
3. Facilitating a Successful UC Rollout
4. Effective Conferencing with Microsoft Lync: Transitioning from Office Live Meeting

How to Start Lync Training with the Instructor-Led Courses

These 4 are the only courses for the whole Lync Training Package (at least for now). You’ll find them, at different priority levels, in almost every training list.

I don’t think all of these benefit the Help Desk most, though. Pick and choose which are the most relevant to the role you’re training for.

Here’s what I would suggest: Use the Instructor-Led training in the following order (by role).

• Executives and Information Workers sign up for 1 & 2 in succession
• Information Workers sign up for 3 & 4 afterward
• Early Adopters sign up for all 4
• Help Desk signs up for 1, 2 & 4
• New Hires and Admin-Receptionists sign up for 1

This way everyone receives at least an overview. From there, more technical roles take on more technical training. All without disrupting everyday workflow.

Next week – we’re talking about Archiving Server. The recent post on Monitoring Server got a lot of attention, so I’m tackling its cousin. Watch for it!

Have you tried out Mobile Lync yet?

Microsoft has released brand new clients for every major mobile platform – iPhone, Android, Windows Phone, even the iPad. Twitter’s abuzz over the new clients.

All of the clients will work with both on-premises Lync Server or Office 365′s Lync Online. (However, some features are not available to Lync Online users.)

Let’s go through what’s available, shall we?

Lync for iPhone

Download Lync for iPhone at the iTunes App Store.
What it does: Presence, IM, Email Contacts, Enterprise Voice Calls, Voicemail, Dial-Out Conferencing, Call Forwarding.
The iPhone client is surprisingly comprehensive. It even has capabilities (Enterprise Voice Calls) the Android client doesn’t right now. Microsoft really pushed to make the iOS client as complete a duplicate of Lync 2010 (desktop) as possible.

Lync for iPad

Download Lync for iPad at the iTunes App Store.
What it does: Presence, IM, Email Contacts, Enterprise Voice Calls, Voicemail, Dial-Out Conferencing, Call Forwarding.
Virtually identical to the iPhone client (adjusted for iPad screens of course). However, the reviews for this version gave it a slightly lower rating the iPhone client. One reviewer noted that push notifications didn’t work for her.

Lync for Android

Download Lync for Android at the Android Market.
What it does: Presence, IM, Email Contacts, Voicemail, Dial-Out Conferencing, Call Forwarding.
The Android client is a fairly basic mobile app. Some features are not supported yet (VoIP, video). Right now it appears to function best as a connector between the phone’s capabilities and Lync Server.

Also, note: Lync for Android runs in the background, all the time. Push notifications aren’t necessary. Something to keep in mind for Android users!

Lync for Windows Phone 7

Download Lync for Windows Phone from the Windows Phone Marketplace.
What it does: Presence, IM, Enterprise Voice Calls, Conferencing, Call Forwarding.
Of all the clients, this one looks the sharpest to me. Look at this screenshot. Slick, isn’t it? Almost a step up from the Lync 2010 interface.

Appearances aside, the Windows Phone client packs in every feature the iOS clients have. Several more than Android, like taking delegate calls & using Call via Work.

However, one thing is missing: access to Lync voicemail. I’m honestly not sure why Microsoft didn’t include this. The system has the same base from server (Lync Server) to hardware platform (Windows Phone). What prevented voicemail?

What’s Missing in Mobile Lync (For Now)

Please note: According to the Microsoft Lync Mobile Client Comparison Tables, NONE of the mobile clients can do the following.

• Automatically log IM conversations in Exchange
• Manage delegates
• View video in meetings
• Conduct two- or more-party calls with external users
• Share desktop or use presentation tools

Looks like we’ll have to wait until V2 for these features.

What’s your experience with a Lync mobile client? Is there something you’d want to see added?

The Duo variant of the BIZ 620 USB. Image courtesy of Jabra.com.

Didn’t we already review this headset? Well, yes and no.

I titled this a “mini-review” because I did post a review on the Jabra BIZ 620 USB headset last month.

But one thing’s different today. Last month’s review was done on the Mono (single earpiece) model.

The Jabra BIZ 620 Duo has two earpieces.

Like its Mono brother, it has an adjustable microphone arm on one earpiece. The mic swivels to either side, so you can use it on the left or right ear (I prefer the right).

In fact switching the headset around is easier to do with the Duo model, since both ears are covered anyway.

Headset controls are located in the same call control knob as the Mono model. Located on the headset’s cord, it has four buttons for adjusting volume up/down, answering a call, and ending a call.

Advantages of the Jabra 620 Duo: Better Focus on Conversations, Music Playback

As someone who’s always used one ear with their phone, the Jabra 620 Duo takes a little bit of adjustment. The good kind – with two earpieces, it’s easier to tune out background noises when you have a call.

Test calls revealed the same audio quality, in and out, as the 620 Mono. That and the dual earpieces make Lync calls easy to make, pay full attention to, and end with a button-push.

Oh, and the 620 Duo will play music through its earpieces ( the Mono wouldn’t).

Comfort Warning: Don’t Fiddle With It Too Much

The only disadvantage I note is the weight of the control knob. It can pull down on the headset if you move it too much. With the Mono headset this isn’t too big a deal.

But with the Duo headset, you’re aware of the other ear piece slipping off your ear when it pulls down. More to adjust. So you notice it more quickly.

Still, pretty small price to pay for an immersive VoIP headset with good sound quality and an adjustable mic!

What headset do you use with Lync?

On Sunday, I received an email from a UK consulting firm. The individual (I’ll call him Mr. B) wanted to know about monitoring Lync Server.

Now, his question was more about identifying the signs of a well-functioning Lync setup. But it touched off a related question in my mind – how much monitoring does Lync Server do for itself?

Turns out, quite a lot. Lync’s Monitoring Server role keeps tabs on just about every communication in & out. It’s not a required server role for Lync to run, but it’s recommended.

Why? Simple reason – Monitoring Server reports help you figure out what’s working (and what’s not).

Reports are broken down into four categories: System Usage Reports, Call Diagnostic Reports, Call Diagnostic Reports (per user), and Media Quality Diagnostic Reports. Makes it easier to identify a specific problem, if you know what type of problem you’re looking at.

What Monitoring Server DOES Provide

Overall, reports cover pretty much everything you’d want to know about how good a job your Lync Server’s doing. For example, you can find all of this in Monitoring Server reports:

1. Information about the communication sessions in your organization. That covers VoIP phone calls, IM sessions and conferences.
2. Endpoint information about each session. IP addresses, connection speeds, which Edge Servers were used, etc.
3. Quality measurements for the different types of communications you use (SIP calls, video conferencing, etc.).
4. Activity lists for each user in the organization, by date and/or session type.
5. Reports on Call Admission Control-restricted sessions.
6. Summary of (and details on) calls made to Response Group workflows.
7. Diagnostic reports and troubleshooting information for session failures (including SIP response codes and diagnostic headers).
8. Server Performance reports:  Shows you which servers have had the most problems, using metrics like packet loss, signal degradation, noise, etc.

And a few more.

Many of the Monitoring Server reports are broken up by type, or medium. For example, one report will tell you about IM sessions, broken down by pool. Another will tell you about VoIP calls in the same pool. A third could provide a summary of all communications in that pool.

What Monitoring Server DOES NOT Provide

• The content of a phone call, IM session or conference. That’s the job of Archiving Server.
• Monitoring for the Windows Servers Lync is installed on. It doesn’t cover Windows processes. Use a standard server monitoring tool for that.
• Non-Lync Server application logging. Use a third-party tracking tool to track activity on these.

Microsoft has a Work Smart guide for Monitoring Server here: Lync Server 2010 Monitoring Server Reports Work Smart Guide – Microsoft Download Center
Plenty of information on each report, what it records, and how to make use of the data.

Have you referred to a Monitoring Server report lately? What did you find out?

Some people learn by reading, some by doing, and some by seeing. Which are you?

Up until now I haven’t done much beyond text on this blog. But today, I have a treat for the visual learners – eight Lync Server how-to videos!

I’ve written a lot of how-to on this blog over the past year. Most of what’s covered in these videos can be found here in text format. However, if you’d rather SEE how to set up an Edge Server or call forwarding, these are for you.

How to Install a Lync Server: Start to Finish, on Video

The first 5 videos come from a YouTube member named “ITBananas.” (Their YouTube Channel is here: http://www.youtube.com/user/itbananas) We’re looking at a 5-part series on how to install and configure a Lync Server 2010 setup.

I suggest watching these in Full Screen mode. It makes seeing the options selected easier.

Video 1 – Install and Configure Lync Server 2010 – Installing ADCS

Video 2 – Install and Configure Lync Server 2010 – Prerequisites

Video 3 – Install and Configure Lync Server 2010 Part 1

Video 4 – Install and Configure Lync Server 2010 Part 2

Video 5 – Install and Configure Lync Server 2010 Part 3

The videos can run a little fast. And there’s no voiceover. (I don’t mind that, but it might throw you off if you expected audio.)

Nonetheless, these make for a good step-by-step visual aid to installing Lync Server.

More How-To: Edge Servers, Call Forwarding and Making Lync Calls

Add an Edge Server to Lync Server 2010

This video was posted by “AhmedYousryHassan,” who’s likely a Microsoft tech. (The “Microsoft TechNet” logo at the beginning, and the contoso.net domain used, sort of give it away.)

This video does have voiceover. It walks you through using Topology Builder to add an Edge server to an existing Lync setup.

It’s a very clear how-to on one specific task. I’m adding this to our training regimen.

Setup Call Forwarding and Simultaneous ring in Lync 2010

We’ve had a few call forwarding questions lately, so I wanted to include a good how-to video for setting it up.

Since this one comes from the Microsoft Lync Adoption and Training Kit, I’d say it qualifies.

Make a Call Using Lync 2010

The acting is kind of bland, but don’t let that ruin this Microsoft training video. It does a good job of showing Lync’s call options. Starting calls from IM, adding people to existing calls, two-click conference calls, and so on.

What other Lync Server videos have you seen? Any good how-to’s we should mention here?

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!