SKILLS & TRICKS
Some of us have already worked with PowerShell and love it, while others seem to be confused and wonder how can one remember so many commands to get things done. Maybe its time we break it down for the guys who find it difficult to work with and show them how powerful it is when dealing with every day tasks related to SharePoint - for both Admins and Developers.
What is PowerShell
Its a scripting language and very similar to batch jobs which are simply plain-text files that execute through a console application to achieve automation tasks on a machine.
I have heard a few people referring to it as a tool or framework and i disagree with this approach. Lets just keep PowerShell a simple plain human-readable language.
What does it Contain, where do we write it and how do we run it
It contains logic loops, variable, methods and other entities from the programming world.
The scripts can be written using any text editor and i usually write my PowerShell scripts using Notepad++ and then save it as a plain-text file having a .ps1 extension. To run the scripts you can initiate PowerShell console session and its basically the command-line console with blue as background color and text in white. You can always change the background color to suit your needs.
The following line will print a line of red text on a yellow background:
Write-Host "See how cool this is?" -Backgroundcolor
orange -Foregroundcolor black
The console keeps the various variable declarations in memory for the entire duration of the PowerShell session. The image below shows you a fairly simple PowerShell session in which variables have been declared and are remembered throughout the execution of the various commands. It starts by declaring two variables, variableA and variableB, whose values will later be reused to perform mathematical operations. The script continues by changing the value of one of the two variables already declared and rerunning the same addition operation to get a different result based on the new value entered.
As usual I am late, I think I am getting used to it with updates and news flowing in from all directions – it’s hard to keep a track of stuff and post about it. Just came back after a week of learning from Sitecore Symposium in Las Vegas and thought about writing something on it, opened the To Do App and found that I need to first finish this piece before I jump on Sitecore.
Microsoft Ignite happened last month with a lot of WOW factor and I can also see some IT Pros even questioning the Wow now, particularly the guys still using SharePoint on Premise. It’s common to have two sides, the first is always about how cool it is and this will be a game changer but sadly the second is more of complains and the learning curve about how to get it right under the current circumstances. (It’s a pain to adjust business processes with updates if not properly planned and thought)
Let’s jump in to what was shared with us during the SharePoint Ignite 2017 sessions and try to constructively look at each one of them.
We often face the challenge of convincing customers that O 365 is the right choice for Digital Workplace and it addresses nearly every aspect with builtin functionality.
In the developed countries its much easier but if you are some where in the APAC region and particularly in South East Asia you will get a list of objections and if your Sales is not up to the game they might give up on the deal.
Below is a simple list which i am sharing and you can add more stuff in to it for Microsoft Teams, Planner, Delve, etc
In this article i am going to share some of the key Project Management elements for a successful SharePoint Intranet Deployment. In my previous articles, I have touched a few and have highlighted some of them and this article will be mostly covering the on premise or hybrid style deployment rather than SharePoint Online. Though you still need to do a few things which can apply to SharePoint Online as well - so lets get down straight to business.
As most of us know that SharePoint deployments in most scenarios are fairly consistent, which makes it easy to just follow the plan and deliver a SharePoint deployment. Personally i use a template with all the main tasks involved in the deployment with minor changes to accommodate third party integrations or updates.
Below is a screenshot of the SharePoint Deployment Template which i have used a lot of times and its a simple version which i am sharing.
I already mentioned in my previous article SharePoint Intranet: Learn to Tame the Monster about things you should consider before implementing an Intranet. Now its time to have a look at the ideal SharePoint Team Task List and Roles. Identifying and defining the roles and responsibilities is the one thing that can make the biggest difference for a SharePoint success with stability. Its extremely critical that we establish these task lists with roles and responsibilities as one of the first tasks on a SharePoint project; its absence is a common thread for any challenged project I have come across, which usually involved skipping or skimping on this step.