IT tutorials
 
Applications Server
 

Microsoft Lync Server 2013 Monitoring and Archiving : Archiving Configuration (part 2) - Using Cmdlets for Configuration Tasks

2/23/2014 8:24:34 PM
- How To Install Windows Server 2012 On VirtualBox
- How To Bypass Torrent Connection Blocking By Your ISP
- How To Install Actual Facebook App On Kindle Fire

Using Cmdlets for Configuration Tasks

As one might logically expect, the policies and configurations can also be created through cmdlets; for example:

New-CsArchivingConfiguration -Identity "site:Santa Clara" -EnableArchiving ImAndWebConf -EnablePurging:$True -PurgeExportedArchivesOnly:$False -BlockOnArchiveFailure:$False -KeepArchivingDataForDays:120 -ArchiveDuplicateMessages:$False

Notice the last argument set in this command: ArchiveDuplicateMessages. This is a good example of where there are options available through the cmdlets that aren’t exposed to the GUI tools.

The power of using cmdlets to manage an application, such as Lync Server 2013, becomes readily evident when you are dealing with a large implementation. By scripting the configuration of the entire environment, you are able to eliminate the human error introduced by having a distributed group of people perform repetitive tasks. Similarly, the script written to perform the configuration immediately becomes the documentation of the configuration. If later changes need to occur, you can perform queries to find the objects and modify them at the same time. If you plan to manage the environment in this manner, it becomes helpful to put some thought into a logical naming convention for policies and configurations. This enables you to search on some common value in the policies and configurations to select them for modification.

In a similar manner, PowerShell-based cmdlets make it easy to pull configuration reports from a large implementation. For example, imagine that your company announced a policy that all IMs will be retained for at least 30 days. More than likely, someone will ask you to make sure that all your configurations retain messages for at least 30 days. Rather than scrolling through the GUI to find configurations with values under 30, you could simply run a cmdlet like the following to produce a report of all configurations in which the CachePurgingInterval is less than 30 days:

Get-CsArchivingConfiguration | Where {$_.CachePurgingInterval -lt "30"} | select Identity

However, if you were going to do that, why not fix it all at once?

$Array=Get-CsArchivingConfiguration | Where {$_.CachePurgingInterval -lt "30"}
Foreach ($Name in $Array)
{
$Var = $Name.Identity
Set-CsArchivingConfiguration -Identity $var -CachePurgingInterval:30
}

This report searches all configurations in the topology and sets any that have a CachePurgingInterval of less than 30 to 30 without touching any that were already higher than 30.

Archiving Administration

This section reviews common administration tasks for the Lync Server 2013 Archiving role, including Data Export and Purge Mode.

In general, there isn’t much day-to-day administration of the Lync Server 2013 Archiving Server role. Instead, this section focuses on the management of data stored in the Archiving database.

One of the most common tasks you perform against the Archiving Server is exporting content from the Archive database. This is performed through the Lync Server Management Shell using the Export-CsArchivingData cmdlet as follows:

Export-CsArchivingData -DBInstance SQLSRV -StartDate 05/15/2012 -OutputFolder
"C:\Archiving" -UserUri Alex@Companyabc.com

This command exports all sessions pertaining to the UserURI defined in the cmdlet. The output is a series of .eml files that are created in the OutputFolder path.

Archiving Troubleshooting

The Archiving Server role is fairly straightforward; however, there are a few things that commonly go wrong during deployment. This section covers the common issues and areas to check if you find your Archiving Server deployment not going smoothly.

Because a lot of server-to-server connections are involved in an Archiving Server deployment, the most obvious problem area is in ensuring proper permissions. Also, ensure that usernames and passwords are typed correctly. When in doubt, reenter the usernames and passwords used for database access for the Archiving Server. Also, ensure that the accounts aren’t subject to password expiration in Active Directory.

The Lync Server event log is also a good place to check for errors. From the Start menu, select Administrative Tools, and select Event Viewer. Expand the Applications and Services Logs item and select Lync Server. All events related to Lync Server 2013 functions reside here. Often the error description is enough to identify the problem and determine the resolution.

One common cause for Archiving to fail is that the Front End Server isn’t able to install the Archiving agent properly due to a problem with the Message Queuing Service. You might see event ID 30517 in the Lync Server logs or you might see event ID 30509. Although the FE role requires Message Queuing Service, it doesn’t require Message Queuing Directory Integration. However, the Archiving agent does require this. The fix is to simply install the additional feature on the FE servers that are targets for Archiving.

 
Others
 
- Microsoft Lync Server 2013 Monitoring and Archiving : Archiving Configuration (part 1) - Creating Site and User Policies
- Microsoft Lync Server 2013 Monitoring and Archiving : Monitoring Components Installation (part 2) - Monitoring Administration
- Microsoft Lync Server 2013 Monitoring and Archiving : Monitoring Components Installation (part 1) - Monitoring Configuration
- Sharepoint 2013 : Packaging and distributing apps (part 5) - Trapping app lifecycle events
- Sharepoint 2013 : Packaging and distributing apps (part 4) - Installing apps at tenancy scope
- Sharepoint 2013 : Packaging and distributing apps (part 3) - Publishing apps
- Sharepoint 2013 : Packaging and distributing apps (part 2) - Packaging apps - Packaging host web features, Packaging for autohosted apps
- Sharepoint 2013 : Packaging and distributing apps (part 1) - Packaging apps - Understanding the app web solution package
- EXchange Server 2013 : Using and managing Exchange services (part 3) - Sample configuration for WinRM
- EXchange Server 2013 : Using and managing Exchange services (part 2) - Configuring service startup,Configuring service recovery
 
Youtube channel
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
programming4us programming4us
 
Popular tags
 
Video Tutorail Microsoft Access Microsoft Excel Microsoft OneNote Microsoft PowerPoint Microsoft Project Microsoft Visio Microsoft Word Active Directory Biztalk Exchange Server Microsoft LynC Server Microsoft Dynamic Sharepoint Sql Server Windows Server 2008 Windows Server 2012 Windows 7 Windows 8 Adobe Indesign Adobe Flash Professional Dreamweaver Adobe Illustrator Adobe After Effects Adobe Photoshop Adobe Fireworks Adobe Flash Catalyst Corel Painter X CorelDRAW X5 CorelDraw 10 QuarkXPress 8 windows Phone 7 windows Phone 8 BlackBerry Android Ipad Iphone iOS