Just a tip for a really useful tool. Our storage department was planning a storage migration so the content share used for applications, packages, etc in MECM (SCCM) changed. We already used a cname to point to the content share for a lot of objects but not for all of them. So I was looking for a tool to change content paths to the correct cname share in MECM.
This tool does the job! I can really recommend it!
I got a request at work if I could create the deployment of the latest versions (Click-to-run) of Microsoft Visio and Project and set the Monthly update channel. The deployment of the applications should be made available in the Company Portal for users that are a member of the Entra ID synced Active Directory group to which the Visio and or Project Online plan licenses are assigned to.
We still run a 32 bits MS365 Apps on devices so got a mix of 32 bits and 64 bits MS 365 apps. The deployment should automatically detect the MS 365 apps architecture and then install the correct 32 or 64 bits version of Project and / or Visio. In this post I will show you how I did this. I will also provide all the sources and scripts you need to accomplish this.
Update 2203 for Microsoft Endpoint Configuration Manager (MECM) is now available. In this post I will show all the steps you have to take to upgrade your current MECM installation. To install MECM 2203 as an update, you must have MECM version 2010 or later installed. If you check for updates in your console and the update is not available this post also shows how to get it using the early update ring script. I personally would not install the new version when it still is in the early ring on your production environment but it would be suited for a lab or test environment. When the new version is available in the production ring usually there is an hotfix available already so that would be a good version to install on your MECM production.
Update 2107 for Microsoft Endpoint Configuration Manager (MECM) current branch is available since 20-8-2021. In this post I will show all the steps you have to take to upgrade your current MECM installation. To install MECM 2107 as an update, you must have MECM version 2002 or later installed.
Update 2103 for Microsoft Endpoint Configuration Manager (MECM) current branch is now available. In this post I will show all the steps you have to take to upgrade your current MECM installation. To install MECM 2103 as an update, you must have MECM version 1902 or later installed. If you check for updates in your console and the update is not available this post also shows how to get it using the fast ring script.