У нас вы можете посмотреть бесплатно Transfer FSMO From a Failed Domain Controller (Running Windows Server 2019) или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Donate Us : paypal.me/MicrosoftLab Transfer FSMO From a Failed Domain Controller (Running Windows Server 2019) 1.Prepare DC31 : Domain Controller(Yi.vn - Primary) # Server down or OS error (Unavailable) IP 10.0.0.31 DC32 : Domain Controller(Yi.vn - Secondary) # Server alive (Available) IP 10.0.0.32 2. Step by step : Transfer FSMO From DC31 to DC32 --------------****************** / microsoftlab ********************------------------- DC32 : Transfer FSMO From DC31 Server Manager - Tools - Active Directory Users and Computers - Yi.vn - Domain Controllers OU - Check number of domain controllers Right-Click Yi.vn - Operations Masters... - RID tab(PDC,Infrastructure) - Change... - Yes === Fail because DC31 error Set the first DNS is DC32(10.0.0.32) Start - Windows PowerShell - Right-Click 'Windows PowerShell' - Run as administrator, type : dsquery server -forest # Check number of domain controllers netdom query fsmo # Check which domain controller is the owner of FSMO roles (all at DC31) regsvr32 schmmgmt.dll # Register the Active Directory schema management library Start - Right-Click 'Command Prompt' - Run as administrator, type : Ping DC31.Yi.vn or 10.0.0.31 === Fail ntdsutil # Seize the roles from a failed DC31 using NTDSUTIL tool ntdsutil : roles fsmo maintenance : connections server connections : connect to server DC32 server connections : q fsmo maintenance : seize naming master # seize naming master role fsmo maintenance : seize infrastructure master # seize infrastructure master role fsmo maintenance : seize rid master # seize rid master role fsmo maintenance : seize schema master # seize schema master role fsmo maintenance : seize pdc # seize pdc role fsmo maintenance : q ntdsutil : metadata cleanup metadata cleanup : connections server connections : connect to server DC32 server connections : q metadata cleanup : select operation target # List the existing Active Directory sites select operation target : list sites select operation target : select site 0 # Site Yi.vn select operation target : list servers in site select operation target : Select server 0 # Select DC31 select operation target : list domain select operation target : select domain 0 # Select Yi.vn select operation target : q metadata cleanup : remove selected server Server Manager - Tools - Active Directory Sites and Services - Sites - Default-First-Site-Name - Servers - Right-Click DC31 - Delete - Yes Windows PowerShell, type : netdom query fsmo # Check which domain controller is the owner of FSMO roles (all at DC32) === OK