Windows Domain and Workgroup Planning Guide EPDOC X250 en 515A
Windows Domain and Workgroup Planning Guide EPDOC X250 en 515A
RELEASE 515
-2-
Contents 3
Chapter 1 - About this document 7
1.1 Revision History 7
1.2 Intended audience 7
1.3 Prerequisite skills 7
1.4 Related documents 7
Chapter 2 - Planning a Windows domain/workgroup 9
2.1 Overview of Windows domain 9
2.2 Overview of a Windows workgroup 10
2.3 Overview of a domain controller 10
2.4 Overview of a Read-only Domain Controller 11
2.5 Overview of a peer domain controller 11
2.5.1 Multiple domain controllers in a domain 12
-3-
2.9.3 DNS naming conventions 24
2.9.4 DNS tools 25
-4-
8.3 Setting up automatic logon 57
8.3.1 Setting up automatic logon in a domain 58
8.3.2 Setting up automatic logon in a workgroup 58
Chapter 12 - Appendix 71
12.1 Experion domain group policy settings 71
12.2 Workstation security settings 124
12.2.1 Security Model specific permissions 124
12.2.2 Local policy settings 129
-5-
CHAPTER
This guide includes high-level planning and design topics for implementing Microsoft Windows domain
controllers for Experion.
-7-
CHAPTER
2 PLANNING A W INDOWS
DOMAIN/WORKGROUP
-9-
Chapter 2 - Planning a Windows domain/workgroup
ATTENTION
For detailed description about the Windows domain concepts, refer to the following Microsoft
documentation.
l http://www.microsoft.com/windowsserver2008/en/us/ad-main.aspx
l http://technet.microsoft.com/en-us/library/cc780336(WS.10).aspx
- 10 -
Chapter 2 - Planning a Windows domain/workgroup
l Performs centralized management of computer settings and restrictions in the form of Group Policy.
You must setup at least one domain controller in every Windows domain. The following figure shows
the domain controller in a Windows domain.
- 11 -
Chapter 2 - Planning a Windows domain/workgroup
Bridgehead controllers are used in situations where we have a single domain that passes over low
bandwidth lines (that is for offshore connections).
Multiple domain controllers in a domain provide the following benefits.
l Improves availability and reliability of network services
l Provides fault tolerance
l Balances load of existing domain controllers
l Provides additional infrastructure support to sites
l Improves performance by allowing the user to connect to a domain controller when logging on to
the network
l Provides continuous functioning of the domain (when one of the domain controllers fail or must be
disconnected, the other domain controller becomes the active domain controller)
A peer domain controller can be setup using one of the following ways.
l Over the network
l By restoring a backup of an existing domain controller
The domain controller backup can be stored on a tape, hard drive, or any other backup media. Before
setting up a peer domain controller, go through the checklist in the following Microsoft documentation.
http://technet.microsoft.com/en-us/library/cc759620(WS.10).aspx
l Multiple domain controllers in a domain
When there are multiple domain controllers in a domain, all domain controllers are peers. All domain
controllers in a domain have read/write copies of the domain database. You can setup an additional
domain controller (peer domain controller) through the Active Directory installation wizard in one of the
following ways.
l Over the network
l By restoring a backup of an existing domain controller
Although all domain controllers in a domain are peers, some domain operations require a single
domain controller to perform a specific function. To perform these specific functions, domain controllers
are assigned specialized roles known as Flexible Single Master Operations (FSMO) roles.
The domain controller FSMO roles are as follows:
l Schema master
l Domain naming master
l Primary domain controller (PDC) emulator
l Infrastructure master
l Relative ID (RID) master
- 12 -
Chapter 2 - Planning a Windows domain/workgroup
The Global Catalog (GC) server is another domain controller role. This role can be configured on
multiple domain controllers in a domain. There is at least one GC server per domain. The first domain
controller in the forest automatically holds all five FSMO roles and is a GC server. When peer domain
controllers are introduced into the domain, the FSMO roles can be redistributed to different domain
controllers.
Refer to the following Microsoft documentation for more information on domain controller roles.
http://technet.microsoft.com/en-us/library/cc786438(WS.10).aspx
The Active Directory manages all elements of the network, including computers, groups, users,
domains, security policies, and other type of user-defined objects. An Active Directory can also be
considered as a distributed database that can have enterprise scope if configured. An Active Directory
provides distributed security, user, group, and computer management dynamic name services.
Active Directory allows administrators to organize objects of a network (such as users, computers, and
devices) into a hierarchical collection of containers known as the logical structure. The following are the
logical components of an Active Directory.
l Domain trees
l Forests
l Domains
l Organizational Units (OUs)
l Site Objects
ATTENTION
Honeywell recommends that you apply this file system security model to protect against
unauthorized file access. This is important if you plan to use SafeView or any application that
employs a browse window. For implementation design guidance/help contact your Honeywell
representative.
l Overview of Forests
l Overview of domain trees
l Overview of Organizational Units
l Using a single domain with multiple OUs
l TPS domains as Organizational Units
l Overview of sites
l Active directory replications
l Functional levels in Active Directory
2.6.1 Overview of Forests
Forests are defined as.
- 13 -
Chapter 2 - Planning a Windows domain/workgroup
The first domain controller in a domain is the forest root. A forest does not require multiple trees, but can
have other trees with a non-contiguous name space. Forests act independently of each other but can
trust each other.
ATTENTION
For information about forests, refer “What are forests?” in the following Microsoft documentation –
http://technet.microsoft.com/en-us/library/cc759073(WS.10).aspx#w2k3tr_logic_what_ovkc
- 14 -
Chapter 2 - Planning a Windows domain/workgroup
The main reason for creating multiple domains is the management of the domain structure. Most
settings are bound by the domain security boundary like password policies. In addition, all child
domains have transitive trusts with other domains in the same tree.
The following are additional reasons for creating multiple domains in a network.
l To manage different organizations or to provide unit identities
l To enforce different security settings and password policies
l To control Active Directory replication
l To decentralize administration
- 15 -
Chapter 2 - Planning a Windows domain/workgroup
OUs can be used for delegating administrative control over objects contained in them to a subset of
users in Active Directory. For instance, the domain administrator needs to designate one person in each
department as the official Password Change Administrator. This reduces the administrative load. The
domain administrator can delegate the authority to modify users' passwords to each user over only their
respective OU. OUs can also be used for easy administration by grouping like objects together, which
can then be used for applying security settings contained in Group Policy Objects.
ATTENTION
For more information about OUs, refer the following Microsoft documentation –
http://technet.microsoft.com/en-us/library/cc759073(WS.10).aspx
ATTENTION
Experion Clusters follow the same basic practice and ensures compatibility with TPS.
- 16 -
Chapter 2 - Planning a Windows domain/workgroup
In Active Directory, a site is a set of computers that are well connected by a high-speed network, such as
a Local Area Network (LAN). All computers within the same site typically reside in the same building, or
on the same campus network. A single site consists of one or more Internet Protocol (IP) subnets.
Subnets are subdivisions of an IP network, with each subnet possessing its own unique network
address. Use of sites allows administrators greater control of domain replication traffic across the entire
domain. In addition, Group Policy Objects can also be applied to the site.
Refer to the following Microsoft documentation for more information.http://technet.microsoft.com/en-
us/library/cc782048(WS.10).aspx
2.6.7 Active directory replications
Active Directory replication is the means by which changes to directory data are transferred between
domain controllers in an Active Directory forest. The Active Directory replication model defines
mechanisms to transfer directory updates automatically between domain controllers, thereby providing
a seamless replication solution for the Active Directory database.
For more information, refer to the following Microsoft documentation.
Active Directory Replication Model Technical Reference –
http://technet.microsoft.com/en-us/library/cc737314(WS.10).aspx
2.6.8 Functional levels in Active Directory
Functional levels determine the available Active Directory Domain Services (AD DS) domain or forest
capabilities and also determines which Windows Server operating systems you can run on domain
controllers in the domain or forest. This is essential for efficient Active Directory replication and domain
renaming activities.
Fpr more details refer https://technet.microsoft.com/library/understanding-active-directory-functional-
levels(v=ws.10).aspx.
ATTENTION
l Experion requires functional level Windows Server 2008 or higher.
l Functional levels define a set of operating systems only for the domain controllers in a
domain or a forest. It does not define the client operating systems in a domain or a forest.
l Before raising the functional level for a domain, or a forest, assess your requirements
appropriately. Once raised, you cannot lower the functional level for a domain or a forest.
Setting the functional level for a domain enables features that affect the entire domain and that domain
only. If all domain controllers in a domain are running , and the functional level is set to , all domain-
wide features are available.
l A domain controller cannot support a higher level than its own release. For example, a Windows
Server 2003 domain controller cannot be set to a Windows Server 2008 domain functional level.
l The domain functional level determines the domain and/or active directory capabilities or behaviors
available from the domain controller.
l All domain controllers in a domain must be at the same domain functional level.
Setting the functional level for a forest enables features across all the domains within a forest. If all
domain controllers in a forest are running and the functional level is set to , all forest-wide features are
available.
- 17 -
Chapter 2 - Planning a Windows domain/workgroup
TIP
l For more information about functional levels in a forest or a domain, refer to the following
Microsoft documentation.
http://technet.microsoft.com/en-us/library/cc738038(WS.10).aspx
l For information on how to raise functional levels in a forest or a domain, refer to the
following Microsoft documentation.
http://technet.microsoft.com/en-us/library/cc787290(WS.10).aspx
Ideally, all the servers in a domain must run the same or latest version of the operating system. Each
domain has capabilities/features associated with it. These capabilities/features depend on the Microsoft
Windows Server operating system running on all the domain controllers in that domain or forest. Until
all domain controllers are at that version or higher version, you cannot use those capabilities/features.
The mixed mode and native mode helps to raise the functional level of a domain or forest.
Mixed mode: allows a domain controller running previous versions of Microsoft operating systems to co-
exist in a domain/forest. The mixed mode is used when you do not want to upgrade all the domain
controllers to the latest version of Microsoft Windows server operating system, but still want some of the
features offered by the latest version in your domain or forest.
For example, consider an organization where all the domain controllers in a domain or forest run on
Microsoft Windows 2008 Server operating system. Upgrading some domain controllers to Windows
2008 R2 Server or Windows 2012 Server, while maintaining some domain controllers on Windows
Server 2008, enables the organization to take advantage of the latest functionality; even though all
domain controllers are not running Windows Server 2008 R2 or Windows 2012 Server. This implies that
the domain/forest is in the mixed mode of operation.
Native mode allows a domain controller to run only one version of operating system in a domain/forest.
It does not support interoperability with the previous version of operating system. Active Directory must
be configured in native mode.
For example, in a domain or forest if all the domain controllers in a domain are running Windows 2008
R2 Server or Windows 2012 Server and does not support the interoperability with Windows 2008, then
it is said to be in the native mode. Since domain/forest functional levels of Windows Server 2008 R2
and higher versions do not support Windows Server 2008 domain controllers, it implies that these
domain functional levels are "native".
ATTENTION
The forest level needs to be at least Windows Server 2003 level to support a read-only domain
controller. The read-only domain controller must be running at least Microsoft Windows Server
2008 operating system.
Refer to the recommended functional level of the domain table in the section Raising the functional
level of the domain of the Windows Domain Implementation Guide for Windows Server 2008 R2.
TIP
For more information on mixed mode and native mode, refer to the following Microsoft
documentation.
- 18 -
Chapter 2 - Planning a Windows domain/workgroup
l http://technet.microsoft.com/en-us/library/cc787290(v=ws.10).aspx
l http://technet.microsoft.com/en-us/library/aa996524(v=EXCHG.65).aspx
l http://technet.microsoft.com/en-us/library/cc738670(WS.10).aspx
l http://technet.microsoft.com/en-us/library/bb632431.aspx
The members in each OU receive the Group Policy assigned to their respective OU.
When you link GPOs to sites, domains, or OUs, the GPO links affect users and computers in the
following ways.
l GPOs are applied to the domain object by the closest linked GPO in the domain hierarchy.
o Site>Domain>OU>Domain Object, meaning if there were linked GPOs that conflicted with
each other at each level, the GPO applied is at the OU level.
l A GPO linked to a domain applies to all users and computers in the domain. By default, any domain
- 19 -
Chapter 2 - Planning a Windows domain/workgroup
l The scope of a GPO can also be controlled. For more information, refer to the topic Controlling the
scope of GPOs.
ATTENTION
The Administrator can also apply the computer-related policy settings manually.
- 20 -
Chapter 2 - Planning a Windows domain/workgroup
l Security settings
l Assigned and published software applications
l User logon and logoff scripts
l Folder redirection options
ATTENTION
The Administrator can also apply the user-related policy settings manually.
The Group Policy Management Console is used for viewing and editing the Group Policy Settings. The
settings under ‘Computer Configuration’ are applied to all computers that have this Group Policy
enforced on them. The settings under ‘User Configuration’ are applied to all users that have this Group
Policy enforced on them.
ATTENTION
l A GPO with settings limited to computer configuration does not have any effect when it is
applied to a user.
l A GPO with settings limited to user configuration does not have any effect when it is
applied to a computer.
- 21 -
Chapter 2 - Planning a Windows domain/workgroup
For more information on Group Policy, refer to Creating a Group Policy and Managing Group/domain
policy in this guide.
2.7.5 Interoperability of group policy objects
ATTENTION
Policy applied to the domain should match the highest version of the Experion/TPS release you
intend to run/support in the domain.
The group policy objects installed for Experion are interoperable with earlier releases of Experion and
TPS. They cannot coexist with policies from earlier releases in the same domain. The policies replace
earlier policy files to provide equivalent settings on earlier releases and enhanced security on
Experion. In addition, note that there are only three Experion Group Policies. For more information, refer
to the section Experion Group Policy descriptions.
2.8.2 Groups
A group is an Active Directory container object. The group can contain users, contacts, computers, and
other groups. The following are the two different types of groups.
- 22 -
Chapter 2 - Planning a Windows domain/workgroup
l Distribution groups
l Security groups
Distribution groups
Distribution groups have only one function that is creating e-mail distribution lists. Distribution groups
can be used with e-mail applications (like Microsoft Exchange) to send e-mail to the members of the
group. Changing group membership follows the same process as security groups. Distribution groups
cannot be used to apply security.
ATTENTION
Honeywell does not recommend the usage of e-mail on the process control domain used by
Experion and TPS.
Security groups
Security groups are an essential component of the relationship between users and resources. Security
groups perform the following functions.
l Manages user and computer access to the shared resources on the domain
l Filters Group Policy settings
Security groups can contain users, computers, and other groups. Using security groups simplifies
security administration by letting you assign permissions to the group rather than assigning permissions
to the individual users. When you add a new user to the group, the user receives all access permissions
assigned to the security group.
For more information about group scope, refer to the following Microsoft website link.
http://technet.microsoft.com/en-us/library/cc755692(WS.10).aspx
- 23 -
Chapter 2 - Planning a Windows domain/workgroup
l DNS deployment
l DNS integration with Active Directory
l DNS naming conventions
l DNS tools
For more information on DNS integration with Active Directory, refer to the following Microsoft
documentation.
l How DNS support for Active Directory works: http://technet.microsoft.com/en-us/library/cc759550
(WS.10).aspx
l DNS integration: http://technet.microsoft.com/en-us/library/cc785656(WS.10).aspx
For more information on DNS naming conventions, refer to the following Microsoft documentation.
http://technet.microsoft.com/en-us/library/cc978006.aspx
ATTENTION
Domain names must have a domain designator like .com, .org, or .local. Domain names without
domain designators will cause name resolution issues on the network.
- 24 -
Chapter 2 - Planning a Windows domain/workgroup
ATTENTION
Ensure that the following considerations are met while setting up domain controllers in an FTE
network.
l Install FTE drivers on the domain controllers. To install FTE drivers on the domain
controllers, there are some additional hardware considerations that must be met. For
more information, refer to the Experion Software Installation User's Guide and Experion
FTE Installation and Service Guide.
l Use Honeywell qualified Experion Server platforms for configuring domain controllers.
l For a basic overview of FTE, refer to the Experion FTE Overview and Implementation Guide.
l For domain controller topology diagrams, refer to the Network and Security Planning Guide.
l Refer to the Experion FTE Installation and Service Guide, for information on FTE installation on a
domain controller.
- 25 -
Chapter 2 - Planning a Windows domain/workgroup
l * – Requires patch
l A – DC security (required on one writable DC, not allowed on RODC)
l A+C – R400 DC Security including TPS Domain Console Configuration (required on at least one
writable DC, not allowed on RODC)
l B – FTE
l C – TPS Domain Console Configuration (optional on all writable DCs, not allowed on RODC)
(included in DC Security in R400.x)
l D – System Management
l E – USB Enable/Disable (R410 and later only)
Following are the rules related to the Experion components installed on a Domain Controller:
l If multiple versions of Experion coexist in a domain, the version of the Experion components
installed on the Domain Controller must be equal to or greater than the latest version of Experion
running in the domain (including point releases).
l If TPS and Experion coexist in a domain, the version of the Experion components installed on the
Domain Controller must be equal to or greater than the latest version of Experion running in the
domain (including point releases).
l The domain functional level of the domain (which is less than or equal to the Domain Controller
Server Operating System version) is restricted to the combinations above that indicate support for A
or A+C. For example, R431.1 supports Windows Server 2008 as the Domain Controller (indicated
by “A” in the R431.1/WS2008 box), however it does not support that Domain Controller being
configured as Windows Server 2003 Domain functional level (there is no an A in the
R431.1/WS2003 box).
- 26 -
Chapter 2 - Planning a Windows domain/workgroup
Microsoft also imposes some rules related to client operating systems joined to a domain of certain
functional levels, as indicated in the following table.
Windows Domain
Clients
Function Level
Server 2008 Server Server 2012 Server
Server 2003 Server 2008
R2 2012 R2 2016
Windows XP/Server
Y*** Y Y Y N N
2003
Windows Vista/Server
Y* Y Y Y Y Y
2008
Windows 7 Y** Y Y Y Y Y
Server 2008 R2 Y** Y* Y Y Y Y
Windows 8/Server 2012 Y** Y** Y* Y Y Y
Windows 8.1/Server
Y** Y** Y** Y* Y Y
2012 R2
Windows 10/Server
Y** Y** Y** Y** Y** Y
2016
l Y – Supported
l N – Deprecated (SMB 1.0)
l Y* – Supported but requires GPO update
l Y** – Supported but requires GPO Update and some features in client may not be supported
l Y*** – Supported but not recommended.
- 27 -
Chapter 2 - Planning a Windows domain/workgroup
ATTENTION
In virtual environments Honeywell recommends that you have at least one DC on each network
level serviced by the virtual environment, this would include a domain controller on level 2.5 and
each level 2 network. If the entire domain is hosted on virtual machines, you must ensure that the
virtual domain is always availability. Refer to the latest version of the following documents on
http://www.honeywellprocess.com for the hardware and software requirements of VM.
l HPS Virtualization Specification
l Virtualization Planning and Implementation Guide
- 28 -
CHAPTER
This section describes the tasks for integrating computers into an existing Windows domain.
This section does not describe how to create a Windows domain. For security-related guidelines about
Windows domains andExperion, refer to the Experion Network and Security Planning Guide.
l Creating mutually trusted domains
l Associating Windows domain account groups with the local account groups on a computer
ATTENTION
Creating a trust between two domains requires name resolution to be setup so that both
domains can resolve the other domain name. An example of this is setting up a secondary DNS
zone for the other domain.
If you are setting mutually trusted domains to support a control configuration such as the CDA-
SP service (ACE) on a different domain to an OPC server, consult your nearest Honeywell
representatives for additional configration requirements.
- 29 -
Chapter 3 - Integrating computers into a Windows domain
3.2.1 Prerequisites
l The computer must already be added to the domain.
l Perform this procedure on every computer in the domain where you want to implement the High
Security Policy.
After running the Link Domain Groups command, the Windows domain account groups are
linked to the local account groups as follows.
- 30 -
CHAPTER
ATTENTION
Any accounts that need to access other computers must have the same user name and
password on all computers. For more information about creating Windows Workgroup users and
groups, refer to the following Microsoft documentation.
http://technet.microsoft.com/en-us/library/cc775771(WS.10).aspx
- 31 -
CHAPTER
- 33 -
Chapter 5 - Security policies configured as part of Experion installation
- 34 -
Chapter 5 - Security policies configured as part of Experion installation
- 35 -
Chapter 5 - Security policies configured as part of Experion installation
- 36 -
Chapter 5 - Security policies configured as part of Experion installation
- 37 -
Chapter 5 - Security policies configured as part of Experion installation
- 38 -
Chapter 5 - Security policies configured as part of Experion installation
- 39 -
Chapter 5 - Security policies configured as part of Experion installation
- 40 -
Chapter 5 - Security policies configured as part of Experion installation
- 41 -
Chapter 5 - Security policies configured as part of Experion installation
- 42 -
Chapter 5 - Security policies configured as part of Experion installation
- 43 -
Chapter 5 - Security policies configured as part of Experion installation
- 44 -
Chapter 5 - Security policies configured as part of Experion installation
- 45 -
CHAPTER
- 47 -
CHAPTER
TIP
For more information about time synchronization and SNTP setup, refer to the Supplementary
Installation Tasks Guide.
NOTE
NTP Source could be a NTP Server at your site by name or IP address.
Example:
- 49 -
Chapter 7 - Setting up time synchronization
NOTE
The address of “10.0.1.10” is provided as an example. Please substitute with the IP or
name of an addressable NTP Server on your network.
ATTENTION
When creating a virtual domain controller, do not convert a physical domain controller to a virtual
domain controller.
TIP
For more information about time synchronization in a virtual environment, refer to the
Virtualization Planning and Implementation Guide.
- 50 -
CHAPTER
Parameter Description
Path to the Station.stn file. Do not include the path if the Station.stn file is in the same
stn
location as the Station.exe file.
-s Startup switches
Disables window resizing so that Station can only operate in full screen mode and is
f
always on top.
Disables window resizing so that Station can only operate in full screen mode and is
l
always on the bottom
x Disables the Exit menu choice
s Disables the Setup menu choice
c Disables the Connect menu choice
- 51 -
Chapter 8 - Securing the operating system
l Lock the Station window in full screen so that users cannot resize the window or access operating
system functions and non-Station applications.
l Disable the Exit menu choice so users cannot close down this Station.
l Disable the Setup menu choice so that users cannot change the connection or display settings for
this Station.
l Disable the Connect menu choice so that the users cannot attempt to connect to a different server
and disconnect from the current server.
By default, access to Intranet and Internet sites are disabled on Station. For information on enabling full
or restricted access via Station's SafeBrowse feature, refer to the section “Customizing Station - Web
Access tab, Connection properties” in the Server and Client Configuration Guide.
1. For domain account scripts, log on to the domain controller with a domain administrator account.
2. Use a text editor such as Notepad, to create the following batch file.
ATTENTION
If you use Signon Manager and Electronic Signatures, you must use the –sl option so
that Station is in full-screen mode but always on the bottom so that the Signon Manager
and Electronic Signatures dialog boxes appear on top of Station.
cd /d "%hwinstallpath%\Signon Manager"
start signon.exe
rem *******************************************
rem change to station directory
rem *******************************************
cd /d "%hwinstallpath%\Experion PKS\Client\Station"
rem *******************************************
rem the following line need only be included
rem if you are on the Server PC
rem and also using automatic logon.
rem It delays Station startup to let the
rem Server start completely first.
rem *******************************************
sleep 70
rem *******************************************
rem start station with "full screen lock" and always on top
rem and all 'Station" menu options inactive.
rem stnsetup.stn is optional, delete if not
rem required.
rem *******************************************
start station.exe "%HwProgramData%\Experion PKS\Client\Station\stnsetup.stn" -sslxc
- 52 -
Chapter 8 - Securing the operating system
WARNING
Do not add a network path to the ‘path’ environment variable.
3. Save the file according to the locations specified in one of the following sections.
l Assigning logon scripts to domain groups and users using group policy.
l Assigning logon scripts to individual domain accounts.
l Assigning logon scripts to local accounts.
To assign logon scripts to domain groups and users using group policy
- 53 -
Chapter 8 - Securing the operating system
- 54 -
Chapter 8 - Securing the operating system
- 55 -
Chapter 8 - Securing the operating system
13. For each user or group that you added to the Group or user names section, perform the following:
a. Click the name in the Group or user names list.
b. In the Permissions for dialog box, click the checkbox in the Deny column next to Read &
Execute/Allow.
14. When all necessary users/groups are denied the access to execute, click OK.
a. On some operating systems, the Windows Security dialog box appears with the following
message:
- 56 -
Chapter 8 - Securing the operating system
ATTENTION
l Computers must be configured individually for auto-logon in a domain or workgroup.
l Automatic logon can be useful in a Plant environment but you must use it with a very
restrictive user account. It should not be used with user accounts with administrative
privileges.
- 57 -
Chapter 8 - Securing the operating system
l If you set up automatic logon for a computer, to log on as an Administrator, you need to
press the Shift key to prevent automatic logon.
l After following the procedures for automatic logon, automatic logon is set the first time
after any restart. To get the computer to automatic logon after each restart and each
logoff, you must set the registry value of ForceAutoLogon = 1 in the same key.
CAUTION
l Editing Windows registry can cause serious problems, if modified incorrectly. To recover
from the problem, you might have to reinstall the operating system. As a best practice,
ensure that you take a back up of the Windows registry before making any changes.
l This mechanism of changing the password is a security risk since a clear text password
would be visible in the registry entry.
To set up an automatic logon in a domain or workgroup, edit the following registry entries.
l HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon key:
l DefaultUserName = the user account name
l DefaultPassword = the password for that account
l DefaultDomainName = computer name for local accounts or domain name for domain accounts
l AutoAdminLogon = 1
- 58 -
Chapter 8 - Securing the operating system
Product Administrators, Engineers, and Supervisors can shut down a computer in several ways.
l From the Start menu.
l By pressing CTRL+ALT+DEL.
l At the logon screen.
To prevent Product Administrators, Engineers and Supervisors from shutting down the computer, you
must change the local policies and edit the registry.
To change the local policies to prevent shut down by selected users on Windows 7 operating system:
1. Choose Start > Windows System > Control Panel > System and Maintenance > Administrative
Tools > Local Security Policy.
2. In the navigation pane, choose Local Policies > Security Options.
3. Select Local Policies > User Rights Assignment.
4. Double-click Shutdown the system.
The Shut down the system Properties dialog box opens. Typical settings will include
Administrators, Backup Operators, Product Administrators, Local Supervisors, and Local
Engineers.
5. Remove any users or groups that must not be able to shut down the system.
6. Add any additional users or groups that must able to shut down the system.
7. Click OK to close the Shut down the system Properties dialog box.
8. Close the Local Security Policy window.
To change the local policies to prevent shut down by selected users on Windows 10 operating
system:
1. Choose Start > Windows Administrative Tools > Local Security Policy.
2. Select Local Policies > User Rights Assignment.
3. Double-click Shutdown the system.
The Shut down the system Properties dialog box opens. Typical settings will include
Administrators, Backup Operators, Product Administrators, Local Supervisors, and Local
Engineers.
4. Remove any users or groups that must not be able to shut down the system.
5. Add any additional users or groups that must able to shut down the system.
6. Click OK to close the Shut down the system Properties dialog box.
7. Close the Local Security Policy window.
- 59 -
Chapter 8 - Securing the operating system
To prevent Product Administrators, Engineers and Supervisors from locking the computer, you need to
change the local policies and edit the registry.
1. Choose Start > Run, type mmc and click OK.
2. On the User Account Control dialog box, click Yes.
3. In the Console Root window, select File > Add/Remove Snap-in.
4. In the Add or Remove Snap-ins dialog box, select Group Policy Object Editor, click Add.
5. In the Select Group Policy Object dialog box, click Finish.
6. In the Add or Remove Snap-ins dialog box, click OK.
7. In the Console Root windows navigation pane, select Local Computer Policy > User Configuration
> Administrative Templates > System > Ctrl + Alt + Del Options.
8. In the right pane, double-click Remove Lock Computer.
9. In the Remove Lock Computer dialog box, click Enabled, and then click Apply.
10. Press CTRL+ALT+DEL to verify that Lock Computer option is disabled. Click Cancel.
11. Click OK to close the Disable Lock Computer Properties dialog box.
To prevent Product Administrators, Engineers and Supervisors from locking the computer, you need to
change the local policies and edit the registry.
1. Choose Start > Run, type mmc and click OK.
2. On the User Account Control dialog box, click Yes.
3. In the Console Root window, select File > Add/Remove Snap-in.
4. In the Add or Remove Snap-ins dialog box, select Group Policy Object Editor, click Add.
5. In the Select Group Policy Object dialog box, click Finish.
6. In the Add or Remove Snap-ins dialog box, click OK.
7. In the Console Root windows navigation pane, select Local Computer Policy > User Configuration
> Administrative Templates > System > Ctrl + Alt + Del Options.
8. In the right pane, double-click Remove Lock Computer.
9. In the Remove Lock Computer dialog box, click Enabled, and then click Apply.
10. Press CTRL+ALT+DEL to verify that Lock Computer option is disabled. Click Cancel.
11. Click OK to close the Disable Lock Computer Properties dialog box.
12. Click Save the settings.
The dialog box prompts location to save template for this settings.
13. Select the default location and save.
- 60 -
Chapter 8 - Securing the operating system
ATTENTION
You can disable these two components only if DNS Server is configured in your network. If DNS
Server is not configured, then disabling these two components will fail Computer name to IP
resolution, which impact Experion functions.
To disable LLMNR.
1. Click Start
2. Type gpedit.msc in the text box
3. Navigate to
Local Computer Policy > Computer Configuration > Administrative Templates > Network > DNS
Client
4. In the DNS Client Folder, double click on Turn Off Multicast Name Resolution and set it to
Enabled.
To disable NetBT.
1. Open Control Panel
2. Under Network and Internet, click View network status and tasks
3. Click Change adapter settings
4. Right-click “<Honeywell FTE Adapter>” and then click “Properties”
5. Double-click on “Internet Protocol Version 4 (TCP/IPv4)”, click “Advanced” then click on the
“WINS” (Windows Internet Name Service) tab
6. Click on “Disable NetBIOS over TCP/IP"
7. Click Ok.
- 61 -
CHAPTER
l Introduction
l Installation of USB Storage Enable Disable feature using Experion PKS Installation media
l Managing the USB Storage Enable Disable feature
9.1 Introduction
An administrator can enable or disable the use of USB-connected storage devices, such as flash
drive, floppy disk, CD/DVD on the Experion systems in domain or workgroup environments. However,
use of other types of USB devices such as keyboards, mouse, finger print readers, and smart cards are
not affected.
- 63 -
Chapter 9 - Enabling or disabling USB-connected storage devices on Experion systems
NOTE
If you prefer to block one or more execution(s), such as read or write access rather than providing
all access. Use one of the following settings instead at step 5:
l Removable Disks: Deny execute access
l Removable Disks: Deny read access
l Removable Disks: Deny write access
By default this change should take effect on machines in the OU within 2 hours, alternately from a
command prompt or PowerShell window on the domain controller, run as an administrator to execute
the following command and push the change out immediately:
gpupdate /force
- 64 -
CHAPTER
10 MANAGING DOMAINS
ATTENTION
You must not modify theExperion group policies, as each update to Experion overwrites these
policies, eliminating any changes you have made. To change policy settings, create a new
Group Policy Object (GPO), add only the settings you need to change, and link the policy such
that the new settings override the Experion setting. Warning: Be cautious while overriding
Experion policy settings as it may affect the operation of Experion.
To edit a group policy, choose Administrative Tools > Group Policy Management, locate the
policy to be edited under Forest > Domains ><<your domain>>Group Policy Objects, and then
right-click and select Edit.
For more information, refer to the following Microsoft documentation-
http://technet.microsoft.com/en-us/library/cc759123(WS.10).aspx.
- 65 -
Chapter 10 - Managing domains
ATTENTION
When unlinking a GPO, do NOT delete the object from the Group Policy Objects, as this
deletes the GPO. Deleting the GPO from under the domain (or an OU) deletes the link to
the object, and not the object itself.
TIP
For more information about working with group policies, refer to the following Microsoft
documentation.
http://technet.microsoft.com/en-us/library/cc783034(WS.10).aspx
Renaming must be done without interruptions to the domain controller. The recommended practice for
renaming a domain controller without interruption to clients is to use the Netdom tool. However, there
would be a temporary interruption when the domain controller is restarted after a rename.
TIP
For more information about renaming a domain controller, refer to the following Microsoft
documentation:
http://technet.microsoft.com/en-us/library/cc782761(WS.10).aspx
- 66 -
Chapter 10 - Managing domains
CAUTION
l If the domain has only one domain controller, removing a domain leads to permanent
loss of data (like User, Groups, and Accounts) contained in the domain. Hence, exercise
caution before taking up this activity.
l As long as the domain has multiple domain controllers, no data loss should happen.
Before performing this task, ensure the following:
o If this domain controller is a GC server, ensure that another GC server is
available to the users.
o Transfer any of the operation master roles held by the domain controller to
another domain controller.
- 67 -
CHAPTER
l Managing security
l DNS Recommendations for large FTE networks
TIP
Refer to the chapter, “Configuring System Security” in the Experion Server and Client
Configuration Guide. Additionally, you can refer to the Appendix in this document.
11.2.1 Overview
There are numerous DNS design strategies based on the location and layout of network resources.
This section only addresses the network design recommendations for large FTE networks. In small
network implementations, having one or two domain controllers running DNS will satisfy most of the
network design goals. When implementing a large FTE network, especially with multiple level 2 FTE
communities that communicate with a common level 3 network, the layout of DNS could affect name
resolution across the entire network.
11.2.2 Recommendation
In a large FTE network, the major design goal is to minimize network traffic that needs to be routed to
the level 3 network while at the same time ensuring name resolution to the local network in which the
domain controller resides. To help minimize DNS traffic, there should be at least one domain controller
running DNS on each level 2 FTE community and at least one domain controller running DNS on the
level 3 network.
The preferred DNS server on each domain controller should be its local IP address. The alternate DNS
server on each domain controller in each level 2 FTE community should be the IP address of the level
3 domain controller that is running DNS.
The computer nodes on each level 2 FTE community should have their preferred DNS server and their
alternate DNS server set to the same IP addresses as the domain controller for that level 2 FTE
community. This will isolate the majority of DNS traffic and domain authentication to the local domain
controller in each level 2 FTE community.
- 69 -
Chapter 11 - Advanced Domain administration
Another configuration aspect that needs to be addressed is that of reverse lookup zone configuration for
this type of network design. It is assumed that each level 2 FTE community and the level 3 network will
have different IP networks. To ensure that reverse lookup (PTR) records are created for each host in
each IP network, the initial reverse lookup zone should be larger than the single IP network.
In the following network example, all of the IP networks share a common network identifier, in this case
172.21.x.x. In this situation, the reverse lookup zone should reference 172.21 as the network ID when
creating the reverse lookup zone. This will allow all of the level 2 and level 3 hosts to be contained in a
single reverse lookup zone.
Level Network
3 172.21.1.x
2 172.21.2.x
2 172.21.3.x
Consider 2 Domain Controllers are hosting DNS. Domain Controller 1 has an IP Address 10.0.1.3 and
Domain Controller 2 has an IP Address 10.0.1.4.
Using the cross registration pattern:
l Domain Controller 1 (10.0.1.3) DNS configuration should have a preferred of 10.0.1.4, and alternate
of 127.0.0.1.
l Domain Controller 2 (10.0.1.4) DNS configuration should have a preferred of 10.0.1.3, and alternate
of 127.0.0.1.
- 70 -
CHAPTER
12 APPENDIX
- 71 -
Chapter 12 - Appendix
- 72 -
Chapter 12 - Appendix
- 73 -
Chapter 12 - Appendix
- 74 -
Chapter 12 - Appendix
- 75 -
Chapter 12 - Appendix
- 76 -
Chapter 12 - Appendix
- 77 -
Chapter 12 - Appendix
- 78 -
Chapter 12 - Appendix
- 79 -
Chapter 12 - Appendix
- 80 -
Chapter 12 - Appendix
- 81 -
Chapter 12 - Appendix
- 82 -
Chapter 12 - Appendix
- 83 -
Chapter 12 - Appendix
- 84 -
Chapter 12 - Appendix
- 85 -
Chapter 12 - Appendix
- 86 -
Chapter 12 - Appendix
- 87 -
Chapter 12 - Appendix
- 88 -
Chapter 12 - Appendix
- 89 -
Chapter 12 - Appendix
- 90 -
Chapter 12 - Appendix
- 91 -
Chapter 12 - Appendix
- 92 -
Chapter 12 - Appendix
- 93 -
Chapter 12 - Appendix
- 94 -
Chapter 12 - Appendix
- 95 -
Chapter 12 - Appendix
- 96 -
Chapter 12 - Appendix
- 97 -
Chapter 12 - Appendix
- 98 -
Chapter 12 - Appendix
- 99 -
Chapter 12 - Appendix
- 100 -
Chapter 12 - Appendix
- 101 -
Chapter 12 - Appendix
- 102 -
Chapter 12 - Appendix
- 103 -
Chapter 12 - Appendix
- 104 -
Chapter 12 - Appendix
- 105 -
Chapter 12 - Appendix
TIP
To Turn off personalized menus without
specifying a setting, click Start, click
Settings, click Taskbar and Start Menu,
and then, on the General tab, clear the
"Use Personalized Menus" option.
TIP
To display the welcome screen, click
Start, point to Programs, point to
Accessories, point to System Tools, and
then click "Getting Started." To suppress
the welcome screen without specifying a
setting, clear the "Show this screen at
startup" check box on the welcome
- 106 -
Chapter 12 - Appendix
screen.
Microsoft
Windows
XP
/Microsoft
Windows
Server
2003 (32- Disables the Windows registry editor Regedit.exe.
bit),
If this setting is enabled and the user tries to start a
Operational Microsoft
registry editor, a message appears explaining that a
\System::Prevent access to Roles and Windows
setting prevents the action.
registry editing tools Engineerin Vista
g Role /Microsoft To prevent users from using other administrative
Windows tools, use the "Run only specified Windows
Server applications" setting.
2008
Standard,
Microsoft
Windows 7
Profession
al (32-bit)/
No
Operational
Disable regedit from
Roles and
running silently
Engineerin
g Role.
Microsoft
Windows
XP
/Microsoft
Windows Prevents users from running the interactive
Server command prompt, Cmd.exe. This setting also
2003 (32- determines whether batch files (.cmd and .bat) can
bit), run on the computer.
Microsoft
If you enable this setting and the user tries to open a
\System::Prevent access to Operational Windows
command window, the system displays a message
the command prompt Roles Vista
explaining that a setting prevents the action.
/Microsoft
Windows Note: Do not prevent the computer from running
Server batch files if the computer uses logon, logoff, startup,
2008 or shutdown batch file scripts, or for users that use
Standard, Remote Desktop Services.
Microsoft
Windows 7
Profession
al (32-bit)/
Disable the command No
prompt script processing Operational
also Roles.
Microsoft Prevents users from locking the system.
\System\Ctrl+Alt+Del Windows
Operational While locked, the desktop is hidden and the system
Options::Remove Lock XP
Roles cannot be used. Only the user who locked the
Computer /Microsoft
system or the system administrator can unlock it.
- 107 -
Chapter 12 - Appendix
- 108 -
Chapter 12 - Appendix
- 109 -
Chapter 12 - Appendix
- 110 -
Chapter 12 - Appendix
- 111 -
Chapter 12 - Appendix
TIP
This setting affects existing tasks only. To
prevent users from changing the
- 112 -
Chapter 12 - Appendix
- 113 -
Chapter 12 - Appendix
- 114 -
Chapter 12 - Appendix
- 115 -
Chapter 12 - Appendix
- 116 -
Chapter 12 - Appendix
- 117 -
Chapter 12 - Appendix
- 118 -
Chapter 12 - Appendix
- 119 -
Chapter 12 - Appendix
- 120 -
Chapter 12 - Appendix
- 121 -
Chapter 12 - Appendix
- 122 -
Chapter 12 - Appendix
- 123 -
Chapter 12 - Appendix
- 124 -
Chapter 12 - Appendix
Permissi
Scop
Registry PermissionsKey on for
e
Subkey
Operator RW Full
Local Servers RW RW R
W
HKLM\software\Clients\Mail (add - legacy) Product RW
Admins
Local Servers RW RW R
HKLM\SYSTEM\CurrentControlSet\Control\SecurePipeServer Local R
s\winreg (add) Servers
Local Servers R R
HKLM\Software\Microsoft\Windows Product R R
NT\CurrentVersion\WbemPerf (add) Admins
Local Servers R R
- 125 -
Chapter 12 - Appendix
Windows Users RX RX RX
Windows Users RX RX RX
Windows Users RX RX RX
Windows Users RX RX R
- 126 -
Chapter 12 - Appendix
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Supervisor RX
- 127 -
Chapter 12 - Appendix
Operator RX
Supervisor RX
Supervisor RX
Operator RX
Supervisor RX
Operator RX
Ack View RX
Supervisor RX
Operator RX
Ack View RX
View Only RX
Engineer RX
Supervisor RX
Operator RX
Ack View RX
View Only RX
- 128 -
Chapter 12 - Appendix
Engineer RX
Supervisor RX
Operator RX
Ack View RX
View Only RX
Engineer RX
Supervisor RX
Engineer RX
Supervisor RX
In the preceding table, strings between percent signs (%) represent system environment variables that
may vary based on installation conditions. The default values for these are:
l .................................%HwProgramData% C:\ProgramData\Honeywell
l .................................%HwEngineeringData%
C:\ProgramData\Honeywell\EngineeringData
l .................................%HwProductConfig% C:\ProgramData\Honeywell\ProductConfig
l .................................%HwSecurityPath%
C:\ProgramData\Honeywell\ProductConfig\Security
- 129 -
Chapter 12 - Appendix
Window
s server Window Window Window
Window Window Window
Window 2008/20 s server s Server Window s Server
Local Policy s 7 for s 10 for s Server
s7 08 R2 2008/20 2012/20 s 10 2016 for
Settings Experio Experio 2016
defaults for 08 R2 12 R2 defaults Experio
n n defaults
Experio defaults defaults n
n
[System Access]
MinimumPasswor
0 0 0 0 1 1 1 1 1
dAge
MaximumPasswo
-1 42(*) -1 42(*) 42 42 42 42 42
rdAge
MinimumPasswor
0 0 0 0 7 7 7 7 7
dLength
PasswordComple
0(**) 0 1(**) 1 1 1 0 1 1
xity
PasswordHistory
10 0(*) 10 0(*) 24 24
Size
LockoutBadCount 0 0 0 0 0 0
RequireLogonTo
0 0 0 0
ChangePassword
ForceLogoffWhen
0 0 0 0 0 0
HourExpire
NewAdministrator Administ Administ Administ Administ
Name rator rator rator rator
NewGuestName Guest Guest Guest Guest
ClearTextPasswo
0 0 0 0
rd
LSAAnonymousN
0 0 0 0
ameLookup
EnableAdminAcc
0(**) 0 1(**) 1 0 0
ount
EnableGuestAcco
0 0 0 0 0 0
unt
[Event Audit]
AuditSystemEven
0 0 0 0
ts
AuditLogonEvent
2 0(*) 2 0(*)
s
AuditObjectAcces
0 0 0 0
s
AuditPrivilegeUse 0 0 0 0
AuditPolicyChang
3 0(*) 3 0(*)
e
AuditAccountMan
0 0 0 0
age
AuditProcessTrac
0 0 0 0
king
AuditDSAccess 0 0 0 0
AuditAccountLog
2 0(*) 2 0(*)
on
- 130 -
Chapter 12 - Appendix
[Registry Values]
HKLM\software\m
icrosoft\Ole\Enabl "Y" "Y" "Y" "Y" "Y" "Y" "Y" "Y" "Y"
eDCOM
HKLM\software\m
icrosoft\Ole\Legac
2 (*) 2 (*) (*) (*) (*) (*) (*)
yAuthenticationLe
vel
HKLM\software\m
icrosoft\Ole\Legac
3 2 3 2 2 3 2 3 2
yImpersonationLe
vel
HKLM\software\m
icrosoft\windows\
currentversion\pol
1 (*) 1 (*) (*) 1 (*) 1 (*)
icies\system\Hide
FastUserSwitchin
g
HKLM\software\m
icrosoft\windows\
currentversion\pol 0 (*) 0 (*) (*) 0 (*) 0 (*)
icies\system\Logo
nType
HKLM\SOFTWAR
E\Microsoft\Windo
ws\Windows Error
10 (*) 10 (*) (*) 10 (*) 10 (*)
Reporting\LocalD
umps\DumpCoun
t
"%HwPr "%HwPr "%HwPr "%HwPr
HKLM\SOFTWAR
ogramD ogramD ogramD ogramD
E\Microsoft\Windo
ata%\ ata%\ ata%\ ata%\
ws\Windows Error
Experio (*) Experio (*) (*) Experio (*) Experio (*)
Reporting\LocalD
n PKS n PKS n PKS n PKS
umps\DumpFolde
\CrashD \CrashD \CrashD \CrashD
r
ump ump" ump" ump"
HKLM\SOFTWAR
E\Microsoft\Windo
ws\Windows Error 2 (*) 2 (*) (*) 2 (*) 2 (*)
Reporting\LocalD
umps\DumpType
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio
0 0 0 0 0 0 0 0 0
n\Setup\Recovery
Console\Security
Level
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio
0 0 0 0 0 0 0 0 0
n\Setup\Recovery
Console\SetCom
mand
HKLM\Software\M
icrosoft\Windows “0” (*) “0” (*) (*) “0” (*) “0” (*)
NT\CurrentVersio
- 131 -
Chapter 12 - Appendix
n\Winlogon\Alloc
ateCDRoms
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio “0” (*) “0” (*) (*) “0” (*) “0” (*)
n\Winlogon\Alloc
ateDASD
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio “1” (*) “1” (*) (*) “1” (*) “1” (*)
n\Winlogon\Alloc
ateFloppies
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio “10” “10” “10” “25”(*) 10 10 10 10 10
n\Winlogon\Cach
edLogonsCount
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio 0 0 0 0 0 0 0 0 0
n\Winlogon\Force
UnlockLogon
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio
5(**) 5 14(**) 14 5 5 5 5 5
n\Winlogon\Pass
wordExpiryWarni
ng
HKLM\Software\M
icrosoft\Windows
NT\CurrentVersio “0” “0” “0” “0” “0” “0” “0” “0” “0”
n\Winlogon\ScRe
moveOption
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
5(**) 5 2(**) 2 5 5 5 5 5
olicies\System\Co
nsentPromptBeha
viorAdmin
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
3(**) 3 1(**) 1 3 3 3 3 3
olicies\System\Co
nsentPromptBeha
viorUser
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P 0 0 0 0 0 0 (*) 0 0
olicies\System\Di
sableCAD
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
1 (*) 1 0(*) 0 1 0 1 0
olicies\System\Do
ntDisplayLastUse
rName
- 132 -
Chapter 12 - Appendix
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
1 1 1 1 1 1 1 1 1
olicies\System\En
ableInstallerDete
ction
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P 1 1 1 1 1 1 1 1 1
olicies\System\En
ableLUA
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
1 1 1 1 1 1 1 1 1
olicies\System\En
ableSecureUIAPa
ths
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
0 0 0 0 1 1 1 1 1
olicies\System\En
ableUIADesktopT
oggle
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P 0 1(*) 0 1(*) 0 0 0 0 0
olicies\System\En
ableVirtualization
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
1 0(*) 1 0(*) 1 0 1 0 1
olicies\System\Filt
erAdministratorTo
ken
HKLM\Software\M
icrosoft\Windows\ "Importa "Importa "Importa "Importa
No No No
CurrentVersion\P nt 0(*) nt 0(*) nt nt
Value Value Value
olicies\System\Le Notice:" Notice:" Notice:" Notice:"
galNoticeCaption
“Do not “ Do not “ Do not “ Do not
attempt attempt attempt attempt
HKLM\Software\M
to log on to log on to log on to log on
icrosoft\Windows\
unless unless No unless No unless No
CurrentVersion\P 0(*) 0(*)
you are you are Value you are Value you are Value
olicies\System\Le
an an an an
galNoticeText
authoriz authoriz authoriz authoriz
ed user” ed user” ed user” ed user”
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
0 1(*) 0 1(*) 1 0 1 0 1
olicies\System\Pr
omptOnSecureDe
sktop
HKLM\Software\M
icrosoft\Windows\
0 0 0 0 0 0 0 0 0
CurrentVersion\P
olicies\System\Sc
- 133 -
Chapter 12 - Appendix
ForceOption
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
1(**) 1 0(**) 0 0 1 1 1 0
olicies\System\Sh
utdownWithoutLo
gon
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
1 1 1 1 1 1 1 1 1
olicies\System\Un
dockWithoutLogo
n
HKLM\Software\M
icrosoft\Windows\
CurrentVersion\P
0 0 0 0 0 0 0 0 0
olicies\System\Va
lidateAdminCode
Signatures
HKLM\Software\P
olicies\Microsoft\
Windows\Safer\C
0 0 0 0 0 0 0 0 0
odeIdentifiers\Aut
henticodeEnable
d
HKLM\System\Cu
rrentControlSet\C
0 0 0 0 0 0 0 0 0
ontrol\Lsa\AuditB
aseObjects
HKLM\System\Cu
rrentControlSet\C
0 0 0 0 0 0 0 0 0
ontrol\Lsa\Crash
OnAuditFail
HKLM\System\Cu
rrentControlSet\C
0 0 0 0 0 0 0 0 0
ontrol\Lsa\Disabl
eDomainCreds
HKLM\System\Cu
rrentControlSet\C
ontrol\Lsa\Everyo 0 0 0 0 0 0 0 0 0
neIncludesAnony
mous
HKLM\System\Cu
rrentControlSet\C
ontrol\Lsa\FIPSAl 0 0 0 0 0 0 0 0 0
gorithmPolicy\En
abled
HKLM\System\Cu
rrentControlSet\C
0 0 0 0 0 0 0 0 0
ontrol\Lsa\ForceG
uest
HKLM\System\Cu
rrentControlSet\C
0 0 0 0 0 0 0 0 0
ontrol\Lsa\FullPriv
ilegeAuditing
HKLM\System\Cu 1 1 1 1 1 1 1 1 1
- 134 -
Chapter 12 - Appendix
rrentControlSet\C
ontrol\Lsa\LimitBl
ankPasswordUse
HKLM\System\Cu
rrentControlSet\C
4 (*) 4 3(*) (*) 4 (*) 4 (*)
ontrol\Lsa\LmCo
mpatibilityLevel
HKLM\System\Cu
rrentControlSet\C
536,870 536,870 536,870 536,870 53, 68, 536,870 53, 68,
ontrol\Lsa\MSV1_ 0(**) 0
,912(**) ,912 ,912 ,912 70, 91, 2 ,912 70, 91, 2
0\NTLMMinClient
Sec
HKLM\System\Cu
rrentControlSet\C
536,870 536,870 536,870 536,870 53, 68, 536,870 53, 68,
ontrol\Lsa\MSV1_ 0(**) 0
,912(**) ,912 ,912 ,912 70, 91, 2 ,912 70, 91, 2
0\NTLMMinServe
rSec
HKLM\System\Cu
rrentControlSet\C
1 1 1 1 1 1 1 1 1
ontrol\Lsa\NoLM
Hash
HKLM\System\Cu
rrentControlSet\C
0 0 0 0 0 0 0 0 0
ontrol\Lsa\Restrict
Anonymous
HKLM\System\Cu
rrentControlSet\C
1 1 1 1 1 1 1 1 1
ontrol\Lsa\Restrict
AnonymousSAM
HKLM\System\Cu
rrentControlSet\C
ontrol\Print\Provid
1 0(*) 1 1 1 1 0 1 1
ers\LanMan Print
Services\Servers\
AddPrinterDrivers
System\ System\ System\ System\ System\ System\ System\ System\ System\
Current Current Current Current Current Current Current Current Current
Control Control Control Control Control Control Control Control Control
Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont
rol\Prod rol\Prod rol\Prod rol\Prod rol\Prod rol\Prod rol\Prod rol\Prod rol\Prod
uctOptio uctOptio uctOptio uctOptio uctOptio uctOptio uctOptio uctOptio uctOptio
ns, ns, ns, ns, ns, ns, ns, ns, ns,
System\ System\ System\ System\ System\ System\ System\ System\ System\
HKLM\System\Cu Current Current Current Current Current Current Current Current Current
rrentControlSet\C Control Control Control Control Control Control Control Control Control
ontrol\SecurePipe Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont Set\Cont
Servers\Winreg\Al rol\Serv rol\Serv rol\Serv rol\Serv rol\Serv rol\Serv rol\Serv rol\Serv rol\Serv
lowedExactPaths\ er er er er er er er er er
Machine Applicati Applicati Applicati Applicati Applicati Applicati Applicati Applicati Applicati
ons, ons, ons, ons, ons, ons, ons, ons, ons,
Softwar Softwar Softwar Softwar Softwar Softwar Softwar Softwar Softwar
e\Micros e\Micros e\Micros e\Micros e\Micros e\Micros e\Micros e\Micros e\Micros
oft\Wind oft\Wind oft\Wind oft\Wind oft\Wind oft\Wind oft\Wind oft\Wind oft\Wind
ows ows ows ows ows ows ows ows ows
NT\Curr NT\Curr NT\Curr NT\Curr NT\Curr NT\Curr NT\Curr NT\Curr NT\Curr
entVersi entVersi entVersi entVersi entVersi entVersi entVersi entVersi entVersi
on on on on on on on on on
- 135 -
Chapter 12 - Appendix
- 136 -
Chapter 12 - Appendix
- 137 -
Chapter 12 - Appendix
ervices\LanManS
erver\Parameters\
EnableSecuritySi
gnature
HKLM\System\Cu
rrentControlSet\S “ “
No No No No No
ervices\LanManS (**) browse browse
value value value value value
erver\Parameters\ r”(**) r”
NullSessionPipes
HKLM\System\Cu
rrentControlSet\S
ervices\LanManS
0 0 0 0 0 0 0 0 0
erver\Parameters\
RequireSecurityS
ignature
HKLM\System\Cu
rrentControlSet\S
ervices\LanManS
1 1 1 1 1 1 1 1 1
erver\Parameters\
RestrictNullSessA
ccess
HKLM\System\Cu
rrentControlSet\S
ervices\LanmanW
0 0 0 0 0 0 0 0 0
orkstation\Param
eters\EnablePlain
TextPassword
HKLM\System\Cu
rrentControlSet\S
ervices\LanmanW
1 1 1 1 1 1 1 1 1
orkstation\Param
eters\EnableSecu
ritySignature
HKLM\System\Cu
rrentControlSet\S
ervices\LanmanW
0 0 0 0 0 0 0 0 0
orkstation\Param
eters\RequireSec
uritySignature
HKLM\System\Cu
rrentControlSet\S
1 1 1 1 1 1 1 1 1
ervices\LDAP\LD
APClientIntegrity
HKLM\System\Cu
rrentControlSet\S
ervices\Netlogon\
0 0 0 0 0 0 0 0 0
Parameters\Disab
lePasswordChan
ge
HKLM\System\Cu
rrentControlSet\S
ervices\Netlogon\
30 30 30 30 30 30 30 30 30
Parameters\Maxi
mumPasswordAg
e
HKLM\System\Cu 1 1 1 1 1 1 1 1 1
- 138 -
Chapter 12 - Appendix
rrentControlSet\S
ervices\Netlogon\
Parameters\Requ
ireSignOrSeal
HKLM\System\Cu
rrentControlSet\S
ervices\Netlogon\ 1(**) 1 0(**) 0 1 1 1 1 1
Parameters\Requ
ireStrongKey
HKLM\System\Cu
rrentControlSet\S
ervices\Netlogon\ 1 1 1 1 1 1 1 1 1
Parameters\Seal
SecureChannel
HKLM\System\Cu
rrentControlSet\S
ervices\Netlogon\ 1 1 1 1 1 1 1 1 1
Parameters\Sign
SecureChannel
[Privileg [Privileg [Privileg [Privileg [Privileg [Privileg [Privileg [Privileg
[Privileg
[Privilege Rights] e e e e e e e e
e Rights]
Rights] Rights] Rights] Rights] Rights] Rights] Rights] Rights]
Everyon Everyon Everyon Everyon Everyon Everyon Everyon Everyon Everyon
e, e, e, e, e, e, e, e, e,
Administ Administ Administ Administ Administ Administ Administ Administ Administ
SeNetworkLogon rators, rators, rators, rators, rators, rators, rators, rators, rators,
Right Users, Users, Users, Users, Users, Users, Users, Users, Users,
Backup Backup Backup Backup Backup Backup Backup Backup Backup
Operato Operato Operato Operato Operato Operato Operato Operato Operato
rs rs rs rs rs rs rs rs rs
Administ Administ Administ Administ Administ Administ Administ Administ Administ
rators, rators, rators, rators, rators, rators, rators, rators, rators,
SeBackupPrivileg
Backup Backup Backup Backup Backup Backup Backup Backup Backup
e
Operato Operato Operato Operato Operato Operato Operato Operato Operato
rs rs rs rs rs rs rs rs rs
Everyon Everyon Everyon Everyon Everyon Everyon Everyon Everyon Everyon
e, Local e, Local e, Local e, Local e, Local e, Local e, Local e, Local e, Local
Service, Service, Service, Service, Service, Service, Service, Service, Service,
Network Network Network Network Network Network Network Network Network
Service, Service, Service, Service, Service, Service, Service, Service, Service,
SeChangeNotifyP
Administ Administ Administ Administ Administ Administ Administ Administ Administ
rivilege
rators, rators, rators, rators, rators, rators, rators, rators, rators,
Users, Users, Users, Users, Users, Users, Users, Users, Users,
Backup Backup Backup Backup Backup Backup Backup Backup Backup
Operato Operato Operato Operato Operato Operato Operato Operato Operato
rs rs rs rs rs rs rs rs rs
Local Local Local Local Local Local Local Local Local
SeSystemtimePri Service, Service, Service, Service, Service, Service, Service, Service, Service,
vilege Administ Administ Administ Administ Administ Administ Administ Administ Administ
rators rators rators rators rators rators rators rators rators
SeCreatePagefile Administ Administ Administ Administ Administ Administ Administ Administ Administ
Privilege rators rators rators rators rators rators rators rators rators
SeDebugPrivileg Administ Administ Administ Administ Administ Administ Administ Administ Administ
e rators rators rators rators rators rators rators rators rators
SeRemoteShutdo Administ Administ Administ Administ Administ Administ Administ Administ Administ
wnPrivilege rators rators rators rators rators rators rators rators rators
- 139 -
Chapter 12 - Appendix
- 140 -
Chapter 12 - Appendix
180934 180934
0420(**) 0420
Local Local Local Local Local Local Local Local Local
SeAssignPrimary Service, Service, Service, Service, Service, Service, Service, Service, Service,
TokenPrivilege Network Network Network Network Network Network Network Network Network
Service Service Service Service Service Service Service Service Service
Administ Administ Administ Administ Administ Administ Administ Administ Administ
rators, rators, rators, rators, rators, rators, rators, rators, rators,
SeRestorePrivile
Backup Backup Backup Backup Backup Backup Backup Backup Backup
ge
Operato Operato Operato Operato Operato Operato Operato Operato Operato
rs rs rs rs rs rs rs rs rs
Local Local Local Local
Enginee Enginee Enginee Enginee
rs, Local rs, Local rs, Local rs, Local
Supervi Supervi Supervi Supervi
Administ
sors, sors, Administ Administ sors, Administ sors, Administ
rators,
Product Product rators, rators, Product rators, Product rators,
SeShutdownPrivil Users,
Administ Administ Backup Backup Administ Backup Administ Backup
ege Backup
rators, rators, Operato Operato rators, Operato rators, Operato
Operato
Administ Administ rs(*) rs(*) Administ rs(*) Administ rs(*)
rs(*)
rators, rators, rators, rators,
Backup Backup Backup Backup
Operato Operato Operato Operato
rs rs rs rs
SeTakeOwnershi Administ Administ Administ Administ Administ Administ Administ Administ Administ
pPrivilege rators rators rators rators rators rators rators rators rators
Local
SeDenyNetworkL Guest Servers,
Guest (*)
ogonRight (**) Guest
(**)
Local
Administ
SeDenyInteractiv Servers,
Guest(*) rators (*)
eLogonRight Guest
(**)
(**)
Administ
Administ Administ
SeUndockPrivileg rators, Administ Administ Administ Administ Administ Administ
rators, rators
e Users rators rators rators rators rators rators
Users (**)
(**)
Administ
Administ rators,
SeManageVolum Administ Administ
rators Remote
ePrivilege rators rators(*)
(**) Desktop
Users(*)
Administ
Administ Administ Administ Administ Administ Administ Administ
rators,
rators, Local rators, rators, rators, rators, rators, rators,
SeRemoteInteract Remote
Remote Servers, Remote Remote Remote Remote Remote Remote
iveLogonRight Desktop
Desktop Guest Desktop Desktop Desktop Desktop Desktop Desktop
Users
Users Users(*) Users(*) Users(*) Users(*) Users(*) Users(*)
(**)
Local
Service,
Local Network
SeDenyRemoteIn
Servers, Service,
teractiveLogonRi (*) (*)
Guest Administ
ght
(**) rators,
Service
(**)
- 141 -
Chapter 12 - Appendix
- 142 -
Notices
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered trademarks of
Honeywell International, Inc.
ControlEdge™ is a trademark of Honeywell International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.
Matrikon® and MatrikonOPC™ are trademarks of Matrikon International. Matrikon International is a
business unit of Honeywell International, Inc.
Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit of
Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark owner, with no
intention of trademark infringement.
Third-party licenses
This product may contain or be derived from materials, including software, of third parties. The third
party materials may be subject to licenses, notices, restrictions and obligations imposed by the licensor.
The licenses, notices, restrictions and obligations, if any, may be found in the materials accompanying
the product, in the documents or files accompanying such third party materials, in a file named third_
party_licenses on the media containing the product, or at
http://www.honeywell.com/ps/thirdpartylicenses.
Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support website at:
http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your feedback to:
[email protected]
Use this email address to provide feedback, or to report errors and omissions in the documentation. For
immediate help with a technical problem, contact your local Honeywell Process Solutions Customer
Contact Center (CCC) or Honeywell Technical Assistance Center (TAC).
Support
- 143 -
For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find
your local CCC visit the website, https://www.honeywellprocess.com/en-US/contact-us/customer-
support-contacts/Pages/default.aspx.
Training classes
Honeywell holds technical training classes that are taught by process control systems experts. For more
information about these classes, contact your Honeywell representative, or see
http://www.automationcollege.com.
- 144 -