ok, I have fixed 1 issue only to replace it with another.   I have VMWorkstation setup.  I have created 2 new Virtual Networks.  18 & 19.   18 - bridged - Ethernet Connection 19 - bridged - Wireless I have 1 DC running Server 2019.  It has both networks added so it can get to my Router (i.e. outside Internet) and the other is for internal traffic within my VM world. I have 1 SCCM server that has both vnets setup the same way. I have another VM, it too has both vnets 18

Hi Niall,   Hope you are doing great. I was following your tutorial on migrating from MBAM to SCCM Bitlocker, as i am working on a project for a customer for same.  Tutorial: https://www.niallbrady.com/2019/11/13/want-to-learn-about-the-new-bitlocker-management-in-microsoft-endpoint-manager-configuration-manager/#comment-2150   Background:      They are currently using SCCM version 2006, and wanted to migrate bitlocker from MBAM. They already have a PKI infrastructure

I've posted other places online and searched for someone else with the problem and I'm coming up empty.  Here's the deal, I'm pretty sure it started right after I upgraded to 2010 (now on 2103).  When I create a software update group with updates in it, the software update group is no longer visible for me under the Software Update Group area.  I'll add a picture and explain a bit more.  Here's my normal process that used to work.  I would select the updates I wanted to roll out to a test group.

Hello, I have a problem running PS scripts packaged as applications. If I run the script once, then everything is OK and the script will run. If I run the same script as an application, I see an error in Deployment Monitoring: Google Chrome Uninstallation test, PS100014, Test collection, Required, Chrome Uninstallation, Failed to locate content, No additional information, 0x87D0032A (-2016410838), The uninstall command line is invalid, WIN10TEST, 14,18.06.2021 12: 19, Error, MSI, No, (SYS

Hi, I have enabled PXE, I have confirmed my boot image is setup to work with PXE.  I have confirmed that my c:\RemoteInstall folder is filled with content.  My SMSPXE log shows this. TST0005 is my x64 boot image   Found new image TST00005    SMSPXE    6/17/2021 7:23:19 AM    3368 (0x0D28) Loaded Windows Imaging API DLL (version '10.0.19041.1') from location 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll'    SMSPXE  

Good Morning, I've been trying to find a solution for this one for a while now.  In our environment, we typically use the OSDComputerName TS variable to manually name devices.  We have about 15 sites and will be rolling out a large count of devices shortly which will be imaged in a centralized location then spread amongst these sites.  My thought is to name each device with <site code><serial>.  I've been able to name the device with a simple PS to make the name "DL-<Serial&g

Hey All -  I'm having an issue in my enviornment.  We have about 1100 clients that are currently on 1909, all done with the same image.  We have been doing regular monthly patching with an ADR set up, but we haven't had to do Feature upgrades yet.   Older versions of Win 10 (1903 etc) we have been doing with an upgrade task sequence, but given this a big patch month and so many of our clients are now out of compliance I want to roll 20H2 into the monthly patching and not by TS. I check

I am fairly new to the SCCM game, so excuse me if this question is overly simplistic   I have inherited the responsibility of looking after the SCCM environment.  I have noticed that there are over 3500 software update groups   Do to me inexperience, I do not know what are the ramifications of such a high number of software update groups what is a manageable number of software update groups how to trim these software groups down Any help or advise wil