Remote Installation of Windows Software

Group PolicyThe idea of deploying software is to deploySoftwareStored in the shared folder of the file server, and then told the user and the computer through the Group Policy. The XX folder of the XX server has the software to be installed. download and install the software. In this way, we only need to set the Group Policy, we can wait for the client to automatically execute the softwareRemote InstallationYou do not need to deploy the client one by one. The following describes how to remotely install the windows software based on the above principles.

In the past, I always had to install applications directly on each computer, at least to say that this was a very time-consuming job. Later, I started to use Dameware in Windows to help me install applications remotely. The software is expensive and hard to use.

Then, with the release of Windows XP Professional Edition, the system comes with the Remote Desktop function. I can remotely log on to each machine to install Windows programs, but this is still very time-consuming. Now, I can automatically distribute applications to my computer and users so that users can obtain the required software no matter whether they are in my domain or not.

Next I will do a Remote Installation of WindowsMicrosoftOffice software, telling you how to do it.

First, the software you want to install remotely must have an MSI file for deployment. The MSI file is simply a Microsoft Installation tool. If you do not have one, you can create multiple methods. After obtaining the MSI file, we can create the required template to select the required options, which can help us set the installation process automatically.

When you have thousands of computers to handle and hundreds of thousands of computers each day, it is necessary to do so. Now we can deploy applications using OU or organization units.

First, open the Active Directory user and computer account.

Select the application to which you want to deploy the application, and right-click the OU and select Properties.

Click the Group Policy tab in the upper-right corner of the window, and then click to open the management interface.

Whether you click a computer or user in OU, you will get a response. That is to say, they will deploy the software to themselves.

Next, return to the screen below.

This is the group policy management interface. The OU you selected prior to the two steps is highlighted on the left, and any policy assigned to it is displayed on the right panel. You can see that I have a GPO Group Policy object called OfcStd, which is short for my OfficeStandard.

This group policy distributes the Office2003 Standard Edition to all computers in the OU. Now let's start from scratch to see how it works.

Right-click the OU and choose here to create and connect a GPO.

This will guide you to a screen named GPO, as shown below.

Give your GPO an easy-to-understand name. I named myself as a test software installation. This will take us back to the same screen and add the newly added empty GPO. You need to right-click and select edit.

Click Edit to open the Group Policy object editor. Based on whether you want to distribute the software to a computer or whether the user's computer will always be installed on the same machine, and the user will follow the machine in use ), expand Computer Configuration → software settings or user configuration → software settings, as shown below.

Click the software installation item in the software settings folder and you will see the following.

Right-click the right panel and choose new> software package, as shown in.

Select Office2003 to install the STD11.msi file in the quasi version. That's easy! You have learned how to deploy the first software installation package. Imagine how much time it will save if you use it properly!

If you select user configuration, you can log on to one of the users for testing. If you select the computer configuration, You need to log on to one of the OU computers. Sometimes you need to restart your computer or, in extreme cases, restart the computer twice to see the program installation. After you have successfully installed the application, you can directly log on to the system and see an interface to remotely install the deployed application. Is it cool?

Summary:

It is hoped that the method of deploying Windows software by using group policies for Remote Installation will be helpful to readers. more knowledge about group policies remains to be explored and learned by readers.