Let’s suppose the following. You are working with PowerShell console and just finished typing a long and complex command. This second it occurs to you, that you forgot to define a variable, create a remote session or something else. You delete the command, execute some required actions, and type the command again.
In this article we will talk about some techniques, that can help us out.
Plaster allows developers to scaffold file and folder structure for a new PowerShell module.
PowerShell keeps the history of executed commands.
PowerShell itself keeps them in memory. In addition to this, the PSReadline module saves them in a file on the hard drive. that allows us to go back to command entered not only in the current session, but also executed some time ago and probably in different PowerShell version.
ForEach-Object is used for performing specified actions on every element of an array.
This array can be specified as a value of the -InputObject parameter, but in the majority of cases it is received from the pipeline.
The -like operator allows us to use wildcards to select required objects.
For example, like this.
Microsoft.PowerShell.Commands.PSPropertyExpression type (it’s type accelerator – [pspropertyexpression]) exists in PowerShell from the beginning, but in version 6.1 it was made public, what makes it accessible to us, as a script and module authors.
What is a delegate? This is an object type, that instantiates by associating with some method so that we can invoke this method by calling the delegate.
Why is this needed? One of the cases – is that we can use delegate as a parameter for another method.
Is PowerShell supports this? Starting with version 6.1 – yes.
In the previous post we discussed SharePoint Online cloud service. Now, let’s talk about SharePoint farm deployed on premises.
We can specify Primary and Secondary site collection administrators in the SharePoint Central Administration portal by clicking on Application Management and then on Change site collection administrators in the Site Collections section.
Primary and secondary administrators are those who, among other things, receive e-mail notifications about various SharePoint event, like when a site collection reaches its storage limit.
Also, you can specify list of other administrators in the Site Settings. To do this, on the site collection click the cog at the upper right part of the page and then click Site Settings. If there is no such a setting in the menu, click on the Site information and then on the View all site settings. Finally, click on the Site collection administrators in the Users and Permissions section.
Now, let’s do it with PowerShell.
In the SharePoint Online admin portal we can specify the primary admin and the list of other admins in the properties menu of the site.
Let’s look at how we can do it in PowerShell.