It's just a known thing/bug/feature with psexec. -- Espi
On Tue, Jul 18, 2017 at 7:58 AM, Michael Leone <[email protected]> wrote: > On Tue, Jul 18, 2017 at 10:42 AM, Micheal Espinola Jr < > [email protected]> wrote: > >> This is likely because you needed to escape the quotes with backslashes. >> But since you didnt need them at all, that worked too. >> > > > Why would the quotes have needed to be escaped at all, tho? The quotes > don't need to be part of the actual passed parameters. Then again, once the > parameter part of the invocation is reached, everything after that is > presumed to be part of the parameters, I guess. Hence no need for quotes > anywhere, I guess .. > > > > >> >> -- >> Espi >> >> >> On Tue, Jul 18, 2017 at 7:22 AM, Michael Leone <[email protected]> >> wrote: >> >>> On Tue, Jul 18, 2017 at 9:54 AM, Melvin Backus <[email protected]> >>> wrote: >>> >>>> Try killing the quotes entirely. >>>> >>>> >>> >>> Well, what do you know , that was it .. >>> >>> C:\SysinternalsSuite>psexec -h \\dctrweb026 >>> c:\windows\system32\klist.exe -li 0x3e7 purge >>> >>> PsExec v2.11 - Execute processes remotely >>> Copyright (C) 2001-2014 Mark Russinovich >>> Sysinternals - www.sysinternals.com >>> >>> >>> >>> Current LogonId is 0:0xa28ef9e >>> Targeted LogonId is 0:0x3e7 >>> Deleting all tickets: >>> Ticket(s) purged! >>> c:\windows\system32\klist.exe exited on dctrweb026 with error code 0. >>> >>> Thanks so much! Now for the 2nd command (gpupdate /force"). That should >>> update everything from the new GPO settings, without having to wait for >>> scheduled refresh. >>> >>> >> >
