Read the same in:      日本語  Polski  Русский  Español  English  
You are welcome to subscribe to "New articles in Knowledge base" mailing list:

Please take a moment to rate the quality of our articles:
Technical level 
Amount of information in articles 
Have we helped you so far?* 
Presentation of information, design 
Your comments* 
makes shorter
make longer
need outline main points
more practical staff, less theory
make a better search engine
translate into my native language (other than EN)
make a structure
need a redesign
write more articles
all perfect
Your own comment 
My comments refer to the articles dedicated to* 
corporate products
home products


 
Search :  
Search tips Article ID # :     
 

Kaspersky Administration Kit 8.0

 

Administration Server and/ or Server database are out of order. How to restore the logical network?

 ID Article: 3252    Other languages:  日本語  Polski  Русский  Español  English      Views for 7 days 11    Last modified on 27.01.2010 15:29 Printable version
­­­­­

Applies to Kaspersky Administration Kit 8.0

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

It deals with cases when there is no actualized backup copy of the Server database available and it is no longer possible to create one.

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

General recommendations on how to restore a logical network

Server database has crashed (SQL server is running)

Only SQL server has crashed

Only Administration Server has crashed (or the computer where it was installed)

SQL-server and Administration Server have crashed

 

General recommendations on how to restore a logical network

In order to restore full functionality of the logical network after Administration Server and/or Server database crash, please ensure the following:

1. same logical network structure (client computer and slave Server groups, tasks, policies, Server properties)

2. same old and new Server certificates on client computers

3. Same server address (NetBIOS name, DNS name or IP address) used for connecting client computers

InformationThe Server address used for connecting client computers is defined in the Network Agent installation package properties. Go to the Console node Repositories, open Network Agent installation package properties on the tab Connection.

Unavailability of a database backup and impossibility to create one makes it impossible to preserve the logical network structure. And in order reconnect to client computers you need:

  • a copy of the Administration Server certificate (saved during its installation)
  • old Server address preserved on the computer where a new Server will be installed (if the Server has crashed)

If at least one objective is missing, you will have to modify Server properties on client computers using the klmover utility (it can be run via a 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 where the old Server was. When installing, you should configure the same (old) connection properties for the SQL server, but give the database a NEW name.

WarningIf you install the Administration Server on another computer without preserving the old Server address, please run the klmover utility (add it to the login script, for example)što set the new Server address on all client computers.

3. Depending on your success in recovering the old Server certificate:

    • If the old Servers certificate has been recovered please proceed with step 4
    • If the old Servers certificate has not been recovered, please run the klmover utility (add it to the login script, for example) to set the new Server certificate on all client computers.

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

5. Add client computers to administration groups manually. Make sure all client computers have connected to the new Server (computer icons are bright). It may take some time (about 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 a new Administration Server on the same computer where the old Server was. Configure new SQL server connection properties.

WarningIf you install the Administration Server on another computer without preserving the old Server address, please run the klmover utility (add it to the login script, for example)što set the new Server address on all client computers.

4. Depending on your success in recovering the old Server certificate:

    • If the old Servers certificate has been recovered please proceed with step 5
    • If the old Servers certificate has not been recovered, please run the klmover utility (add it to the login script, for example) to set the new Server certificate on all client computers.

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

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

Top of page

 

Only Administration Server has crashed (or the computer where it was installed)

1. Install a new Administration Server (it is better to install it on the same computer where the old Server was or preserve the old Server address). You can use the old SQL Server but it is necessary to create a new database. It is impossible to reconnect to the old database.š

WarningIf you install the Administration Server on another computer without preserving the old Server address, please run the klmover utility (add it to the login script, for example) to set the new Server address on all client computers.

2. Depending on your success in recovering the old Server certificate:

    • If the old Servers certificate has been recovered please proceed with step 3
    • If the old Servers certificate has not been recovered, please run the klmover utility (add it to the login script, for example) to set the new Server certificate on all client computers.

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

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

Top of page

 

SQL server and Administration Server have crashed

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

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

InformationSpecify the old Administration Server certificate if you have recovered it.

WarningIf you install the Administration Server on another computer without preserving the old Server address, please run the klmover utility (add it to the login script, for example) to set the new Server address on all client computers.š

3.Depending on your success in recovering the old Server certificate:

    • If the old Servers certificate has been recovered please proceed with step 4
    • If the old Servers certificate has not been recovered, please run the klmover utility (add it to the login script, for example) to set the new Server certificate on all client computers.

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

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

Top of page


 Did the provided info help you?

                       

 Give your detailed feedback.

 

Kaspersky Lab

Copyright © 1997-2013 Kaspersky Lab
Site map  |   Contact us  |   International Support Service  |  Send us a suspected virus

Stay connected