Network Management O & M requires clever use of group policies to complete tedious work

BKJIA exclusive Article] It is a headache when O & M personnel encounter tedious Application Layer configuration and maintenance. In fact, group policies in Microsoft products can help us solve this headache.

In the face of the application layer, we need to deploy more business servers, which must be in line with the parent company, accept its supervision and monitoring. At the network level, we must comply with the IT policy of the parent company, the architecture and performance must strictly meet the requirements. For the security layer, from the solidification of a single server to the secure deployment of the entire network, it must be fully implemented.

However, these aspects seem to be easy to solve. You can simply operate the server in the data center by clicking the mouse or editing commands, the difficulty is that thousands of terminal computers in the network must meet the IT policy of the parent company. This is another headache for it o & M personnel. If each terminal computer is deployed once, I am afraid it will delay a lot of time. At this time, we can ask for group policies to help.

A) Unify the enterprise Logo group policies to help

We must follow the arrangement of the parent company in terms of IT security policy and synchronize with the parent company in terms of corporate culture. The first thing we need to change is the desktop background and Screen Protection Program of the terminal computer.

This setting is relatively simple, and employees can set it on their own. However, the computer operation level of employees is uneven, and some users will not set it. On the other hand, it is difficult for new employees to find background pictures and screensaver, in this case, we can turn to the Group Policy to force the push from the server. Its policy is very simple.

Desktop background settings:

1. Create a shared folder on the file backup server to store the desktop and screen saver that reflect the corporate culture. The shared folder name is logo. the desktop background file name is wall.jpg, and the screen saver file name is screen. scr ";

2. log on to the domain controller, start the "Active Directory users and computers" program, find the OU for which you want to set the Group Policy, and enable the Group Policy Options, select "user configuration"> "management module"> "Desktop"> "Active Desktop", locate the "enable Active Desktop option" attribute, and enable it;

3. Select the "Active Desktop Wallpaper" attribute, select "enabled", and add the "wallpaper name" to the shared file \ 192.168.1.100 \ logo \ wall.jpg 192.168.1.100 ), select "stretch" for the wallpaper style. See figure 1)

Figure 1

4. After the Group Policy is set up and takes effect, find a client and restart the computer. The desktop is changed.

Screen Saver settings:

1. Select the OU you want to set, start the Group Policy Editor, and find "user configuration"> "management module"> "Control Panel"> "display ", set "Screen Saver" to "started ";

2. Set "executable screen Saver name" to "started", and enter the shared screen Saver address and file name in the text box, \ 192.168.1.100 \ logo \ screen. scr, OK;

3. After the Group Policy takes effect, you can view the effect on the client.

The simple setting can reduce a lot of repetitive work, and the role of group policy is indispensable.

B) group policies for large-scale software deployment

After the enterprise culture is unified, what needs to be done next is information security compliance. for clients, the first thing is the replacement of anti-virus software.

For anti-virus software earlier, we used the server-side anti-virus software management platform to push IT down. uninstalling IT can also be solved on the server. it o & M personnel do not have to operate on various terminal computers, the new anti-virus software is an installation package, which is troublesome during the installation process. In this case, we can apply a group of policies for batch deployment.

The file format that can be assigned or distributed by the Group Policy is the ZAP or MSI installation package file. If the file to be deployed is in EXE format, we can convert it to an MSI file through WinINSTALL2003, after the conversion, you can proceed to the next step.

1. Create a shared folder on the file backup server to store the software to be deployed. The shared folder name is soft. If you are worried that the contents of the folder may be illegal, you can hide the shared folder, add the $ symbol after the shared name. Place the prepared MSI installation package in the shared folder by deploying nod32.msi;

2. log on to the domain controller, find the OU for which you want to set the Group Policy, open the group policy options, and select "Computer Configuration"> "software Settings"> "software installation ", select New "package" in the window on the right, browse to the file "nod32.msi" to be assigned, and then select "assigned" in the deployment method ";

3. restart a computer under policy control. When the computer is restarted, the NOD32 antivirus software installation prompt is displayed, as shown in Figure 2. Wait a moment and the software is installed.

Figure 2

How can we make our work much easier with the help of group policies.

BKJIA exclusive Article. For details about the cooperation site, please indicate the original author and source .]