I received the following error on step 7, part 17 (see screenshot) when running the script:
Install-ADDSDomainController -NoGlobalCatalog:$false -CreateDnsDelegation:$false -CriticalReplicationOnly:$false -DatabasePath "C:\Windows\NTDS" -DomainName $currentDomain -InstallDns:$true -LogPath "C:\Windows\NTDS" -NoRebootOnCompletion:$true -SysvolPath "C:\Windows\SYSVOL" -credential $cred -Force:$true -Confirm:$false -SafeModeAdministratorPassword (ConvertTo-SecureString 'ADRestoreModePassword_ChangeThis' -AsPlainText -Force)
I checked that the domain admin was part of Schema Admins and Enterprise Admins (which it was). I noticed that the script created the new computer account (in a disabled state) on the small business server but the actual 2019 server was still in a workgroup so I enabled the account, moved it to the Domain Controllers group, logged into the 2019 server and manually added the computer to the domain.
Everything seems to be reporting back okay. The Event Log doesn't show any DFRS errors and the dcdiag test reports everything as functioning properly.
My question is, was I okay to proceed in this way? Will this cause issues further down the migration path? Do I need to spin up a new 2019 server and try again?
Thank you.
Hmmm, that looks weird to me. Do you have a shared Netlogon and Sysvol on both?
I ran 'net share' and they exist on both the sbs server and 2019 server.
Open Group Policy Management on both servers and access and 'edit' some policies. Does that work?
I was able to edit group policies on both servers, and all group policies showed up on the 2019 server.
Form the answers I got from you it looks like it is OK to proceed. Make sure you run all reports from the kit once more after you move FSMO roles and also shortly before you demote the old server.
Will do. Thanks for the prompt replies.
Your browser doesn't have Flash, Silverlight or HTML5 support.