I just need some clarification on the ports that need to be opened on the client. Following this document, https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/ports#BKMK_CommunicationPorts Client Wake on Lan UDP 9 Wake-up Proxy UDP 25536 Remote Control TCP 2701 Remote Assistance TCP 3389   Are there any additional needed?

Hi Everyone, This is such a pain!!!!  We have an old physical server running Windows Server 2008 R2 with an old SCCM install on it.  Working great and OSD takes about 45mins, but we need a new one to support Windows 10. We have built a new SCCM server on Windows Server 2016 running SCCM 1710 (latest updates, ADK, MDT etc etc).  This server has way more CPU and RAM than the old one, and using it is super fast. The only issue is with imaging new machines, booting from PXE.  We have

I deployed the latest March Update for Office 365 to one Test Machine and it was marked as compliant even though it hasn't installed the update and is still on the old Office 365. I have checked the logs, nothing there. I went through the logs mentioned here https://technet.microsoft.com/en-gb/library/bb693878.aspx Can you someone please point me in the right direction of troubleshooting? Thank you

Hello to all, I have a customer that is asking how he can deploy the drivers like SCCM task sequence step is doing it but via command line... where can I find the command that explain how the task sequence step is querying the drivers folders and applying them ?    what is the task sequence variable that represents the driver library \ drive packages locations ??? and how are they applied to the system ? do we know the exact command string ?    thank you all in

Hi guys, Trying to deploy Windows 10 Fall Creators Update 1709 using SCCM 1606. Everything works fine until a restart step and it gets stuck on a black screen until you press a key or tap the mouse pad and then it carries on to the next step. Deploying to Surface Pro 4s SCCM 1606 Simple TS - Install OS from WIM, join domain, install few apps, and that's it. https://i.imgur.com/BuGSczP.png https://i.imgur.com/EQYmeYW.png   It happens to every

My upgrade task sequence to go from 1511 and 1607 to 1709 was working perfectly. Now it just hangs forever (days) when it starts the upgrade the task os step. There are no errors in the SMSTS log, it just stops at the executing command line step. Setupact and Setuperr logs show some errors but I could use some help figuring out what happened to make this stop working!

My task sequence is pretty simple, I just want to include Office 365 in it as it takes a long time to install during a normal W10 deployment, which is why I'm including it in my Capture. It's coming up with this error 0x00001007 This is the log from CONFIGMGR TASK SEQUENCE MONITOR ... ESULT=80091007 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,798) TS::Boot::BootImage::StageBootImage(sPkgID), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.c

I have been upgrading systems from 1511 to 1709 with a task sequence and it was working fine until I got the mobile devices. This task sequence was tested to work on the Surface Pros fine. I upgraded all the desktops with no problems. But now when deployed to 64 Surface Pros only 4 were successful. The rest just got stuck "in progress" at the executing command line step "Executing command line: "C:\_SMSTaskSequence\Packages\P010001A\SETUP.EXE" /ImageIndex 3 /auto Upgrade /quiet /noreboot /postoo