Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This article describes how to use Group Policy to automatically distribute programs to client computers or users. You can assign a program distribution to users or computers.
If you assign the program to a user, it's installed when the user logs on to the computer. When the user first runs the program, the installation is completed. If you assign the program to a computer, it's installed when the computer starts, and it's available to all users who log on to the computer.
When a user first runs the program, the installation is completed. You can publish a program distribution to users. When the user logs on to the computer, the published program is displayed in the Add or Remove Programs dialog box, and it can be installed from there. Windows Server Group Policy automated-program installation requires client computers that are running Microsoft Windows or a later version. To publish or assign a computer program, create a distribution point on the publishing server by following these steps:.
To assign a program to computers that are running Windows Server , Windows , or Windows XP Professional, or to users who are logging on to one of these workstations, follow these steps:.
Click the Group Policy tab, select the policy that you want, and then click Edit. Thank you dbeato, going to talk this over with my co-workers and may make this part of our Standards and Practices. In this case you need something more robust, which can report on each computer installation state and retry failed installations. I recommend using Action1 to install software remotely on multiple computers.
To continue this discussion, please ask a new question. Laplink Software, Inc. Neil Laplink. Get answers from your peers along with millions of IT pros who visit Spiceworks. All, I want to install an. I am a bit confused on the psexec command for this. Do I have this right? Thanks and much appreciated! With our admin command shell, we're going to enter the wmic command followed by enter.
WMIC's install call allows compatible WMI applications to be installed with no interaction from the user they see nothing, the program is simply installed according to the default installation parameters you or the product packager have specified. Here's the rub: individual MSI packages will have different "options" the second input required in the install call as shown in the attached screenshot.
To simplify our example, we're installing from an MSI that requires no options. To which we must answer yes y to confirm. Method execution successful. Which will iterate through the list in computers. As indicated in the introduction, we must have the MSI and installation files located on the remote computer's local hard-disk for this method to work. In most situations, this isn't preferable - it would be ideal to install from a network drive.
Unfortunately without advanced scripting using delegation techniques for mapping network disks , this is not possible. The reasons for this stem from WMI's need to run as in this case a domain admin and WMI's inability to negotiate a network drive's connection by this domain admin ID without some security concerns. There are work-arounds Hopefully you've been intrigued by the potency of WMIC This is great.
I'm having a little problem though. I'm getting the following error when trying to install a program. Please advise. Oh, I can uninstall a program, just not install one through wmic. Mike, sorry I didn't see this until now. Which asks msiexec to attempt a silent, admin install of your msi package
0コメント