In November I posted a collection of how-to videos for Lync Server.

This month, someone has one-upped all of those.

Kevin from MacroConnect emailed me the other day to tell me about his new video series. He’s named it the “Lync Complete Training Guide” Playlist on YouTube.

After watching videos and reading his documentation, I told him I would happily blog about it. You’ll see why in just a moment.

What To Expect – Setup Videos and Documented Specs

MacroConnect.net is a Detroit IT firm. One of their specialties (like ours!) is supporting Lync Server. Where I blog about it, Kevin created a video series explaining how to setup Lync Server 2010.

Here’s the playlist URL: Lync Complete Training Guide Playlist – MacroConnectLync. It’s 31 videos, average viewing time between 3-5 minutes each.

But that’s only half the guide. Kevin has also posted documentation for each video at his website:
Lync Complete Training Guide Documentation – MacroConnect.Net

The documentation is a follow-along for the videos. Each video has a link to its documentation section in the Description. Pretty high-value stuff.

Who Should Watch – Lync Pros and Support Pros

The training videos and documentation are geared toward Lync administrators, help desk personnel, and anyone who’s looking to fill these roles.

Some technical skill is assumed for the audience. Basic knowledge of Windows Server environments for one. Understanding of Lync’s primary functions, as well.

Kevin is thorough, and gives details fast. He does use MacroConnect’s FQDNs, number extensions, and PSTN gateway. Take all this into account; your setup will obviously differ.

I recommend you use the videos as the last review stage in training. The documentation is there to refresh your memory, and the videos give you a visual reminder.

What it Covers – Step-By-Step Lync Server Setup

You start in at the very top – basic server setup, SIP connections, etc. From there, the videos run through the Lync setup process, from prerequisites to server configuration. Most of the videos are devoted to configuring Exchange Server, Lync Front End, and Lync Access Edge.

The reason for documentation becomes obvious fast: the screen is not very visible in YouTube, so you can’t always see the Lync setup options selected or numbers typed in. The documentation provides the specifics you’ll need, all laid out in bullets.

(Especially useful when you’re dealing with Management Shell commands!)

———-
Special Note: There is one section in the documentation list which does NOT have a video. “ADDING EXCHANGE UNIFIED MESSAGING ROLE TO VSERV2″ is between “Configuring AD on vserv1″ and “Install Exchange from Scratch on vserv2 – Stage 1″ in the list.

The documentation does appear correct for adding Exchange UM. But Kevin has six videos in the list for installing Exchange Server – which you need to do first, before installing Unified Messaging! So, keep that in mind.
———-

I like that he covered configuring Lync Mobile and locking down the Lync Server environment . He even ends with some ideas on custom Lync programming in Visual Studio, too.

From here of course, you’ll need to add Edge servers, Mediation, Monitoring/Archiving and so on.

Kevin’s series gives a detailed method for setting up the foundation of Lync Server. If you want a video reference for a typical Lync install, these are a great choice. Thanks for all the work Kevin!

Again, here are the links:
Lync Complete Training Guide Playlist – YouTube
Lync Complete Training Guide Documentation – MacroConnect.Net

What would YOU like to see in a Lync video?

In case you’re just joining us…we’re tackling a complex answer to a fairly simple question. How do we connect (Office 365′s) Exchange Online Service to Lync Server for voicemail?

This is the third (and final) post on the solution.

Ordinarily, we’d recommend using an internal Exchange Server over Exchange Online. But the question came from one of our readers, who already had a different setup in place.

So we’re digging through all the steps necessary to make an internal communications system (Lync) work with an external service (Exchange Online).

In Part 1, we discussed providing Lync users with voice mail on Exchange Online.
In Part 2, we walked through a Unified Messaging Dial Plan and adding a voicemail policy domain to Office 365.

Two steps remain: configuring your Edge Server to integrate with Exchange Online’s Unified Messaging, and directing Lync Server to use Exchange Online.

The hard work’s done. The rest, as you’ll see, only takes some time in the Management Shell. So it’s just a matter of entering one command after another.

How to Configure the Edge Server for Integration with Exchange UM

A) Configure the Edge Server for Federation

1. Open the Lync Server Management Shell.
2. Run the Set-CsAccessEdgeConfiguration cmdlet to configure the server for federation:

Set-CsAccessEdgeConfiguration -UseDnsSrvRouting -AllowFederatedUsers 1 -EnablePartnerDiscovery 0

UseDnsSrvRouting tells the Edge Server to use DNS SRV records for sending/receiving federation requests. (The DNS SRV records were set in Part 1.)

AllowFederatedUsers is set to 1 so that internal users can communicate with users from federated domains.

EnablePartnerDiscovery is set to 0 to make sure Lync federates only with domains in the Allowed Domains list (instead of everybody).

B) Replicate Central Management Store Data to the Edge Server

1. Replicate the Central Management store data to the Edge Server. Use this cmdlet:

Export-CsConfiguration -FileName (ConfigFile.zip)

2. Copy the config file to external media. Load it on your the Edge Server.

C) Create a Hosting Provider on the Edge Server

Still in the Management Shell, run the New-CsHostingProvider cmdlet to configure the hosting provider.

New-CsHostingProvider -Identity UMDomain.com -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFQDN “proxyserver.UMDomain.com” -IsLocal $False -VerificationLevel UseSourceVerification

This cmdlet uses the following parameters (you may not need all of them):

• Identity – A unique identifier for the new hosting provider. The command will fail if you’ve used this identity value for an existing provider!
• Enabled – Must be set to True to connect your domain and the hosting provider. Can’t send/receive messages otherwise.
• EnabledSharedAddressSpace – Is the new hosting provider in a shared SIP address space (split domain)? If so, set to True.
• HostsOCSUsers – Will the hosting provider host Lync Server accounts? If False, the provider hosts other account types, like Microsoft Exchange accounts.
• ProxyFQDN – The FQDN for the proxy server used by the hosting provider. Make sure this is accurate, because you can’t change it once set. If the hosting provider changes its proxy, you’ll need to recreate its entry.
• IsLocal – Is the hosting provider’s proxy within your Lync topology? If so, it’s local (True). If not, set to False.
• VerificationLevel – Indicates the verification level for messages sent to/from the hosted provider. Putting in UseSourceVerification tells the system to rely on the verification level included in sent messages. (If this isn’t specified, the message will be rejected as unverifiable.)

How to Direct a Lync Server to Exchange Online UM

Home stretch! And we don’t even have to leave the Management Shell.

1. Use the Set-CsHostedVoiceMailPolicy cmdlet to modify the hosted voicemail policy. Specify the Destination parameter as “exap.um.outlook.com” and the Organization parameter as the FQDN of your Exchange Online routing domain (YourDomain.com here):

Set-CsHostedVoiceMailPolicy -Destination exap.um.outlook.com -Organization YourDomain.com

2. Now we’ll create a Lync contact to represent the Exchange Online UM dial plan we made in Part 2. Use the New-CsExUMContact cmdlet. Remember the dialing rules you set for your numbers then? We’ll enter the full routing number here, with the DisplayNumber parameter (use E.164 format).

New-CsExUMContact -DisplayNumber +14085551122 -SipAddress sip:exchangeuser1@lync.YourDomain.com -RegistrarPool edgepool.lync.YourDomain.com -OU “OU=ExUmContacts,DC=YourDomain,DC=com”

3. Now we’ll associate a hosted voice mail policy with this new dial plan contact. If you’re using the default global hosted voice mail policy, this cmdlet will do the job:

Grant-CsHostedVoiceMailPolicy -Identity exumsa@lync.YourDomain.com

4. Associate the dial plan contact with the Exchange Online UM dial plan we created in Part 2.

And we’re done!

Take a breath, grab a drink, and relax. Thanks to this process, you should now have:

• Established routing between Lync Server 2010 and Exchange Online.
• Voice mail storage & transfer capability between the two servers.
• Consistent dial plans for all users.

And for one more reference: Here’s the checklist for this entire process, from Microsoft.
Checklist: Connect Lync Server 2010 to Exchange Online UM

Next week we’ll feature some very helpful training videos. Good change of pace from big how-to posts. Catch you then!

Before we get to Part 2 of our latest Lync how-to series, there’s a question we should ask.

Why would you WANT to connect an internal Lync Server 2010 setup to Office 365′s Exchange Online? Why not use an internal Exchange Server instead? Or go for Lync Online?

Sometimes Email Isn’t Enough – You Need a Phone!

The customer who asked the original question didn’t say. But I suspect it involves the fact that Lync Server includes VoIP. Very important difference when it comes to value.

(Maybe it’s a smaller organization, and Exchange Online works for their needs. If so, more power to them!)

Anyway, continuing on the topic. In Part 1 we provided Lync users with voice mail on Exchange Online. According to the checklist Microsoft has laid out, the next step is to configure Exchange Online’s Unified Messaging to work with Lync Server 2010.

This process will look a bit more familiar to Lync admins. It involves setting up dial plans. Yes, very similar to Lync’s standard dial plan setup – with a couple extra steps added. Let’s get into it.

How-To, Step 2 – Configure Exchange Online Unified Messaging

A) Create a new UM Dial Plan.

Quick refresher: Dial Plans are sets of rules for normalization and governance of calls. In this case, the dial plan will govern:

• How your Lync Server connects to Exchange Online UM
• Dial rules & settings for user access
• Outlook Voice Access connectivity

Creating the dial plan is itself not difficult. Follow these steps:

1. Select Manage My Organization > Phone & Voice > UM Dial Plans.
2. Under UM Dial Plans, click New.
3. Under Name, enter a name that is unique in your organization. It can be up to 49 characters long.
4. Enter the following information for the dial plan:
1. Extension Length: Enter the number of digits you’ve assigned to your Lync phone extensions.
2. Dial Plan URI Type: Because we’re connecting to Lync Server, select SIP URI here.
3. Audio Language: Select the language to use. It’ll cover the automated greetings, phone navigation prompts, Voice Mail Preview, and Outlook Voice Access.
4. Country/Region Code: Enter your country code (or regional code) so UM dials domestic and international numbers correctly. Accepts 1-4 digits.
5. Click Save to create the dial plan.

B) Configure the Dial Plan.

1.  Select the UM dial plan you just created.
2.  Click Details. We have many details to fill out, so make sure you have the following information on hand:

• General. Verify that this information matches what you just created. (If it doesn’t, you may have to go back & recreate the dial plan.) You should see Name, Extension Length, URI Type (SIP!) & Audio Language.
• Dial Codes. Specify the number formats so your outgoing calls reach their destinations.
• Outside Line Access Code – Enter the code for accessing an outside line, if needed to reach external numbers (usually 9).
• International Access Code – Enter the code needed to place international calls for your location (US is 011, Europe is 00).
• National Number Prefix – Enter the prefix required for outgoing calls in your country/region. North America’s is 1.
• Country/Region Code – Same code as the one entered when we created the dial plan earlier. Accepts 1-4 digits.
• Country/Region Number Format – Enter the number format to resolve caller ID for users dialing outside this dial plan to other dial plans in your company. If you wanted to add a 4-digit extension for caller ID (like 1234), you’d enter 1234xxxxx.
• International Number Format – Same as the point above, but for international calls. For instance, if you wanted to add 011-1234 as a prefix to an international caller extension, you’d enter 0111234xxxxx.
• Number Formats for Incoming Calls – Enter the number format to use to provide caller ID on calls placed to users of this UM dial plan. For example, you’d enter 2345xxxxx to add the 2345 prefix to a 5-digit extension for incoming calls.
• Outlook Voice Access. Select the greetings & numbers for Outlook Voice Access. Recorded greetings & announcements must be in 16-bit, 8kHz .wma or .wav file format.
• Welcome Greeting – Click “Change File” if you want to upload a custom greeting file for Outlook Voice Access callers.
• Informational Announcement – Click “Change File” to upload a custom recording to be played for callers after hours.
• Allow Announcement to Be Interrupted – Check the box if you want callers to be able to skip the announcement.
• Numbers for Users to Access Voice Mail – Enter a number for dial plan users to access their mailboxes, and click Add. Letters and numbers are supported.
• Settings. Options for name searches, operator extensions, max recording length, and more.
• Primary Way of Searching for Names – How should callers search for people in the address book? Specify it here. Could be by last name and first name, first name and last name, or an alias.
• Secondary Way of Searching for Names – You can enter a second search method here, or select None to skip the option.
• Audio Codec – Select the codec to use for recording voice mails. Available codecs are: MP3 (default), GSM, G711, and WMA.
• Operator Extension – Enter the extension you want callers to connect with when they press zero. Could be an Auto Attendant, a specific person, or an external number.
• Number of Sign-in Failures Before Disconnecting – How many sign-in attempts before disconnection? Default is 3, but you can choose from 1 to 20.
• Timeouts and Retries – Change these settings to control how long recordings can last. Also controls when to timeout after a failed option.
• Maximum Call Duration – How long should incoming calls last? Default is 30 minutes, but you can change the number (from 10 to 120) for all calls in the dial plan.
• Maximum Recording Duration – Enter the maximum time a voice mail recording can last. Default is 20 minutes. Can go from 1 to 100 minutes (must be less than the Maximum Call Duration).
• Recording Idle Timeout – Enter the number of seconds of silence to allow in a voice mail, before disconnecting the call. Anywhere from 2 to 10 seconds. (default is 5).
• Number of Input Failures Before Disconnecting – How many times should callers be able to enter incorrect information when searching the address book, before they’re disconnected? 1 attempt to 99, default is 3.
• Audio Language – Select the language to use for automated greetings, phone navigation prompts, Voice Mail Preview, and Outlook Voice Access. Same as the one you selected creating the dial plan.
• Dialing Rules. These rules define the types of calls users can make. They also change the number users dial to the number that UM dials for outgoing calls. Adding a 9 for outside lines, etc. Groups of rules are placed into dialing rule groups, which you use to authorize all the rules together. You authorize rules under Dialing Authorization (see below), UM mailbox policies, and/or UM auto attendants.
• In-Country/Region Rules – Create these dialing rules to define what kind of in-country/in-region calls your UM users can make.
• International Rules – Same thing, except for international calls.
• Dialing Authorization. Previously we created dialing rules for controlling the types of calls users can make. This is where we authorize those rule groups.
• Allow Calls in the Same UM Dial Plan – Select the check box to allow unauthenticated callers calling into the access number to call/transfer to other users of the UM dial plan.
• Allow Calls to Any Extension – Checking this box allows unauthenticated callers calling the subscriber access number to call/transfer to extensions of non-UM-enabled users.
• Allowed In-Country/Region Dialing Rule Groups – Dial plan users can dial the numbers authorized by the dialing rule groups in this list.
• Allowed International Dialing Rule Groups – Same as the previous setting, but for the international dialing rule groups.

Don’t forget to click Save!

C) Add the domain configured for your Lync voice mail policy to your Office 365 domains.

By now you already have domains set up for Lync, from Part 1. Microsoft recommends using the third-level domain assigned when you signed up for Office 365 (e.g., office365.yourdomain.com).

(Note: It can’t be the same one you use for Lync users’ SIP addresses.)

To Add the Domain:

1. On the Admin page in Office 365, under Management, click Domains
2. Click “Add a domain.”
3. Under Specify domain on the next page, type the domain name you want to add, and then click Next.
4. Follow the next steps in the wizard to verify with Office 365 that the domain name belongs to you.

Once the domain name is added, you must specify services with which you’ll use it.

1. In the Add a Domain wizard, on the Specify services page, select the services you want. In this case, Exchange Online.
2. Click Next.

Finally, you must edit your DNS records on this domain.

1. If you just completed the Add a Domain wizard, click “Configure DNS records.”
2. Otherwise, click Domains on the Admin page.
3. Click the domain name you just set up, and click the DNS Settings tab. Here are the DNS records for Office 365′s services.
4. Take these records to your domain registrar’s website, and add them into your DNS file.

For more details on this process, read this reference: Add Your Domain to Office 365.

In Part 3 we make the last connection – directing the Lync Server to Exchange Online. Check back next week, and we’ll wrap up the whole how-to.

The Lync questions keep coming! Yesterday, one came in with a request that appeared pretty simple:

“I tried to connect our Lync Server to Exchange Online. Now we can’t use voice mail. What went wrong?”

VERY good question. Let’s tackle it.

Connecting an Internal Lync Server to an External Exchange Server?

Let’s take a step back from this. What they did was try to connect a Lync Server to Office 365′s Exchange Online package. One internal system (Lync), interoperating with an external one (Exchange Online).

There are several reasons you might want to do this.

• Sharing of calendar information and Out of Office messages
• Voice mail interoperability
• IM and Presence status showing up in Outlook Web App (as in, outside the organization)

Yes, it’s possible to connect these two services. But it’s more complicated than you’d think at first. Several management steps are required for Lync and Exchange Online to see each other, THEN talk to each other.

In fact, there’s a whole checklist you need to follow to make it all work:
http://help.outlook.com/en-us/140/gg702674.aspx

Microsoft posted this late last month. Many people missed it due to the holidays. (But that’s why we have the Lync Insider blog, right?)

How-To, Step 1 – Provide Lync Users with Voice Mail on Exchange Online

(Please note, I’m starting at #2 on the checklist linked above. #1 is deploying Lync Server 2010, with Edge Servers and Enterprise Voice. If you need help with those, read our Path to Lync Server – Step 6: Install Lync Server post.)

A) Create a DNS SRV Record for integration.

1. Log on to your external DNS server (as a DnsAdmins group member!).
2. Click Start / Administrative Tools, and then click DNS.
3. In the console tree for your SIP domain, expand Forward Lookup Zones. Select the SIP domain where your Lync Server is installed (e.g. “edge1.yourdomain.com”).
4. Right-click the SIP domain, and click Other New Records.
5. Click “Service Location (SRV)” under Resource Record Type.
6. Click “Create Record.”
7. In the New Resource Record window, click Service. Enter _sipfederationtls (don’t forget the underscore).
8. Click Protocol. Enter _tcp
9. Click Port Number. Enter 5061
10. Click “Host offering this service.” Enter the FQDN of the Lync Server Edge pool that provides access to external clients.
11. Click OK. Then click Done.

Make sure the domain used in the SRV record you’re creating here matches the domain used in the DNS Host (A) record.

B) Set up external Edge Certificates.

You may already have certificates set up on the external Edge Server. If they’re set up for federation, then you’re fine here. If not, use these instructions:

• Switch to a member login with higher permissions (e.g. the RTCUniversalServerAdmins group).
• Follow the steps at this TechNet page:  http://technet.microsoft.com/en-us/library/gg398409.aspx
• They will guide you through creating the certificate request, submitting it, importing & assigning the certificate to your Edge Servers.

C) Configure the Edge Server for integration.

1. Configure your Edge Server for federation. Start the Lync Server Management Shell (under Start / All Programs / Microsoft Lync Server 2010). Enter this cmdlet:

Set-CsAccessEdgeConfiguration -UseDnsSrvRouting -AllowFederatedUsers 1 -EnablePartnerDiscovery 0

It indicates that Edge Servers will use DNS SRV records for federation requests, allows federated users, and specifies that Lync should use DNS records to discover a partner domain (in this case, the Exchange Online service).

2. Still in the Management Shell, we’ll create a hosting provider on the Edge Server. Do this using the New-CsHostingProvider cmdlet.

New-CsHostingProvider -Identity ExchangeOnline.com -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFQDN “proxy.ExchangeOnline.com” -IsLocal $False -VerficationLevel UseSourceVerification

Where I’ve inserted “ExchangeOnline.com” – for the Identity and ProxyFQDN parameters – enter the URLs for your Exchange Online setup.

3. Verify that the Central Management Store data replicates to your Edge Server. See this TechNet link if you need help.

D) Enable your users for hosted voice mail.

Still in the Management Shell, use the Set-CsUser cmdlet:

Set-CsUser -HostedVoiceMail $True -Identity “YourDomain\JoeSmith”

Identity parameter can use either the user’s SIP address, their domain\logon name (like the above), their AD-DS display name or their User-Principal-Name. Easy to do – but you’ll have to enable every user this way!

E) Create Contact Objects for Exchange UM Online.

You’ll need contact objects for each auto-attendant (AA) number and subscriber access (SA) number in your deployment. Set these in Management Shell with the New-CsExUmContact cmdlet:

New-CsExUmContact -SipAddress “sip:ExampleAddress@YourDomain.com” -RegistrarPool “LocalPool.YourDomain.com” -OU “Exchange Online Integration” -DisplayNumber “+14085551111″ -AutoAttendant $True

New-CsExUmContact -SipAddress “sip:ExampleAddress@YourDomain.com” -RegistrarPool “LocalPool.YourDomain.com” -OU “Exchange Online Integration” -DisplayNumber “+14085551111″

SipAddress should be a new address, not in use by a user or contact object in AD-DS. RegistrarPool is the FQDN for the pool where your Registrar service runs. OU specifies where your contact object will be. DisplayNumber must be a unique number for each contact object. If AutoAttendant is set to True, the contact object is set as an Auto Attendant Object. If set to False, it’s a Subscriber Access object.

This is a lot to go through, I know.  Stay sharp – that’s just Part 1 of the setup!

In Part 2 next week, I’ll go through configuring Exchange Online so its Unified Messaging works with Lync. See you then!

Lots of questions coming in this month! If you’ve sent one in, don’t worry, we’ll get back to you. (I know we’re testing some changes in our local Lync Server, before we respond to one of them.)

Last week we received this question:

“Can we set up a global policy so everyone has a 5-minute idle in Lync?”

The answer to this question is yes – and no.

Right now, you can’t use a GPO (Group Policy Object) to set a Lync 2010 client’s default idle limit – when Lync switches from Available to Away.

You could go around changing each client’s idle settings, of course. But that’s way too time-consuming (and no self-respecting sysadmin would work that slow).

Don’t worry though! There IS a way to enforce a default idle for Lync users: Use a Management Shell script.

Run a Script at Startup to Set Global Idle

That’s right. One simple script will enforce global idle limits on all clients.

In a moment I’ll show you the script. But before that, a quick reminder: the Lync Server Management Shell isn’t set to run scripts by default! You’ll have to modify the execution policy so you can run scripts.

Which is easy. Just enter this command in the Management Shell prompt:
Set-ExecutionPolicy RemoteSigned

With that done, let’s move to the script itself. Copy the following into Notepad and save it as “set-global-idle.ps1″.

$computer = "."
$registry = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey("CurrentUser", $computer)
$key = $registry.OpenSubKey("SOFTWARE\Microsoft\Communicator", $True)
$key.SetValue("IdleThreshold",5,"DWORD")

Those of you who are familiar with PowerShell will see how this script works at a glance. Even if you aren’t, this script’s pretty easy to understand: It makes a small change to the client PC’s registry, relating to Lync’s registry keys.

In this case, we’re changing the “IdleThreshold” or idle timeout point.

You will have to run Set-Global-Idle.ps1 on everyone’s PCs at startup. It’ll act like a pseudo-GPO, making a background change during boot. We’ve tested it and had no errors.

Modify the script as you like! Setting idle isn’t all you can do with this method. But be careful; this causes a change to client PC registries. The wrong parameters could cause registry corruption…and nobody wants every single PC in the office to crash at once!

Bravely Standing In for Lync GPO

We’re sure Microsoft will release a Lync Server patch that lets you control global idle soon. Use our Set-Global-Idle.ps1 script as a stand-in/workaround for now. It works, but it’s an extra step imposed on your Lync setup.

Have you modified your Lync Server installation using Management Shell? How?

Archiving Server provides a repository for information exchanged via Lync Server. Why? Two reasons:

1. It gives you a log of Lync activity everyone can draw upon. How many times have you tried to remember what Jane said about the Michaels project? Thanks to Archiving Server, you have a saved copy of that IM conversation.
2. It helps you fulfill legal compliance requirements. Many organizations must keep track of project steps, client files, and so on to meet compliance regulations. Since Archiving Server tracks automatically, its archive database acts as a regulatory resource.

What DOES it track though? It’s important to know what is and is not archived by Archiving Server. Otherwise, you might assume it just grabs everything. It doesn’t.

What Lync Archives on the Archiving Server

• Instant messaging conversations (both person-to-person, and between multiple parties)
• Content uploaded in Web conferences
• Conference events (joins, parts, etc.)

What Lync DOES NOT Archive on Archiving Server

• File transfers
• Conferencing annotations and polls
• Audio & video for person-to-person IM and conferences
• Application sharing for IM and conferences
• Diagnostic reports for session failures (those come from Monitoring Server)

Caution – There’s a Time Limit on Archived Materials

It’s important to note: Archiving is NOT intended to work indefinitely! As you can imagine from the above lists, storing uploaded files and daily IM logs will fill up space fast.

The server will keep archives until one of two things happens:

1. You tell it to purge old archived files.
2. Its storage fills up.

Obviously, you don’t want to reach #2.

In the Lync Server 2010 Control Panel, there’s a setting that dictates when to purge old archive files. You can control the time interval for this under Archiving Configuration. How long you keep archived files depends on your legal compliance requirements. 1 year, 2? Talk to Legal.

Then head to this page for a how-to: Enable or Disable Purging for Archiving – TechNet.

Want to add Archiving Server to your Lync setup? Use this deployment guide to help you.

If you’re having trouble with Archiving Server (e.g. conversations aren’t showing up in Conversation History), use NextHop’s “Troubleshooting Archiving Server” post as a guide.

Do you use an Archiving Server? What’s the big value from it, for you?

While on Twitter yesterday, I saw a new Lync download making the rounds:

Microsoft Lync 2010 Training Download Package

From the overview:

“The Lync Training Download Package contains all of the available training and user education resources for Lync.”

All of these resources are sorted for you in an Excel workbook, & divided up by office role.  Information Worker, Early Adopters, New Hires, Admin-Receptionists, Executives, Help Desk and Lync Online.

Each list is broken up by a category, defined by Lync Server Role or communication method.  They are:

• IM and Presence
• Collaboration and Conferencing
• Voice and Video
• Devices
• Group Chat
• Attendee
• Lync Web App
• Lync for Mobile Clients
• Lync for Mac

The training material for each category is ranked, from “Optional” to “Strongly Recommended.”  Some of the material comes in the training package download.  The rest is available on Microsoft’s support websites.

Organizes Current Lync Training Material For You

Why use this new training package?  It makes Microsoft’s Lync education resources neat & easy to find.

Everything (to date!) is included:

–WorkSmart Guides
–Quick Reference Cards
–FAQs
–Training Videos
–Instructor-Led Training (registration needed)

However, it’s important to know:  This is NOT recommended as a resource for Lync certification.  There’s almost no server-side material.   The package is clearly intended to help you train to support Lync’s client-facing functions.

Training List 1:  New Hires

The “New Hires” category is a good starting point.  It lists out what I’ll call the “standard set” of training materials.  FAQs, Quick Reference Cards, introductory How-To  Videos, and Self-Paced Training.

You’ll find these in every other category, with additional resources and/or different recommendation levels depending on the role.  Pay attention to Recommendation levels…they’ll give you a path to follow.  Start with “Strongly Recommended” and work down from there.

For instance, under Collaboration & Conferencing for New Hires, a Quick Reference Card and Self-Paced Training are “Strongly Recommended.”  A How-To Video is “Recommended.”  And Instructor-Led Training is “Optional.”

Catch-All for Microsoft Lync Education

How effective will this training package be?  That depends on how you decide to use it.  The download includes a lot of information, some of it new.  (I’m putting the “Help Desk Troubleshooting” doc on our SharePoint right after this post.)

Microsoft has written the workbook as a catch-all and a starting point.  So you can build training into your office’s activities by grabbing certain elements and putting them in front of the people who need them most.

Next week I’ll go into more detail with comparisons between categories.  Until then – planning to use this download?  How?

We’re back, with another hardware review! Up for today is our newest acquisition (and already our favorite conferencing tool): the Jabra SPEAK 410-USB speakerphone.

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?

Something a little different this week – two mini-posts!

One today on a Lync Server update. One tomorrow on the Jabra BIZ 620 Duo USB headset.

Mobile Clients are Coming Soon: Prepare Lync Server

Yesterday I tweeted a link to a recent Microsoft announcement: Lync clients coming soon for Windows Phone 7, the iOS platform, and Android (via Engadget).

Last week, Microsoft also released a new Cumulative Update for Lync Server 2010 – one intended to prepare Lync for use of these new mobile clients.

The update, Cumulative Update 4, consists of multiple server-side (and client-side) updates, as well as six new Cmdlets. The cmdlets are what mark this as a mobility update. Tom Arbuthnot has written thorough descriptions of the cmdlets over at the Lync’d Up blog. I’ll just give overviews on what they do here (go read his post for full information – it’s worth it!).

1. CsAutodiscoverConfiguration: Lets you change Autodiscover settings. Autodiscover helps client apps (like a mobile Lync client) find certain resources, like a user pool.
2. New-CsWebLink: Creates a Web link to Autodiscover. Handy for updating configuration with new clients.
3. Test-CsMcxPushNotification: Verifies that Push Notification’s working, so you’re able to send notifications out to mobile devices.
4. CsMobilityPolicy: Lets you control Mobility Policies. In Lync, these policies govern who can use a mobile client, as well as if you can use Call via Work (using work numbers instead of mobile numbers for calls).
5. CsMcxConfiguration: Configures Lync Server Mobility Service settings. Enabling mobile devices to use many of Lync’s services – Presence information, voicemails, conferencing, etc.
6. CsPushNotificationConfiguration: This cmdlet lets you configure Push Notification.

Lync Server Updates for Core Components, Administration and Clients: Install Them All

The Cumulative Update 4 files are available for download at Microsoft Downloads. The easiest installation method would be to use the Cumulative Update Installer (LyncServerUpdateInstaller.exe).

If that doesn’t work for you, look under “Installation Methods” on this Microsoft Support page for a manual install option.

And as Justin Morris wisely reminds us – don’t forget to backup your Lync Server setup first!

Check back tomorrow for our second Lync headset review!