Troubleshooting using Remote Power Shell on FSx for Windows File Server
You can administer your FSx for Windows File Server file systems using custom remote-management PowerShell commands.
Topics
New-FSxSmbShare command fails with one-way trust
Amazon FSx does not support executing the New-FSxSmbShare
PowerShell command in cases where you
have a one-way trust and the domain in which the user resides is not configured to trust the domain associated with Amazon FSx file system.
You can resolve this situation using one of following solutions:
The user executing the
New-FSxSmbShare
command needs to be in the same domain as the FSx file system.You can use the fsmgmt.msc GUI to create shares on your file system. For more information, see Managing file shares with the Shared Folders GUI.
You can't access your file system using Remote PowerShell
There are a number of potential causes for being unable to connect to your file system using Remote PowerShell, each with their own resolution, as follows.
To first ensure that you can connect successfully to the Windows Remote PowerShell Endpoint,
you can also run a basic connectivity test. For example, you can run the
test-netconnection endpoint -port 5985
command.
The file system's security group lacks the required inbound rules to allow a remote PowerShell connection
The file system's security group must have an inbound rule that allows traffic on port 5985 in order to establish a Remote PowerShell session. For more information, see Amazon VPC Security Groups.
You have an external trust configured between the Amazon managed Microsoft Active Directory and your on-premises Active Directory
In order to use the Amazon FSx Remote PowerShell with Kerberos authentication, you need to configure a
local group policy on the client for forest search order. For more information, see the Microsoft documentation
Configure Kerberos Forest Search Order (KFSO)
A language localization error occurs when trying to initiate a remote PowerShell session
You need to add the following -SessionOption
to your command: -SessionOption (New-PSSessionOption -uiCulture "en-US")
Following are two examples using -SessionOption
when initiating a remote PowerShell session on your file system.
PS C:\Users\delegateadmin>
Invoke-Command -ComputerName
Windows Remote PowerShell Endpoint
-ConfigurationName FSxRemoteAdmin -scriptblock {fsx-command
} -SessionOption (New-PSSessionOption -uiCulture "en-US")
PS C:\Users\delegateadmin>
Enter-Pssession -ComputerName
Windows Remote PowerShell Endpoint
-ConfigurationName FsxRemoteAdmin -SessionOption (New-PSSessionOption -uiCulture "en-US")