Microsoft Virtualization Discussions - Page 58

StevePutre · ‎2025-02-13

We found what appears to be a bug or unintended behavior with add-ncnfsservice. We want to create a new NFS service configuration on a vserver, but we want to have NFSv4.0 and NFSv4.1 disabled; only NFSv3 enabled. We first obtain a default configuration: $nfs_config = get-NcNfsService -template If we examine the template values, we can see that NFSv3 is enabled and NFSv4 is disabled: (I have shortened the output but I have attached the full output to my post) PS> $nfs_config Vserver GeneralAccess IsNfsv3 IsNfsv4 IsNfsv41 DefaultWindowsUser ------- ------------- ------- ------- -------- ------------------ True True False False Using this template, I create a new NFS service on my SVM: PS> add-NcNfsService -vservercontext XXXXXX -attributes $nfs_config Vserver GeneralAccess IsNfsv3 IsNfsv4 IsNfsv41 DefaultWindowsUser ------- ------------- ------- ------- -------- ------------------ XXXXXXX True True True True If I go to the OnTAP CLI and perform a "nfs show", it shows that v4.0 and v4.1 are enabled, which is not the desired config. Please comment and provide a resolution for this.

TMADOCTHOMAS

I just upgraded the PowerShell Toolkit from 9.15.1.2407 to 9.16.1.2410. As it seems to happen with nearly every upgrade, it isn't working. First, what happened to install.ps1? That made installations super easy and now it's gone. Second, if I understand correctly, we should unzip the NetApp.OnTAP download, then unzip the underlying NetApp_OnTAP zip file, and finally copy the NetApp.OnTAP folder to the appropriate path, in our case "C:\Program Files (x86)\Netapp\NetApp PowerShell Toolkit\Modules" (that's where the existing folder is located). I tried copying on top of the existing folder and replacing files, and I tried deleting the original folder and replacing it with the whole new folder. In both cases, when I run Import-Module NetApp.ONTAP I get the following. Anyone know the cause? The file it lists (OntapiPS.dll) is in the location it lists. ------------------------------------------------------------ Import-Module : Could not load file or assembly 'file:///C:\Program Files (x86)\Netapp\NetApp PowerShell Toolkit\Modules\NetApp.ONTAP\OntapiPS.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) At line:1 char:1 + Import-Module NetApp.ONTAP + ~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Import-Module], FileLoadException + FullyQualifiedErrorId : FormatXmlUpdateException,Microsoft.PowerShell.Commands.ImportModuleCommand --------------------------------------------------------------

PowerShellToolkit

Please let me check the system requirements for using PowerShell Toolkit 9.16.1. The Windows 2022 server on which I plan to install the PowerShell Toolkit currently has .NET Framework 4.8 installed. Will it only work with .NET Framework 4.7.2, which is listed in the system requirements? I would like to know if it will work with .NET Framework 4.8. I have confirmed that the installation URL for the NetApp.ONTAP PowerShell Toolkit contains the following information: https://mysupport.netapp.com/site/tools/tool-eula/ontap-powershell-toolkit Operating System Version Microsoft Windows PowerShell 5.1 or 7.3.4 or later Microsoft .NET Framework .NET Framework 4.7.2 Microsoft Windows 8.1, 10, Server 2012 R2, 2016, 2019, 2022 Microsoft Windows 8.1,10, Server 2012 R2, 2016, 2019 ,2022

PowerShellToolkit

PowerShell Toolkit 9.16.1を使用するためのシステム要件について確認させてください。 PowerShell Toolkitをインストール予定のWindows2022サーバは現在.NET Framework 4.8が導入されていますが、システム要件に記載がある.NET Framework 4.7.2 以外は動作しないのでしょうか？ NetApp.ONTAP PowerShell ToolkitのインストールURLに下記記載があるのは確認済みとなっております。 https://mysupport.netapp.com/site/tools/tool-eula/ontap-powershell-toolkit Operating System Version Microsoft Windows PowerShell 5.1 or 7.3.4 or later Microsoft .NET Framework .NET Framework 4.7.2 Microsoft Windows 8.1,10, Server 2012 R2, 2016, 2019 ,2022

Enagon · can't optain cifs options using RestAPI on pstk 9.16.1.2501

i'm trying to get all cifs options from a svm via pstk (9.16.1.2501) using option -ZapiCall gives me all the options with values. Without this option there are only some options populated with settings, for most of them i see the value false. studying the help for the command didnt reveal how to do this via rest. Any help is appreciated.

Board Activity

PSTK cmdlet add-ncnfsservice is not creating correct service properties

PowerShell Toolkit Won't Upgrade

System Requirements for PowerShell Toolkit 9.16.1

PowerShell Toolkit 9.16.1のシステム要件について

can't optain cifs options using RestAPI on pstk 9.16.1.2501