A.2 Prerequisites for connection destinations
This section describes the prerequisites# for connection destinations that can be used in JP1/AO.
For details about the OSs supported for connection destinations, see the Release Notes.
For details about the protocols that can be used for communication between JP1/AO servers and connection destinations, see List of protocols used by each plug-in in the manual JP1/AO Service Template Reference.
For details about the OSs supported for the basic Plug-in, see Operation target devices usable as connection destinations in the manual JP1/AO Service Template Reference.
For details about the OSs supported for the service templates and plug-ins provided by JP1/AO, see the descriptions of the individual service templates and plug-ins in the manual JP1/AO Service Template Reference.
#
If the local execution function is enabled, the prerequisites do not have to be satisfied for the local host.
When you use Windows as a connection destination, the following limitations apply to the users who can connect to the connection destination and to the administrative share setting.
- Organization of this subsection
(1) Users who can connect to the connection destination
The following Windows users are supported at the connection destination:
Built-in Administrator
Users who belong to the Administrator group#1#2
Built-in Administrator of Active Directory
Users who belong to the Domain Admin group of Active Directory#1#2
- #1
Commands are executed using the permissions of the System account when a content plug-in is configured to be executed using System account permissions, and when true is specified for the runAsSystem property of a general command plug-in.
- #2
If the OS of the connection destination meets one of the following conditions, specify the registry settings:
The UAC function is enabled in Windows Server 2008 R2.
The OS is Windows Server 2012 or later.
Table A‒5: Registry settings (local user settings) Item
Value
Registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Registry entry
LocalAccountTokenFilterPolicy
Value to be set in the registry entry
1 (DWORD)
- Tip
You can also use the following command to set the registry values:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1
(2) Administrative share setting
If you use a service template that uses one of the following plug-ins at the Windows connection destination, you must enable administrative shares:
General command plug-in
File-transfer plug-in
Content plug-in
If administrative shares are disabled, specify the registry settings shown in the following table, and then restart the OS at the connection destination.
Item |
Value |
---|---|
Registry key |
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\parameters |
Registry entry |
AutoShareServer |
Value to be set in the registry entry |
1 (DWORD) |
- Tip
You can also use the following command to set the registry values:
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\parameters /v AutoShareServer /t REG_DWORD /d 1
- Important
-
To connect to a Windows connection destination from multiple JP1/AO servers, you must configure the property files of the connection destination. For details, see the "Connection-destination property file (connection-destination-name.properties)" in the document JP1/Automatic Operation Configuration Guide.