JP2985809B2 - How to install client components - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client component for automatically installing a client component on a client in a computer network system in which a domain including a plurality of servers as domain controllers and the client are connected via a network. How to install.

[0002]

2. Description of the Related Art In recent years, a computer network system in which a domain including a plurality of servers serving as a domain controller and a client are connected via a network such as a LAN has been put to practical use. As such a computer network system, for example, Windows
There is a client / server system with WS NT.

In a client / server system based on Windows NT, a client component is automatically installed in a client when the client joins a domain.
Conventionally, this has been done as follows. When a client issues a logon request to a domain, one domain controller in the domain accepts the request and executes logon processing. In this logon process, the domain controller installs the client component prepared on the hard disk in its own device on the client that has issued the request (for example, “Microsoft S”).
systems Management Server Administrator's Guide, "pp. 97-98, 1st print issued on March 1, 1995, Microsoft Corporation).

[0004]

According to the conventional technique described above, one domain controller in a domain accepts a logon request from a client, and the domain controller that accepts the logon request installs a client component on a requesting client. I am trying to do it. For this reason, it is necessary to prepare the client components in all the domain controllers in the domain, and there is a problem that a large amount of the hard disk in each domain controller is consumed to prepare the client components.

Accordingly, an object of the present invention is to provide a client component installation method that can install a client component on a client without preparing a client component in all domain controllers in a domain. .

[0006]

SUMMARY OF THE INVENTION In order to achieve the above object, the present invention provides a computer network system in which a domain including a plurality of servers serving as domain controllers and a client are connected via a network.
Prepare a client component to be installed on the client in a specific server specified by an administrator among servers connected to the network, and provide a client prepared in the specific server to each server serving as the domain controller. A logon script describing a process for installing a component by a client is prepared, and a server that has received a logon request from the client among the servers serving as the domain controller is the logon script prepared in its own server. The requesting client is notified of the script, and the requesting client installs the client component prepared in the specific server on its own client according to the notified logon script.

Further, in the present invention, the logon script determines whether the client component has been installed in order to prevent the installation process from being performed many times on the already installed client component. The client that has made the logon request, including the description of the processing, determines whether or not the client component has been installed according to the notified logon script, and is prepared in the specific server only when it is determined that the client component has not been installed. Install the client component on the local client.

The present invention also provides a computer network system in which a domain including a plurality of servers serving as domain controllers and a client are connected via a network in order to reduce the load on a server serving as a domain controller. Prepare a client component to be connected to the network and to install a server on the server, the client component prepared for the server not included in the domain is provided to each server serving as the domain controller. A logon script that describes processing for installation by a client is prepared, and a server that has received a logon request from the client among the servers serving as the domain controller is a server of its own. The logon scripts that are prepared notifies the requesting client, requesting the client installs the client components being prepared on servers that are not a part of the domain in accordance with the notified logon script to the local client.

[0009]

Embodiments of the present invention will now be described in detail with reference to the drawings.

FIG. 2 is a diagram showing an example of a computer network system to which the client component installation method of the present invention is applied. In this computer network system, domains 1 and 2, clients 3 and 4, and a server 5 not included in the domain are connected to each other via a LAN 6.

The domain 1 includes a server 11 as a primary domain controller and a server 12 as a backup domain controller.

The domain 2 includes a server 21 as a primary domain controller and a server 22 as a backup domain controller.

FIG. 1 is a block diagram showing a configuration example of the server 11, client 3, and server 5 in the domain 1.

The server 11 in the domain 1 includes a domain user management unit 111-11, domain user management information 112-11, and a logon reception unit 113-11.
And a logon script storage unit 114-11.

The domain user management means 111-11 includes:
It has a function of changing and setting the domain user management information 112-11, a function of maintaining consistency of the domain user management information between the servers 11 and 12 in the same domain 1, and the like.

The domain user management information 112-11 includes:
As shown in FIG. 3, the information includes an account name of a user who can log on to domain 1, authentication information, and a process name (logon script name) executed at the time of logon. Here, the authentication information needs to be set for all account names, but the logon script name does not necessarily need to be set for all account names. In the example of FIG. 3, the authentication information for the account name USR1 and the logon script name are PASS, respectively.
1, LS1 indicates that the authentication information for the account name USR2 is PASS2.

The logon accepting means 113-11 has a function of accepting a logon request from a client and notifying the requesting client of a logon script.

Logon script storage means 114-11
, A logon script is registered.

The other servers 12, 21, 22 have the same configuration as the server 11, and in the following description, the domain user management means in each of the servers 11, 12, 21, 22 will be described. To distinguish between domain user management information, logon accepting means, and logon script storing means,
The components in the servers 12, 21 and 22 are denoted by reference numerals, respectively.
12, -21 and -22. Therefore, for example, when the domain user management information 112-22 is described,
This domain user management information represents the domain user management information managed by the server 22.

The client 3 has a log-on execution means 31-3 for executing a log-on process. Note that the client 4 also has the same configuration as the client 3,
In the following description, the logon execution means in the client 4 will be denoted by reference numeral 31-4 in order to distinguish the logon execution means in the clients 3 and 4.

The server 5 includes domain user management information operating means 51, component preparation means 52, and client component storage means 53.

The domain user management information operating means 51
Domain user management information 112-11, 112-12, 112-21, 11 in servers 11, 12, 21, 22
It has a function to operate 2-22.

The component preparing means 52 has a function of copying a client component to be installed on a client to a specified drive on a server specified by an administrator.

Client component storage means 53
Is composed of, for example, a hard disk and stores client components to be installed in the clients 3 and 4.

FIG. 4 is a flow chart showing a processing example of the domain user management information operating means 51 in the server 5, FIG. 5 is a flow chart showing a processing example of the component preparation means 52, and FIG. 6 is a flow chart showing the processing in the servers 11, 12, 21, and 22. Domain user management means 111-11, 111-12, 111-21, 111-
FIG. 7 is a flowchart showing a processing example of the server 22, and FIG.
Logon receiving means 113-11,1 in 21 and 22
FIG. 8 is a flowchart showing a processing example of logon execution units 31-3 and 31-4 in the clients 3 and 4, and FIG.
The operation of this embodiment will be described below with reference to the drawings.

The administrator of the system has clients 3, 4
When preparing a client component to be installed on a specific server, an instruction to prepare the client component is given to the domain user management information operating means 51.

When this instruction is received, the domain user management information operating means 51 displays a setting screen as shown in FIG. 9 on a CRT or the like (not shown) (S41 in FIG. 4). Thus, the administrator can use the displayed setting screen to set the server name of the server for preparing the client component,
Set the drive name and the domain name of the domain whose domain user management information is to be changed. When the setting is completed, an OK button on the setting screen is clicked. Now, for example, as shown in FIG. 9, the server name of the server for which the client component is prepared and the drive name of the drive are the server 5 and the drive C, respectively.
SERVER5 and DRIVEC are domain names DOMAIN1 of domains 1 and 2 as domain names of domains to be changed in the domain user management information 112.
It is assumed that DOMAIN2 is set.

The domain user management information operating means 51
When the OK button is clicked, a request is made to the component preparation means 52 to prepare a client component in the drive C of the server 5 set on the setting screen (S42).

Upon receiving this request, the component preparing means 52 sets the client component storing means 53
The client component is read from the server 5 and copied to the drive C of the server 5 (S51 in FIG. 5).

When the processing of the component preparing means 52 is completed, the domain user management information operating means 51
Servers 11 and 12 existing in domain 1 via N6
Requesting the acquisition of domain user management information from any one of the servers 2 and the server 2 existing in the domain 2
A request is made to either one of the servers 1 and 22 to obtain domain user management information (FIG. 4, S43). Here, the domain user management information 112-11 and 112-12 held by the servers 11 and 12 in the domain 1 are kept consistent by the domain user management means 111-11 and 111-12. , Server 2 in domain 2
Domain user management information 112 held by 1, 22
21 and 112-22 are domain user management means 111
21 and 111-22, the content obtained is the same even if a request to obtain domain user management information is made to any server in the same domain.

Now, for example, the domain user management information operating means 51 is connected to the server 1 in the domain 1 via the LAN 6.
Suppose that a request for obtaining the domain user management information 112-11 is made to the server 22 in the domain 2 and a request for obtaining the domain user management information 112-22 is made to the server 22 in the domain 2.

This request is received by the domain user management means 111-11, 111-22 in the servers 11, 22 (S61 in FIG. 6).

Domain user management means 111-11, 1
11-22 receives the request from the domain user management information operating unit 51 via the LAN 6 and requests that the domain user management information 112-11 and 112-22 be obtained (S62). Is YES),
The domain user management information 112-11 and 112-22 held by the servers 11 and 22 are transmitted to the domain user management information operating unit 51 (S63).

The domain user management information operating means 51
From the domain user management means 111-11 and 111-22 to the domain user management information 112-1 of the domains 1 and 2
When 1,112-22 is obtained (S44 in FIG. 4), it requests the domain user management means 111-11, 111-22 to change the domain user management information and the logon script (S45).

The process of S45 will be described in detail with reference to an example. Now, for example, in S44, the servers 11, 22
Domain user management means 111-11 and 111-2 within
It is assumed that the domain user management information 112-11 and 112-22 of the domains 1 and 2 obtained from the domain 2 are as shown in FIG.

Referring to FIG. 10, USR1 and USR2 are included in the domain user management information 112-11 of the domain 1.
Account name exists, and one account name U
The logon script name LS1 is set for SR1, but the logon script name is not set for the other account name USR2. In addition, the domain user management information 112-22 of domain 2 includes US
There are two account names R3 and USR4, and the logon script name LS2 is set for one account name USR3, but the other account name USR
No logon script name is set for No. 4.

After that, the domain user management information operating means 51 sets the domain user management means 111-11, 111
Domain user management information 112 sent from -22
Attention is focused on one of -11 and 112-22. Now, for example, the domain user management information 112-11 of the domain 1
Let's focus on

Next, the domain user management information operating means 51 requests the server 11 to set the logon script name LS3 for the account name USR2 for which the logon script name is not set, and also requests the account name USR1 for the account name USR1. Request that the contents of the logon script name LS3 be added to the set logon script name LS1, and further transmit the logon script name LS3.

Here, the logon script of the logon script name LS3 includes descriptions a to d for performing the following processing.

A. It is determined whether or not the client component has been installed. If the client component has been installed, the process ends. If the client component has not been installed, the processes described thereafter are performed. b. A connection request to the drive C of the server 5 set on the setting screen shown in FIG. 9 is made. c. A request is made to copy a client component prepared in drive C of the server 5 to a local directory. d. A request to disconnect from the drive C of the server 5 is made.

Domain user management information 11 of domain 1
When the processing of 2-11 is completed, the domain user management information operating unit 51 pays attention to the domain user management information 112-22 of the domain 2 sent from the domain user management unit 111-22 in the server 22.

Next, the domain user management information operating means 51 requests the server 22 to set the logon script name LS3 to the account name USR4 for which no logon script name has been set, and to the account name USR3. Request that the contents of the logon script name LS3 be added to the set logon script name LS2, and send the logon script name LS3. Thus, the process of S45 ends.

A request for changing the domain user management information and the like output from the domain user management information operating means 51 in the server 5 to the server 11 is received by the domain user management means 111-11 in the server 11 (FIG. 6, FIG. 6). S6
1).

The domain user management means 111-11 comprises:
When the request is received, the request is a request for a change of the domain user management information and the like (FIG. 6, S64: YES), and the process of S65 is performed.

In S65, the domain user management means 111-11 first stores the logon script of the logon script name LS3 sent from the domain user management information operation means 51 in the logon script storage means 11
4-11. Next, a logon script name LS3 is set for the account name USR2 in the domain user management information 112-11 according to the request sent from the domain user management information operating means 51. Next, it is checked whether or not the contents of the logon script with the logon script name LS1 requested to add the contents of the logon script with the logon script name LS3 are already included. Only when not included, the contents of the logon script name LS3 are added to the logon script name LS1 stored in the logon script storage unit 114-11.

A change request for the domain management information and the like output from the domain user management information operating means 51 in the server 5 to the server 22 is received by the domain user management means 111-22 in the server 22 (FIG. 6, FIG. 6). S6
1) The same processing as described above is performed.

By performing the above processing, the domain user management information of the domains 1 and 2 is as shown in FIG.

Thereafter, for example, when the logon executing means 31-1 of the client 3 issues a logon request to the domain 1 (S81 in FIG. 8), the logon request is accepted in the server 11 constituting the domain 1 This is accepted by the means 113-11 or the logon accepting means 113-12 in the server 12. The logon request includes an account name and authentication information.

For example, if the logon receiving unit 113-11 in the server 11 receives a logon request, the logon receiving unit 113-11 refers to the domain user management information 112-11, and It is determined whether or not the logon request is correct based on the authentication information in step 11 and the authentication information in the logon request (FIG. 7, S71, S72).

Only when it is determined that the logon request is correct (S72: YES), the logon accepting means 113-11 associates the domain user management information 112-11 with the account name included in the logon request.
The logon script name set therein is obtained, the logon script having the obtained logon script name is read out from the logon script storage unit 114-11, and the read logon script is read by the logon execution unit 31 in the client 3 that has issued the request. -3 is notified (S
73). Now, assuming that the account name USR1 is included in the logon request from the client 3, for example, the logon accepting unit 113-11 transmits the logon script with the logon script name LS1 to the logon execution unit 31- No. 3 (see FIG. 11).

Logon execution means 31 in client 3
-3, when notified of the logon script with the logon script name LS1, determines that the logon request has been accepted (YES in S82), and executes logon processing according to the notified logon script.

Here, the logon script of the notified logon script name LS1 includes the above-described descriptions a to d.
The following processing will be performed.

First, it is determined whether or not the client component has been installed. If it is determined that the server has been installed, the process is terminated.
Make a connection request to Next, a copy request to the local directory of the client component prepared in the drive C of the server 5 is made. Thereby, the client component prepared in the drive C of the server 5 is installed in the client 3. Thereafter, a request for disconnecting from the drive C of the server 5 is made.

In the above embodiment, the domain user management information operating means 51, the component preparation means 52, and the client component storage means 53 are provided in the server 5 not included in the domain. Servers 11, 12, 21, 22 in 1, 2
May be provided with each of the means 51, 52, and 53 described above. In this case, the server 5 becomes unnecessary. However, when the server 5 not included in the domain is connected to the LAN 6 and the client 5 is installed by the server 5 as in the embodiment, the load on the server serving as the domain controller is reduced, and the system Overall processing efficiency can be improved.

[0055]

As described above, according to the present invention, a client component to be installed on a client only on a specific server designated by an administrator is prepared, and a server in a domain that has received a logon request from the client is prepared. Since the logon script describing the process for installing the client component prepared on the specific server is notified to the client that has issued the logon request, the client component is prepared on all servers in the domain. You can install client components on the client without having to do this. As a result, it is possible to reduce server resources as compared with the conventional technology in which client components must be prepared in all servers in a domain.

Further, according to the present invention, a description of a process for determining whether or not the client component has been installed is included in the logon script, and the client component is installed only when the client component has not been installed. Therefore, it is possible to prevent the installation process from being performed many times on the already installed client component.

Further, according to the present invention, a server not included in the domain is connected to the network, and the client component is installed using the server. Therefore, the load on the server serving as a domain controller can be reduced. it can.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration example of a server 11, a client 3, and a server 5.

FIG. 2 is a diagram showing an example of a computer network system to which the method of the present invention is applied.

FIG. 3 is a diagram showing an example of contents of domain user management information.

FIG. 4 is a flowchart showing a processing example of a domain user management information operating means 51;

FIG. 5 is a flowchart showing a processing example of a component preparation unit 52;

FIG. 6 is a flowchart showing a processing example of a domain user management means.

FIG. 7 is a flowchart illustrating a processing example of a logon receiving unit.

FIG. 8 is a flowchart illustrating a processing example of a logon execution unit.

FIG. 9 is a diagram showing an example of a setting screen.

FIG. 10 is a diagram showing an example of contents of domain user management information before a change process is performed.

FIG. 11 is a diagram illustrating an example of contents of domain user management information after a change process has been performed;

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 ... Domain 11 ... Server (Primary domain controller) 111-11 ... Domain user management means 112-11 ... Domain user management information 113-11 ... Logon acceptance means 114-11 ... Logon script storage means 12 ... Server (Backup domain controller) 2 Domain 21 Server (primary domain controller) 22 Server (backup domain controller) 3 Client 31-3 Logon execution unit 4 Client 5 Server 51 Domain user management information operation unit 52 Component preparation unit 53 Client component storage means 6 LAN

────────────────────────────────────────────────── ─── Continuation of the front page (56) References JP-A-9-305500 (JP, A) JP-A-9-292980 (JP, A) JP-A-9-44342 (JP, A) JP-A 8- 221340 (JP, A) JP-A-6-89181 (JP, A) JP-A-7-146851 (JP, A) JP-A-5-120023 (JP, A) JP-A-2-143353 (JP, A) JP-A-61-199156 (JP, A) (58) Fields investigated (Int. Cl. ⁶ , DB name) G06F 13/00 G06F 9/445 G06F 15/177

Claims (3)

(57) [Claims] 1. In a computer network system in which a domain including a plurality of servers serving as domain controllers and a client are connected via a network, a specification specified by an administrator of a server connected to the network. Prepare a client component to be installed on the client on the server, prepare a logon script describing a process for the client to install the client component prepared on the specific server on each server serving as the domain controller, The server that has received the logon request from the client among the servers that become the domain controller notifies the client of the requesting source of the logon script prepared in the own server. The client component installation method, wherein the requesting client installs the client component prepared in the specific server on its own client according to the notified logon script. 2. The logon script includes a description of a process for determining whether or not a client component has been installed. The client that has made a logon request has installed the client component in accordance with the notified logon script. 2. The method according to claim 1, wherein it is determined whether or not the client component has been prepared, and only when it is determined that the client component has not been completed, the client component prepared in the specific server is installed in its own client. 3. In a computer network system in which a domain including a plurality of servers serving as domain controllers and a client are connected via a network, a server not included in the domain is connected to the network and the server is connected to the server. Preparing a client component to be installed on a client, preparing a logon script describing a process for a client to install a client component prepared on a server not included in the domain on each server serving as the domain controller, A server that has received a logon request from the client among the servers serving as the domain controller notifies the logon script prepared in its own server to the requesting client. And a requesting client that installs a client component prepared in a server that is not included in the domain according to the notified logon script in its own client.