If you are deploying Microsoft Teams but don’t want it to start on login, or force users to login to disable the auto start then you can do it after installation of Teams simply by editing a file. The file is located in the install location of the Teams installer, by default is it here: 1 %programfiles% (x86)\Teams Installer\setup.json The contents of the file should be as follows:
Office Update Manager for 365/2019 I’ve overhauled Office Update Utility and have improved the reporting. It also includes all the same improvements that the other refactored utilities have. 2020-03-03: Version 20.03.01 ‘Crosshair’ New features: Refactored code. Fully backwards compatible. Added ASCII banner art when run in the console. Added option to disable the ASCII banner art. Config report matches design of Image Factory Utility. Office Update Utility can be downloaded from:
If you use Microsoft Teams you may want to be able to send information from external services. There are many apps that can be added to teams to accomplish this but what if you have an internal system or custom script and you want it’s output to be sent to Teams? Well, there’s an app for that too. You can add the Incoming Webhook app to your Teams instance and configure where and who it should deposit information as.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 ___ __ __ _ _ _ /___\/ _|/ _(_) ___ ___ /\ /\ _ __ __| | __ _| |_ ___ // // |_| |_| |/ __/ _ \ / / \ \ '_ \ / _ |/ _ | __/ _ \ / \_//| _| _| | (_| __/ \ \_/ / |_) | (_| | (_| | || __/ \___/ |_| |_| |_|\___\___| \___/| .
If you’re familiar with deploying Office 2016 or any previous version, then the first big change when looking into Office 2019 or Office 365 is that there is no longer an MSI installer. Office 2019/Office 365 is now only available as a ‘Click-to-Run’ installation, which means we’ll need to change how we package, deploy and update Office 2019 or Office 365. Links to sites used in this post: Download the Office Deployment Tool (ODT) from Microsoft here.
Update 2019-06-16 I recently learned that Office 365 licensing can be managed via Azure Active Directory’s group based licensing feature and I have since switched to using this and have retired this script. I’ll leave this post and the script itself available here, on the Microsoft TechNet Gallery and GitHub, but I’ll not be developing the script any further. For more information on Azure Active Directory group-based licensing please check out Microsoft’s documentation here and here to start with.
Update 2018-11-04: I’ve evolved the script in this post into a more friendly utility which I’ve posted about here. If you are familiar with my other PowerShell scripts/utilities this isn’t as complete or polished as them, but it get’s the job done, and that’s all we can really ask for right? Let’s say it’s in early beta. The purpose of this script is to automate the process of setting the location and Office 365 license for users, using a local Active Directory to specify the users.
In my previous scripts I’ve included a function to send log files to an on-premises Exchange server. I’ve now put together an example script to improve this function to send emails to external e-mail providers, for example: Office 365, Outlook.com or GMail.com. This new code is designed to support many different requirements: No logging at all. Logging but with no e-mail. Logging with e-mail. E-mail with username & password authentication, with SSL.