How to cause workstations on network to install msi package?

Question

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?

score 1 · Answer 1 · answered Jan 14 '13 at 06:54

1

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

http://support.microsoft.com/kb/816102

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

answered Jan 14 '13 at 06:54

TomTom

50,857
7
52
134

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 07:07
Domain. Pretty much all higher admin functions in windows and for windows are made for domains. – TomTom Feb 13 '13 at 07:10

score 0 · Answer 2 · answered Apr 08 '15 at 20:53

0

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.

answered Apr 08 '15 at 20:53

Simon Catlin

5,222
3
16
20

pylover · Answer 3 · 2013-01-14T06:49:41.837

-2

You have three options:

But i recommend you to use psexec, because its so easy and stable.it 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 computer.it 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]

EDIT 1:

On unix based workstations, you may use WINEXE instead.

edited Jan 14 '13 at 06:49

answered Jan 14 '13 at 06:36

pylover

708
3
9
15

2

-1. THere are 4 optiosn. Nr 4 is simply Publishing it in the Group policy as published application. – TomTom Jan 14 '13 at 06:53
1

With `psexec` do you have to know the username/password of the remote computer? – CJ7 Jan 14 '13 at 07:05
Does your option 2 require there to be a Active Directory domain? – CJ7 Jan 14 '13 at 07:10
SMS was rebranded to SCCM over a decade ago. – MDMarra Mar 09 '15 at 12:51

How to cause workstations on network to install msi package?

3 Answers3