Dear Admin, My Apologize - I feel to raise this Question separately to make myself clarity on asking question and getting answer, As per the previous post, Phase I : Upgrade from SCCM 2012 SP2 to SCCM CB V1606 At Present, the Environment is having as below and mentioned with To - BE State After Successful, Completion with Phase I - Progressing Phase II as follows (As-IS and To-BE Infra) Please Validate if the As-IS to Phase I, II (To-BE) is Okay / Please

So, my sccm site died.  Luckily,  I had the site backups configured.  I went through the restore process, everything went well.  Only thing I had to do was remove the dp role and put it back.  However, When I try to run any of my osd task sequences, they fail after partition and format on the apply operating system task.  The error is 0x080004005 which i know you are going to say is generic, but the smssts.log on the machine is not showing the failure.  I am attaching one from the computer I was

Hi all, Done alot of browsing and can't find an answer that seems to do what im after. Basically we are rebuilding our SCCM environment for the move to WIndows 10 (sigh). At the moment our existing console is a mess due to the ammount of rebuilds and refreshes our devices go through, creating duplicate client entries in the console mainly because when a device moves rooms within the building it gets rebuilt and renamed as part of the task sequence. I'm looking for a step that i ca

Hello everyone, I have the client that wants to do something specific with bitlocker and its pins, but that is beyond of this topic. Issues is: When you create a step in task sequence to set up the bitlocker, if you choose TPM and PIN, you will be able to backup the recovery key into Active Directory. But, if you try to do the same  via command line on the client, you will get the error: The key protector specified cannot be used for this operation. Somebody have a clue how t

Guys   I am trying to run a 'Build and Capture' on Windows 10 1709.. All works fine until the Capture Operating System [obviously last in the list] section of the Task Sequence.. when this runs the target machine [tried physical and a VM with same issue] has lost its NIC driver, so it connot write the WIM to the network share   Has anybody seen this before?   OS's...   Target build is Windows 10 1709 Enterprise SCCM is 1710 on Windows Server

Hi Everyone, We are managing clients on the LAN, DMZ (Domain joined and workgroup) and Internet.  Currently everything is running over SSL and we have only enabled the correct ports for SCCM between our DMZ and LAN. There is one niggle though.  Currently there is only one root CA server with no subordinates.  Obviously this server is not accessible from outside of the LAN.  Due to this, CRL checking has been disabled for clients and 443 IIS management sites on both the primary sccm ser

We are experiencing build failures in maybe 10-15% of cases since SCCM 1710 upgrade. OSD initiated from the SCCM client can lead to a failure on reboot into WinPE where the computer goes into the WinRE recovery environment. If the computer is power cycled it will continue the build. This is happening on three different types of hardware. I can get to a command prompt in WinRE so can provide logs though can't see anything in SMSTS log. It's the same issue as reported here but

Hi all, I have built a site server in the DMZ running (MP, DP, SUP) which uses an RODC and is for deploying software updates to both internet clients and clients within the DMZ. There are two additional servers in the DMZ.  One is domain joined and is working great, the second is on a workgroup.  I have created and deployed workgroup certificates and everything seemed to go ok. I installed the sccm client on the workgroup server using these switches: ccmsetup ccmhostname:extserver