We just downloaded Win 10 1809 and started to attempt to roll it out (testing) but every time the task sequence fails with unknown errors (0x80004005) at the Apply Operating System Step.  I did some searching and it sounded like the version of SCCM we were on was not compatible so yesterday I upgraded to Config Mgr 1806 and also the 1806 hotfix.  Thought that would resolve the issue but it doesn't.  I copied the original task sequence for 1803 that was working and replaced the OS thinking that w

Our Setup: - SCCM 1806 on Server 2016 - Clients are running Windows 10 1709 (about 25000 clients) - Clients running corresponding SCCM client v5.00.8692.1008 We are trying to utilize Peer Caching but are unsuccessful in getting it to work. After a number of tries to connect to a peer, it uses the DP as last resort and successfully downloads the data (but not from a peer cache source). We verified that firewall ports (8003, 8004) are opened at the source peer. We re-entered the NA

It’s finally released, the long awaited Windows 10 Enterprise, version 1809 (otherwise known as The Windows 10 October 2018 Update) is available for download on Microsoft’s MSDN site, also to note, the Windows 10 Enterprise LTSC 2019 version is released. There is a corresponding download for Windows 10 Enterprise version 1809 also on VLSC however it’s for ARM Architecture only (64bit), so probably not of much use to you and me… This release is packed with lots o

Hello, We have an issue that has introduced itself into what was a working system so I'm guessing it is update related We are running the latest version with latest updates of SCCM with the latest ADK and capture media After the build process a machine will capture. If you make a single change i.e. installing software the capture will fail at initialising configuration manager client - 0x80040154. SMSTS.log shows the same error code against "Class not registered" This is a pr

Hi Folks, Hope all is well! I'm trying to enable IPv6 PXE boot on my DP, but the checkbox simply isn't there. I'm on 1806, and I've already selected 'enable PXE responder without WDS'. My DP does not have an IPV6 address assigned at the moment (although IPv6 is certainly enabled at the NIC/OS) - does that need to be configured first?   p.s. my clients will be PXE booting from a different subnet. Currently I use IP helpers to point the clients to the PXE server.

I am new to sccm I want to do lots of stuff in SCCM, existing sccm admin left without handovering anything, now there are lots of folders created, I want to clean it up. 2nd i want to create a new folder with my name download all the patches & Operating system deployment, help me out by sharing a layman steps to achieve this. I want to create a folder as per the OS eg Win 2012, Win 2012R2, win 2016, your guide will be very well appreciated, please reply as soon as possible.

I have been looking at the Config Manager Antivirus Exclusion list (https://blogs.technet.microsoft.com/systemcenterpfe/2017/05/24/configuration-manager-current-branch-antivirus-update/) and was wondering how others have this organized. I am looking at having at least 2 policies (Workstation and Servers) but for servers, are you adding all the exclusions under one policy or making it neater in the console and making a new exclusion policy for SQL, IIS, ConfigMgr, etc.?    

I am trying to prevent smsdbmon.log from getting spammed about Azure. Since I'm not currently using Azure I decided to remove the Azure connection. Every time I delete the Azure Service is comes right back before I can remove the Tenant. Any ideas how I can get around this?