anyweb

ok sorry about the delay, busy working, from first (quick) looks it looks like your logs are way too small and therefore missing details (such as the info we really need to see to diagnose this_), so you'll need to modify the ccmsetup command line to increase the log file size this will show you how to do that once done, deploy a machine again and capture the new logs, attach them here cheers niall

it all depends on what you mean 'forcing systems over to the new environment' means, for example do you have client push enabled and boundaries defined ? i'd suggest you take a look at this guide I wrote recently to get a good understanding of the different discovery methods and enabling them.

hi is this primary under a CAS ? can you attach the cmupdate.log please...

on your extensions tab, what does your CRL Distribution Point (CDP) list ?, attach it here...

I did this 8 part series several times in separate labs to be 100% sure of the result and it always worked, so i know it works. You might have done something incorrectly or missed a step, as regards requesting a certificate via a webbrowser, i didn't cover this in my guide but if you try it you'll see the following text, i've bolded the interesting bit... does that explain things ?

have a look at the comments at the end of Part 8 here

creating a dp and enabling pxe are two separate things, so are you trying to enable pxe ? is WDS installed ?

here you go https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/site-and-site-system-prerequisites#bkmk_2012dppreq

what does the smsts.log file tell you ? and the netsetup.log in %windir%\debug

here's some info about it https://social.technet.microsoft.com/Forums/windows/en-US/1323ea44-7f8d-41b7-a258-ae4c1d6c12ee/slow-wim-winpe-download-via-pxe-tftp-with-sccm-wds?forum=configmgrgeneral and here http://blog.danovich.com.au/2011/07/28/slow-sccm-osd-tftp-pxe/

it's slow to download the boot image because it's using old technology to download the winpe.wim file, aka tftp (trivial ftp), you might be able to tweak registry settings on the server hosting WDS to get it to go faster, but it might also break pxe boot capability.

First things first. the BitLocker capability I blogged about above is not yet released, it's still in technical preview as of todays date, however it's coming soon. Secondly, you state you want to export the keys, what keys exactly ? are you referring to Sophos disk encryption ?

where did you make that change ? on the dp ?

hi Christian, i'm not using any prestage TS, so yes that might be part of your problem. my user also doesn't have access to the ccmcache but as i said, it's working just fine for me

i suspect this is why it's failing for you verify this tab on your package

ok just tested it in my lab with a user that is a standard user, and it starts the powershell wrapper no problem at all. so something else must be different in your environment, double check your settings pls

hi Christian, I'll double check in my lab and come back to you shortly, thanks for your patience cheers niall

have you tried right clicking it to view what the actual errors are ? those errors will give you an indication of what is actually wrong with it.

pls attach your entire smsts.log file, the error above is not relevant to your issue.

can you do a teamviewer session so i can take a look ?

the other method is only for creating bootable media, did you update your boot images to your distribution points as a matter of interest after you enabled HTTPS ?

did you do step 4 here ? and step 5 here that is how the boot image gets the certificate, the other method for getting the cert into the boot image is documented here

hi, i've fired up one of my HTTPS configmgr labs and verified that all the certs are working, then i pxe booted and compared my smsts.log to yours, have a look here, it looks like you are missing certificates in the boot image as suspected. You log to the left, my working vm on the right. I'd double check you've done everything in my converting sccm from http to https guides again.

if you are not getting the screen press f8 as soon as you can, grab the smsts.log and attach it here i'll take a look

the central server is just a Primary server, avoid a CAS if at all possible, it will only cause grief, you can have DP's at your 3 locations no problem, if you want to get certified then take training with Kent Agerlund or Johan Arwidmark, both offer training via their companies, i would also try and get trained up on Microsoft Intune as that is where a lot of focus (and companies) are moving towards, on-premise management is via SCCM cloud management=Intune mix of both=SCCM co managed with Intune cheers niall