How to use WMIC is a batch file to trigger SCCM actions?

Hello All,
    First a little background:  I have the Right-click tools installed.  However, it doesn't work on all my subnets - make that most of my subnets.  That is, if for example, I try to initiate a Machine Policy Retrieval & Evaluation Cycle Action, it will work on clients in a particular subnet, but fail wit hthe "RPC server unavailable..." error on others.
   So, I was thinking of using PSExec to copy a batch file to a problem client and run the command using WMIC:
WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000022}" /NOINTERACTIVE
The problem is that when I try it, it actually connects and inputs the command, but sits there.  As soon as I use Control+C (Exit won't kill the session), the command is triggered and I get the desired result.
So, I'd liek to ask how can I write the batch file so the actually kicks off the TriggerSchedule action?  I've looked at other batch files that use the WMIC, but don't seee any extra commands that could give me a clue.
Also, trying to get the issue of what's stopping the tool on those subnets solved is a non-starter for the moment.  It'd take many months (if ever) to get it done, from what I am seeing.
Thanks,

Why complicate it with PSEXEC? WMIC does remote on its own.
WMIC /node:Computername /namespace:\\root\ccm blah blah blah

bmason, that was my first thought, as well.  But, the command returned the same "RPC server unavilable" error.   I think that on some of these subnets, any attempt to connect directly to WMI on the clients is blocked.  I get the same behavior and error when trying to use SCCM Client Center as well.
   So, I figured, it I had a way to run the command locally on the target, that it might work.  Clunky? Yes, but at least I'd be able to reach these clients and get what I want done.

Maybe remote into one and hit the rest from there.  I wonder what all they're blocking.  Also, do you run a GPO health startup script?

Maybe remote into one and hit the rest from there.
I can't do that since the users cannot be "disturbed".
 
I wonder what all they're blocking.
So do I.  But, trying to get to the root cause would take me forever, so that is why I am looking for a viable workaround.
 
Also, do you run a GPO health startup script?
No, they don't have one running in the environment.  That is another thing I am trying to get added.  Also trying to get them to use SC Software Updates Manager.
 
That said, any ideas of how I can get this little script to work?  Again, the script connects to the remote PC, but it won't run until I press Control+C to abort it.  Otherwsie, I just see the command line and nothing  happens.

you could psexec to one of them remotely and get their command prompt and hit the rest with out bothering the user.
psexec -u account -p password cmd.exe /c cmd.exe
then run your batch.