Administration. Installing and updating the platform on a large number of computers via a shared network directory Adding an infobase to the list of infobases

The specialist who has to run around all the workplaces and work with his feet is bad. You need to work with your head :)

You can install the platform on each client computer manually.

But then the administrator will have to bypass all computers sequentially.
If there are 2-3 computers, then this is not a problem. But if there are a dozen or more computers, then such a process may be delayed.

Updating the platform on client computers will also be a problem.

To automate this process, you can use the ability to install the platform on a large number of computers through a shared network directory.

This method can be used when Windows is installed on client computers.
The administrator places the platform distribution kits and a set of configuration files in the shared network directory.
To update the platform, you only need to place the new platform distribution in the public directory.

Mass installation and update of 1C: 9 video and PDF

We invite you to look at more detailed materials:

Shared directory structure

This video shows how a network directory with platform distributions should be organized so that it can be used for installation on a large number of computers.
It explains in what form the platform distributions should be laid out and what configuration files are needed.

Preparing a Shared Directory on the Server

This video shows in practice how to populate a network directory with platform distributions. The distribution kit of the platform is laid out, the configuration launch is edited. Shows you how to find the launcher for the desired release.

Actions on the client computer

This video covers the specifics of installing the platform from a shared network directory on a client computer.

Platform update

This video shows you how to correctly locate the new release platform distribution on a shared network directory. Describes what actions must be performed on the client computer in order for the platform to be updated.

Configuration file that defines the location of a shared network directory

This video shows you where the network share settings are stored on the client computer, which should be consulted to check for a platform update.

Access rights when installing the platform through a shared network directory

This video covers the most common error that occurs when working with a shared network directory.

Work as a user without administrative rights

This video shows how you can install the platform on a client computer for a user without administrative rights. Attention is drawn to the disadvantages of this method.

Potential security issues when using the AlwaysInstallElevated policy

This video explains why the AlwaysInstallElevated policy is a serious computer security issue and why it should be avoided in practice whenever possible.

And the last day of starting discounts.

This course will allow you to solve ALL tasks for the deployment and support of information systems on 1C.

Here are some topics from the course:

• Installing and updating the 1C:Enterprise 8 platform - manual and automatic, under Windows and Linux
• Automatic start to perform routine operations
• Updating Configurations from user mode
• Updating non-standard configurations. How to avoid problems when updating modified standard configurations
• Create your own cfu delivery files
• BSP tools: external forms, processing of filling out documents, etc.
• Usage free DBMS PostgreSQL
• Installation and launch server cluster 1C:Enterprise 8
• Administration utility to set up a cluster and production servers
• Setting RLS on the example of SCP 1.3 and ERP 2
• What to do, if data in IB is corrupted
• Setting data exchanges between configurations
• Organization group development
• Setup and use hardware security keys
• Software licenses 1C: installation and binding to external equipment

In any case, someday you will have to deploy 1C, set up reservations, access rights, various launch modes, test the integrity of databases, ensure the operation of servers, etc.

And it's better to do it right.

So that later there will be no “…! Well what a…! Yours…!” - and other expressions of regret :)

If you have an additional multi-user license, you must install 1C:Enterprise 8.0 on all workstations, so it is recommended to perform a sample installation or an administrative installation, and then install on the workstations.

Typical installation and update

A typical installation of the 1C:Enterprise 8.0 platform requires a separate installation on each user's computer. Further platform updates are performed only on each user computer.

The new version of 1C:Enterprise 8.0 is released as a full distribution and as an update distribution. Any of them can be used to update the installed 1C:Enterprise 8.0.

For the client-server use case of 1C:Enterprise 8.0, the work of client and server applications of different versions is not allowed, therefore it is necessary to update both the server application and client applications.

Administrative installation

Administrative installation of the system is designed to install the 1C:Enterprise 8.0 system in the local network. When using this mode, the local network administrator gets the opportunity to install 1C:Enterprise 8.0 from a single source in the network, and then update the version of 1C:Enterprise 8.0 only at the administrative installation site. Further updating of versions on local workstations can be done by the users themselves.

To perform an administrative installation, you must run setup.exe with the /a switch. After launch, a dialog is displayed in which you must specify the administrative installation directory. A set of files required for installation on local workstations will be created in the specified directory. To install 1C:Enterprise 8.0 on local workstations, you must run the setup.exe program from the administrative installation directory.

Installation according to the sample

If you need to install the 1C:Enterprise 8.0 system on several computers of the same type (for example, to prepare a computer class), you can install on one computer, and then install on other computers following the pattern of the first one.

To do this, you need to run the setup.exe setup program from the command line, specifying the keys.

When installing for the first time, you must specify the /r switch. As a result of the installation, a setup file will be created in the Windows system directory. iss containing the user's responses to the installer's questions. This file can be used in subsequent installations by specifying the /s switch, the setup. iss must be in the same directory as setup.exe, or its location must be specified with the /f1 switch. If you install using the sample installation, the installer will create a setup.log file that records the progress of the installation - this file will be created in the same directory as setup. iss

Launch modes

Run Dialog

1C:Enterprise 8.0 system can be launched in one of the following modes:

To start the 1C:Enterprise 8.0 system, select the appropriate line in the "1C:Enterprise 8.0" menu (Start - Programs). A launch dialog opens, which you can customize. The "Settings:" button in the launch dialog opens the launch settings dialog box.

If the "Display as a tree" checkbox is checked in this window, the list of infobases is displayed as a tree.

If the "Sort by name" checkbox is checked, then the list is sorted by name within each group.

If the "Show last selected infobases" box is checked, then the number of last called bases is indicated in the "Remember last selected" field. The list of last selected bases is shown at the top of the general list. Infobase names are highlighted in bold type. This the list is displayed in order of selection - at the top of the list is the base selected last. Setting the sorting of the list does not affect the order of the bases in the list of selected ones. Only selection is allowed in this list. Editing and deleting an infobase becomes available when you select it in the general list of infobases.

The "Configuration templates and updates directory" field specifies the directory of configuration templates and updates. Changing this field changes the directory of used templates.

To install the platform, in general, it is enough to run the setup shortcut of the distribution distribution:

And select the components to install:

The configuration is even easier to install - the template is unpacked to the selected directory:

The order of installation is unimportant, but without a platform, the configuration will not work.

Question 09.01 of exam 1C: Platform professional. What is the order in which platform and configuration are installed?

1. You must first install the platform, then install the configuration based on the template
2. You must first install the configuration, and after the platform
3. Installation order doesn't matter

The correct answer is the third one.

Question 09.02 of exam 1C: Platform professional. Typical installation of the 1C:Enterprise 8 platform

1. involves a separate installation on each user computer, further platform updates can be performed automatically from the server
2. involves a separate installation on each user computer, further platform updates can only be carried out on each user computer
3. involves installation on a server with further copying of the necessary files to users' computers, further platform updates can be performed automatically from the server
4. involves installing a local version per user

The correct answer is the second.

Question 09.04 of exam 1C: Professional on the platform. Administrative installation...

1. involves installing the platform on each individual user computer
2. involves the installation of the platform by the Administrator on one computer, with further copying of executable files from it to the workstations of local network users
3. involves installing the configuration on the 1C:Enterprise server, with the definition of a user with Administrator access rights

The correct answer is the second, apparently group policies are meant.

Question 09.03 of exam 1C: Platform professional. What needs to be done to update the technological platform during a normal installation of 1C:Enterprise?

1. Specify the update file in the configurator mode
2. Run the installer included with the distribution
3. Specify the delivery file in the configurator mode

The correct answer is the second, the configurator has nothing to do with updating the platform.

Question 09.05 of exam 1C: Platform professional. When updating the technological platform during the administrative installation of 1C:Enterprise...

1. it is enough for the administrator to update the platform only in the place of the administrative installation, the users themselves can update the platform on local computers
2. the administrator must update the platform at the administrative installation site and on all computers on the local network, users do not have the right to update
3. the administrator needs to update the platform only on LAN computers, users have the same option
4. the administrator must update the platform only on computers on the local network, users do not have such an opportunity

The answer is first.

Question 09.06 of exam 1C: Platform professional. Is it allowed during a normal installation of 1C:Enterprise in the client-server version, the operation of client and server applications of different releases of the technological platform?

1. Allowed
2. Not allowed, it is necessary to update both the server application and client applications
3. It is allowed, it is necessary to update the server application

The correct answer is the second - in no case is it allowed, otherwise comparability is lost.

Question 09.11 of exam 1C: Professional on the platform. Configuration Templates...

1. serve as prototypes for the created infobases and are installed in the template directory specified by the user
2. correspond to the current configuration parameters and are responsible for compliance with releases, are installed in the template directory specified by the user
3. determine deviations of the changed configuration from the typical one, are installed in the template directory specified by the user

The correct answer is the first, configuration templates are typical solutions.

This article will discuss in detail the algorithm for installing the client part of the 1C:Enterprise system. 8.3 (for versions 8.2 , 8.1 and 8.0 the installation algorithm is similar, about installing the 1C:Enterprise system 7.7 I wrote) in operating systems of the . Typical variants of 1C:Enterprise operation are considered, and a brief description of all system components will be given.

0. Initial information about the 1C:Enterprise system

The 1C:Enterprise system is a set of software modules designed to develop and use application solutions ( configurations) - on keeping records and automating the economic activities of enterprises. The software modules of the 1C:Enterprise system are universal and can work with any configuration. R working with infobases is possible both in file, as well as in client-server option.

In the case of working with a file infobase, the database files are located either directly on the computer of the user working in the program 1C:Enterprise, or on a network resource to which 1C:Enterprise connects to work with the infobase. The figures below show the most common scenarios for the operation of 1C:Enterprise with file databases.

This mode of operation is suitable only for infobases with which a small number of users work simultaneously.

If it is assumed that a large number of users will work with the infobase at the same time, or a significant load on the infobase is expected, you should use 1C:Enterprise server cluster. In this case, the database files will be located in a separately installed DBMS (database management system), and the server cluster will interact with the end user with this DBMS. In the general case, the scheme of operation of the 1C:Enterprise system will then be as follows:

I wrote in detail about installing a 1C:Enterprise server cluster in the article. The following is only about installation. client application 1C:Enterprise system, i.e. system modules required to work with file infobases or to connect to an existing cluster of 1C:Enterprise servers. For this we need:

1. The computer responsible for installing the client application of the 1C:Enterprise system running Windows operating systems.
2. Local administrator rights on this computer.
3. Distribution kit for installing 1C:Enterprise modules. This example uses the version 8.3.4.389 . Installation of 1C:Enterprise modules of earlier versions is similar.
4. or , suitable for the required 1C:Enterprise mode of operation.

1. Installing the components of the 1C:Enterprise system

Open the directory with the 1C:Enterprise installation files and run the filesetup.exe.

The 1C:Enterprise 8 installation assistant will start, click " Further" on the first page.

On the next page, you can change the folder for installing 1C:Enterprise modules by clicking the " Change” and specifying a new path for installation, and you also need to select the components that will be installed. The list of components depends on what needs to be installed. Depending on the distribution type, not all components may be available for installation. If you need to install a component (or cancel the installation), you need to mark it by clicking the icon to the left of the component name (or Space), in the menu that appears, select one of the options:

• This component will be installed on the local hard drive.
• This component will not be available.

Here is a brief description of the installed components:

• 1C:Enterprise— the main components of 1C:Enterprise, including components for administration, configuration, thick and thin clients.
• 1C:Enterprise - thin client- thin client components only for working in the client-server version.
• 1C:Enterprise - thin client, file version— thin client components, including components for working with the infobase file version.
• Server 1C:Enterprise— components of the 1C:Enterprise server (read more about installing the 1C:Enterprise server).
• Web Server Extensions— web server extension modules required for the operation of the web client and Web services (read more about setting up web access to 1C:Enterprise databases).
• 1C:Enterprise server administration— additional components for administering a 1C:Enterprise server cluster.
• Interfaces in different languages— user interfaces in various languages.
• Configuration storage server 1C:Enterprise— components of the 1C:Enterprise configuration storage server.
• Converter IB 1C: Enterprise 7.7- infobase converter.

After selecting the necessary components for installation, click " Further».

At the next step, you must select the interface language to be used in the future (by default, the language of the operating system). After specifying the interface language, click " Further».

Press " Install to start the installation of 1C:Enterprise.

Upon completion of the installation process, the assistant will offer to install the protection driver - HASP Device Driver. It is necessary to install the protection driver only if the USB port given HASP4 NET hardware protection key will be installed on the computer (you can also install the driver later using the menu item " Start» — « Programs» — « 1C Enterprise 8» — « Installing the HASP Device Driver"). Leave or remove the flag "Install protection driver» and press « Further».

If the installation is completed successfully, the final page of the installation assistant will open. If you leave the flag Open Readme File”, then a file with information will be opened, which seems to be recommended to read before using this version of the system. Press " Ready» to complete the wizard.

2. Adding an infobase to the list of infobases

During installation, a shortcut will be created on the desktop to launch 1C:Enterprise. If you run it, the 1C:Enterprise launcher will open with an empty list of infobases and a suggestion to add a new infobase to the list.

The next steps depend on your specific situation:

• If you need to create a new database to start accounting, click " Not» and, first of all, we install a typical configuration template, and only then, based on the template, we create a new infobase. Read more about this in the article.
• If you need to connect to an existing infobase, click " Yes» and add this database to the list of infobases. Read the article on how to do this.

3. Installing a 1C:Enterprise license

1C:Enterprise software products version 8can be protected from copying by hardware LPT or USB dongles such as HASP4 Net from the company Aladdin or through the software licensing system. It is also possible to use both types of protection at the same time. After system installation "1C:Enterprise" and creating infobases, it remains only to install a license for the operation of "1C:Enterprise".

• I wrote about installing and configuring HASP security keys in the article ""
• I wrote about the software licensing system in the article "", as well as about the case of the initial receipt of a license in the article "".

Did this article help you?

• How to install the 1C:Enterprise 8.2 platform on a large number of computers?
• How to maintain the current version of the 1C:Enterprise 8.2 platform on a large number of PCs?
• How to give users the right to update the 1C:Enterprise 8.2 platform without granting administrator rights?
• How to automate the process of installing and updating the 1C:Enterprise 8.2 platform in a corporate network?

In this post I will try to answer these questions based on personal experience.

Administrative installation of the “1C:Enterprise 8.2” platform

There are several options, so to speak, for the administrative installation of the 1C:Enterprise 8.2 platform:

1. Installation recommended by 1C from a shared network resource with a specially configured structure.
2. Installation using the "Program Installation" policy of Windows group policies.
3. Installation using a logon script assigned by Windows group policies.

Each method has its pros and cons.

Method 1: Administrative installation of the 1C:Enterprise 8.2 platform from a shared network resource.

The 1C:Enterprise 8.2 Administrator's Guide recommends that platform users create a public network resource with the following file location for installation by platform users:

\\Server\1CEDistr

\\Server\1CEDistr\1CEStart.exe

\\Server\1CEDistr\1CESCmn.cfg

\\Server\1CEDistr\ibcommon.v8i

\\Server\1CEDistr\8.2.9.10

\\Server\1CEDistr\8.2.9.10\Setup.exe

\\Server\1CEDistr\8.2.9.150

\\Server\1CEDistr\8.2.9.150\Setup.exe

\\Server\1CEDistr\8.2.xx.xx

\\Server\1CEDistr\8.2.xx.xx\Setup.exe

In the diagram above:

• \\Server\1CEDistr is a directory on the Server where the files necessary for system deployment are located.
• 1CEStart.exe is a launcher. For initial installation, it is enough to run the launcher from this network directory.
• ibcommon.v8i - list of common infobases, if it exists (the name is conditional and is optional)
• 1CESCmn.cfg is a general configuration file. It is recommended to specify the following parameters in it:

CommonInfoBases=ibcommon.v8i – if you want users to have a list of common infobases at startup.
InstallComponents - specify the components that are required for installation on users' computers. Example:

Default Fersion=8.2.13-8.2.13.205
InstalledLocation=C:\Program Files\1cv82
InstallComponents=DESIGNERALLCLIENTS=1 THINCLIENTFILE=1 THINCLIENT=1 WEBSERVEREXT=0 SERVER=0 CONFREPOSSERVER=0 CONVERTER77=0 SERVERCLIENT=0 LANGUAGES=RU
CommonInfo Bases=\\Server\1CEDistr\ibcommon.v8i
DistributiveLocation=\\Server\1CEDistr

• 8.2.9.100, 8.2.9.150 and 8.2.xx.xx – directories with distributions of the corresponding versions of “1C:Enterprise 8”
• Setup.exe – program for launching the installation of the 1C:Enterprise program system

How it works.

1. Initial installation. After creating the above network share, the user for the initial installation must run the 1CEStart.exe launcher, as a result of the launch, the latest version of the 1C:Enterprise 8 platform present in this directory will be installed, while those components that are specified in the InstallComponents parameter of the 1CESCmn file will be installed. .cfg.
2. Platform update. After the release of the next version of the 1C:Enterprise 8 platform, it is necessary to add the appropriate directory of the 8.2.xx.xx type with the distribution kit of this version to the network share. The next time the user launches 1C:Enterprise 8, the new version will be automatically installed.

The advantages of this method:

• can be used in workgroup based networks;
• to install a new version, it is enough to copy the corresponding distribution kit to a shared network resource, i.e. no need for additional actions on the part of the administrator;

Minuses:

• users must have local administrator rights to be able to install, or you must enable the installation permission policy in group policies;
• over time, the list of installed versions can become quite impressive, this method does not automatically remove obsolete versions of the platform.

This method, in my opinion, is convenient where users have sufficient rights, or in small networks, when the administrator is able to bypass all workstations and run the update on his behalf.