Then, in the section of task scheduler I also check the box "Run with highest privileges", though I don't know whether that would be necessary in your case.
Main Topics
Browse All TopicsI am trying to manually install the SCCM client on remote machines (can't do it through the SCCM console, I've tried). I've made the batch file listed below; it runs fine under the local administrator account, but does not run when a normal user is logged in. I've tried running this remotely through the command line using psexec, but am not having luck with it either.
It would be nice to be able to run this batch file remotely, silently, so I don't have to log off any users, etc. Best case is that I can run it through psexec using a .txt file with all of the computers that need it.
Maybe a .vbs file would work better?
I am open to any ideas on how to execute this process.
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
psexec in fact does run as the user running the command window that initiated the command. I use this command almost daily to run either command shells, batch or vbscripts, etc on remote computers. I've learned some about its behavior from watching the results.
Basically, psexec copies itself to the ADMIN$ share on the remote computer. It then installs a service on the remote computer, and runs that service, which is the copied file. This then executes the command that you specified in the psexec command line.
So, with that in mind, the user running psexec from the command line needs to have admin rights to the remote computer. You can bypass this requirement by using the "-u" parameter, and specifying a domainname\username. Domainname can be the remote computer's name if you have a local user. By putting in just the -u parameter, you'll then be prompted to type in the hidden password.
Once running on the remote computer, psexec will function in one of three ways:
1 - If no special parameter used, will run in the same user account as the person initiating the psexec command.
2 - If the "-u" parameter is used, it will run as that user.
3 - If the "-s" parameter is used, it will run as a local system account
In either of these 3 cases, you first have to have admin rights to use the ADMIN$ share and install a service.
When domain membership is broken on a computer, I'll frequently use a command line like this:
psexec -u COMPUTERNAME\Administrator
This will allow me to have local admin rights by connecting to the remote computer as the local administrator account. It will also run the cmd.exe command as the local admin account.
Business Accounts
Answer for Membership
by: netcmhPosted on 2009-09-01 at 08:00:59ID: 25232258
You're running this as a batch file executed by psexec on a remote computer with the admin creds, right?