Error Code: [68:174] Failed to install File System Core Package, the credentials entered may not have permission to use WMI on remote machine. Please check WMI configuration and user credentials.

When you receive this error message, it is commonly related to the fact that the Windows Management Instrumentation (WMI) port on the destination client is either not defined (so it's not listening to incoming requests) or that the destination client is configured to deny WMI service requests. WMI initiates connectivity on TCP port 135 and maintains its connection by moving through a wide range of dynamic ports. WMI runs as part of a shared service host with ports assigned through DCOM by default.

Symptoms

This error could additionally expand out to other remote service ports so please confirm that these following ports are configured and acceptable through the client's Windows Firewall as well:

Port 135 for DCOM (Distributed Component Object Model).
Port 139 for NetBIOS Session Service (if you are using legacy Windows computers (Windows NT and prior)).
Port 445 for SMB (Server Message Block) file sharing.

Resolution

How to confirm WMI Connectivity Issues?

You can even test WMI connectivity by leveraging the "wbemtest" utilizing the command prompt on your CommServe. Here is a link as to How to leverage the WBEMTest tool

How to define a fixed port for WMI?

You can set up the WMI service to run as the only process in a separate host and specify a fixed port. The following procedure is an automated setup to allow WMI to have a fixed port

Lastly, you'll always want to confirm that the Active Directory User Account being leveraged for the remote install has proper permission over the remote client to even be able to perform the installation of the software. Please additionally refer to KB 50088 for additional guidance around installing a Windows File System Client as the issue is commonly related to Windows Firewall (locally to the remote client) or a Firewall Device (blocking traffic over these ports).