Limitations in Workgroup environments

AVEVA Batch Management supports deployment in both Windows Domain and Windows Workgroup environments. However, the recommended deployment model depends on the intended use.

Production deployment (recommended)

AVEVA Batch Management is intended to be installed in a Windows Domain (Active Directory) environment for production systems. A domain environment provides centralized identity management, policy enforcement, and consistent authentication and authorization across Batch Management components and nodes.

Workgroup deployment (restricted use)

A Windows Workgroup environment is supported only for an all-in-one, single-server installation, where all Batch Management components are installed on the same computer. This deployment model is intended for evaluation, proof-of-concept, or standalone use cases.

The following limitations have been identified when AVEVA Batch Management is deployed across multiple computers in a Windows Workgroup environment.

Distributed Workgroup Deployment

The following example illustrates a distributed workgroup deployment:

Limitations

1. SMS configuration limitation:

   SMS cannot be configured to use a remote SMS server. Each node must act as its own SMS to generate the certificates required for configuring Batch Management features.

2. Deployment issue on the GR node:

   The remote Windows platform on the GR node fails to deploy.

   Error: Failed to deploy 'WinPlatform_001': Access denied, invalid credentials.

   This prevents the IBMX service from starting on the Batch Server node and blocks batch execution with IBMX.

3. Development Client configuration failure:

   The Development Client cannot be configured because users on the Development Client node do not have permission to access the Batch Server shared folder.

   Error: Batch Management folder on the Server node is not shared, or the current user does not have permissions on the share. Manually grant 'full control' permissions to the current user on the Server share.

4. History Server configuration failure:

   Unable to configure the History Server when pointing to a remote SQL server.

   Error: Create failed for Login 'INBATCHWGVM\BMLocalUser'. An exception occurred while executing a Transact-SQL statement or batch. Windows NT user or group 'INBATCHWGVM\BMLocalUser' not found. Check the name again.

   This occurs because the local user account from a remote workgroup computer cannot be added to SQL Server. This is a known SQL Server limitation.