Migrate email to Office 365

Migrate email to Office 365 at PlexHostedWhen administrators first set up Office 365, many of them migrate email from existing systems. Your organization can migrate email to Office 365 from another system as well. The Office 365 administration user interface can be used for this purpose. You can also do this by using Windows PowerShell to migrate email. Your users are free to import their own email, contacts, and other mailbox information to their newly created Office 365 mailbox.

There are three types of email migrations that can be performed from an Exchange Server:

  • Migrate all mailboxes at once (cutover migration). With the help of cutover migration you can migrate the contents of user mailboxes from a source email system to Office 365 all at once.  A cutover migration can be performed by using the Setup wizard, or by starting from the Exchange admin center (EAC).
    Note: The Setup wizard is limited to migrating 150 mailboxes only. If cutover migration is started from the EAC, you can move up to 2000 mailboxes.
  • Migrate mailboxes in batches (staged migration). You can migrate the contents of user mailboxes from a source email system to Office 365 over time using a staged migration. This kind of migration is targeted at users who want to set a long-term mail coexistence with Exchange Online and their on-premises environments.
  • Migrate using an integrated Exchange Server and Office 365 environment (hybrid). This type of migration allows you to maintain both on-premises and online mailboxes for your organization and to gradually migrate users and email to Office 365. Hybrid migration is applicable for the following situations:
    – You have Exchange 2010 and more than 150-2000 mailboxes.
    – You have Exchange 2010 and want to migrate mailboxes in small batches during a specific time frame.
    – You have Exchange 2013. There is also an option to migrate email from another IMAP-enabled email system.

The O365 migration engine uses the information that’s provided by IT admins of a non-Exchange-based mail system in the EAC to connect to IMAP mailboxes and download mailbox data. IT admins need to provide a list of users to migrate in a CSV file. When the IMAP migration method is used, only the items in the users’ inbox or other mail folders are migrated. Tasks, contacts and calendar items cannot be migrated with IMAP, but can be migrated by the user.

New Features for SharePoint 2016

New Features for SharePoint 2016The SharePoint Server 2016 release, based on customers’ feedback to meet their exact requirements for the product, introduces significant improvements in SharePoint functionality.

The following list provides a summary of the new features available with SharePoint Server 2016.

– Improved User Experience. SharePoint Server 2016 has now updated the ribbon from SharePoint 2013, so it matches the Office 365 ribbon, meaning that if users are swapping between systems, they will get a consistent experience.

– Extensible Hybrid App Launcher. SharePoint Server 2016 Beta 2 introduces the App Launcher to gain a common access experience across applications and solutions in Office 365 and SharePoint Server 2016.

– Improved Mobile Experience. SharePoint Server 2016 comes with a touch friendly interface to allow you to make decisions faster and keep in contact with colleagues.

– Hybrid OneDrive for Business. Users can sync files with Office 365 and share them with others. They can also get access to their files through the Office 365 directly from any device.

– Cloud Hybrid Search. SharePoint Server 2016 provides a truly unified search experience across SharePoint on-premises and SharePoint Online for the end users. It now enables you to effectively index all of your content and thus provide a single set of results with combined search relevancy ranking, instead of separated lists of results from your on premises and SharePoint online within one page as it was previously.

– Durable Links. The idea is to make sure that links, you sent to your folks continue to work regardless of what happens to the document, i.e. the file name was changed or the document moved.

– Increased File Size for Uploads. The limit for maximum size of the uploaded file to SharePoint, set to 2Gb in previous versions, is no longer an issue. Though there’s no real limit now, Microsoft has strongly recommended for it not to go beyond 10Gb.

– Sites you follow in one place. Users now have the ability to follow SharePoint Server and SharePoint Online sites, and see them aggregated in a single list.

What do you need to run SharePoint 2016?

In this article we are going to cover some important things, you need to know about system requirements, configuration and scenarios for planning and running SharePoint Server 2016.
– MinRole feature. With the help of this new feature SharePoint farm administrators can now define each server’s role in a farm topology. When you select a role, SharePoint automatically configures the services on the chosen server based on the respective server role.
– Standalone Farm Installations. The option for a standalone installation on a single server is no longer available in SharePoint Server 2016. The SharePoint administrators now must separately install and prepare Microsoft SQL Server to be included as a SharePoint Single-Server Farm.

Below are few sets of System Requirements for SharePoint 2016:



If you are considering the upgrade from SharePoint 2010 or SharePoint 2013, these are the tips you should keep in mind during this process:

  • To upgrade from SharePoint Server 2010, you should first upgrade to SharePoint 2013 and then to SharePoint 2016.
  • To upgrade SharePoint Server 2013 to SharePoint Server 2016, you need to make sure that you first upgrade the SharePoint Server 2013 Site Collections that are still using SharePoint 2010 mode to SharePoint 2013 mode.
  • To upgrade from SharePoint Server 2013 to SharePoint Server 2016 you can either perform an in-place upgrade, or apply the database-attach method as described below:
  1. Create a SharePoint Server 2016 farm.
  2. Copy SharePoint Server 2013 content and service application databases.
  3. Attach the databases to SharePoint Server 2016 farm.

How to publish a SharePoint 2013 blog article via Microsoft Word 2013

This guide will show you how to publish a SharePoint blog article via Microsoft Word 2013.
  1. Run Microsoft Word 2013.
  2. Go to the File tab – New and choose Blog post from the available templates.
  3. If you publish a blog post via Microsoft Word 2013 for the first time a new window will pop up asking you to register a blog account. Click on Register now.
  4. Choose SharePoint blog from the drop-down menu and click Next.


  5. Enter the URL of your SharePoint blog and click OK.
  6. A password prompt window will pop up. Enter your credentials and click OK.
  7. Now you can see that your account has been successfully registered.
  8. Now you can create a blog post. Type the name of your article and fill in the body. Then click on Publish and choose Publish from the drop-down menu.
  9. Once you`ve published your article, you will be provided with publishing information.
  10. Now you can go to your SharePoint blog and see the published article.

SharePoint 2013 integration to Outlook

SharePoint 2013 supports connection to MS Outlook application in order to collaborate and coordinate activities and projects and to improve business efficiency and productivity, especially if you work offline and don’t have instant access to your SharePoint sites all the time.

You can synchronize information in two directions for items in Contacts lists, Calendars, Tasks lists.

But you should keep in mind that, unlike Contacts and Calendars, syncing SharePoint Tasks with Outlook relies on the installation of Exchange Server 2013 within your organization.

SharePoint Server 2013 and Exchange Server 2013 must both be installed in the same environment. Otherwise, you will not be able to accomplish this, in spite of the “Sync to Outlook” button will still be active.

How to: Create and publish InfoPath 2013 template to a SharePoint 2013 Enterprise site

This article will give you a walk-through for the process of creating and publishing an InfoPath 2013 template to a SharePoint 2013 Enterprise site.
  1. Run the Microsoft InfoPath Designer 2013.
  2. Go to the File tab, click SharePoint Form Library located at the New tab and click Design Form at the right side.
  3. Create an InfoPath template or you can open an existing InfoPath template that you want to publish to your SharePoint site.
  4. Go to the File tab and choose Publish form to a SharePoint Library by clicking at the SharePoint Server icon located at the Publish tab.
  5. Type the URL of the SharePoint 2013 site where you want to publish the Info Path template and click Next.
  6. Type your credentials and click OK. Please make sure that you have all required permissions to publish template at the SharePoint 2013 site.
  7. Choose the required configuration and click the Next button.
  8. You can choose an existing library to publish your InfoPath template or create a new library for the publishing your InfoPath template.
  9. If you have selected “Create a new library” complete the required fields with the name and the description of the new InfoPath library and click the Next button.
  10. Add columns if required or just skip this step by clicking the button Next.
  11. Verify the form information and then click Publish.
  12. When your InfoPath form template is published click at the Open this form in the browser link and then Close.
  13. Click the floppy icon to save your template at the SharePoint library.
  14. Type the name of your InfoPath template and click the Save button.
  15. You can see your InfoPath template at your SharePoint site.

Exchange Server 2016 overview

Since email remains a key element in every business, it is vital to use the most up-to-date and secure tools for business communications. The developers have improved Exchange Server 2016 integration with other Office products; cloud technologies, additional recovery functions and other elements have also been added.makes document sharing easier and eliminates version control problems. For example, in Outlook 2016 or Outlook browser version, you can now attach a document as a link to SharePoint 2016 or OneDrive for Business instead of a traditional attachment. Developers have also substantially improved Outlook web experience, by adding new features, such as Sweep, Pin, Undo, inline reply, a new single-line inbox view, improved HTML rendering, new themes, emoticons and more.

Improved search architecture delivers more accurate and complete results. Outlook 2016 is optimized to use the power of the Exchange 2016 backend to fasten search process. An intelligent search tool provides search suggestions, search refiners, people suggestions, and the facility to search events scheduled on your calendar.

Exchange 2016 has a reformed eDiscovery tool, with reliability improved by a new, asynchronous architecture, which spreads the work across multiple servers. It lets you search, hold, and export content located in public folders.

The developers has gained growth of overall productivity and stability, which come along with automated repair improvements and the Microsoft Exchange Server 2016 architecture characteristics, which simplify the process of planning hybrid and on-premises deployments.

“Site storage exceeded” error (part 2)

Following up the previous post, published in our blog last week, regarding the “Site storage exceeded” error, where two-stage SharePoint 2013 recycle bin origin was indicated as possible reason of running out of storage space on SharePoint 2013 site, we would like to point out another potential cause of such behavior. Version history enabled for the SharePoint list or library may lead to over occupation of storage space.

The version history contains information about when the item or file was changed, who changed it, and information about what was changed. In libraries, the version history might also contain comments written by the people who made changes. Which is very useful functionality for users’ collaboration, but also it can bring inconveniences with site storage management, since every version saved occupies actual file size on the site.

So, to free up some space on your SharePoint site, you should review version history for the “heaviest” files first to remove unnecessary and outdated versions.

Using MySQL database as a Datasource

How to connect to MySQL database from PowerPivot

One of the supported data sources that you can use to connect to your workbooks and create PowerPivot reports is MySQL database. But before creating such connection you need to make sure that the following requirements are fulfilled:

  • Make sure your MySQL server is binded on public IP address and accept traffic from PlexHosted`s SharePoint app server where your site is deployed, on default port 3306 (port 3306 used for demonstration purposes in this case).
  • You have a user that have read only permissions to required databases (root user is used for demonstration purposes in this case) GRANT ALL ON employees.* TO root@′ IDENTIFIED BY ‘verysecurepassword’; or GRANT ALL ON employees.* TO root@’%’ IDENTIFIED BY ‘verysecurepassword’; (if you have a firewall)
  • Your Desktop machines which are building excel reports must have permissions to connect to your MySQL server using public IP address.
  • The MySQL Connector/ODBC has been installed on the machine from which you are going to connect to MySQL. You can download and install it from [here].
Creating a connection to MySQL database
  1. Open the Excel workbook you would like to connect to the database and go to the PowerPivot tab. In the PowerPivot tab click Manage.
  2. When the PowerPivot for Excel window opened, click on From Other Sources button in the Get External Data section.
  3. Choose Others (OLEDB/ODBC) option.
  4. Type the name for your connection and enter the connection sting using the pattern below:
    Provider=MSDASQL.1;Persist Security Info=True;Extended Properties=”DRIVER={MySQL ODBC 5.3 ANSI Driver};UID=readonlyuser;Server=;Database=employees;Password=verysecurepassword;Option=3DRIVER={MySQL ODBC 5.3 ANSI Driver}”;Server=;Database=employees;Option=3;”;
    UID=<user with permissions to connect to your database>
    Password=<your user password>
    Server=<your MySQL server public IP address>
    Database=<your database name.
    After entering the connection string click on Test Connection button.
  5. Click OK in the connection status window.
  6. Click Next.
  7. In the Table Import Wizard choose the option Write a query that will specify the data to import and click Next.
  8. Enter the query to import the required data from the database and click Validate. Once you query is validated click Finish.
  9. The Table Import Wizard will start importing data from your database to the PowerPivot model. Once the status of the wizard changes to Success click Close.
  10. You can see the data imported to the model and can start creating your PowerPivot reports by clicking on the PowerPivot table button.

“Site storage exceeded” error

You are 100% sure you should have free space on your SharePoint 2013 site, but still getting “Site storage exceeded” error, when trying to upload some new content. Is this situation familiar to you?Let’s analyze what might be the cause of such behavior.

Make sure you have considered two-stage SharePoint 2013 recycle bin origin, as soon as files moved to recycle bin occupy the storage of the site, as if they were present in an ordinary SP library. Since the Recycle Bin in SharePoint 2013 provides two-stage protection against accidental deletions, you should delete files not only from the site’s recycle bin, but site collection’s recycle bin also.
To completely remove a file or an item from SharePoint site, check site collection’s recycle bin under Site Settings -> Site Collection Administration -> Recycle bin and clear up both locations:
– “End user recycle bin items”
– “Deleted from end user Recycle Bin”.
Try to upload new content then.