asked on

SCCM Heart Beat

I have a short script I'm trying to push out to my domain computers that uses psexec to force each of the machines to updated their SCCM heart beat. when I ran it I got an error that said: " 'psexec' is not recognized as an internal or external command,
operable program or batch file. "My script is fairly simple and my psexec and script are in the root of C: on the host computer. the script looks like:

C:\Windows\system32>psexec \\<computername> -u <domain\adminusername> -p <password> WMIC/namespace:\\root\ccm path sms_client CALL TriggerSchedule '{0000
0000-0000-0000-0000-000000000003}'

when I run the WMIC from command line on my local computer it works just fine, when I try to script it, not so much.

please assist.

Joseph Daly

Have you tried the WMIC /node:"computername" switch

This should take psexec completely out of the equation.

AlfonsoPina

ASKER

no but I'll try it now as a matter of fact

AlfonsoPina

ASKER

well, I'm still getting invalid parameter. the fact is that I simply don't want to walk around to 120 desktops and update the SCCM heartbeat. I was trying to do it this way but if you have a better suggestion, so be it.

ASKER CERTIFIED SOLUTION

merowinger

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

AlfonsoPina

ASKER

well, that got me closer, now I just get this error:

'0000-0000-0000-0000-000000000003}'"' is not recognized as an internal or extern
al command,
operable program or batch file.

AlfonsoPina

ASKER

found my error there, i had word wrap on when I pasted it and it cut off 4 of the "0's" but now I'm getting:

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com

Executing (sms_client)->TriggerSchedule()
ERROR:
Description = Access denied
cmd exited on sddc05wk842d209 with error code -2147217405.

AlfonsoPina

ASKER

actually, with one little change to this statement I was able to get it to work. it appears that our network has some sort of security measure that blocks my credentials the way I put them in. so this one worked.