Everything can be done automatically, as long as you configure it manually… 8-)
This is a topic I see quite often as well. Both on the TechNet forums as well as in the facebook groups I follow. So hereby a continuation of my back to basics series, giving you some insights on the Client Push installation process and how to troubleshoot some of the most common issues.
My previous post was about Patch My PC and Third-Party Software Updates in SCCM 1806. This one is a quick continuation, where I’m going to share a complete Powershell script to create collections for (at the time of writing) 23 different third-party products. Products that’s all available through Patch My PCs update catalog.
Currently Patch My PC has 272 different products in their catalog. I initially needed collections for the first 23. This is work in progress. I will add more products to it as an ongoing process. (Bare with me, there’s a lot of work involved into installing the applications, creating the queries and testing them)
Also, I have no idea if this is something that’s already been created out there, but that’s no excuse not to do another one. 🙂
Patching 3rd party applications can be a trivial and time consuming task, especially if doing everything yourself in terms of downloading the application, customizing for the enterprise, creating applications/packages in SCCM and.. the list can probably go on.
Does above sound familiar? Patch My PC made this task super easy and combined with the latest additions to SCCM 1806, the complexity in setting this up has been reduced to almost zero. Curious? Continue reading and be amazed 🙂
Continuing the back to basics blog series, and this time addressing how you can move the computer object in AD (Active Directory) from one OU (Organization Unit) to another during an in-place upgrade of Windows. A good guess is, that this will be relevant for a lot people working with WaaS (Windows as a Service), where putting the computers into a new and fresh OU, with some new and fresh Group Policies might be needed.
This is all done using a web service and powershell. Curious? Continue reading 🙂
Do you need a simple, but yet effective way of forcing people into updating iOS on their company enrolled Apple devices? Simply block access to company resources if iOS is not up to date. Here is how you can do that using Microsoft Intune and Conditional Access in Microsoft Azure.
UE-V is not something new, but when combined with OneDrive Known Folder Move, Enterprise State Roaming in Azure and OneDrive as the storage path for UE-V, you will find yourself with a very solid solution ensuring roaming of end users data and settings.
I have previously shown you how you can enable OneDrive KFM with SCCM. This time, I’m going to show you how you can enable UE-V during OSD with Configuration Manager, and how you make sure those settings are stored in OneDrive. I hope you can see the pattern here: No on-premise file share for UE-V settings – everything stored in the users OneDrive.
More Configuration Manager 1806 and more awesomeness. 1806 gives us additional improvements to the Cloud Management Gateway and removes the need for PKI in your environment. With these improvements, it has never been easier to setup the CMG. In this post I will walk you through the exact steps I went through in order to successfully deploy the CMG in a HTTP only environment.
Again, continuing the Co-management and flipping the switch journey, and moving the brand new Device Configuration workload to Intune MDM. This is the latest addition to the co-management world introduced in Configuration Manager 1806 (released 2 days ago at time of writing) and it’s absolutely amazing.
This means we finally (almost) can ditch group policies altogether and do our device configurations with Intune MDM. I will give you how to and an excellent example in this post. Read on. 🙂
Just like I did with SCCM 1802, where I went through the exact steps for upgrading Configuration Manager Current Branch to the latest and greatest version, I’m going to do something similar in this post with 1806.
Nothing really changed, but I know someone would fancy to have an A-Z guide to walk them through the process, and as of such, I here give you the exact steps I went through to upgrade my environment.
This will be something completely different and new coming from my end. So please be aware; a lot of strong coffee is potentially needed. That be, because I usually talk about how to do something technically around Configuration Manager and Microsoft Intune, or something technically related to those topics, and the typical reader would probably expect content in that context.
This time I’m going beyond that. “Why?” you may ask. Because I felt like giving back with a topic and content that I know that can make a difference. Not just limited to a specific technical topic, but as a whole, make a difference on how one will succeed in general with Configuration Manager and Microsoft Intune (and possibly other stuff too).
I believe in helping and promoting others, and as of such, I will give you 5 (and possibly some unique) advice on how you can improve and strengthen your SCCM and Intune knowledge. (No guarantees though, but the bullets mentioned in this post helped me a lot)
