Restarting a virtual machine does not give me a guarantee as always because I’ve encountered many cases in which something went wrong after restarting. One of the Search in my customers’ SharePoint 2013 farm recently got several errors on its component after a SharePoint virtual machine running a set of Search components was restarted. At least Content Processing, Analytics Processing, Query Processing and Index Partition have a red triangle icon which you wish not to see in your life. The SharePoint Search Host Controller (Windows service) somehow continuously terminated after restarting. I was called to look into this issue because I was the one who designed this Search into multi-server Search farm.
I’ve recently had a good short conversation with a senior developer, having worked more than 5 years in SharePoint platform. He shared with me that he found SharePoint really challenging and really wanted to master it. It’s pretty difficult for him to have deep understanding about SharePoint plus update about this emerging technology. He came to ask me my idea on what to do next to step up his experience in SharePoint development.
This post is not going to introduce what MinRole in SharePoint 2016 is. You are better to get it from massive number of articles written by SharePoint experts in the community. Personally MinRole is only helpful to those who are not familiar with designing and administering medium to large farm. When Microsoft says “Hey you only need to select the role this server is going to play!” then you feel like you are going to be an unoccupied SharePoint administrator perhaps because MinRole is your friend, giving you advise on compliance from the farm management perspective. The description made by Microsoft sounds so straightforward that SharePoint farm architect can just select without really understanding and planning their farms. There is not any article which deeply tells you how SharePoint processes each role in MinRole mode behind the scene.
One of the big advantages of Microsoft Azure I often introduce to folks surrounding me is how quick I can provision an environment for demonstration . As a SharePoint geek, you would love to see how the latest on-premises version looks like. I know you do even folks now seem to head to SharePoint Online doing client-side stuffs.
You would be pretty much looking forward to an approach to migrate a large file share to SharePoint thanks to the article’s title. Unfortunately, this article is not going to cover that. Migrating a large file share to SharePoint consists of a good process of both business and technical, including information classification, scalable architecture, planning information architecture to data migration. Hence, I’m not going to write so much about that here in this article. As SharePoint is a proven content management platform so there are many reasons to get rid of file share and move things to SharePoint.
Deployment Guide is always required naturally in software development project. However, writing a good deployment guide is not easy. I have seen a lot of deployment guide without care, contributing to bad deployment of an application. In SharePoint, it becomes more complicated to deploy an application if your deployment guide is written without care. In real-world scenario when SharePoint farm hosts many applications developed by number of different development teams or vendors, deployment task is usually done by the internal staff team who may have just a little bit of SharePoint knowledge.
The deprecation of Sandbox solution is actually not new to those who continuously keep their eyes on Microsoft, which was announced in 2014. And 2 years later in 2016, Microsoft announced that its steps to completing the removal of code-based sandbox solution in SharePoint Online. Customers who have been using code-based sandbox solution have only 30 days before existing code gets stopped. This message does contribute to the list of pain points that exists.
We have heard a lot about hybrid model between SharePoint on-premises and Office 365, along with many benefits and reasons, from making the best use of your investment to on-premises to utilizing workloads running beneath cloud-based infrastructure, while meeting the requirement of data compliance regulatory. The buzzword about SharePoint hybrid today is almost Search to give end users the access to content stored in both SharePoint On-premises and Office 365. You might have heard of connecting on-premises LOB to Microsoft cloud services. But how about workflow which is an inevitable component to a successful digital workplace deployment? Yes, I mean hybrid workflow.
Migrating from legacy file servers to the latest file storage or to the cloud is not a simple task. As I have used LepideMigrator for Document for several projects, in this article I try to give you the knowledge to overcome the common pitfalls and challenges that you may come across.
1. Migrating from different source environments to different target environments
A lot of companies only want to migrate a selection of documents which results in a hybrid environment. Others want to migrate their documents to a variety of places, including SharePoint online/on-premise, Office 365, One Drive for Business and Google Drive.
With so many possible source-target combinations, finding the right way to run different jobs for each pairing is not easy. LepideMigrator for Documents offers a solution to this problem. It not only migrates to and from all source-target combinations mentioned above, but can also migrate Exchange and Office 365 Public Folders to SharePoint online/on-premise.
2. Migrating poorly-managed, scattered and un-structured files
Migrating poorly managed, un-structured and scattered files can be a big headache for admins. Files and folders need to be logically restructured before being uploaded to SharePoint or the Cloud. If there is a large volume of data in your organization it can make this process difficult. LepideMigrator allows you to shape the files and folders to suit the target environment’s requirements so that the migration runs smoothly.
3. Uncertainties in migration
Uncertainties in migration may arise from the fact that certain target environments may have limitations; the file name must not have invalid characters, the name ending string should be compatible, the file names and file paths must be within limits, the file size must be within limits and the file extensions must not be in the blocked list. LepideMigrator for Documents helps you address these problems and determine how much time it will take to complete the migration.
4. Handling files and folders metadata
Files and folders’ attributes are important for meeting internal and external compliances, internal record keeping and for litigation purposes. LepideMigrator for Documents allows the following document attributes to be migrated: Name, Title, Created At, Modified At, Modified by, and Created By. These attributes can be even changed at the time of migration. The value can be set by SharePoint, a custom value can be provided, or it can be mapped with a selected column in the source.
5. Inability to maintain the same file / folder hierarchy in the target
If you are migrating a large number of files and folders, you may well want to keep their original hierarchies one they have been moved to the target environment. LepideMigrator migrates documents with or without the original folder hierarchy depending on the requirement of the user.
6. Slow migration
The speed of the migration, whether to an on-premise system or to the cloud, is determined by the network bandwidth and the ability of the application. For example, the number of file servers in parallel it can connect to, the different targets it can migrate to concurrently and the number of migration jobs it can run in parallel. LepideMigrator was specifically designed to overcome these obstacles in order to speed up the migration time.
7. Manually doing the migration during non-office hours
Performing a migration manually will require time and attention. If this is done during office hours it can affect the day-to-day work of your employees. With LepideMigrator you can schedule the migration to run at any time to suit you. It will run automatically so there is no need to worry about downtime.
8. Migrating different types of content at different times
In any organization the on-premise data may consist of a number of different types. There could be files and folders stored on the File Servers, sites, lists and libraries on SharePoint and there could be Exchange Public Folders. LepideMigrator allows these documents to be migrated together by running different migration jobs in parallel.
9. Keeping on-premise and cloud data in sync
For non-cut-over migrations, the data on the on-premise systems on the cloud needs to be in sync. Synchronization between two lists, libraries and sites on the different SharePoint servers can be achieved using LepideMigrator.
10. Downloading from the cloud
At some point you may find yourself in the situation where you have to download data from the cloud. LepideMigrator allows you do to this simply and quickly.
LepideMigrator for Documents allows you to overcome 10 of the most potentially difficult problems that you could face during document migration. The solution automates many of the tasks that would be time-consuming and complicated to carry out manually and helps to ensure that you have a smooth migration no matter the size.
As SharePoint is a web-based platform it is supposed to have a trusted SSL certificate imported for better security. In a highly secure environment SSL certificate is part of security policy and is always required. In this article I’m going to share some cases you may have to deal with SSL certificate and SSL protocol.