Installation guide

Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2013
65
Adding more tags than currently licensed
To add more tags than currently licensed:
1. Contact your Emerson Process Management Sales/Service Office to obtain new
license codes to cover the number of tags needed.
2. Run the Licensing Wizard on the Server Plus Station (see “Licensing a
Distributed System” on page 57).
3. Start AMS Device Manager.
4. Install and configure the additional devices.
Installing AMS Device Manager on domain
controllers
AMS Device Manager creates a Windows user account (AmsServiceUser) on each
station in a distributed system. When AMS Device Manager is installed on a domain
controller, this account is created as a domain user. Communication failures will result
if installation is not done correctly as follows:
• If Windows domain controllers are used in a distributed network, AMS Device
Manager must be installed on one of these stations first, followed by any other
domain controller stations and non-domain controller stations. If AMS Device
Manager is installed on a domain controller, all other stations that are part of
that domain use the domain account, not a local account.
• If AMS Device Manager will be used in a cross-domain configuration and AMS
Device Manager will not be installed on a domain controller, create the
AmsServiceUser account on any domain-resident PCs prior to installing AMS
Device Manager on them. Refer to KBA NA-0800-0113.
Note
If a Server Plus is installed on a domain controller, all Client SC Stations that are part of that
domain must be clients of this Server Plus. Only one AMS Device Manager distributed
system is allowed on a single domain.
Note
AMS Device Manager is not supported on a Windows Server 2008 read-only domain
controller.