BatchPatch Forums Home › Forums › BatchPatch Support Forum › Remote Execution – cannot find/fails to create output log
- This topic has 1 reply, 2 voices, and was last updated 5 years, 7 months ago by doug.
-
AuthorPosts
-
April 3, 2019 at 2:26 pm #8693notnAPParticipant
I’m failing on one fresh Windows 7 workstation.
Remote execution is not creating the expected output files in C:Program FilesBatchPatch
It is successfully creating the directory, but when trying to run a simple remote execution (in this case, “wmic bios get serialnumber”) no batchpatch files are created, and the output folder remains empty.
The command can be run by executing psexec \target wmic bios get serialnumber from the system running batchpatch (\bpSystem).
All other batchpatch built in commands that I’ve tried have succeeded (get Mac addy, get hostname, get OS version, download WSUS updates, install updates, reboot…)
Only the remote executable fails.
The remote code works on all (100+) other systems I’m using batchpatch to manage.
I’ve tried:
– reboot to clear the decks
– Looking for instances of psexec.exe on the target. Cannot find any.
– “sc.exe stop psexesvc” and “sc.exe delete psexesvc” on \target report that no such service exists
– checking to make sure file and printer sharing firewall access is enabled on \target
– checking to make sure wmic (WMI-In) firewall access is enabled on \target
– \targetc$ and \targetadmin$ can been accessed from \bpSystem
– temporarily disabling the windows firewall on \target
– deleting the folder \targetCProgram FilesBatchPatch and running the remote code from \bpSystem causes the folder to be recreated, but nothing ever gets placed into that folder.
output log on batchpatch:
Wed-10:07:51> Remote Command (logged output): Exit Code: 1
Wed-10:07:50> Remote Command (logged output): Executing \target -s
Wed-10:07:50> Remote Command (logged output): Establishing connection…
Could not find file ‘\targetC$Program FilesBatchPatchBatchPatchRemoteProcessOutput1702163417.log’.
\target is a fresh install of Windows 7 SP1, fully patched
FWIW, the system was previously the same OS install, and batchpatch successfully managed it with remote executions working before the OS was wiped and a fresh OS was installed.
\bpSystem (the system running batchpatch) is also Win 7 SP1, fully patched
There is no NSA firewall between \bpSystem and \target
I’ve searched the forum and found a number of similar threads, suggesting the solutions I’ve tried. But I’ve seen no effect on any of them yet.
Any more ideas?
Thanks!
April 3, 2019 at 5:46 pm #9849dougModeratorYour log illustrates the problem at this line:
Wed-10:07:50> Remote Command (logged output): Executing \target -s
You are executing an empty/blank/non-existent command. You are not executing ‘wmic bios get serialnumber’ as you think, else we would see the command in that line. I’m not quite sure where you’re going wrong, but hopefully this helps you figure things out. Maybe you are creating the command under Remote command logged output 1 but then executing Remote command logged output 2? Maybe you created a saved remote command but you only gave it a title but didn’t give it command syntax to execute? Seems like the issue has got to be something similar to that where you just aren’t properly executing the command, so you end up submitting a blank command instead.
-Doug
-
AuthorPosts
- You must be logged in to reply to this topic.