Was just fiddling with my FreeNAS host to ensure things come up under a cold start. Given the DC that i joined the domain with is a VM stored on FreeNAS I was re-pointing everything to our backup, physical DC, so that we have a clear boot order to get everything up without user intervention (Backup DC > FreeNAS > VM Hosts).
A funny thing i noticed is that whilst I could join a domain without the PDC running (but FreeNAS was) - when i went to reboot with the Backup DC running, FreeNAS doesn't join AD (thus none of the folder redirections etc work) - and actually claims an error saying that it needs to talk to the DC that is the PDC Emulator.
If you jump in the web gui after boot, then just tick "enabled" and then save - it joins and functions as normal.
I have moved the PDC Emulator role to the Backup Physical DC, rebooted and everything is fine.
Is this expected behaviour?
A funny thing i noticed is that whilst I could join a domain without the PDC running (but FreeNAS was) - when i went to reboot with the Backup DC running, FreeNAS doesn't join AD (thus none of the folder redirections etc work) - and actually claims an error saying that it needs to talk to the DC that is the PDC Emulator.
If you jump in the web gui after boot, then just tick "enabled" and then save - it joins and functions as normal.
I have moved the PDC Emulator role to the Backup Physical DC, rebooted and everything is fine.
Is this expected behaviour?