5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
I forgot I posted this here but this has been resolved. The issue is with the poor menu design. There can be a scroll bar inside a scroll bar when the menu drops down. In other words, the bottom-most menu items aren’t visible unless you position your mouse just perfectly next to the visible scroll bar. You’ll then see inner scroll bar and able to scroll down to see other menus. This took many hours of remote support and then more time after being escalated to Dev. It was really quite surprising that Support was not aware of this.
Agreed. Thank you for your assistance.
I think I know what you mean → the step #1.2.5 shown on this site https://shabaztech.com/installing-and-configuring-dfs-n-on-windows-server-2016/ You’re wanting to point “Local path of shared folder:” to \\<NutanixFilesCluster>\Share right? Whatever server you want to make the DFS-N namespace server has to support certain APIs… I think that’s where this gets kind of tricky. https://docs.microsoft.com/en-us/windows/win32/dfs/distributed-file-system-dfs-functions “Targets on computers that are running Microsoft Windows can be published in a DFS namespace. You can also publish any non-Microsoft shares for which client redirectors are available in a DFS namespace. However, unlike a share that is published on a server that is running Windows Server, they cannot host a DFS root or provide referrals to other DFS targets.” I think I get it now. Copy the files to the Nutanix files share Add the folders to the namespace as targets Remove the non-nutanix file targets that hold the d
Hi @DenaliDan We migrated to Files from another NAS like system. To my knowledge (and I could be wrong) Nutanix Files can only be a DFS-N folder target, not a namespace server… Searching their latest 3.6 documentation & release notes, I didn’t find any references for a namespace server migration or support. To be 100% I’d recommend calling support... Add new Namespace server(s) to each namespace - (Windows Server) (wait ‘til clients refresh/pickup new namespace servers) Replicate data (& verify) - Depending on amount of data, this could be going on in the background before cutover Add new folder target (shares on Nutanix Files) but leave their state Disabled Maintenance window Disable old folder target (if this can be offline at all) Replicate one last time & verify data is identical Enable new Folder target on Nutanix Files Disable old Folder target Thanks for that, DavidN. The first step you mentioned, “Add new Namespace server to each namespace” is the stumbling
I had this same issue. Glad to see it will be resolved when NCC 3.5.2 is available. Thanks
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
