Hi guys, Having a slight issue trying to get a remote DP up and running, as far as I am aware i have set this up correctly. I installed the IIS role on the new server before i ran the DP install to this server from the primary server. I installed all the pre reqs that the web seems to state across various articles i.e WMI compatibility etc. Opened up firewall ports 445/135/49152-65535 on the new DP server and also installed the WDS server role but I didnt set the PXE option up during the DP

Hello all - I'm trying out Windows 10 Servicing and on a 1607 machine, I can see the upgrade deployment and it downloads properly but then hangs after that at installing.  UpdateDeployment.log ---- Update (Site_6486F88A-6CE4-45F7-865B-FB7832923564/SUM_2c038450-6726-4512-bd3b-a00f3bb0f865) Progress: Status = ciStateInstalling, PercentComplete = 100, DownloadSize = 0, Result = 0x0 UpdatesDeploymentAgent 11/3/2017 11:58:16 AM 3212 (0x0C8C) ---- UpdatesHandler.log

any way to stick a pre-start command to a PXE boot image? I understand the technical limitations, just wonder if anyone ever had it working.

Hi All, Hoping someone can help point me in the right direction. I am replacing old 2008 R2 MP/DPs with new 2016 Servers. The old servers have custom shares on the root of the DP Drive(TOOLS$ for example). These custom Shares are copied over as a result of adding the new DPs into the DP Groups to update content. There is no Package Deployment in SCCM to create these shares on the new DP.  Nothing is deployed to any of the Collections that these DPs are a part of that create th

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