TF08 - Operating Systems Considerations RSTechED2014

8/19/2019 TF08 - Operating Systems Considerations RSTechED2014

http://slidepdf.com/reader/full/tf08-operating-systems-considerations-rsteched2014 1/107

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

PUBLIC INFORMATION

Operating Systems Considerations




Overview

2

This session provides an “introductory overview” of Operating System

considerations such as:

Hardware & Software Domain & Workgroups

Name Resolution

DNS DHCP

Security

FactoryTalk® Directory Configuration

Best practices and the importance of proper operating system configuration

within a manufacturing environment.



Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 3

Agenda

Best Practices

FactoryTalk Configuration

Windows Roles and Features

Hardware and Software

What Are We talking about?




What are we “Talking About”

4

Where is breakfast?

What time does “Happy Hour” start ?

What’s EDFest all about ?

Everybody Being SUCCESSFUL





5

Operating Systems

Anoperating system (OS) is a collection of software that manages computer

hardware resources and provides common services for computer programs

For hardware functions such as input andoutput andmemory allocation, the

operating system acts as an intermediary between programs and the computer

hardware

The operating system is also responsible for security, ensuring that unauthorized

users do notaccess the system.





6

One of the most prevalent IT industry trends at the moment is the

proliferation of consumer devices in the workplace.

Employees and partners want to access protected corporate data from

their personal devices, from checking email to the consumption of

advanced business applications.

IT administrators in organizations, while wanting to enable this level of

productivity, would like to continue to ensure that they can manage riskand govern the use of corporate resources.





7

Where do we fit?Manufacturing the control of physical equipment

Failure Severity “High”

Determinism “High”

Environment “Hostile”

What’s Changing





8

Where do we fit?Other layers or tiers

Enterprise

Data Processing and transfer

Cloud

Information

Web based





9

Manufacturing some of the “pieces” and “parts” and “phases”

Segmentation

Plant floor devices Controllers

Data Servers

HMI Software

Data Storage Databases

Historian Servers

Visualization Reporting Software

Mobile Devices

The OS plays a role in all 5 phases

Requirements

Phase

Architectural

Phase

Technical

Design

Implementation

Phase

MaintainPhase




Where do we “Start”

10

What’s the “ end goal”

We ALL want to be successful

What are the “givens”

We work in a Windows environment

What’s the “reality”

We configureRoles andFeatures

Where do we “start”

A really good question




Agenda

Best Practices








Software Requirements

12

Manufacture Software Requirements

Operating System

Database

FactoryTalk Services Platform

RSLinx® Enterprise

Software is designed to use the Roles and Features of a given OS

Must consider ALL third party software requirements for both Server and

Clients





13

What type of Operating System (OS)

Server –Client


Software product A + B + C on a given computer

Software required for Computer 1 –2 –3

Rockwell Automation Product Compatibil ity Center




Choosing an Operating system

14

Select Multi-Product Compare




Choosing an Operating system

15

Rockwell Software to Install

Select software

Compare

Click Compare




Choosing a Server Operating system

16

Windows 2008 R2




Choosing a Compatible Database

17

MSSQL 2008 R2




Choosing a FactoryTalk Services

Platform

18


Product Compatibili ty and Download Center (PCDC)




Hardware Requirements

19

Manufactures minimum hardware requirements for Server and Client





20

What type of “Hardware”

Individual Industrial Hardware

Virtualized Hardware (private cloud)

Cloud Based Hardware (public cloud)

Hardware “Counts” Pick with the end goal in mind





21

Three Main components

Processor (hard to upgrade) Speed

Number of processors

Number of Cores

Memory (RAM) (up gradable) Amount

Type (speed)

Hard Drive (up gradable) Size

Speed

Type (Hard Disk Drive) or (Solid State Drive)





22

Introduction to VMware Product Suite Virtualization Solutions

Virtualization in Manufacturing Industries Building a hardware Infrastructure for a Virtualized Solution

Introduction to Cloud Computing for Manufacturers




Server Operating SystemsServer 2008 R2 and Server 2012 R2




Windows Servers

24

At the heart of IT (Business & Control) Infrastructure

The default installation steps are streamlined

The base OS installation & configuration tasks are now separated

Servers offers a rich set of new and improved management andmaintenance tools

After the basic server installation the server can be configured by Adding Roles and Features

Configuring Roles and Features




Windows Servers

25

Server 2008 R2 Management Console




Windows Servers

26

Server 2012 R2 Server Manager Dashboard

Local Server

Roles that were added




Windows Servers

27

Server 2014 R2 Server Manager > Local Server

Properties

Events

Services

Best Practices Analyzer

Performance Roles and Features




The system maintenance needs to reflect the changes in the environment:

Capacities

Workloads

Additional Installation

Memory requirement

Network Bandwidth Disk Space.

Windows Servers -- Manage & Maintain

In absence of proper maintenance,

systems tend to become less responsive and reliable




Use System Manager as the central point of administration

Manage servers based on their roles

Maintain the network environment's systems periodically to avoid anyinefficiency

Audit not only to identify security breaches or suspicious activity, butalso to gain insight into how the network, network devices, and systemsare accessed

Enable audit policies through the local system policy or Group PolicyObjects

Windows Servers -- Manage & Maintain




Virus Protection Considerations

30

While Virus protection is always and highly recommended, scanning certain fileand folders can actually have adverse effect on system performance.

Care should be exercised in following installation procedure or best practicerecommendations if certain files or folders need to be excluded.

For example in case of FactoryTalk Historian Site Edition:

On Historian server computers, the Server\dat directory and any directorywhere archive or event queue files are located, should be exclude

For Interface nodes, the pipc\dat andpipc\log directories, as well as thedirectory where buffer queue files are located, should be excluded

The exclusion is to avoid random signature match incidents, potential performanceimpacts, and conflicts with locked files:




Agenda

Best Practices








Getting StartedSequence of tasks




A General Installation Sequence

33

Load Operating system

Decide what if any Service Packs or Updates need to be applied

Change, Verify computers names before loading any additional software

Security Model

Domain

Workgroup

Select Computer Roles and Features

Domain Controller

DNS Server

DHCP Server

Web Server (IIS)

Application Server




A General Installation Sequence

34

Assign IP address

Static IP addresses

DHCP server

Control network considerations

Name Resolution

NetBIOS Host Files

DNS

Users

Windows

FactoryTalk




Security ModelDomains or Workgroups




Security Model Domain Vs. Workgroup

36

Workgroup: Decentralized Administration

No domain Controller (Windows Server OS) to purchase.

One less computer in network to maintain. Recommended only for small applications where user accounts don’t

change often.

Domain: Centralized Administration

One place to manage Users, Groups and Security.

If the FactoryTalk Directory is part of a domain, then windows-linked

users can be added in for use within FactoryTalk. Automate IP addresses with Dynamic Host Configuration Protocol

(DHCP), and Name Resolution and with Domain Name Service (DNS)and Windows Internet Name Service (WINS).




Workgroup

37

All computers are peers; no computer has control over another computer.

Each computer has a set of user accounts. To log on to any computer inthe workgroup, you must have an account on that computer.

There are typically no more than ten computers.

Limitation is 10 concurrent connections to any share in the workgroup at

any one time

All computers should be on the same local network or subnet.




Workgroups

Workgroup: Decentralized Administration

Local Users

Joe

Henry

Mary

Isaac

Local Users

Joe

Henry

Mary

Isaac

Local Users

Joe

Henry

Mary

Isaac

Local Users

Joe

Henry

Mary

Isaac

Logged in:

Joe

Logged in:

Henry

Logged in:

Mary

Logged in:

Isaac

FactoryTalk View

Studio

SE Client SE Client SE Client

New User?

Administer

each computer BobBobBobBob




Domain

39

An architecture that one or more servers are responsible for dealing with

security and permissions on the network.

Network administrators use servers to control the security and permissionsfor all computers on the domain.

Network modifications are easy, as changes are automatically made to all

computers.

Domain users must provide credentials each time they access the domain.

With a user account on the domain, one can log on to any computer on thedomain without needing an account on that computer.

The computers can be on different local networks.




Domain Organizational Unit

40

Organizational Units are containers within a Domain into which you can

place users, groups, computers and other organizational units.

An organizational unit can not contain objects from other domains.

An organizational unit is the smallest scope or unit to which you can assign

Group Policy settings.




Domains

Domain: Centralized Administration

41

New User?

Administer theDomain Controller

Logged in:

Joe

Logged in:

Henry

Logged in:

Mary

Logged in:

Isaac

FactoryTalk View

Studio

SE Client SE Client SE Client

DomainController

Domain UsersJoe

Henry

Mary

Isaac

Bob

Copyright © 2008 Rockwell Automation, Inc. All righ ts reserved.




Domain or Workgroup

42

New or Existing

Network Architecture or Scope

Number of computers Number of users

Management




IP Addresses

Static and DHCP




Assigning IP Addresses

44

Regardless of Workgroup or Domain infrastructure, IP address need to be

assigned to each computer that will be on the network

Mission critical computers should have a static IP addresses

Industrial concerns

Using static IP address

Manually entered

Assigned on system startup

Using a DHCP address

DHCP server is a Role of the OS

DHCP server must be available

DHCP server should use a reserved IP address





45

DHCP IP Address Reservations

Based on MAC addresses





46

DHCP IP Address Exclusion

Exclude static IP addresses




Name Resolution

Host Name and NetBIOS




Name Resolution

48

Regardless of Workgroup or Domain infrastructure, Name resolution is requiredfor the computers to communicate with each other on the network.

Name resolution resolves Domain \ Host Names to IP addresses

Two types of Name Resolution

Host Name resolution

Host Files

Domain Name Server (DNS)

NetBIOS resolution

Broadcast

WINS Server




A Windows host (2000 and later) will attempt to resolve the location of anetwork resource in the following order:

1. Hostname (the name of the local machine)

2. Local DNS Resolver Cache

Loads Host Files on start up

Files cached from the DNS Server

3. DNS (Centralized name server )

4. NetBIOS Broadcast (depends on the type of NetBIOS Node)

49

Host Name Resolution Order

Absent of ANY configuration, step 4 will be used to achieve some level of name resolution




Host Files

A Host file is a flat text file used to resolve IP addresses to Host

names

Windows 2000 and later Host files are loaded in to the local DNSresolver cache first on startup.

You can use different names for the same IP address (nick names)

Host files must be entered and maintained manually

50




Host Files Considerations

51

Useful Application

Redirecting Local Domains

i.e. test local websites in development

Internet Resource Blocking

i.e. Redirecting undesirable sites to harmless destinations

Security Concerns

The hosts file represent an attack vector for malicious software.

i.e. They can be modified by malware to redirect traffic to malicious or

unwanted sites




Domain Name System/Server (DNS)

52

Add as a Server Role

Server 2008

Server 2012





53

Translates Domain/Host names into IP address

www.example.com = 192.0.43.10

Facilitates the internet usage as meaningful names in URLs and emails

instead of cryptic series of numbers can be used.

The DNS is an essential component of the functionality of a robust network

infrastructure





54

Dynamic Updates in a Domain

Only applies to Domain users

Dynamic Updates in a Workgroup

Applies to ALL users

Name Resolution & Domains




DNS Components

Components of the DNS Editor:

Reverse Lookup Zone – allows forresolving an IP address to a host name.Some software applications will requirethis for security, to make sure it’s

running from a certain machine.

Resource Records – The types ofentries in the database. Host (A)records associate a host name with anIP address.

Zones – allows for the DNS databaseto be split up and administered amongmultiple DNS Servers

Forward Lookup Zone – allows forresolving a host name to an IP address




DNS … How does it work?

56

A

CB

D

1 – Needs to go www.acme.com .

Checks local DNS cache first if not found

Requests address from DNS Server B

2 – Does not have the

www.acme.com in its DB.

Forwards the request to

another DNS Server (C)

3 – Does have the address for

www.acme.com in its cache

(IP address of Server D).

Passes the info back to server B4 – Passes along the info

Returned from server C, andcaches it for a while as well

5 – Caches address

goes to server

D for www.acme.com




DNS … How does it work?

57

A

CB

D

1 – Needs to go www.acme.com .

Checks local DNS cache

5 – finds address in

It’s cache then

goes to server

D for www.acme.com




NetBIOS name resolution is based on the Node Type

Hybrid checks Local network then Enterprise

NetBIOS Broadcast -- Node Type (Hybrid)

1. NetBIOS name Cache

2. WINS Server

3. Broadcast

4. Lmhosts file

5. Host File

6. DNS Server

58

NetBIOS Name Resolution Order

N BIOS N R l i O d




NetBIOS name resolution is based on the Node Type

59

NetBIOS Name Resolution Order

N tBIOS N d T




Ipconfig /all

60

NetBIOS Node Type




Users

Windows -- FactoryTalk -- SQL Users

U U U




Users, Users, Users

62

At least four sets of users

Domain Users

Domain Scope Users Workgroup Users

Single Computer Scoped

SQL Server Users

Can be Windows Users

SQL Server (unlinked) Users

FactoryTalk Users

Can be linked to Windows Users

Independent (Unlinked) Users

Provides some of the Domain user name management conveniences for a

workgroup environment.




Windows Considerations

IIS

IIS (Internet Information Services)




IIS (Internet Information Services)

64

IIS is a Role of the OS

Server 2008 R2

Server 2012 R2

FactoryTalk System & IIS




FactoryTalk System & IIS …..

65

FactoryTalk system requires a Windows network and depends on a

number of Windows elements, including Internet Information Services (IIS).

A Proper IIS configuration plays a critical role in many FactoryTalk products

particularly those which have a client server infrastructure (web presence).

i.e.

FactoryTalk VantagePoint

FactoryTalk View Site Edition (SE)

FactoryTalk Metrics

etc

Internet Information Services (IIS)





66

IIS turns a computer into a web server

Most Rockwell software products require at a minimum

Common Files

Internet Information Services Snap-in World Wide Web Publishing

Personal Web Manager

Check the knowledgebase on a per product basis






67

IIS is not installed on by default.

IIS manager is accessed through Microsoft Management Console or

Administrative Tools in the Control Panel.

IIS Role example for FactoryTalk Metrics




Add Web Server (IIS)

Ensure that the following role services are installed for IIS

Common HTTP Features

HTTP Redirection

Application Development

ASP .NET

.Net Extensibility

ISAPI Extensions

ISAPI Filters

Security

Windows Authentication

Management Tools

IIS 6 Metabase Compatibility

IIS 6 WMI Computability

IIS Role example for FactoryTalk Metrics

Internet Information Services (IIS)Application Pools




Application Pools

69

An Internet Information Services (IIS) application pool is a grouping of

URLs that is routed to one or more worker processes.

They provide a convenient way to administer a set of Web sites and

applications and their corresponding worker processes.

Process boundaries separate each worker process; therefore, a Web site

or application in one application pool will not be affected by application

problems in other application pools.

Application pools significantly increase both the reliability and

manageability of a Web infrastructure.





Application Pools

70

To verify that an IIS Application Pool is configured for 32-bit operation on a

64-bit OS?

Open Administrative Tools >IIS Manager

In the Explorer tree, expand the IIS Server

In the Explorer tree, select Application Pools

Select the appropriate Application Pool (typically 'DefaultAppPool')

Right-click and select Advanced Settings In the General section, verify that Enable '32-Bit Applications' = True





Application Pool is important because software installation modifies it.

When you have a mix of 32 bit and 64 bit applications, installation of a 32 bit

application will modify 'DefaultAppPool' (and any other existing Application Pools)for 32-bit operation.

This may cause issues for other applications that are only compatible with 64-bit

Application Pools.

To address such issues, one of the following approach can be taken

To avoid the issue, installation sequence needs to be modified

To correct the issue, the application pool of the non-functioning softwareneeds to be modified

Please refer to knowledgebase for more details (117888, 111218, 449497,460423, 477031, ….)

Application Pools





DEP

Data Execution Prevention (DEP)




( )

73

DEP is a set of hardware and software technologies that perform additional

checks on memory to help prevent malicious code from running on a

system.

Software DEP by default monitors essential Windows and service. You can

increase your protection by having DEP monitor all programs EXCEPT

those which you select.

DEP discussed here is the software-based feature of Windows. Some

processor provide hardware-based DEP under various names.

Generally for Rockwell Software Installation, Data Execution Prevention

should be turned on for Essential windows programs and services only

Data Execution Prevention (DEP)




( )

74





Time Zone

Time Zone Consideration




In a distributed system such as FactoryTalk Historian SE, where logged

information, and their timestamps ARE essential, special attention needs to

be paid to Time Zone configuration and Time Synchronization


Example – FactoryTalk Historian SE Pre-Installation Tasks




Synchronize Time Settings on Historian System Computers

Times must be set correctly and synchronized with the FactoryTalk Historianserver on all machines that are part of the FactoryTalk Historian system.

All Windows machines must have the proper time-zone settings and are setto automatically adjust for daylight-saving changes.

Time synchronizations is typically done through the domain Controller.

The domain Controller's time is synchronized first by an Network TimeProtocol (NTP) source.

The domain controller synchronizes all the other computers that are a part ofthe FactoryTalk Historian system.


Example – HistorianSE Pre-Installation Tasks




Disable the Windows time zone

The Windows time zone (TZ) environment variable adversely affects the Historianserver. You must ensure that TZ is not set on the Historian server computer.

To confirm that the TZ variable is not set on Windows 7, Server 2008 and 2008 R2: Right-click on My Computer and select Properties

Click Advanced system settings.

Click Environment Variables.

If the TZ variable is present, delete it. If prompted, restart the computer.

To confirm that the TZ variable is not set on computers with other Windows OS: Right-click on My Computer and select Properties

In the System Properties dialog box, click the Advanced tab. Click Environment Variables.

If the TZ variable is present, delete it.

If prompted, restart the computer.




Windows 32 and 64 Bit Considerations

Files, Registry and ODBC

Program Files




Some Rockwell Automation software products that support 64-bit operating

systems are 32-bit (x86) applications that are "64-bit compatible".

The 'Rockwell Automation', 'Rockwell Software' and 'Incuity' folders are

located within the 'Program Files (x86)' folder on a 64-bit OS

On a 64-bit OS, the 'Program Files' folder is for true 64-bit (x64)

applications, while the 'Program Files (x86)' folder is for backwards

support of 32-bit (x86) applications that are "64-bit compatible".

Program Files --- Little More Details




Applications in the 'Program Files (x86)' folder use theWindows 32-bit On

Windows 64-bit (WoW64) subsystem.

WoW64 is the x86 emulator that allows 32-bit Windows-based applications

to run seamlessly on 64-bit Windows.

WoW64 is provided with the 64-bit operating systems and does not have to

be explicitly enabled

32-bit applications running in the WoW64 subsystem aresuffixed in theProcesses tab of the Task Manager with "*32" (e.g., iexplore.exe

*32; EXCEL.EXE *32).

FoldersProgramData




The 'ProgramData' folder is a hidden system folder that is used to store

application programrelated data

Introduced in Vista OS, It replaces the 'Documents and Settings\All

Users\Application Data' folder that was used in previous versions of

Windows.

Like its predecessor, it works in conjunction with applications

installedwithin the 'Program Files' folder (and the 'Program Files (x86)'

folder on 64-bit operating systems).NOTE: As a rule, folders and files within the 'ProgramData' folder should not be

manually manipulated (or deleted) using Windows Explorer or other file system

tools.

Windows Registry




Managing 32-bit registry keys in a 64-bit Windows Operating System?

64-bit Program: @HKEY_LOCAL_MACHINE\SOFTWARE\Rockwell Software 32-bit Program: @HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Rockwell Software

References

http://suport.microsoft.com/kb/305097

RA Knowledgebase ID 507187

Windows Registry




While not recommended, if you have to modify the registry manually,

EXTREME care should be exercised when merging .REG files into registry

when mix of 32 and 64 bit registries are involved.

Right-click Merge of .reg file will always place the registry information

in the 64 bit location which is not accessible by the 32 bit programs

Use the correct version of the Registry Editor

32-BIT VERSION: C:\Windows\SysWOW64\regedt32.exe

64-BIT VERSION: C:\Windows\System32\regedt32.exe

ODBC DSN Considerations




The 64-bit ODBC Data Source Name (DSN) cannot be used by a 32-bit

applications running in the WoW64 subsystem.

On a 64-bit OS, the 32-bit ODBC Data Source Administrator must be used

for a 32 bit application:

%windir%\SysWOW64\ odbcad32.exe(typically Windows\SysWOW64).

The 64-bit ODBC Data Source Administrator (also odbcad32.exe) is

accessedusing the traditional method:

All Programs > Administrative Tools > Data Sources (ODBC)

NOTE: Both 64 bit and 32 bit version of the ODBC Data Source admin is

odbcad32.exe but in different locations.

ODBC DSN




In some products (i.e. FactoryTalk Metrics, and FactoryTalk View SE) even

when installed on a 64 bit OS, the SQL Server database portion of their

install is a 32 bit version.

The 32 bit version of the ODBC Data Source Administrator at the following

location should be used:

%windir%\SysWOW64\odbcad32.exe

NOTE: If you try tocreate a DSN by using Administrative Tools > Data

Sources (ODBC) on a 64 bit Operating System, it will open the64-bitsystem ODBC Data Source Administrator configuration GUI.

The 64 bit DSN GUI has no visual indication that it only relates to 64-bit.

ODBC DSN




64 Bit

32 Bit

Agenda




Best Practices





What is FactoryTalk?





A service oriented architecture

(SOA) that delivers value

through FactoryTalk-enabledproducts

Reduces customer learning

curve and project engineering

time through commonality andreuse

FactoryTalk System Design

Considerations




Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.(Confidential –For Internal Use Only) Copyright © 2007 Rockwell Automation, Inc. All rights reserved. 90

Common address book ofresources that are shared

among FactoryTalk Servicesenabled products

Centralized security

authority for all componentsin the system.

Enterprise-wide access to

real-time manufacturinginformation.

Central location for

warnings and errorsgenerated by the system.

Comprehensive record of

any changes made to themanufacturing system.

Common software license

management for all products

Enterprise-wide access to

real-time alarms and eventsthat require action.

“Required for FactoryTalk Products”

FactoryTalk Directory




FactoryTalk Directory

• Allows FactoryTalk-enabled products to organize applications,

share definitions and manage services. The FactoryTalk

Directory provides a central lookup service so that all definitionsdon’t have to existing in a single physical location like a project

file. Instead references or “pointers” are saved in the

FactoryTalk Directory and used to locate definitions when they

are needed.

• FactoryTalk Directory is a core service of the FactoryTalk

Services Platform allowing customers to build an integrated

system from FactoryTalk and Integrated Architecture

FactoryTalk Security

F t T lk S it




FactoryTalk Security

• FactoryTalk Security performs two critical tasks:

• Authenticationverifies a user’s identity and verifies that a

request for service originates with that user.

• Authorizationverifies a user’s request to access a softwareproduct, feature, or system resource against a set of

defined access permissions.

• FactoryTalk Security authenticates and authorizes users againsta set of defined permissions held in the FactoryTalk Directory.

FactoryTalk Directory Security




FactoryTalk Directory provides centralized security services without

requiring a Windows Server and domain controller …. However Life is

much easier in a Domain environment

Workgroup

Do not use Windows-linked accounts. Instead, create user accounts

that are managed and authenticated by FactoryTalk Security.

DomainYou can use Windows-linked accounts that are managed and

authenticated by the Windows operating system

FactoryTalk Security provides separate permissions for accessing theautomation system.

FactoryTalk Administration Console

Planning




(Confidential –For Internal Use Only) Copyright © 2007 Rockwell Automation, Inc. All rights reserved.

94

Planning

Security

Networks

Availability Defining

Installation

Configuration

Integration

Supporting

Diagnostics

Part of the FactoryTalk ServicesPlatform




Load FactoryTalk Services Platform on each computer

Choose which computer will Host the FactoryTalk Directory

Have all other computers join that FactoryTalk Directory

Local

Global / Network

RNAServer

RNAClient

Computer A

Local

Global / Network

RNAServer

RNAClient

Computer B

Local

Global / Network

RNAServer

RNAClient

Computer C

Global / Network

RNAClient RNAClient

RNAServer

RNAClient RNAClientRNAClient

FactoryTalk Directory…How does it work?




A

C

B

D

1 – Needs Tag ABC value

Checks for DS Address

Ask the FTD for the DS Address

2 – Does not have the

DS address. Ask known DS for

knowledge of tag ABC C or D

3 – Does not have knowledge of

Tag ABC4 – Has knowledge of tag

ABC returns acknowledgement

5 – Caches address

Goes to DS

D for Tag ABC value

FTD

DS

DS

HMI

FactoryTalk Directory…How does it work?




A

C

B

D

1 – Needs Tag ABC value

Checks cache for DS Address

2 – Finds address

In it’s local cache

Goes to DS

D for Tag ABC value

FTD

DS

DS

HMI

Agenda




Best Practices





Installing Rockwell Automation Software

V if d t t ALL Wi d R l dF t




Verify and test ALL Windows Roles and Features

Have network configure

Install FactoryTalk Services Platform

Install Activations services

Select which FactoryTalk Directory to use

Have all other FactoryTalk computers join that FactoryTalk Directory

Install Application Software per installations instructions

Installing Rockwell Automation Software

V if d T t h d t b f i t lli dditi l ft if




Verify and Test each product before installing additional software if

possible

Create your FactoryTalk Application

Add Data Servers

Configure communication drivers

Add HMI servers

You can test the FactoryTalk Application configuration using the

“ FactoryTalk Live Data Test Client” tool

Starting a FactoryTalk Application

Start theFactoryTalkDirectorycomputer




Start the FactoryTalk Directory computer

Start ALL Data Servers

Start ALL HMI servers

Start other Servers (FactoryTalk Metrics, FactoryTalk Historian,

FactoryTalk Transaction Manager and others

Start Clients

Updates and Patch Management

Microsoft releases security patches and product updates on regular basis




Microsoft releases security patches and product updates on regular basis

Recommended to have Windows Updates turned off

Patches may have adverse affect on installed software operation

A robust patch & update policy is a critical part of a good software

maintenance plan

Use knowledgebase as a reference

On a working Automation System, Patch and Update installations should be a part of a

Deliberate activity and not an Automatic one

Backup, Backup and then Backup again

Windows




Windows

Files

System Image Backup

Previous Versions

System restore

FactoryTalk Directory and Applications

Backup

Restore

Backup, Backup and then Backup again

RSLinx




RSLinx

Backup and Restore Utility

Controllers Backup

Restore

Automatic on a schedule (FactoryTalk AssetCentre)

Network Pieces and Parts

Routers

Switches

Backing up a SYSTEM has many parts and needs to be a Deliberate activity and not

left to chance




www.rsteched.com

Follow RSTechEDon Facebook & Twitter.Connect with us on LinkedIn.

PUBLIC INFORMATION

Questions?

We care what you think!

Please take a couple minutes to complete a quick




On the mobile app:

1. Locate session using

Schedule or Agenda Builder

2. Click on the thumbs up icon on

the lower right corner of thesession detail

3. Complete survey

4. Click the Submit Form button

106

Please take a couple minutes to complete a quicksession survey to tell us how we’re doing.

2

3

4

1

Thank you!!




PUBLIC INFORMATION

Thank you for participating!

Please remember to tidy up your work area for the next session.We want your feedback! Please complete the session survey!

TF08 - Operating Systems Considerations RSTechED2014

Documents

Transcript of TF08 - Operating Systems Considerations RSTechED2014