SharePoint Online VS. On-Premises & 2019 Version Review

The major difference between SharePoint Online and On-premises is that to run the on-premises version you'll need an IT team to maintain the server, to install updates and patches. This means more people and hardware. With the online version your internal resources are reduced. There's no new hardware to buy and maintain, which means your IT staff can focus on more impactful tasks.

The cloud version of SharePoint Server is Office 365. Microsoft has enabled SharePoint Online in Office 365 since 2010 and when Microsoft releases new features in any version of SharePoint, those features are already tested and used in Office 365 for months.

SharePoint Online (Office 365)

Some of the most important features of Office 365 are:

Microsoft applies security patches and installs platform updates.

SharePoint farms are hosted in Microsoft's cloud infrastructure.

Office 365 has committed to 99.9% availability in their service level agreement (SLA) – anything less than that and you may receive a service credit.

The cloud version receives more new features and it is geographically redundant.

SharePoint Server On-Premises

Here are some notable features of on-premises SharePoint servers:

SharePoint farms will be hosted by your company.

Your internal IT staff will be responsible for updates, patches, change control, etc.

Your organization will manage the Active Directory Domain Services on-premises.

You need to buy Client Access Licenses (CALs) for each person/device accessing the SharePoint server.

There are obvious differences between online and on-premise, but if your organization needs an on-premise solution, then SharePoint server can be "the" solution. However, if you think about switching from on premise to Cloud version of SharePoint to take advantage of more up time, more new features and spend less time maintaining your SharePoint environment, then you should go with Office 365.

Migrations to SharePoint solutions are essential to maintain business efficiency and continuity. However, some executives are still reluctant when it comes to migrate to a new environment because they believe the migration will be too costly and complex, but this is not always an accurate statement.

When it comes to users and the differences between SharePoint Online and On-Premises, focusing on what your organization's goals are is a good starting point. You may also want to think about who is going to manage SharePoint, and how would you make a successful transition from On-Premises to a hybrid model or to a Cloud environment.

Businesses realize now more than ever that to be more successful they need to have certain capabilities: coordination, full collaboration, social capabilities etc. With Office 365, Microsoft simplifies day-to-day business administration and management.

New In SharePoint Server 2019

Modern sites & pages

The modern experience is designed to be flexible, mobile, compelling and easier to use.
With SharePoint Server 2019 you can create and publish modern pages quickly and easily. These pages are responsive and will look great on any device.

Modern libraries

Helping people share and collaborate on content has always been a priority to SharePoint specifically. Therefore, modern libraries combine the power of SharePoint with OneDrive usability – these libraries have an updated UI that offers a unique experience. It is more intuitive to create new folders and upload files in your browser with SharePoint 2019.

Modern lists

SharePoint Server 2019 introduces a modern list experience that simplifies how people create, modify and engage with content having a set of capabilities that work across all devices and browsers.

SharePoint Mobile

As we all know, for any company, the intranet is extremely important. It provides collaborative space that offer teams the resources they need to work productively. It also hosts relevant applications that support and automate relevant business processes.

SharePoint Server 2019 makes your intranet more accessible, innovative and intelligent increasing the efficiency of its users.

Improved Communication

SharePoint Server 2019 launched a new generation of intelligent intranet, so now you can communicate with fellow colleagues using dynamic, mobile-friendly sites and pages.

Large file support, special characters in file names & URL path length

It's clear that the world of professional collaboration has changed, so text-based files are shifting to modern media, videos, audio files, and more. SharePoint Server 2019 now provides default support for uploading files up to 15GB.

In addition, SharePoint Server 2019 has increased the maximum length of any URL path from 260 Unicode characters to 400.

SharePoint Server 2019 now delivers support for several other types and naming conventions. This will allow users to create, store, sync files containing # and % characters whether those characters are used within file or folder names.

Eventually, this is just part of what's new in SharePoint Server 2019. For a complete list of new features and capabilities refer to the new SharePoint Server 2019 Reviewer's Guide and for technical documentation you may check: https://docs.microsoft.com/en-us/SharePoint/sharepoint-server.

Source :- Click Here

Order Your Output by Easily Sorting Objects in PowerShell

Summary: Much of the time, there is no guarantee to the order in which Windows PowerShell returns objects. This blog explains how to fix that issue.

Use Sort-Object to organize output

Lets take example of Get-Process cmdlet to check how sorting works in powershell, by default it sort on the ProcessName property.

One could make a good argument that the processes should sort on the process ID (PID) or on the amount of CPU time consumed, or on the amount of memory utilized. In fact, it is entirely possible that for each property supplied by the Process object, someone has a good argument for sorting on that particular property. Luckily, custom sorting is easy to accomplish in Windows PowerShell. To sort returned objects in Windows PowerShell, pipe the output from one cmdlet to the Sort-Object cmdlet. This technique is shown here where the Sort-Object cmdlet sorts the Process objects that are returned by the Get-Process cmdlet.

Get-Process | Sort-Object id

The command to sort the Process objects on the ID property and the output associated with that command are shown in the image that follows.

Reversing the sort order

By default, the Sort-Object cmdlet performs an ascending sort—the numbers range from small to large. To perform a descending sort requires utilizing the Descending switch.

Note:  There is no Ascending switch for the Sort-Object cmdlet because that is the default behavior.

To arrange the output from the Get-Process cmdlet such that the Process objects appear from largest process ID to the smallest (the smallest PID is always 0—the Idle process), choose the ID property to sort on, and use the Descending switch as shown here:

Get-Process | Sort-Object id –Descending

The command to perform a descending sort of processes based on the process ID, and the output associated with that command are shown in the image that follows.

When you use the Sort-Object cmdlet to sort output, keep in mind that the first position argument is the property or properties upon which to sort. Because Property is the default means that using the name Property in the command is optional. Therefore, the following commands are equivalent:

Get-Process | Sort-Object id –Descending

Get-Process | Sort-Object -property id –Descending

In addition to using the default first position for the Property argument, the Sort-Object cmdlet is aliased by sort. By using gps as an alias for the Get-Process cmdlet, sort as an alias for Sort-Object, and a partial parameter of des for Descending, the syntax of the command is very short. This short version of the command is shown here.

gps | sort id –des

Sorting multiple properties at once

The Property parameter of the Sort-Object cmdlet accepts an array (more than one) of properties upon which to sort. This means that I can sort on the process name, and then sort on the working set of memory that is utilized by each process (for example). When supplying multiple property names, the first property sorts, then the second property sorts.

The resulting output may not always meet expectations, and therefore, may require a bit of experimentation. For example, the command that follows sorts the process names in a descending order. When that sort completes, the command does an additional sort on the WorkingSet (ws is the alias) property. However, this second sort is only useful when there happen to be multiple processes with the same name (such as the svchost process). The command that is shown here is an example of sorting on multiple properties.

Get-Process | Sort-Object -Property name, ws –Descending

The figure that is shown here illustrates the output from the command to sort Process objects based on name and ws properties.

When the name and ws properties reverse order in the command, the resulting output is not very useful because the only sorting of the name property happens when multiple processes have an identical working set of memory. The command that is shown here reverses the order of the WorkingSet and the process name properties.

Get-Process | Sort-Object -Property ws, name –Descending

The output that is shown here shows that there is very little grouping of process names. In this example, adding the name property does not add much value to the command.

Sorting and returning unique items

At times, I might want to see how many different processes are running on a system. To do this, I can filter duplicate process names by using the Unique switch. To count the number of unique processes that are running on a system, I pipe the results from the Sort-Object cmdlet to the Measure-Object cmdlet. This command is shown here.

Get-Process | Sort-Object -Property name -Descending -Unique | measure-object

To obtain a baseline that enables me to determine the number of duplicate processes, I drop the Unique switch. This command is shown here.

Get-Process | Sort-Object -Property name -Descending | measure-object

Performing a case sensitive sort

One last thing to discuss when sorting items is the CaseSensitive switch. When used, the CaseSensitive switch sorts lowercase letters first, then uppercase. The following commands illustrate this.

$a = "Alpha","alpha","bravo","Bravo","Charlie","charlie","delta","Delta"

$a | Sort-Object –CaseSensitive

When the two previous commands run, the output places the lowercase version of the word prior to the uppercase version. This output appears in the figure that follows.