An IT specialist’s work time can now be monitored with SkypeTime

An easy, flexible and transparent way to tackle the problem of time and attendance management at IT companies.

Like any other company, IT companies providing high tech services – whether software development, IT outsourcing, or remote infrastructure support – need tools to maintain adequate work discipline.

One method traditionally used is a time-and-attendance management system, which provides the employer with detailed information about who was present at their work places and when, which software was open on employees’ office computers, and employee’s web requests, including the ability to use a webcam to monitor employees’ physical presence at their computers.

This method is moderately effectively for regular office workers, but it negatively affects the performance of expert teams. There are several reasons for this.

First, a high-tech company’s employees (let’s call them “experts”) do not only work at their desk and during standard work hours. They might need to do some work at night, participate in late meetings due to time zone differences with customers, or simply reach peak performance between 11pm and 4am. Accordingly, it is the actual work performed on the office computer (sometimes remotely from home) that must be estimated, not the time spent in close proximity to it.

Second, experts are usually freedom-loving individuals. Just the thought that some software program is monitoring their activities is demoralizing to innovative teams and, as a result, has a negative effect on their performance.

Third, experts have professional ambitions. The existence of software that discourages work may induce them to fight this software during work hours and at their workplace. This is hardly the effect you desire.
In our view, the best way to account for and monitor employee time is a program that meets several criteria:

  • It should be invisible to employees. Ideally, it should not be detected on employees’ computers.
  • The program should allow estimating the time employees spend accessing their work computer, based not only on when they are physically present but also when they are working remotely. Thus, the system should be able to identify the type of employee presence.
  • The program should support great flexibility in adjusting employees’ schedules. For example, it should allow for rules such as “If not present at work at 9:15 – send notice of absence without leave” or “Allow coming late no more than twice a week,” or “When working with a customer at night, allow time-off until noon or work from home.”
  • The program should ensure the required level of monitoring without encroaching on employees’ privacy (for instance, Internet traffic).
  • The program should not require significant investment in additional servers and system software.

Servilon has developed such a program and we now offer it to you. It is called SkypeTime – a time and attendance management system based on Microsoft Skype for Business.

SkypeTime is an ideal solution for IT companies where:

  • Microsoft Skype for Business is used for corporate communication;
  • Employees’ work is associated with resource intensive software and/or access to internal corporate resources, and therefore requires physical or remote access to an office computer.
  • The work day is not strictly measured by physical presence in an office but rather by the number of hours worked, and can be coordinated with senior management to allow for individual rules and exceptions.

SkypeTime discreetly monitors employees’ work without making them uncomfortable. It provides the flexibility needed to take into account the specific characteristics of the work schedule.

How SkypeTime Works?

SkypeTime collects employees’ work statistics based on changes to their Skype status (online, offline, inactive, away, in call, in call – mobile) and based on information about the device from which the status is obtained, which are recorded by the Skype for Business server. In addition, the system receives information from RDGs (Remote Desktop Gateways), and you can see whether an employee accessed a computer locally or remotely (from home or another location).

SkypeTime uses the information received to build accurate work schedule reports that include the following:

  • Start of work day;
  • Lunch breaks;
  • End of work day;
  • Total number of hours worked versus the expected number of hours;
  • Work performed from home.

All components are installed on SkypeTime servers, and Skype4B clients provide the information about presence. In other words, no additional software needs to be installed employees’ computers. Thus, the monitoring system cannot be removed, blocked, or otherwise affected. Moreover, the system does not interfere with employees’ work, so they cannot have a negative reaction to it.

Close integration with Active Directory and Skype for Business minimizes the effort required to configure SkypeTime – users are added and removed automatically after the integration is complete.


SkypeTime features for monitoring and recording work time

Reports on employees’ work statistics

SkypeTime generates the following reports on employee work:

Average and maximum tardiness for a period;

  • Absence history with an indication of whether the manager’s permission had been given;
  • Periods of overtime;
  • Employees’ ranked by work discipline violations for a period;
  • Summary and detailed reports on daily changes in employees’ statuses;
  • Statistics on employees’ work from home;
  • Departmental summary of the work day (latecomers, absent, current requests, work time for the previous day);
  • Weekly employee summary.

Authorized managers can receive these reports both by accessing the program’s interface and through a regular email.

Work calendar management

SkypeTime allows users to set up an employees work calendar and indicate standard work hours for a specific department or employee. Time zones can be accounted for when setting up your work calendar, thus supporting the work of geographically distributed teams.

The system also lets you keep logs of holiday calendars, create and manage employee requests for time off, and change work schedules.

  • Employees within the same department can plan their holidays easily and avoid overlap by using a shared holiday calendar. This helps prevent key personnel on a project from taking holiday leave at the same time.


Both managers and employees access the system via the Dashboard – an easy-to-use interface that provides access to the following personal and group settings:

  • Create, send and approve requests for holiday, absence with leave, and other personal situations;
  • Manager or employee control over employees’ work schedules;
  • Monitor unused holidays and sick leave days;
  • Manage individual, group and system settings.

Prices and terms for installation

SkypeTime licenses start at $10 for one registered user and depend on the number of user licenses and additional services purchased. Discounts are available, if:

  • You are an IT company.
  • You order both the application and services to deploy it.
  • You purchase Microsoft Skype for Business or any other software license from us.
  • You are our client.
  • You are not our client, but you order other services from us along with SkypeTime.

Your purchase of a SkypeTime license gives you one year of free technical support and an annual subscription to all program updates, including new versions. Additionally, for one year from your purchase of SkypeTime you will receive a discount on our other services. Furthermore, when you buy more than 50 licenses you will receive a 50% discount on deployment of Skype for Business.

Contact us for a custom quote for SkypeTime with all applicable discounts.

SkypeTime features

Manager interface


The Manager Interface is a side menu containing all of the application’s functionality, as well as up-to-date information on employees in four separate sections (Latecomers, Absent, Work Time, and Requests). Detailed information is available by clicking on each section’s name.

Employee Dashboard


Employees can work more productively using web data from the Dashboard, which summarizes the information for a selected period of time, e.g. the beginning and end of a work day, planned work time per day / week, overtime, tardiness, and much more.

Employee Requests


Editing employee requests is a key feature in time and attendance management systems. Managers can approve, deny or edit employee requests.

Employee report for a specified time period


Employee summary report

To make it easier to read, the “Report by Period” generated as a table and Gantt chart. This makes it possible to interpret the tabular data in the chart.


This report is a Gantt chart in the form of a table showing how much time the employee spent at work and how much he or she was offline during the working day. More information is available in the “Detailed Report” tab. You can see the device the employee was working from, as well as his or her status in the system and the duration of that status.

Report by holidays


The holiday report contains a list of all employees and indicates the number of used and remaining holiday days during a year/period. The Gantt chart displays employee requests as a horizontal bar showing the number of days. By clicking on the bar, you can edit the request. By clicking on the employee’s name in the table, the request search page opens for the selected employee.

More articles about Skype for Business

bitlocker windows

How to enable BITLOCKER on EXCHANGE servers

The Exchange Architecture recommends enabling BitLocker on fixed data drives that store Exchange database files for Exchange Server 2013 and Exchange Server 2016.

What is BitLocker?

BitLocker is the built-in Microsoft Windows feature for full disk encryption that offers enhanced protection against data theft on stolen or lost computers or hard disks.

BitLocker first appeared in Windows Vista and Windows Server 2008. Since then, BitLocker functionality has expanded and now includes encrypting data volumes, encrypting only used disk space, and provisioning flexibility.

Windows BitLocker enables data protection on volumes with 128-bit (default) and 256-bit key using AES (Advanced Encryption Standard) encryption algorithm.

How to deploy BitLocker?

BitLocker can be deployed on Exchange servers using the following methods.

  1. Encrypting the operating system volume, as well as, the Exchange data volumes either via TPM (recommended) or with the help of network unlock, the Data Recovery Agent and PKI infrastructure.
  2. Only encrypting the Exchange data volumes.

To use BitLocker in a FIPS-compliant manner, note that:

In case that you are not using Windows Server 2012 R2 or later as the base OS, then you cannot utilize recovery passwords for BitLocker. For more details, see What’s New in BitLocker and KB 947249.

Volume Encryption Method

There are two approaches for volume encryption:

  1. Encrypting the entire volume. This option works best when you need to encrypt volumes which already comprise existing messaging data. With a 3TB disk, it will take more than 8 hours to encrypt the disk completely.
  2. Encrypting the used space only. This method works for new deployments or for new disks without existing data.

Prior to beginning the encryption of an entire volume, make sure to set the servers in maintenance mode to prevent impact to end users. Performance can significantly deteriorate (~90% CPU usage) and free OS volume space will be limited (less than ~2GB) while the volume is being encrypted. Remember to deploy BitLocker on one DAG server at a time to ensure availability.

OS Volume and Exchange Data Volume Encryption Scenario

BitLocker provides the most protection when used with a TPM. The TPM is a hardware component installed in the server and we recommend a TPM 2.0 chip. It works with BitLocker to help protect user data and to ensure that a server has not been tampered with while the system was offline.

Specifically, BitLocker can use a TPM to verify the integrity of early boot components and boot configuration data. This helps ensure that BitLocker makes the encrypted drive accessible only if those components have not been tampered with and the encrypted drive is located in the original server.

BitLocker helps ensure the integrity of the startup process by taking the following actions:

Checks that the early boot file integrity has been maintained, and helps ensure that there has been no malicious modification of those files, such as with boot sector viruses or rootkits.

Enhances protection to mitigate offline software-based attacks. Any alternative software that might start the system does not have access to the decryption keys for the Windows operating system drive.

Locks the system when it is tampered with. If any monitored files have been modified, the system does not start. This alerts the administrator to the tampering, because the system fails to start as usual. In the event that system lockout occurs, follow the BitLocker recovery process which includes unlocking the system with a password or a USB key.

Important: A TPM can only be used in a physical server deployment. Virtualized servers are not capable of using a TPM. If you encrypt the guest operating system volume, a password or USB key must be used to allow the guest operating system to boot.

Setting up the Environment

The steps below assume the Exchange Server operating system is Windows Server 2012 R2 or later.

Important: When enabling BitLocker on existing Exchange servers, it is important to place the servers in maintenance mode to prevent the encryption process from affecting the end user experience.

  1. Create an Organizational Unit to contain the Exchange servers, if one does not already exist. Open PowerShell with the appropriate Active Directory permissions.
New-ADOrganizationalUnit "Exchange Servers" -path "dc=contoso,dc=com"

$ExchangeOU = Get-ADOrganizationalUnit -Filter ‘Name -like "Exchange Servers"’

Get-ADComputer "Exchange Server" | Move-ADObject -TargetPath $ExchangeOU.DistinguishedName

2. Create group policy object and link it to the Exchange Servers OU.

Import-Module grouppolicy #RSAT должен быть установлен

New-GPO -Name "Exchange Server BitLocker Policy" -Domain

New-GPLink -Name "Exchange Server BitLocker Policy" -Enforced "yes" -Target $ExchangeOU.DistinguishedName

3. Install the BitLocker module on the Exchange servers.

  • Open PowerShell with local administrative privileges.
  • ExecuteInstall-WindowsFeature BitLocker -Restart.
  • Reboot the server.

4. Enable TPM on the Exchange servers.

  • Refer to your hardware vendor’s BIOS manual for details on how to enable/activate the TPM.
  • Verify the TPM state by using the Trusted Platform Module Management tool (msc).

5. Allow TPM Recovery Information to be stored in Active Directory.

  • Open the Exchange Management Shell with an account that has the necessary permissions in Active Directory to apply access control entries.
  • Execute the following.

Add-ADPermission $ExchangeOU.DistinguishedName -User "NT AUTHORITY\SELF" -AccessRights ReadProperty,WriteProperty -Properties msTPM-OwnerInformation,msTPM-TpmInformationForComputer -InheritedObjectType Computer -InheritanceType Descendents

6. Configure the Bitlocker GPO settings.

  • Open the Group Policy Management Console (gpmc.msc).
  • Navigate the hierarchy to the Exchange Servers OU.
  • Right-click the Exchange Server BitLocker Policy and select Edit.
  • Open Computer Configuration, open Policies, open Administrative Templates, open Windows Components, and open BitLocker Drive Encryption.

In the right pane, double-click Choose drive encryption method and cipher strength. Select the Enabled option. If you want to use AES 256-bit encryption, select it and click OK.

Choose drive encryption method and cipher strength

  • Open Computer Configuration, open Policies, open Administrative Templates, open Windows Components, open BitLocker Drive Encryption, and finally, open Operating System Drives.
  • In the right pane, double-click Require additional authentication at startup. Select the Enabled option. If you want to disable or change any of the authentication methods, do so and click OK.


  • In the right pane, double-clickChoose how BitLocker-protected fixed drives can be recovered. Select the Enabled  Select the Do not enable BitLocker until recovery information is stored to AD DS for fixed data drives option. Click OK.

Choose how BitLocker-protected fixed drives can be recovered

  • In the right pane, double-click Enforce drive encryption type on fixed drives. Select the Enabled option. Select the Used Space Only encryption option for the encryption type. Click OK.

Used Space Only encryption

  • Open Computer Configuration, open Policies, open Administrative Templates, open Windows Components, open BitLocker Drive Encryption, and finally, open Fixed Data Drives.
  • In the right pane, double-click Choose how BitLocker-protected fixed drives can be recovered. Select the Enabled option. Select the Do not enable BitLocker until recovery information is stored to AD DS for fixed data drives option. Click OK.

Do not enable BitLocker until recovery information is stored to AD DS for fixed data drives

  • In the right pane, double-click Enforce drive encryption type on fixed drives. Select the Enabledoption. Select the Used Space Only encryption option for the encryption type. Click OK.

Used Space Only encryption option

  • Open Computer Configuration, open Policies, open Administrative Templates, open System, and open Trusted Platform Module Services.
  • In the right pane, double-click Turn on TPM backup to Active Directory Domain Services. Select the Enabled option. Click OK.

Turn on TPM backup to Active Directory Domain Services

  • Ensure the group policy is applied to the Exchange servers.

$Servers = Get-AdComputer -SearchBase $ExchangeOU.DistinguishedName -Filter

Foreach ($Server in $Servers) {invoke-gpupdate -Computer $Servers.Name -Force -Target Computer}

  • Enable OS encryption.
  • Create a recovery key: manage-bde -protectors -add -RecoveryPassword C:
  • Execute the following against the operating system drive: manage-bde -on C: –usedspaceonly
  • Enable data volume encryption (C:\ExchangeVolumes\ExVol1 defines the mount point for an Exchange data volume, replace as appropriate).

Create a recovery key: manage-bde -protectors -add -RecoveryPassword “C:\ExchangeVolumes\ExVol1”

Execute the following for each Exchange database volume: manage-bde -on “C:\ExchangeVolumes\ExVol1” –usedspaceonly

Execute the following for each Exchange database volume to enable automatic unlock: Enable-BitLockerAutoUnlock –MountPoint “C:\ExchangeVolumes\ExVol1”

Note: Bad disk sectors can result in BitLocker volume encryption failure. For more information, please see Event ID 24588.

In the situation where a TPM cannot be used (e.g., the server does not have a TPM, or it is virtualized), encrypting the OS volume requires the use of a password or USB key to allow the operating system to boot. As that can be detrimental for a service like Exchange, you could choose not to encrypt the OS volume. Instead, you only encrypt the fixed data volumes. Since the OS volume is not encrypted, the operating system cannot automatically unlock the encrypted volumes on boot. Therefore, one of two things must happen:

  1. An administrator manually enters the recovery key and unlocks each drive after OS boot.
  2. A scheduled task is invoked to unlock the encrypted volumes during OS boot.

The following steps outline how to setup the scheduled task and assume the Exchange Server operating system is Windows Server 2012 R2 or later.

  • Create an Organizational Unit to contain the Exchange servers, if one does not already exist.

New-ADOrganizationalUnit "Exchange Servers" -path "dc=contoso,dc=com"

$ExchangeOU = Get-ADOrganizationalUnit "Exchange Servers"

Get-ADComputer "Exchange Server" | Move-ADObject -TargetPath  ExchangeOU.DistinguishedName

  • Create group policy object and link it to the Exchange Servers OU.

Import-Module grouppolicy #RSAT должен быть установлен

New-GPO -Name "Exchange Server BitLocker Policy" -Domain

New-GPLink -Name "Exchange Server BitLocker Policy" -Enforced "yes" -Target $ExchangeOU.DistinguishedName

  • Create BitLocker scheduled task service account (_bitlockersvc).
  • Create security group for BitLocker management, placing the security group in a protected container.

New-ADGroup -name "Exchange BitLocker Management" -groupscope Universal -path "cn=users,dc=coe,dc=local"

Add-ADGroupMember "Exchange BitLocker Management" -members "_bitlockersvc", "Organization Management"

  • Install the BitLocker module on the Exchange servers.

Install-WindowsFeature BitLocker

  • Reboot the server.
  • Add BitLocker security management group to local administrators group on the Exchange servers.
  • Grant the BitLocker security management group permissions to access the msFVE-RecoveryPassword AD object. This allows the accounts to access the recovery password.

$ExchangeOU = Get-OrganizationalUnit "Exchange Servers"

DSACLS $ExchangeOu.DistinguishedName /I:T /G "contoso\Exchange BitLocker Management:CA;msFVE-RecoveryPassword"

  • Configure the BitLocker GPO settings.
  • Ensure the group policy is applied to the Exchange servers.

$Servers = Get-AdComputer -SearchBase $ExchangeOU.DistinguishedName -Filter

Foreach ($Server in $Servers) {invoke-gpupdate -Computer $Servers.Name -Force -Target Computer}

Create the script that unlocks the volumes when the operating system boots.

Save the below file to your script directory (e.g., c:\bitlocker).


$computer = Get-ADComputer $env:computername $RecoveryInformations = get-ADObject -ldapfilter "(msFVE-Recoverypassword=*)" -Searchbase $computer.distinguishedname -properties *
$vols = gwmi win32_encryptablevolume -Namespace "Root\CIMV2\Security\MicrosoftVolumeEncryption"
$lockedvols = $vols | ? {$_.GetLockStatus().LockStatus -eq 1}
$vols[0].GetKeyProtectors().VolumeKeyProtectorID foreach($lockedvol in $lockedvols)
$RecoveryInformations | % {$lockedvol.UnlockWithNumericalPassword($_."msFVE-RecoveryPassword")}

  • Create the scheduled task to run at system start and unlock the volumes, replacing the bold items.

Save the below file to your script directory.

  • Executeschtasks /create /s $env:computername /ru contoso\_svcexbitlocker /rp /XML c:\Bitlocker\UnlockDrivesAtStart.xml /TN UnlockDrivesAtStart.

System Changes

It’s important to keep in mind that any of the following system changes can cause an integrity check failure and prevent the TPM from releasing the BitLocker key to decrypt the protected volumes:

  • Moving the BitLocker-protected drive into a new computer.
  • Installing a new motherboard with a new TPM.
  • Turning off, disabling, or clearing the TPM.
  • Changing any boot configuration settings.
  • Changing the BIOS, UEFI firmware, master boot record, boot sector, boot manager, option ROM, or other early boot components or boot configuration data.
  • Applying BIOS/UEFI firmware updates.

As part of your customary procedure, it’s best to suspend BitLocker encryption (via the Suspend-BitLocker cmdlet) before introducing any changes to the server. Additionally, make sure to test any hardware and software configuration changes in a lab setting (that has BitLocker enabled) before deploying in production.

Also, be sure to develop a standard operating procedure about how to recover in the event the BitLocker recovery must be performed. This will ensure that downtime is minimized. For more information, please see the BitLocker Recovery Guide.

Disk Maintenance Activities

During the server’s lifecycle, disks will die. As part of your standard operating procedures, you need to ensure that when a disk is replaced the new volume is formatted and encrypted via BitLocker.

In the event you are using AutoReseed to recover from failed disks, you have two options: format and encrypt the disks prior to usage, or encrypt after failure.

Format and encrypt the disks prior to usage

In this scenario, your standard operating procedure will be to prevent Disk Reclaimer from formatting hot spare disks. Instead, you will format and encrypt all hot spare disks prior to usage.

  1. Disable Disk Reclaimer on the DAG: Set-DatabaseAvailabilityGroup -AutoDagDiskReclaimerEnabled $false
  2. Format and encrypt all hot spares. Do not assign mount points or drive letters.
  3. As disks fail, AutoReseed will assign the hot spare volumes, replacing the failed volumes, and reseed the afflicted database copies.
  4. Schedule a maintenance window. Replace the failed disks. Format and encrypt.

Encrypt after failure

In this scenario, your standard operating procedure will be to allow Disk Reclaimer to format hot spare disks (default behavior). After the spare is formatted and databases are reseeded, you will encrypt the disk.

  1. As disks fail, AutoReseed allocates, remaps and formats a spare disk.
  2. AutoReseed initiates reseed operations.
  3. Using SCOM, or another operations management tool, you will monitor for events 1127 (initiated reseed of a database) and 826 (completed reseed of a database) that are located in the Microsoft-Exchange-HighAvailability/Seeding crimson channel.
  4. Schedule a maintenance outage for the affected server and encrypt the new volume.

We hope that this post will help understanding BitLocker encryption and configuring BitLocker for Exchange servers. As demonstrated, the best approach is to use a TPM for storing the recovery data and to allow the operating system to unlock volumes automatically during boot. If your servers do not have access to a TPM, you can consider encrypting only the data volumes and making a mechanism to ensure that the data volumes unlock at OS boot.

Exchange Architecture recommends enabling BitLocker on fixed data drives that store Exchange database files, both for Exchange Server 2013 and Exchange Server 2016.

More articles about BitLocker

Skype for bisuness


What is Skype for Business Server?

Until recently, “public” communication tools (such as Skype, Telegram, WhatsApp) and corporate communication tools (Lync, Sametime, etc.) were separated by a difficult-to-penetrate wall. Corporate messengers have well-developed security and auditing features. They integrate well with the corporate IT infrastructure and are mostly administered by the customer.  The main shortcoming of corporate messengers is their inability to include those outside of the “secure perimeter” (customers, partners, and subcontractors) in the conversation. The public tools allow anybody anywhere on the earth to easily communicate, but their utter lack of control over information streams creates serious problems for corporate IT and security departments. As a result, building a full-fledged communication environment, whether inside or outside of a company, amounts to a set of technological and organizational compromises and introduces significant risks.

Given this situation,  Skype for Business Server represents a new turn in the development of corporate communication tools, bringing together two previously incompatible worlds. On the one hand, this is the corporate version of Skype (previously better known as Microsoft Lync) with all of its advantages – secure channels, centralized management, Active Directory integration, Microsoft Office integration, and integration with the corporate phone system. On the other hand, it’s an opportunity to bring any Skype user – no matter where – into this “convenient” and fully manageable communication system. Moreover, thanks to Skype for Business Server’s complete integration, connecting these external users entails no risk and is fully manageable.

Why is a Microsoft Skype for Business Server Launch Service necessary?

When deciding whether to deploy new technology such as Skype for Business Server (Microsoft announced it in spring of 2015), IT- and business managers regularly have questions like these:

– Will Skype for Business Server work for us? Does the product include everything we need (functionality and security)? Will the product integrate well with our corporate environment (both organizationally and technologically)?

– Are the expenses for Skype for Business Server excessive? How much does it cost and how can we optimize our expenses?

To make this barrier easier to overcome, Microsoft invites customers to use its Microsoft Skype for Business Server Launch Service – an authorized service to deploy Microsoft Skype for Business Server 2015 Standard Edition on the Customer’s premises and provide practical training to the Customer’s IT specialists.

The Skype for Business Server 2015 Launch Service was created with the following objectives:

  • To improve the Customer’s effectiveness and reduce risks when deploying Skype for Business Server 2015;
  • To give the Customer’s IT specialists practical experience managing and supporting Skype for Business Server 2015;
  • To give the ability to assess the full functionality of Skype for Business Server 2015 and facilitate making a decision about the need for full deployment of the product.

The service is offered by official Microsoft partners and makes it possible, with minimum expenditures, to start trial (or regular) use of Skype for Business in just 3 days.

How is the service provided and what do I get out of it?

The service assumes the following schedule:

Day 1
  • Review Skype for Business Server 2015’s capabilities and architecture;
  • Design the server infrastructure;
  • System requirements;
  • Deploy server components.
Day 2
  • Review and deploy Skype for Business Server 2015’s client components;
  • Integrate Skype for Business Server 2015 client tools with the company’s work environment;
  • Integrate with Microsoft Office and Microsoft SharePoint;
  • Review and conduct a web conference.
Day 3
  • Review Skype for Business Server 2015’s capabilities when integrating with a traditional telephone system;
  • Set up the ability to work remotely and from mobile devices;
  • Review additional features regarding message archiving and system monitoring.

The service produces the following:

  • A server with Skype for Business Server 2015 Standard Edition installed, which provides the following capabilities:
    • Instant messaging;
    • Audio- and video calls and conference calls between users;
    • Schedule and conduct a web conference;
  • 5-10 workstations with deployed client software to interact with Skype for Business Server 2015;
  • Training for 5 of your company’s IT specialists. (We propose 2 groups of IT specialists: administrators and technical support specialists);
  • Your company’s specialists learn the theory and gain practical skills managing and supporting the solution, and also receive recommendations from an experienced consultant.

Skype for Business Server can be deployed both using permanent licenses (in which case a Microsoft partner will help you choose the best mix of licenses and subscriptions) as well as trial licenses from Microsoft, which are valid for up to 120 days – a period that is entirely sufficient for making a decision.

First, Servilon is an authorized Microsoft partner, which automatically guarantees the quality of our service.

Second, Servilon is a team of IT professionals, which will support you not only while providing the launch service but also during large-scale deployment of Skype for Business, and will resolve any problems that may arise in this process.

Third, Servilon offers this service at one of the lowest prices on the market – only 1400 Euro.

If our offer interests you, call us now and your Microsoft Skype for Business Server deployment project can begin as early as tomorrow.

More articles about Skype for Business