Photo of Grant Dickins

Grant Dickins


Mystery of Required Reboots during Autopilot

Businesses pay tens of thousands of $currency for Microsoft Partner consultants to come in, “modernise” their EUC estate, and leave behind a plethora of bugs and issues that shouldn’t exist because said partners are supposed to be “industry experts”. Completely unrelated, an issue I was working on at a client was with their Autopilot setup left behind from an MS partner that was causing a forced reboot mid-ESP. Shortly after entering company credentials, there would be a 10 minute reboot warning and no way to cancel - other than Shift+F10 and running shutdown -a which a normal end user wouldn’t know and shouldn’t need to know.

FSLogix App Masking Rules for M365 Apps

I’m deploying Azure Virtual Desktop currently for a client and they want a “general shared desktop” pool that will have a bunch of core apps including Microsoft 365 Apps installed. However, not every user will be licensed for Visio or Project, and only a very select few users are allowed to use Publisher, and fewer still allowed MS Access (They’ve signed contracts so that if they dare create anything in Access, they have to support it for free till day they die, then their next of kin take over support.

Teams Channel Notification when OSD Fails

How would you like this lovely notification appearing within MS Teams every time a build failed? Better than getting a helpdesk ticket or not finding out at all. Well, now you can! Removed broken screenshot - editor Step 1 - Configure Teams You need to make sure your O365 Administrator has enabled Incoming webhooks connectors in your O365 Tenant. Open Teams. Select a channel, or create a new channel specific for these notifications (This is best practice so normal channels are not spammed) Click the … Next to the channel name and choose Connectors Removed broken screenshot - editor

Managing Multiple Office 365 Deployments with ConfigMgr

At the client I’m currently working for, we have FIVE different deployments of Office 365 Client within Microsoft Enterprise Configuration Manager. The business decided that they only wanted users to have exactly what was needed. Essentially, this is the legacy approach to Office deployment in the MSI days where you could fully customise which components were installed and was easy to add bits back in at a later date. These are the options they wanted: