Eds89
Contributor
- Joined
- Sep 16, 2017
- Messages
- 122
Hi,
I have an environment whereby my active directory domain controller is a VM, stored on storage that FreeNAS hosts.
As such, the domain controller is not available when FreeNAS boots.
I can see that during the boot process, FreeNAS is trying several times to bind to AD, and obviously failing.
Once the postinit is completed, FreeNAS is left with directory services disabled, and I have to manually go in and enable the service once the domain controller starts.
I have two questions really;
1. Does directory bind hold up the boot process of FreeNAS? I.e. can the boot attempts to bind be given more retries or longer timeouts without preventing FreeNAS from completing it's init phase?
2. Is there a way to have FreeNAS boot and keep the directory service enabled, even if it is unavailable during boot? My timeout and retry settings would therefore cover the startup time of my domain controller.
I'm looking at the above two options, as it will save me adding ANOTHER startup script to manually restart the AD service once the DC is booted.
Thanks
Eds
I have an environment whereby my active directory domain controller is a VM, stored on storage that FreeNAS hosts.
As such, the domain controller is not available when FreeNAS boots.
I can see that during the boot process, FreeNAS is trying several times to bind to AD, and obviously failing.
Once the postinit is completed, FreeNAS is left with directory services disabled, and I have to manually go in and enable the service once the domain controller starts.
I have two questions really;
1. Does directory bind hold up the boot process of FreeNAS? I.e. can the boot attempts to bind be given more retries or longer timeouts without preventing FreeNAS from completing it's init phase?
2. Is there a way to have FreeNAS boot and keep the directory service enabled, even if it is unavailable during boot? My timeout and retry settings would therefore cover the startup time of my domain controller.
I'm looking at the above two options, as it will save me adding ANOTHER startup script to manually restart the AD service once the DC is booted.
Thanks
Eds