anyweb

That used to be the way it was when SCCM had a hybrid mode, that has been depreciated and now, it uses cloud attach. Please see our series of blog posts on the subject here. Parts 2 and 3 will help you setup a CMG which can also function as a CDP (cloud distribution point).

they are there, try again, only logged on members of windows-noob.com can download scripts

so are you converting the computer from legacy to UEFI and also converting the file system > if not it won't work

IIS doesn't host the recovery keys, they are stored in the ConfigMgr database. The recovery service runs on IIS and that's probably what you are thinking about. The following guides should cover everything you need including HTTPS (pki) which is listed at the bottom of the blog post. If you don't want to go all https (and i'd recommend you do...) then simply add the HTTPS cert to IIS as explained in https://www.niallbrady.com/2019/11/13/want-to-learn-about-the-new-bitlocker-management-in-microsoft-endpoint-manager-configuration-manager/ why are you testing with ConfigMgr 2002, 2

Introduction In a previous blog post I explained how you could use the SendGrid resource in Azure to send emails, and with a PowerShell script create an Intune app to give end users additional options when resetting their Windows Autopilot provisioned pc. This app would gather the Autopilot diagnostic logs (and other relevant logs) and send an email to your support inbox prior to resetting the pc. I've now updated the code quite a few times with the following changes. modified text boxes to 'read' better modified warnings to make it clear when a device might become unboot

the best thing for you to do for now is to create a lab environment, three or four virtual machines, where you can learn SCCM and understand how it works and practice things before doing them in 'production'. Start with this guide.

i would ignore that for now, your MP is way more important.

start by checking your MP (management point), you need that working before dealing with any other issues MP Control Manager detected MP is not responding to HTTP requests. The http error is 12002. Possible cause: MP service is not started or not responding. Solution: Manually restart the SMS Agent Host service on the MP. Possible cause: IIS service is not responding. Solution: Manually restart the W3SVC service on the MP. log file retetion is explained here https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/about-log-files

take a look at this for some clues

no problem ! glad to hear you got it resolved

ok @EngiNerd I got the files from a fellow MVP, please confirm that it solves your problem (check your pm)

ok that sounds like it's in HTTP mode. If you check the site component status, how does it look are there any major issues there? On the clients, what do you see in this screen (a screenshot would help)

I will check with Microsoft, but in the mean time you may have to raise a case with Microsoft Premier support

is this a http or https (pki) environment ?

hi, what version of ConfigMgr and how many clients are connected to it ? are the clients the same version as the primary site ?