34. Manually Removing A Domain Controller Windows Server 2022

Поделиться
HTML-код
  • Опубликовано: 27 окт 2024

Комментарии • 10

  • @glenntembo2693
    @glenntembo2693 8 месяцев назад +1

    Thank you MSFT

  • @khalidkachachi6595
    @khalidkachachi6595 7 месяцев назад +1

    Thank you so much this was very helpful

  • @BASHIRGANIYU
    @BASHIRGANIYU 3 месяца назад

    This was extremely helpful, thank you. One question please, followed your instructions but at point (7:44) where we should check for SRV Records (Under DC__Sites__First Site__tcp), I can see SRV records for my crashed DC there, can I also go ahead and delete those SRV records for the crashed DC ?

  • @joelsalamanca5331
    @joelsalamanca5331 2 месяца назад

    Do the same procedures apply if I want to remove just the AD and keep the DNS features?

  • @Raheelzari9211
    @Raheelzari9211 8 месяцев назад +1

    Thanks Man

  • @dragutak
    @dragutak 5 месяцев назад

    So, since you only have one additional DC, that one automatically became the FSMO holder. What if you have a DC3, DC4 or more? Once you deleted the DC1 (FSMO holder), which DC would take over the FSMO roles? Is there a way to transfer the FSMO roles to a specific DC using a similar "manual" method, instead of using "metadata / ntdsutil" ?

    • @MSFTWebCast
      @MSFTWebCast  5 месяцев назад

      Yes, you can transfer the FSMO roles manually. Option:1 Use ntdsutil command or option:2 Use move-addirectoryserveroperationmasterrole powershell cmdlet. Check out this video: ruclips.net/video/yWjMI2F5k20/видео.html

  • @olegwinkler2466
    @olegwinkler2466 8 месяцев назад

    Does this also work with DC Windows Server 2012R2, 2019?