I am trying to integrate Napp-it/OmniOS into my domain to share files & folders.
For years, I had been sharing files & folders from large virtual disks attached to a Windows Server VM (SBS2011). This was easy to set up, but I would like to take advantage of the benefits of sharing files & folders using SMB server from Napp-it.
I now have 2x ESXi hosts, 2x Domain Controllers and a File Server using Windows Server 2019. Domain clients & workgroup clients are using Windows 10 pro.
I can access the SMB shares from all domain and workgroup machines by name or IP, but the shares are not visible in Windows 'Network' folder.
What is the best practice for setting these up for Napp-it SMB shares in a Domain? what are typical mistakes to avoid?
Can Napp-it communicate with 2 domain controllers? The Primary DC1 is stored on the Napp-it NFS share, therefore the DC1 will start after the SMB server is started; but DC2 will be available from the other host. I would rather keep the primary DC1 on the more powerful host, I could move it to a local datastore to start before OmniOS, if this is more sensible, but then it wouldn't benefit from the features of ZFS.
In SBS2011, I managed shares and folder redirection etc. from vmdk drives attached to the server VM. Now I have separated DC, File Server and SMB server. Therefore, where should I manage file shares and folder redirection now, should this be from a Windows Server 2019 File Server role, or is this redundant and just use Napp-it and the DC to manage?
The VMs are currently like this:
Host 1 (ESXi 6.7U3 on USB) Xeon E-2278G/128GB
VMs on local SSD datastores:
- vCenter Server Appliance
- OmniOS r151034 / napp-it 20.01 pro
VMs on NFS shares from Napp-it:
- Domain Controller 1 (Windows Server 2019)
- File Server (Windows Server 2019)
- Servers: Veeam, media, etc (Windows 10 pro)
- Virtual desktops (Windows 10 pro)
Host 2 (ESXi 6.5U2 on USB) Xeon X3450/16GB
VMs on local SSD datastores:
- OmniOS r151034 / napp-it 20.01 pro
VMs on NFS shares from Napp-it:
- Domain Controller 2 (Windows Server 2019)
For years, I had been sharing files & folders from large virtual disks attached to a Windows Server VM (SBS2011). This was easy to set up, but I would like to take advantage of the benefits of sharing files & folders using SMB server from Napp-it.
I now have 2x ESXi hosts, 2x Domain Controllers and a File Server using Windows Server 2019. Domain clients & workgroup clients are using Windows 10 pro.
I can access the SMB shares from all domain and workgroup machines by name or IP, but the shares are not visible in Windows 'Network' folder.
What is the best practice for setting these up for Napp-it SMB shares in a Domain? what are typical mistakes to avoid?
Can Napp-it communicate with 2 domain controllers? The Primary DC1 is stored on the Napp-it NFS share, therefore the DC1 will start after the SMB server is started; but DC2 will be available from the other host. I would rather keep the primary DC1 on the more powerful host, I could move it to a local datastore to start before OmniOS, if this is more sensible, but then it wouldn't benefit from the features of ZFS.
In SBS2011, I managed shares and folder redirection etc. from vmdk drives attached to the server VM. Now I have separated DC, File Server and SMB server. Therefore, where should I manage file shares and folder redirection now, should this be from a Windows Server 2019 File Server role, or is this redundant and just use Napp-it and the DC to manage?
The VMs are currently like this:
Host 1 (ESXi 6.7U3 on USB) Xeon E-2278G/128GB
VMs on local SSD datastores:
- vCenter Server Appliance
- OmniOS r151034 / napp-it 20.01 pro
VMs on NFS shares from Napp-it:
- Domain Controller 1 (Windows Server 2019)
- File Server (Windows Server 2019)
- Servers: Veeam, media, etc (Windows 10 pro)
- Virtual desktops (Windows 10 pro)
Host 2 (ESXi 6.5U2 on USB) Xeon X3450/16GB
VMs on local SSD datastores:
- OmniOS r151034 / napp-it 20.01 pro
VMs on NFS shares from Napp-it:
- Domain Controller 2 (Windows Server 2019)