Difference between revisions of "BCX Network Management Tools Installation Assistant"
m (→Prerequisites) |
m (→Packages) |
||
| Line 11: | Line 11: | ||
===Packages=== | ===Packages=== | ||
| + | |||
| + | The client service runs under the context of the local computer SYSTEM account. | ||
| + | When installing packages from a package task, the installer is ran within the same context as the client service. | ||
| + | For this reason, when the computer authenticates itself against the shared package location, the computer account needs permission to access the shared location. | ||
| + | When creating a new location this is done automatically, when using an existing location | ||
| + | these options can be set manually or the Installation Assistant can attempt to change them for you. | ||
| + | Below is an example of the security permissions set correctly on the folder. | ||
| + | |||
| + | Image of security rights | ||
| + | |||
| + | If you don't already have an existing central packages location, or want to start a new collection of software, the location can exist on the new BCX Management Server. | ||
| + | Otherwise use your existing location if you already deploy software in a similar fashion. | ||
===Active Directory=== | ===Active Directory=== | ||
Revision as of 12:11, 4 December 2020
Use the links below for details of installer steps during use of the Installation Assistant.
Contents
Prerequisites
Version 4 requires .NET 4.7.2 or later.
If this is not installed, the Installation Assistant will try and make this easier by offering to automate the process if the check fails. All that is needed is the install media relevant to the edition of Windows Server that you are installing the BCX Management Tools on. Once mounted, it can be browsed to and the Installation Assistant will add the feature for you.
Packages
The client service runs under the context of the local computer SYSTEM account. When installing packages from a package task, the installer is ran within the same context as the client service. For this reason, when the computer authenticates itself against the shared package location, the computer account needs permission to access the shared location. When creating a new location this is done automatically, when using an existing location these options can be set manually or the Installation Assistant can attempt to change them for you. Below is an example of the security permissions set correctly on the folder.
Image of security rights
If you don't already have an existing central packages location, or want to start a new collection of software, the location can exist on the new BCX Management Server. Otherwise use your existing location if you already deploy software in a similar fashion.
Active Directory
Wake on LAN
DNS
SQL
Update and Backup
Group Policy
Return to Installation Guide