This post was originally a reply to an email thread on the ITMEL mailing list, discussing Google to Microsoft migrations and Microsoft Teams. Ended up being somewhat comprehensive so figured I’d record it (slightly edited) here. Perhaps may discuss some of these topics more at some stage.
Here’s a quick script I’ve been using to do in-place upgrades to build 1803 on some shared trolley machines these holidays. It uses the setup exe in the VLSC ISO. I used a batch file as, unlike a PowerShell script (unfortunately), its quick and easy to launch from the Run dialogue.
There are plenty of paid options out there to manage Office 365 email signatures, but what if you could do it for free?… PowerShell to the rescue! This post is collation and adaptation of what I’ve found online when implementing staff signatures in my environment. Note: the focus here will be on applying signatures in the Outlook Web App, although these signatures can be deployed to Outlook desktop applications when placed in the right userprofile folder etc. Might do an update down the track.
As an IT pro with a “functional” PowerShell knowledge, I hunted around a bit online looking for a way to do this. None of the solutions I found were doing what I wanted so I thought I’d share my simple solution. In this case, I was looking for a solution to quickly and easily reset and document bulk passwords for restricted student exam accounts.