First variant: Installation from NT-based to NT-based:

 

(Under NT-based it is implied Windows NT 4 Server, Windows NT 4 Workstation, Windows 2000 Server è Windows 2000 Professional, Windows XP Professional).

 

1. In Deployment tab of AVP Server (via Network Control Centre)  computer-based deployment” installation type must be pointed out.

 

2. In Storage tab of AVP Server (via NCC) the package of the installation product must be prepared with these data pointing out: *.kpd, *.key, policy.dat  - there:

  *.kpd – product description file (it is located in KAV for Workstations, KAV for NT Server distributives)

  *.key – key file,

  policy.dat – settings file of target computer’s KAV Control Center 

 

You can create this file on the PC there AVP is already installed and there all settings are configured.

Also you can do not point this file. In this case all settings will be default.

 

3. It is recommended to set the Control Center’s password to have a possibility to manage the remote workstations.

 

This password will be used during the adding of this workstation in AVP network.

 

Attention!  It is necessary to press <ENTER> after AVPCC password configuration.

 

4. In the network tree (in the right window) chose the computers on that you want to install selected product.

 

Please pay your attention that all PCs will be shown in this tree but the remote installation is possible for NT only.

 

 

5.       The access rights that are needed for remote installation.

 

It is necessary to set the login and password that belong to local administrator on the remote workstation (it can be also the administrator of the domain that remote workstation belong to).

 

If login/password are not set up, the program will use the account that you have used to log on. 

 

“Administrative disk share name” – is the directory, there the remote installation distributive will be copied.  As default it is used Hidden System Share C$ (with access rights for Administrators group only).

 

6.       You can choose the setting “Do not reboot computer after installation”. In this case the installation will not be over with forced reboot. But the product will work correctly after the first reboot only.

 

 

7.  Set the necessary options in the settings tree.

 

8. Press  "Deploy" to begin the remote installation.

________________________________________________________________________

 

The second variant: the installation using login-script.

 

(This variant is possible on all these OS: Windows95/98/Millenium, Windows NT4 Server/Workstation, Windows 2000 Server/Professional).

 

 

For this installation type the same settings must be set, but with some difference (for example, you shouldn’t set the user names, the passwords etc.).

 

It is needed to point the Target Folder, there the prepared distributive will be placed and that press ‘Deploy’.

 

After that the directory Product.avp will be created in this target folder.

 

Attention! Please provide the shared access to this directory (Target folder).

 

 

If you will run AVPDTUP.EXE file from remote workstation, the “silent installation” will be done.

 

If the product of this version is already installed on remote PC, the recurrent installation will not run.

 

 

 

Also you can run AVPDTUP.EXE using login-script.

 

For example, in case of NT domain you should do following:

 

1. Create bat-file with such line:

 

start \\servername\sharename\AVPDTUP.EXE

 

there the ‘servername’ – is the server’s name,

and the ‘sharename’ – is the name of the Target Folder (the directory there product.avp is located).

 

 

This bat-file must be placed on Primary Domain Controller in the NETLOGON folder (as default - Winnt\System32\Repl\Import\Scripts). This script must be set for the users. And the launch of this script will done during their login to the NT domain.

 

! These settings are implemented in User Manager for Domains.

 

 

 

 

During the first users’ login the installation will run. Then it will be over, the reboot will be execute if it’s needed.

 

 

You shouldn’t delete this script after installation (as it mentioned above, if the product of this version is already installed on remote PC, the recurrent installation will not run.)

BTW, this procedure can be used for centralized upgrade.