I am using PsExec to start an application under the system account:
psexec -i -s -d cmd.exe /c c:\far\far.exe
This form works fine with PsExec 2.20 but fails with "Error creating key file on <COMPUTERNAME>. The network name cannot be found" error on all newer versions that I could find, including 2.34. Now I am not too surprised that I get a network-related error because my firewall is set up to prevent most network access and since I removed the administrative shares, but I don't see a reason why running a process under the system account should require a network access - and apparently it doesn't since PsExec version 2.20 can run the command just fine. I can only assume that the change was done to facilitate some network-related stuff, which is just fine if someone needs it, but is there a way to make PsExec work in the local-only fashion as it used to?