Since my last two articles, PowerShell, as well as the terminal itself, has evolved. It is therefore time to bring Retro PowerShell up to date. Where the first two parts cover Windows PowerShell, this article is an update for PowerShell Core and Windows Terminal and will show you how to let your Terminal look like a Commodore 64.
Since we, in the company I work for, have rolled out 65,000 Office 365 licenses and are one of the most successful companies ever with Yammer and Teams, I had the great luck this year to be invited by Microsoft as a speaker to the Ignite 2018 in Orlando. Together with my colleague we held a total of 3 sessions and were interviewed in a podcast.
How do you load the PowerShell OfficeP PnP module for SharePoint?
Addendum: I've added a try/catch block to the code. This way you can be sure the module is loaded.
# Loading Office Online PnP Module
try {
if((Get-Module "Microsoft.Online.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) {
Import-Module Microsoft.Online.SharePoint.PowerShell
Write-Host "PowerShell module Microsoft.Online.SharePoint.PowerShell initialized"
}
else {
Write-Host "PowerShell module Microsoft.Online.SharePoint.PowerShell loaded"
}
}
catch {
throw "PowerShell module Microsoft.Online.SharePoint.PowerShell initialization failed"
exit 3
}
How do you connect to your SharePoint Office365 tenant with the PowerShell if you are locked behind a proxy? This hint will probably work for all kind of PowerShell scripts, not only for Office PnP. I tried this with the Microsoft SharePoint Online extensions as well and it worked.
So my problem was, the company I was working for, had a proxy which could not be bypassed. The proxy settings have been set by a GPO and the network settings where fine so far. However the proxy used user authentication to access the internet. Now if I want to use the SharePoint Online tools, I must authenticate my PowerShell session at the proxy so the tools can access the internet too.
The trick to get your PowerShell connected is quite simple. You only need to enter the following line:
[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials
Now you should be able to connect to Office365 SharePoint without problems. If you don't want to enter this line every time you open a new PowerShell, you could add it to your PowerShell profile.
ise $PROFILE
then add this to the profile file:
#Set user default credentials for any webrequest "Setting the users default credentials for WebRequests..." | Write-Host -ForegroundColor White [System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials
What do you need to uninstall from your server if the installation with AutoSPInstaller wasn’t successful?
Installing a SharePoint Server with the AutoSPInstaller job has become the gold standard for administrators. It’s much easier for large farms and offers a high degree of quality. However, using AutoSPInstaller can be a bit of a hassle. Until you get the xml configuration right, you normally need a few approaches. You can start the installation again, but you need to remove a few things first before it will re-run successfully.
If you are installing language files with your SharePoint Farm, remove these packages first. Open the Windows Control Panel, go to Programs -> Uninstall a program. Search for any SharePoint Language Package that has been installed and remove them all.
Leave the Control Panel open. Search for the SharePoint Server binary installation package and remove that file as well.
These files must not be removed. They can stay on the server.
Open the IIS Management and look for any Web Application that was created during the AutoSPInstaller setup. Remove all of them and the Application Pools as well. Because AutoSPInstaller will create all of them again, I normally delete all Application Pools and Web Applications from IIS. This way I’ll have a clean system after setup. The Web Applications create directories in the VirtualDirectories folder of the IIS working directory. You normally find it here: C:\inetpub\wwwroot\wss Remove the folders from the Web Applications you have deleted from here as well.
Remove the log files from the ULS logging directory or do a clean up after you sucsessfully installed SharePoint.
If the SharePoint Search has been created already, go to the directory where the search index is stored. Delete all GUID directories you find there.
Open the SQL Management Studio and connect with the SQL instance you are using to host the SharePoint databases. Delete any database that has been created by the AutoSPInstaller script. At the prompt to delete the database, you should select to close any connection to the database.
Now reboot your server. After login back into the server you can restart the installation with AutoSPInstaller. Any traces of previous installations will be gone then.
Get-Module SQLPSIf it isn't loaded, do so by using
Import-Module SQLPSFor scripts you should check if the module is loaded before you import it like this:
if ((Get-Module "SQLPS" -ea silentlycontinue) -eq $null)
{
Import-Module SQLPS -DisableNameChecking
}
Now you can change to the SQL server by simply entering SQLSERVER:
foreach ($db in ls) {
if ($db.RecoveryModel -ne "Full") {
$db.RecoveryModel = "Full"
$db.Alter()
}
}
How to iterate thru all SiteCollections and containing the Websites. This script also shows a progressbar on screen:
$sites = Get-SPSite -Limit All
$siteIter = 0
foreach($site in $sites) {
Write-Progress -PercentComplete (($siteIter / $sites.Count) * 100) -Activity "Iteration Sites" -Status $site.HostName
$webIter = 0
# Do something here
foreach($web in $site.AllWebs) {
Write-Progress -PercentComplete (($webIter / $site.AllWebs.Count) * 100) -Activity "Iteration Webs" -Status $web.Title -Id 2
Write-Host $web.Title
$webIter++
# Do something here
}
$siteIter++
}
How do you load the PowerShell module for SharePoint?
Addendum: I've added a try/catch block to the code. This way you can be sure the module is loaded.
# Loading SharePoint Module
try {
if ((Get-PSSnapin "microsoft.SharePoint.Powershell" -ea silentlycontinue) -eq $null)
{
Add-PSSNapin Microsoft.SharePoint.Powershell
}
}
catch {
throw "Microsoft SharePoint PowerShell AddIn initialization failed"
exit 3
}
 |
| Picture by Caroline Gutman |
With Office 365 Search, Microsoft has created a central entry point for the modern workplace. In one convenient spot, users can access all ...
