Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have remote access to a Windows Small Business Server 2008 machine. There are about 5 workstations connected to this network.

How can I make every workstation install an .msi package without having to remotely connect to each workstation?

share|improve this question

Have you simply considered using your active Directory to publish the application via a Group Policy?

explains how to do it (and no, I will not Quote a 2 page Long checklist of steps to do).

share|improve this answer
Can this method cause the application to be published to all workstations on a per-machine basis and does this require a domain? – CJ7 Feb 13 '13 at 7:07
Domain. Pretty much all higher admin functions in windows and for windows are made for domains. – TomTom Feb 13 '13 at 7:10

PsExec... erk. OK for v-small environments, but doesn't scale into the enterprise. Seen plenty of bombed PSExec child processes / residual PSExecSvc services.

If AD based deployment isn't an option, and the clients are Win7/8, use WinRM.

share|improve this answer

You have three options:

  1. Windows logon script
  2. Miscrosoft Systems Management Server
  3. PsExec

But i recommend you to use psexec, because its so easy and has working for me about 3 years without any problem. the main role of psexec is to execute a command remotely on another computer, even the executable does not exists on remote may copy executable on remote computer and then executes it.

Usage: psexec [\\computer[,computer2[,...] | @file][-u user [-p psswd]][-n s][-l][-s|-e][-x][-i [session]][-c [-f|-v]][-w directory][-d][-<priority>][-a n,n,... ] cmd [arguments]


On unix based workstations, you may use WINEXE instead.

share|improve this answer
-1. THere are 4 optiosn. Nr 4 is simply Publishing it in the Group policy as published application. – TomTom Jan 14 '13 at 6:53
With psexec do you have to know the username/password of the remote computer? – CJ7 Jan 14 '13 at 7:05
Does your option 2 require there to be a Active Directory domain? – CJ7 Jan 14 '13 at 7:10
SMS was rebranded to SCCM over a decade ago. – MDMarra Mar 9 '15 at 12:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.