New update options for Office 365 ProPlus using System Center Configuration Manager!!!


IT admins can now manage Office 365 client updates—including those for Office 365 ProPlus, Visio Pro for Office 365 and Project Pro for Office 365—directly via the System Center Configuration Manager’s built-in software updates workflow engine.

One of the top feature requests we hear from IT admins is to use System Center Configuration Manager to update Office. To accomplish this, we streamlined the ongoing update management for Office 365 clients by integrating with Configuration Manager and the Microsoft Update service to allow a consistent process to discover, view, deploy and track available software updates—similar to how you manage other apps in your organization.

Each time an Office update is published, information is automatically sent to the Microsoft Update service. Configuration Manager automatically receives notifications when updates are available and validates whether your PCs require the update. IT admins can use the existing workflow engine to download and distribute the update.

The new capability is available in the upcoming release of Configuration Manager update 1602.



Purchase this Product



Microsoft Exchange Online Plan & Features !!!



Exchange Online Plan 1


Exchange Online Plan 2


Exchange Online Kiosk


User maximum






Large mailboxes

Each user gets 50 GB of mailbox storage and can send messages up to 150 MB in size.


 Yes  Yes


        2 GB inbox per user

Outlook support

Users can connect supported versions of Outlook to Exchange Online, so they can use the rich client application they already know.


 Yes  Yes  Yes

Web-based access

For web-client access, Outlook Web App provides a premium browser-based experience that matches the look and feel of the full Outlook client.


 Yes  Yes  Yes

Outlook app

Get more done on your phone and tablet with the Outlook app for iOS and Android—and soon in Windows 10.


 Yes  Yes  Yes

Inbox management

Stay focused on the most important messages with Clutter, which applies machine learning to clean up your inbox and set up rules that match the way you work.


 Yes  Yes  

Document collaboration

Save attachments directly to OneDrive for Business with just one click and share the link to the file—right from Outlook Web App


 Yes  Yes  


Simplify collaboration with Office 365 Groups, which lets teams self-organize, work together across tools and devices, and build upon the expertise of others.


 Yes  Yes  

Shared calendar and contacts

Compare calendars to schedule meetings and access collaboration features, including shared calendars, groups, the global address list, external contacts, tasks, conference rooms, and delegation capabilities.


 Yes  Yes  

Third-party apps for Outlook

Spend less time switching between apps with an extension model that allows third-party web applications easy plug-in access for both Outlook and Outlook Web App.


 Yes  Yes  


Every mailbox is protected with premier anti-malware and anti-spam protection via Exchange Online Protection.


 Yes  Yes


Premium anti-malware protection and anti-spam filtering

In-Place Archive

Keep your inbox clean by automatically moving old messages to an In-Place Archive


 Yes  Yes  

In-Place Hold

Use In-Place Hold to preserve deleted and edited mailbox items from users’ primary mailboxes and In-Place Archives.



Unlimited storage

Take advantage of unlimited storage (50 GB of storage in the user’s primary mailbox, plus unlimited storage in the user’s In-Place Archive)



Hosted voicemail

Take advantage of hosted Unified Messaging services that provide call answering, a dial-in user interface, and company automated attendant capabilities.



Data loss prevention (DLP)

Control sensitive business data with built-in DLP policies based on regulatory standards such as PII and PCI, which help to identify, monitor, and protect sensitive data through deep content analysis.



Built-in mobile device management now generally available for Office 365 commercial plans!!!

we are pleased to offer the general availability of MDM capabilities for Office 365. With MDM for Office 365, you can manage access to Office 365 data across a diverse range of phones and tablets, including iOS, Android and Windows Phone devices. And what makes today’s news even better: the built-in MDM features are included at no additional cost in all Office 365 commercial plans, including Business, Enterprise, EDU and Government plans.


These new capabilities help you better manage and protect access to Office 365 data while enabling people to be mobile and productive from anywhere.

 Office 365’s MDM capabilities work to keep your data safe in three ways:

  • Conditional Access—You can set up security policies on devices that connect to Office 365 to ensure that Office 365 corporate email and documents can be accessed only on phones and tablets that are managed by your company and are compliant. Behind the scenes, Office 365 leverages Microsoft Intune and the Microsoft Azure Active Directory to deliver this capability. The Conditional Access policies apply to Office applications such as Word, Excel, PowerPoint and other business applications—making management easier for admins while ensuring users can securely work with their preferred productivity applications.


  • Device management—You can set and manage security policies such as device-level pin lock and jailbreak detection to help prevent unauthorized users from accessing corporate email and data on a device when it is lost or stolen. Additional settings and rich reporting are also available within the Office 365 admin center so you can gain critical insights about devices accessing your corporate data.


  • Selective wipe—You can easily remove Office 365 company data from an employee’s device while leaving their personal data in place. This is an increasingly important requirement as more businesses adopt a “bring your own device” (BYOD) approach to phones and tablets.

Configure message size limits for a mailbox!!!

Configure message size limits for a mailbox

You can control the size of messages that recipients can send and receive. If a user sends a message larger than the specified size, the message will be returned to the user with a descriptive error message. If the user receives a message larger than the specified size, the message will be returned to the sender with a descriptive error message.

To configure message size limits for a mailbox

Do one of the following:

  1. Sign in to Office 365 with your work or school account.

Tip   You need to sign in as either a Global admin or a Billing admin.

  1. Select the app launcher icon in the upper-left and choose Admin.
  2. Select exchange Option
  3. In the EAC ( Exchange Admin Center), navigate to RecipientsMailboxes.
  4. In the list of user mailboxes, click the mailbox that you want to change the message size limits for,
  5. Then click Edit.

7 .On the mailbox properties page, click Mailbox Features.

8 .Under Message Size Restrictions, click View details to view and change the following message size limits:

  • Sent messages to specify a maximum size for messages sent by this user, select the Maximum message size (KB) check box and type a value in the box. The message size must be between 0 and 2,097,151 KB. If the user sends a message larger than the specified size, the message will be returned to the user with a descriptive error message.
  • Received messages to specify a maximum size for messages received by this user, select the Maximum message size (KB) check box and type a value in the box. The message size must be between 0 and 2,097,151 KB. If the user receives a message larger than the specified size, the message will be returned to the sender with a descriptive error message.

9 .Click OK, and then click Save to save your changes.



Enable / Disable Skype for Business client !!!

Enable / Disable Skype for Business client

In my previous post, I shed some light on new Skype for Business Client (formally known as Lync client ) look and options available to end user. This post will focus on the steps require to enable or disable Skype for Business Client for end user. Being an administrator you can control whether a user can use Skype for Business or not. With that being said, let’s get started with this post.

Before we start, i assume that you currently have Lync 2013 deployed in your infrastructure and the steps mentioned below are tested on Lync 2013 server edition. Here are the steps to Enable or Disable Skype for Business client in Lync 2013 server.

Mostly Microsoft product updates are pushed to end users from Windows Updates and Microsoft prefer to push new product updates from Windows Updates too. You can either manage Windows Updates centrally using WSUS and allow which updates can be pushed to end users machine and if you don’t have any centralized Patching system then you probably come up with this scenario where few users update their Lync client to Skype for Business and few using Lync. Once lync client is updated to Skype for Business client users will get the following pop up.

Restart Skype For Business


Step-by-Step Guide to Migrate from Exchange Server 2007 to Exchange Server 2013!!


Step-by-Step Guide to Migrate from Exchange Server 2007 to Exchange Server 2013

Before planning your Exchange Server 2013 migration ensure you are familiar with all its features like virtualization, retention, modern public folders, managed availability, transport, unified messaging, EWS, Outlook Web App etc.

As Exchange is critical to the communication network, it is important to do a smooth Exchange migration which causes minimum or zero interruption to the organizational communication. In this blog, we will see how to migrate all users and services from Exchange 2007 to Exchange 2013 and finally decommission the old Exchange 2007.

The high-level steps that we will take to devise the migration are:

  1. Deploying Exchange 2013 as new environment
  2. Configuring Digital Certificates for the new Exchange
  3. Configuring Name Space and Virtual Directories
  4. Offline Address Book (OAB) configuration
  5. Mail Flow Configurations
  6. Moving Client Access to Exchange 2013
  7. Moving Mailboxes to Exchange 2013
  8. Moving Public Folders to Exchange 2013 and decommissioning old Exchange Server

1. Deploying Exchange 2013 as new environment

Active Directory Preparation

When we install Exchange Server it needs to store User mailboxes’ and Exchange Server’s configuration information in the organization. So it is important that Active Directory is duly prepared before you install Exchange 2013 in the organization. Following things need to be done before you deploy Exchange Server 2013 in the environment: a> Extend Active Directory Schema b> Prepare Active Directory and 3> Prepare Active Directory Domains. To ensure that AD preparation is done correctly, verify that the rangeUpper property on ms-Exch-Schema-Version-Pt is set to the correct value. After this force AD replication.

Exchange Server 2013 Installation

When you are ready for running Exchange Server setup ensure that server is fully updated with latest patches. To install Windows Features using PowerShell Run Windows PowerShell as Administrator and paste the following command:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

After the installation is complete restart your server. And after the reboot, download and install Microsoft Unified Communications Managed API 4.0. Core Runtime 64-bit, Microsoft Office 2010 Filter Packs 64 bit, Microsoft Office 2010 Filter Packs SP1 64 bit.

2. Configuring Digital Certificates

You should be using as few certificates and host names as possible for cost control since certificate providers charge a fee based on number of host names you add to your certificate. By default, Exchange comes with self-signed certificates, we will replace this certificates with the ones relevant to our case.

  • FQDN for most connections to Exchange including Microsoft Outlook, Outlook Web App, Outlook Anywhere, the Offline Address Book, Exchange Web Services, POP3, IMAP4, SMTP, Exchange Control Panel, and ActiveSync.
  • FQDN used by clients that support Auto discover, including Microsoft Office Outlook 2007 and later versions, Exchange ActiveSync and Exchange Web Services clients.
  • FQDN used by all external and internal clients for old server i.e. Exchange Server 2007.

Next we will create certificate request, for this open EMS and run the New-ExchangeCertificate cmdlet command:

Once the certificate is created, get it signed by the appropriate certification authority (CA) and use the Import-ExchangeCertificate to import the certificate.

Then Exchange Server 2013 need to be configured to use the certificates using the Enable-ExchangeCertificate command.

Please note that Enable-ExchangeCertificate cmdlet cannot be used to enable a wildcard certificate for POP and IMAP services, also it cannot be used to enable a certificate for federation.

Use private key to export the certificate and import it on Exchange 2007 CAS servers using the same steps.

3. Configuring Name Space and Virtual Directories for Exchange Server

Follow the given steps to configure Exchange Server 2013 virtual directories using EMS:

Exchange Control Panel

To configure Exchange Control Panel (ECP) virtual directories properties, use Set-EcpVirtualDirectory cmdlet.

Outlook Web App

To configure Outlook Web App virtual directories use Set-OwaVirtualDirectory cmdlet.

Offline Address Book

To configure offline address book virtual directory use Set-OABVirtualDirectory cmdlet.


Use Set-ActiveSyncVirtualDirectory cmdlet to configure the Microsoft Exchange ActiveSync settings on specified virtual directory.

Web Services

To modify Exchange Web Services virtual directory use Set-WebServicesVirtualDirectory cmdlet on the server running Exchange Server 2013.


To set properties on specified Client Access Server objects use Set-ClientAccessServer cmdlet.

Outlook Anywhere

To set properties on a computer running Microsoft Exchange Server 2013 enabled for Microsoft Outlook Anywhere use Set-OutlookAnywhere cmdlet.

4. Offline Address Book (OAB) configuration

In Exchange Server 2013, OABGen (Offline Address Book Generation) service which runs on Mailbox server generates offline address book.

Change the default OAB on Exchange 2013 database using Get-MailboxDatabase and Set-MailboxDatabase

5. Mail Flow Configurations on Exchange 2013

Receive Connector

To create this connector use the New-ReceiveConnector cmdlet.

Send Connector

Now add the new Exchange Server to the existing send connector by the Set-SendConnector cmdlet.

Transport Rules:

Transport rules cannot be migrated from Exchange Server 2007 to 2013. So you need to do the following to get Transport rules in Exchange Server 2013.

  1. Use Export-TransportRuleCollection cmdlet to export all transport rules from Exchange Server 2007.
  2. Copy the exported Transport Rule file to the system which has Exchange Server 2013 installed on it.
  3. Use Import-TransportRuleCollection cmdlet to import the Transport Rules from the file to the Exchange Server 2013.

6. Moving Client Access to Exchange 2013

In the Exchange 2007 management shell you need to run the following commands.

Outlook Web App

Use Set-OwaVirtualDirectory cmdlet to modify properties of MS Outlook Web App virtual directories.

Offline Address Book

Use Set-OABVirtualDirectory cmdlet to configure offline address book virtual directory.


Use Set-ActiveSyncVirtualDirectory cmdlet to configure the Microsoft Exchange ActiveSync settings on specified virtual directory.

Web Services

To modify Exchange Web Services virtual directory use Set-WebServicesVirtual Directory cmdlet on the server running Exchange Server 2007.

Unified Messaging

To modify an existing Exchange Unified Messaging virtual directory, run the Set-UMVirtualDirectory cmdlet.

Outlook Anywhere

To set Microsoft Outlook Anywhere properties on Microsoft Exchange Server 2007 use Set-OutlookAnywhere cmdlet.

Threat Management Gateway Rules

Now create and update your TMG publish rules.

Next update your publish rules for Exchange 2007 to accept connections for Legacy name space. And then publish Exchange Server 2013 using TMG.

Domain Name System Configurations:

In the Internal DNS, point and to Exchange 2013 server. And in new record points to Exchange 2007 Server. In the Public DNS, point and to TMG listener and for point new record to TMG Listener.

7. Moving Mailboxes to Exchange 2013

Next you can use New-MoveRequest cmdlet to start mailbox or personal archive migration. To check mailbox readiness before starting to move mailboxes you can use WhatIf parameter. You can also create batch move if you want.

8. Moving Public Folders to Exchange 2013 and decommissioning old Exchange

To start with, take snapshot of the current Public Folders in Exchange Server 2007 EMS using the following commands: Get-PublicFolder, Get-PublicFolderStatistics and Get-PublicFolderClientPermission.

Next create CSV files using scripts (Export-PublicFolderStatistics.ps1 and PublicFolderToMailboxMapGenerator.ps1). In this way you will get the CSV file mapping PFs to new PF mailboxes.

In the Exchange 2013, create PF mailboxes using New-Mailbox –PublicFolder cmdlet. Migrate PF content using New-PublicFolderMigrationRequest cmdlet.

Before starting the final migration, lock down Exchange Server 2007 using the following cmdlets.

Set-OrganizationConfig –PublicFoldersLockedForMigration $True (In Exchange 2007)

Set-PublicFolderMigrationRequest <name> -PreventCompletion $False (In Exchange 2013)

Resume-PublicFolderMigrationRequest <name> (In Exchange 2013)

Test new public folders to ensure everything is alright. Then us the following cmdlet to unlock the PF migration.

Set-OrganizationConfig -PublicFolderMigrationComplete:$true

Decommissioning Exchange Server 2007

Open Exchange Server 2007 management shell and run the following command to remove mailbox databases.

Get-MailboxDatabase | Remove-MailboxDatabase

Remove the public database and in the cmd run the following command to uninstall Exchange: /mode:uninstall

Thus we complete the entire Exchange Server 2007 to 2013 migration process.

For Additional Support Contact :


Using Outlook Web App (OWA) offline !!!

Using Outlook Web App (OWA) offline

Offline access lets you use Outlook Web App on your laptop or desktop computer when you’re not connected to the Internet. After you’ve enabled offline access, Outlook Web App will work in an offline mode as needed depending on your network connection. When you’re online, Outlook Web App will automatically update the offline information.

The last few days of messages. Supported folders include Inbox, Drafts, and any folders viewed within the last few days, up to 20 folders

What can I do when I’m offline?

Most tasks that you can do online are available when you’re offline. Tasks you can do while offline include but aren’t limited to:

  • Reading and responding to messages.
  • Sending new messages.
  • Viewing and editing your calendar.
  • Responding to meeting requests.
  • Viewing and editing your contacts.


How do I turn offline access on or off?

  1. To turn Outlook Web App offline access on or off, select one of the following, depending on the options you see:
    • Settings > Offline settings


  • Settings > Options > General > Offline Settings
  1. Select or clear the Turn on offline access check box.
  2. Select OK (or Save).

When you turn on offline access in some browsers, you may see a message warning you that the website is requesting space on your disk. For the best offline experience, accept the request for space.