Kaspersky Administration Kit 6.0 MP1/MP2

	Useful links
	System requirements to install an Administration Server The klmover.exe utility to change the Network Agent parameters on client computers The klnagchk.exe utility to analyze connection parameters of the Administration Agent

This article gives recommendations how to restore efficiency of the logical network after the Administration Server and /or SQL-server have crashed (or the Server database is damaged).

It investigates the cases when the actual backup copy of the Server database has not been made and it cannot be backed up.

If you have already created the backup copy of the database which you can restore, then use the link to get recommendations how to go to a new Administration Server and/or new SQL-server (depending on what has crashed).

General recommendations how to restore logical network

Server database has crashed (SQL-server is running)

Only SQL-server has crashed

Only Administration Server has crashed (or computer on which it is installed)

SQL-server and Administration Server have crashed

General recommendations how to restore logical network

The three following conditions are necessary, to restore full functionality of the logical network after the Administration Server and /or the Server database has (have) crashed:

1. the structure of the logical network (grouping of client computers and slave Servers, tasks, policies, Server properties) should be saved

2. certificates of the Server on client computers and on a new Server should correspond (coincide)

3. the Server address (NetBIOS-name, DNS-name or IP-address), by which client computers will connect to the Server, should be saved

The Server address which the client computers will use to connect to the Server is defined in the Administration Agent’s properties: in the Console open properties of a client computer > the Applications tab > Kaspersky Network Agent > Properties > the Settings tab).

As the database has not been backed up and cannot be backed up now, the structure of the logical network cannot be restored. If the connection with client computer can be restored or not depends on the following conditions: 

• Was the certificate copy of the Server saved during the installation of the Administration Server? 

• Can the Server address be saved on the computer on which a new Server is going to be installed (if it has crashed)?

If at least one answer to the questions is negative, then to change the Server parameters run the klmover utility on client computers (it can be run using login-script).

Top of page

Server database has crashed (SQL-server is running)

1. Uninstall Administration Server

2. Install a new Administration Server on the same computer, on which the old Server was installed. When installing, define parameters to connect to the same SQL-server; the database name must be NEW.

If you saved the certificate when installing the old Administration Server, specify this certificate when installing a new Server!

If you install an Administration Server on another computer and do not save the address of the old Server, then run the klmover utility for all client computers (for example, writing it to login-script) to define new address of the Server to client computers!

3. Your further actions will depend on whether the old Server’s certificate is restored or not: 

• If the old Server’s certificate is restored – go to step 4. 

• If the old Server’s certificate is not restored, then run the klmover utility on all client computers (for example, write it to login-script) to define a new Server certificate to client computers.

4. Open the Administration Console and connect to a new Server. Create necessary policies and tasks.

5. Add client computers to administration groups manually. Make sure all client computers have connected to the Server (the computer icons are bright) it may take some time (60 minutes)

Top of page

Only SQL-server has crashed

1. Uninstall Administration Server

2. Install new SQL-server (according to system requirements)

3. Install new Administration Server on the same computer, on which the old Server was installed. When installing define the parameters to connect to the same SQL-server.

If you saved the certificate when installing the old Administration Server, specify this certificate when installing a new Server!

If you install an Administration Server on another computer and do not save the address of the old Server, then run the klmover utility for all client computers (for example, writing it to login-script) to define new address of the Server to client computers!

4. Your further actions will depend on whether the old Server’s certificate is restored or not: 

• if the old Server’s certificate is restored – go to step 5. 

• if the old Server’s certificate is not restored, then run the klmover utility on all client computers (for example, write it to login-script) to define a new Server certificate to client computers.

5. Open the Administration Console and connect to a new Server. Create necessary policies and tasks.

6. Add client computers to administration groups manually. Make sure all client computers have connected to the Server (the computer icons are bright) it may take some time (60 minutes)

Top of page

Only Administration Server has crashed (or computer on which it is installed)

1. Install a new Administration Server (better install it on the same computer where the old Server was earlier installed or save the old Server’s address). You can use the old SQL-server but new database should be created. You cannot connect to the old database!

If you saved the certificate when installing the old Administration Server, specify this certificate when installing a new Server!

If you install an Administration Server on another computer and do not save the address of the old Server, then run the klmover utility for all client computers (for example, writing it to login-script) to define new address of the Server to client computers!

2. Your further actions will depend on whether the old Server’s certificate is restored or not: 

• if the old Server’s certificate is restored – go to step 3. 

• if the old Server’s certificate is not restored, then run the klmover utility on all client computers (for example, write it to login-script) to define a new Server certificate to client computers.

3. Open the Administration Console and connect to a new Server. Create necessary policies and tasks.

 4. Add client computers to administration groups manually. Make sure all client computers have connected to the Server (the computer icons are bright) it may take some time (60 minutes)

Top of page

SQL-server and Administration Server have crashed

1. Install a new SQL-server (according to system requirements)

2. Install new Administration Server on the same computer, on which the old Server was installed. When installing define the parameters to connect to a new SQL-server.

If you saved the certificate when installing the old Administration Server, specify this certificate when installing a new Server!

If you install an Administration Server on another computer and do not save the address of the old Server, then run the klmover utility for all client computers (for example, writing it to login-script) to define new address of the Server to client computers!

3. Your further actions will depend on whether the old Server’s certificate is restored or not: 

• if the old Server’s certificate is restored – go to step 4. 

• if the old Server’s certificate is not restored, then run the klmover utility on all client computers (for example, write it to login-script) to define a new Server certificate to client computers.

4. Open the Administration Console and connect to a new Server. Create necessary policies and tasks.

5. Add client computers to administration groups manually. Make sure all client computers have connected to the Server (the computer icons are bright) it may take some time (60 minutes)

Top of page