The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.
Hi all,
I am currently deploying and RN15/FlexDeply locally at a client site.
I have configured Windows credentials and performed validations against several Windows servers with different AD credentials and get the same failures each time.
I am getting failures when the RN150 is trying to perform cmd.exe commands on the Windows servers.
When I RDP to the remote server and run cmd.exe locally it works fine and I can perform the required 'netstat -anop TCP' and 'ipconfig /displaydns' commands.
Using 'AD Account 1' - RN150 failures seen as in the attached txt file. If I RDP to the server and login with this AD account locally on the remote server, I 'cannot' run cmd.exe. I get a message saying 'cmd.exe is disabled by administrator. I suspect this is the cause of the RN150 failures.
So, I tried another AD account with higher privileges and a member of 'Domain Admins'. The RN150 still gives me the same failures! Yet when I RDP to the remote windows server this account can run cmd.exe locally and I can run the netstat and ipconfig commands successfully.
Question: Has anyone come across this issue where it seems that the RN150 is being refused to run cmd.exe on the Windows servers and if so, what was done to resolve it?
See attached files.
Cheers,
Darren
Apr 30, 2020 03:49 AM
Apr 30, 2020 04:51 AM
Apr 30, 2020 04:51 AM
Another item that can cause this issue is where one NIC on a server will permit remote commands, but when testing the credential to another NIC, the remote commands will fail. We recommend testing to each interface on the server to also verify.
May 08, 2020 03:02 PM