Hello Experts, Need your Guidance. we recently upgraded our SCCM from 1606 to 1610. we have PXE environment enabled for OSD. it was perfectly fine before the Upgrade. We have task sequence deployed to the device collection for the OSD. Whenever the client machine initiated the OSD it will set the PXE flag on the machine.Next time it will not start the PXE process until we cleared the PXE flag on the console. But after 1610 upgrade when OSD deployment started it's not set any PXE f

Hey Running latest CB and newest ADK. When running a build and capture (Windows 10 - Edu - 1703 - on HyperV)  - the computer does not restart after sysprep. (if i manually restart the computer - it continues capturing) (The NIC seems to be disabled after Sysprep?) See attached log-file. Any ideas? Michael smsts.log

Hello, I'm trying to install SCCM from scratch with a brand new virtual machine on Windows Server 2016. I installed SQL Server 2016 SP1 CU3 and I followed the guide from CB 1702 guide. I have already an Active Directory with extended schema (from a previous install of SCCM 2012 R2), so I skipped this part. When I try to install SCCM I have a warning regarding the System Management container. It seems that the computer account has not rights on Children objects (create&delete)

I have a wim with two windows images, one x86 and x64.   i have apply operating system step set to use image index 2, and a set task sequence variable of OSDImageIndex equals 2. I have a condition that the task won't run unless the variable is 2. Yet, apply operating system fails with an error of 0x080070002. Any suggestions?  

Hello Experts, Need your Guidance. we recently upgraded our SCCM from 1606 to 1610. we have PXE environment enabled for OSD. it was perfectly fine before the Upgrade. We have task sequence deployed to the device collection for the OSD. Whenever the client machine initiated the OSD it will set the PXE flag on the machine.Next time it will not start the PXE process until we cleared the PXE flag on the console. But after 1610 upgrade when OSD deployment started it's not set any PX

hi    so I've upgrade to 1702 though after this clients cannot communicate back to the primary server.   I'm seeing the following issues on the primary server   in system logs The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {1A9FFCE9-10C1-40BC-9815-B20C1DC2D156}  and APPID {AD65A69D-3831-40D7-9629-9B0B50A93843}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address

So I find today that in trying to test a new TS that when booting PXE, I get an error screen from WDS that just only displays the error code 0xc000000f. Digging around, I've found some that say it's a WDS problem and another that says it's an SSL issue because the MP is SSL but the DP is not.  One article states that if the MP is SSL, the DP also has to be using the PKI Cert as well instead of the self-signed. Another article mentions no problems with the DP being non-SSL. This is what

Ransomware has been around for a few years now but up until yesterday, it wasn't that well known about. This latest RansomWare called WannaCry has changed that for ever. Ransomware encrypted data on at least 75,000 systems in 99 countries on Friday. Payments were demanded for access to be restored. European countries, including Russia, were among the worst hit. Companies around Europe were hit and investigations are underway to see who was responsible. This was such a big attack t