How To Disable SSL 2.0/3.0 and Enable TLS 1.2 on windows Server in registry

Рет қаралды 54,858

rajbhatt_TechVlog

3 жыл бұрын

Video about how to disable legacy protocol SSL 2.0/3.0 TLS 1.0/1.1 and Enable TLS 1.2 on windows servers using registry

Пікірлер: 70

@terrancepinkney777 2 жыл бұрын

Thank You! Thank You! Sir for your time in making this video. I was at a stopping point for two days because I couldn't get AZURE AD Connect to work because of the TLS 1.2 server issue! YOU ARE AWESOME!

@rajbhatt1988 2 жыл бұрын

Thank you👍

@Cmart6444 2 жыл бұрын

Of course i liked your video and marked it so, Rajhatt. I am about to probe it in my instance. Looking foward to watch the 2nd method, let us know whenever is ready. Thanks indeed again Bro, regards from Venezuela

@rajbhatt1988 8 ай бұрын

2nd Method is already there in another video. Thanks for letting me know...

@munishgoyal7518 3 жыл бұрын

Thanks Raj! Its very knowledgable.

@rajbhatt1988 2 жыл бұрын

My pleasure

@INDIANSinghX Жыл бұрын

super explaination and really requirement fulfilling , thanks senior 🙏

@rajbhatt1988 Жыл бұрын

Always welcome

@timhayes45 8 ай бұрын

Very nice walk through.

@mehrdadpourmoghadam8007 2 жыл бұрын

So helpful. Thank you so much.

@rajbhatt1988 2 жыл бұрын

Glad it was helpful!

@souravbiswas-tk3se 8 ай бұрын

Thank you for the video.....I was searching for this type of comprehensive video....

@rajbhatt1988 8 ай бұрын

Glad, it helped you. Thanks

@robyirloreto Жыл бұрын

Thanks a lot brother

@ErikRahman 2 жыл бұрын

Thanks bro....it works

@anilthomas7342 Жыл бұрын

Saved one day. Thanks a lot

@rajbhatt1988 Жыл бұрын

Glad it helped!

@robertparker7243 Жыл бұрын

Absolutely great job - nice and clear tutorial and a comprehensive and thorough treatment of the subject

@rajbhatt1988 Жыл бұрын

Good to know. Thanks

@ou812927 2 жыл бұрын

Another question, when creating the folders, can you put the Client folders first, then the Server folders? Or must the Server folder come first? Thanks again!

@rajbhatt1988 2 жыл бұрын

Yes. That doesn't make any diff, what you creating first. They all should be there, that's the point

@webersonudi 3 жыл бұрын

Parabens pelo video

@rajbhatt1988 2 жыл бұрын

Obrigado|

@naveenrajkali1790 3 жыл бұрын

Super

@rajbhatt1988 2 жыл бұрын

Thanks

@mustafagullu3519 2 жыл бұрын

thanx

@MrElston007 2 жыл бұрын

Thanks a lot... Worked... :D

@rajbhatt1988 2 жыл бұрын

Cool

@Cmart6444 2 жыл бұрын

Thanks Elston, i was reviewing all commets till i could find this confirmation that it works. thanks indeed, regards from Venezuela

@omkar2735 2 жыл бұрын

cheero bro zeero

@awarenessabhinav2159 3 жыл бұрын

Hi Sir, do we require reboot after making changes?

@rajbhatt1988 3 жыл бұрын

Yes ofcourse..

@calebhuggins6706 3 ай бұрын

I need to replicate this under the WowNode for 64-bit systems, correct?

@rajbhatt1988 3 ай бұрын

Nope. It doesn't need to add there.

@aidataverse 2 жыл бұрын

thanks

@rajbhatt1988 2 жыл бұрын

Welcome

@danielwestmoreland6407 2 жыл бұрын

Will this work without a reboot? I cant reboot live servers until a maintenance window.

@rajbhatt1988 2 жыл бұрын

Yes must be rebooted after changes, to take in effect..

@ravijoshi2362 Жыл бұрын

Hi Raj, Ravi your buddy here!! Have a curiosity to know about the Azure, now days I m hearing about Azure from my IT team, what exactly Azure is?

@rajbhatt1988 Жыл бұрын

Azure is cloud based IT infrastructure, provides IT infra resources.

@LuigiZambetti Жыл бұрын

I can follow this procedure also to check if TLS 1.2 is enabled on a Windows Server?

@rajbhatt1988 Жыл бұрын

Yes

@user-tr2ts3bv2e 7 ай бұрын

When i make changes in my server after that i am able to take RDP also web page not open pls suggest

@rajbhatt1988 7 ай бұрын

Sorry, didn't get your question. What changes you made?

@kT2015N Жыл бұрын

Do I need to reboot the server these changes to effect

@rajbhatt1988 Жыл бұрын

Yes

@muhammadaliff9277 8 ай бұрын

May i know if the folder is not there meaning the SSL or TLS is enable right?

@rajbhatt1988 8 ай бұрын

That means still negotiating with legacy protocols

@ultraweapon1004 Жыл бұрын

I have found a website ,.in which TLS 1.0 enabled ,.Is this a Vulnerability? Can I report it?

@rajbhatt1988 Жыл бұрын

Yes absolutely. TLS 1.0/1.1 are already legacy. Its more concerning if website is in production..

@WNasiri Жыл бұрын

But could please tell me sir ? That I have already installed sql server 2022 and I also installed SCCM when I execute the setup after the installation I want to to configure the SCCM , then during the installation it gives me an error that is that there is no TLS 1.2 installed or updated so when I see the documentation of the Microsoft, it doesn’t tell me it says that for the sql server 2022 you can not updated and install TLS 1.2 , so could you please help me how I can install or update it on SQL server 2022 ? I would be thankful to you

@rajbhatt1988 Жыл бұрын

Hi, so you may follow the steps in this video as how we enable TLS 1.2 and disable other legacy protocol before installing SCCM. Once disabled legacy and enabled TLS 1.2, you need to reboot server for changes to take effect. Once server is up after reboot, try to install and configure SCCM again. It should work. If you still come across such issue, let me know. Will love to help you.

@WNasiri Жыл бұрын

@@rajbhatt1988 thank you so much sir to are so kind that reply me fast thanks cuz I have the projet for that but I have come across with problem so of course If I have any problem again I can send you a message thank you so much again

@WNasiri Жыл бұрын

Hello sir I hope you are fine ? So I wanted to configure SCCM as you know so I just solved the problème of the TLS 1.2 but I just install from the Microsoft site so again I am coming across with so many problems so that during the installation of the SCCM . It said that SCCM should be reduced the version to 2012 R2 in the forest of the main server but it is already 2016 server that is normal and the other side it tells me that the stockage is not enough for the disposition according to the memory for the SCCM premaire site and honestly I have given just 8 g to the SCCM in hyper v but I also don’t have enough space in my physic machine while I want to give more space to SCCM on the other hand in server 2016 what version of sql server and what version of SCCM we could install and configured cuz I have downloaded the versions of sql server 2022 and sql server 2022 studio and SCCM 2022 manager but it can not configured on server 2016 ? How is the solution and what should I do ?

@rajbhatt1988 Жыл бұрын

@@WNasiri Hi, As per your OS configuration it looks okay as SCCM 2022 supports server 2012 + and Sql 2012 r2 sp3+. Here it looks like your primary site needs to be upgraded first. Please check this detail doc for the same. For storage, it should be having enough storage and Memory to function properly. By the way, what errors it gives you during pre-requisites check.if Possible share screenshot of error www.systemcenterdudes.com/step-by-step-sccm-2211-upgrade-guide/

@WNasiri Жыл бұрын

@@rajbhatt1988 i would like to send you the screenshot but i speak french and my server is in french langauge tha is why you wouldnt understand but thanks again for your response so could you please send me your email adresse something so you can see there and you will at least understand the problem

@naveenrajkali1790 3 жыл бұрын

Where to find another way to mitigate the vulnerability.

@rajbhatt1988 3 жыл бұрын

There is another video for disabling these legacy protocol using iiscrypto tool.

@naveenrajkali1790 3 жыл бұрын

@@rajbhatt1988 Thanks for the quick response. I have one question, after setting the enabled value to "0", DisabledByDefault setting up to 1 is necessary, what if we don't set the DisabledByDefault to 1??? Please clarify.

@rajbhatt1988 3 жыл бұрын

@@naveenrajkali1790 shouldn't make any difference but as per MS article, this is how it is.

@naveenrajkali1790 3 жыл бұрын

@@rajbhatt1988 oh Great, thanks for the confirmation 🙏👍👌

@LuigiZambetti Жыл бұрын

These are the paths: TLS 1.2 Client subkey Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client DWORD name: DisabledByDefault DWORD value: 0 DWORD name: Enabled DWORD value: 1 TLS 1.2 Server subkey Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server DWORD name: DisabledByDefault DWORD value: 0 DWORD name: Enabled DWORD value: 1