Hi, I am deploying in-place upgrades to many systems using standard task sequence.  This has been working well with version 1607, I've done over 1,500 machines this way.  I have tried to switch to use the 1703 or 1709 media however on system models which were fine with 1607 we now see them fail with a hard block due to having older Intel HD Graphics.  Systems with this issue include HP EliteDesk 800 G1 range. I cannot get the block to be ignored using the options in ConfigMgr and I'm n

I would like to build a second SCCM site in my lab. One is 1706 and i would like to build 1710. Same AD. I just build a new server for CM 1710 and can see that exising server already pushed a client. What would be the best config? Thank you.

Hi all Have an issue with my 1703 TS. I did a Build & Capture using MDT (just the same as i've always done). Uploaded the .WIM into CM12, distributed, etc, etc. The TS itself throws no errors but upon completion, when the user logs on, it says that Windows is not activated. Anyone come across this issue before?

I am creating a WIP rule and deploying it to a Windows 10 machine 1703. my SCCM CB is 1702 ... I follow the rules and i see the WIP rule in my sccm client but it is shown as not applicable : Summary: Name Revision Type Baseline Policy Compliance State Non-Compliance Severity Discovery Failures Non-Compliant

SCCM 1706 Is it possible to generate report or query for an deleted task sequence OS Deployment?

Hello! I want to run the following command after OneDrive application deployment: %LocalAppData%\Microsoft\OneDrive\OneDrive.exe /configure_business Appreciate any assistance! Elad.  

Hi, I'm testing an Upgrade TS to Win 10 1709. I tested 4 devices now. On  devices, all was working fine. Update was successful. On other two devices, the OS upgrade was successful, but after the OS boots again the TS doesn't complete successfully. I have two batch files in the Post-Processing group which are not executed. One of them just creates a txt file so I know it did run actually.  In Software Center, the TS has status "Installing..." and it keeps spinning like tha

SCCM CB 1706 - Win7 to Win10 migration using USMT, LTI (non-upgrade) -  When re-imaging a machine using the same computer name, the client does not recognize the PKI cert.  The machine pulls the previous PKI cert that was issued and ClientIDManagerStartup.log has the following errors: 1) Failed to acquire certificate private key. 2) Certificate [Thumbprint...] issued to 'machine name' doesn't have private key or caller doesn't have access to private key. 3) Unable to find PKI