RES Automation Manager Reference Architecture - RESguru ...

RES Automation Manager Reference Architecture

TABLE OF CONTENTS: Reference Architecture Overview

Document Purpose What is Automation Management Solution Architecture

Component Quick Overview RES Automation Manager Architecture Agent – Dispatcher Communication Agent – Master Dispatcher Communication Site Design Hardware Prerequisites Software Prerequisites Other Requirements Database Prerequisites Architecture Components

Datastore Consoles Engines Agents Enterprise Considerations

RES Automation Manager Network Load Compatibility Matrix

Microsoft Operating Systems Other Operating Systems Directory Services Database Mail Servers Application Virtualization Microsoft System Center Configuration Manager Microsoft PowerShell Citrix VMware RES HyperDrive RES Workspace Manager Citrix Ready Certification Conclusion

2 0 1 4 0 3 0 4 g t

3 3 3 5 5 6 8 9 11 15 15 15 16 21 21 21 21 21 22 22 24 24 24 25 25 25 25 26 26 26 26 26 26 27 28

2

Reference Architecture Overview Document purpose The focus of this document is to highlight the architecture of RES Automation Manager and it’s components. Additionally, within the document, you will find some best practice recommendations, design considerations and network observations that should assist a competent RES Software Certified Professional with the design and deployment of a stable and scalable platform.

What is Automation Management? RES Automation Manager delivers the automation of tasks beyond the traditional command line. It enables IT professionals to deliver any set of changes to IT environments, whether hosted, virtual, or web-based and automates provisioning of IT resources, all from a single Console. RES Automation Manager have three main capabilities:

Task and Run Book Automation The change activities that are required on a daily basis to keep desktops, servers and systems in optimal shape are time consuming. By automating these tasks, you improve IT productivity and reduce delivery time. RES Automation Manager makes automation truly simple, because the most common activities you need are already predefined as tasks that you can deploy instantly. Predefined Tasks: RES Automation Manager contains 200+ predefined IT tasks. This allows you to configure common IT tasks out–of–the–box, without complex scripts and local administrative access. Run Books: Combine different types of Tasks into a single recipe for easy scheduling. User Provisioning: Automatically create and manage user accounts, user mailboxes, user home drives, and set the correct permissions. Computer Provisioning: Automatically install software, patches and manage the configuration of your IT environment. Team Scheduling: By creating logical groups of computers, you can target multiple computers at once . Building Blocks: Easily transfer RES Automation Manager configurations from one IT environment to another. This is ideal in testing, acceptance and production environments.

2 0 1 4 0 3 0 4 g t

3

Extensive Integration Through the extensive set of built in tasks RES Automation Manager integrates with virtually any existing infrastructure component. This allows for easy IT process automation across IT functions including software as a service and cloud computing. Generic Integration: Integrates with existing technologies such as Enterprise Mobility Management, Service Management and PC Life Cycle Management. RES Workspace Manager: Enable RES Workspace Manager to invoke RES Automation Manager Tasks. This allows for user-initiated context-aware automation. RES IT Store: Enable RES IT Store to automatically deliver and return any infrastructure change based on business qualification and intuitive self-service.

Advanced Delegation and Control Automation in today’s agile enterprise requires full change control. RES Automation Manager enable IT to manage and maintain control over changes across the enterprise with increased security and policy compliance. Delegation of Control: Address different job responsibilities within RES Automation Manager. Trust Security: Enable bidirectional trust between agent and task to prevent unauthorized changes. Audit Trail and Job History: Automatically gather and save Task activities and administrator activities in a central data store. This allows you to meet compliancy requirements and assists in troubleshooting. Advanced Job Scheduling: Control the moment of Task execution on multiple computers

2 0 1 4 0 3 0 4 g t

4

Solution Architecture Component Quick Overview RES Automation Manager uses four major components:  Console  Datastore  Dispatchers  Agents

Console When you have set up the entire RES Automation Manager environment and have deployed all of its components, the Console functions as the central point of administration of your RES Automation Manager environment. You schedule all Tasks from here. Datastore The Datastore is the central database for your RES Automation Manager environment. It runs on a central database server that you have installed prior to installing RES Automation Manager. The Datastore contains all RES Automation Manager settings and can contain Resources that are needed for your Tasks. The Datastore can run on any of the following database types:  Microsoft SQL Server 2000 and higher (including Express editions)  Oracle (10.2 and higher, including Express)  IBM DB2 (9.1 and higher)  MySQL (5.0 and higher)

Dispatcher A Dispatcher is a service that runs on a computer in your RES Automation Manager environment. It communicates information from the Datastore to Agents. A Dispatcher can cache Resource, thereby lightening the load on the Datastore. The availability of a Web API allows you to build and deploy RESTful and SOAP web services and use the Dispatcher to integrate Job scheduling in external systems.

Agent An Agent is a service that runs on a computer in your RES Automation Manager environment. It executes the Tasks that you configure.

2 0 1 4 0 3 0 4 g t

5

RES Automation Manager Architecture A basic RES Automation Manager environment can be represented as follows:

Communication Model

2 0 1 4 0 3 0 4 g t

6



An RES Automation Manager environment can contain multiple Consoles, Dispatchers and Agents.



When you deploy, repair or remove a Console, Dispatcher or Agent on a computer, the Console that you are logged on to extracts the necessary data from the Datastore and then connects directly to the target computer.



When you create Modules, Projects or Run Books, the Console stores all data in the Datastore, including the Tasks and Resources involved. When you schedule Jobs with these Modules, Projects or Run Books, the Console sends this assignment to the Datastore.



A Dispatcher manages all communication between the Datastore and an Agent by contacting the Datastore at regular intervals. If a new Job is available for the Agent, the Dispatcher will download all necessary data from the Datastore and store it.



In its turn, the Agent contacts the Dispatcher at regular intervals. If a new Job is available, the Agent will download all necessary data from the Dispatcher and perform the Job. If a Dispatcher is too busy, the Agent will try to contact a different Dispatcher.



RES Automation Manager uses port 3163 (TCP/UDP) for communication between the Agent and the Dispatcher. This port is hard-coded and cannot be changed.



When using a Datastore based on Microsoft SQL Server, RES Automation Manager uses port 1433 for communication between the Dispatcher and Datastore. If necessary, you can change this port on the Microsoft SQL server. Oracle, MySQL and IBM DB2 use different ports, please refer to the documentation of those servers for the correct port numbers.



When using a Datastore based on Microsoft SQL Server 2000 or higher, you can optionally secure communication between the Datastore and the components that connect to it (Consoles and Dispatchers). See Protocol encryption.



You can secure communication between Dispatchers and Agents by configuring a global setting. This setting functions irrespective of database type used.

2 0 1 4 0 3 0 4 g t

7

Agent - Dispatcher Communication

Agent Dispatcher    

2 0 1 4 0 3 0 4 g t

The Datastore and Dispatchers contains all global changes (GUIDs and Agent GUIDs). An Agent contains multiple GUIDs (for schedule, properties etc.). The Agent checks Agent GUIDs with the Dispatcher. If there is a change, only the relevant Agent GUID (schedule, properties, etc.) is fetched from the Dispatcher.

8

Agent – Master Dispatcher Communication

Master Dispatcher

2 0 1 4 0 3 0 4 g t

9

Master Caching Resources are files that are used in the execution of RES Automation Manager Tasks and can be stored in the Datastore. For example, a Task Perform Unattended Installation may use an application executable that is stored as a Resource in the Datastore. Depending on the global settings in your RES Automation Manager environment, each Dispatcher caches this Resource, so that it can be downloaded by Agents to execute a certain Task. This can be a problem if the bandwidth in your RES Automation Manager environment is limited: if many Dispatchers connect to the Datastore simultaneously to download the Resource to their cache, the download speed will decrease and the maximum bandwidth capacity may be reached, especially if the Resource is large. Master caching makes it possible for Dispatchers to share a common Resource cache on a specific environment: By assigning a master Dispatcher, only this Dispatcher is allowed to download Resources from the Datastore. After downloading the Resources from the Datastore, the master Dispatcher stores them in its cache, after which other Dispatchers can download the Resources from the master Dispatcher. If you "redirect" the other Dispatchers to this master Dispatcher, they can only download Resources from the master Dispatcher, because they can no longer contact the Datastore directly. This reduces bandwidth consumption between the Dispatchers and the Datastore, and so improves the reliability of the connection with the Datastore and increases the overall speed at which Resources are downloaded. Setting up a Master Dispatcher When setting up master caching, RES Software recommends to make a master Dispatcher exclusively available to Dispatchers: this prevents Agents from being able to contact the master Dispatcher. Keep in mind though that this may require additional Dispatchers, because any Agent will be unable to contact the master Dispatcher.

2 0 1 4 0 3 0 4 g t

10

Site Design The following scenario gives an example of how an RES Automation Manager environment can be set up and adapted as circumstances change. The examples are based on the fictional company The Demo Company, which initially consisted of a single office in New York, where 50 people were employed. Over the years, The Demo Company expanded rapidly and its number of employees in New York increased from 50 to 2,000. Furthermore, a second office was opened in Amsterdam with 200 employees, as well as a satellite office in Singapore with 20 employees.

Small Business Initial setup in New York:

New York 50 Agents 1 Dispatcher SQL Server: SQL-NY Datastore: RAMNY

  

2 0 1 4 0 3 0 4 g t

One Datastore (Microsoft SQL Server) One Dispatcher (only 50 Agents: one Dispatcher suffices. A 2nd Dispatcher would cause unnecessary Dispatcher Datastore traffic) 50 Agents

11

Medium Sized Business After rapid growth in New York:

New York 2000 Agents 2 Dispatchers SQL Server: SQL-NY Datastore: RAMNY

   

2 0 1 4 0 3 0 4 g t

One Datastore Two Dispatchers (1500 Agents per Dispatcher: a reasonable number, though depending on the number of concurrent connections) 2000 Agents The additional Dispatcher and Agents have been deployed from the Console

12

Enterprise with Branch Office When the office in Amsterdam was opened:

New York 2000 Agents 2 Dispatchers SQL Server: SQL-NY Datastore: RAMNY

Amsterdam 200 Agents 1 Master Dispatcher 1 “regular” Dispatcher

The office in Amsterdam has:    

2 0 1 4 0 3 0 4 g t

One master Dispatcher that connects to the Datastore RAMNY in New York. One Dispatcher that connects to the master Dispatcher (one Dispatcher suffices). 200 Agents that only connect to the "regular" Dispatcher in Amsterdam, not the master Dispatcher. (Their Dispatcher Address List only contains the "regular" Dispatcher in Amsterdam, and they do not retrieve a complete Dispatcher List.) All Dispatchers and Agents have been deployed from the Console in Amsterdam.

13

Multi-Site Enterprise When the satellite office in Singapore was opened

New York 2000 Agents 2 Dispatchers SQL Server: SQL-NY Datastore: RAMNY

Amsterdam 200 Agents 1 Master Dispatcher 1 “regular” Dispatcher

Singapore 20 Agents 1 Dispatcher The office in Singapore has:  

One Dispatcher. This Dispatcher was deployed from New York and connects to the existing Datastore in New York. Master caching is not needed. 20 Agents, which use the Dispatcher in Singapore. (Their Dispatcher Address List only contains the Dispatcher in Singapore, and they do not retrieve a complete Dispatcher List.)

It is very easy to administer an RES Automation Manager environment from a single point. Because of RES Automation Manager's scalability, it is just as easy to maintain an environment with 2000+ users as it is to maintain one with just 50 users.

2 0 1 4 0 3 0 4 g t

14

Hardware Prerequisites     

All hardware must comply with the Microsoft Hardware Compatibility List (HCL). The installation of a Console takes 50-60MB of disk space. The installation of a Dispatcher takes 7-8MB of disk space. The installation of an Agent takes 7-8MB of disk space. Verify that the database server that hosts the RES Automation Manager Datastore has sufficient disk space to store Resources. Resources can also be stored on file servers.

For environments with 1000+ agents a dedicated database server is recommended.

Software Prerequisites RES Automation Manager supports the following operating systems:  Microsoft Windows XP SP3 Professional x86 /x64  Microsoft Windows Vista x86 / x64  Microsoft Windows 7 x86 / x64  Microsoft Windows Server 2003 (including R2) x86 / x64  Microsoft Windows Server 2008 (including R2) x86 / x64 Additionally, the following software is required:  Microsoft .NET Framework 4.0 or later (Client Profile) on the machine that runs RES Automation Manager installation .MSIs or RES Automation Manager update packs.  Microsoft .NET Framework 4.0 or later (Full version: Client Profile and Extended) on all machines hosting a Dispatcher. Please make sure to upgrade all Dispatcher hosts with this version before running an RES Automation Manager installation .MSI or an RES Automation Manager upgrade pack. .NET Framework 4.0 Full Version can be installed on your Dispatchers from the Console.  Agents do not require Microsoft .NET Framework 4.0 or later.

Other requirements When deploying components from the Console on machines running Microsoft Windows Vista or higher, disable the User Account Control feature, as this feature does not support silent installations. Agents    

2 0 1 4 0 3 0 4 g t

No active Windows Firewall Remote Registry service must be running Simple File Sharing disabled IPC$

15

Database Prerequisites Microsoft SQL Server When using a Datastore based on Microsoft SQL Server, you can choose whether to connect to this Datastore using SQL Server Authentication or Windows Authentication. For environments with 1000+ agents a dedicated database server is recommended. Prerequisites and preparations for SQL Server Authentication  Mixed Mode authentication  A named SQL Server System Administrator login ID, or an alternative account with server role "sysadmin" and user mappings to master, model, msdb and tempdb  Microsoft .NET Framework 2.0 or higher Prerequisites and preparations for Windows Authentication When connecting to a Microsoft SQL Server, Microsoft recommends to use Windows Authentication whenever possible, as this authentication mode is much more secure than SQL Server authentication. Depending on the configuration of your database server, you can use Windows Authentication on server-level or on database-level only. Please note that switching between authentication modes on server-level will also affect other databases on this server. Before you can start using Windows Authentication in RES Automation Manager to connect to the Datastore, follow these steps: New installations 1. In Microsoft Active Directory, create a Group for service accounts. 2. Create an Active Directory User that is a member of this service accounts group. 3. Create the following policy:  Logon as a service for the service accounts group.  Add the service accounts group to the local administrators group. 4. Link the policy to the OU that contains the computers running the Consoles and/or Dispatchers. 5. Open Microsoft SQL Server Management Studio.  In the Security folder, create a new login.  Click Search and then Object Types.  Add the service accounts group that you created earlier.  Add Domain Admins (or any other group of RES Automation Manager administrators that use the RES Automation Manager Console). 6. Create a new default database with the following settings:  Size 150MB, autogrow 25MB  Log 75MB, autogrow 10MB 7. Open the properties of the service accounts group. 8. On the User Mapping tab, select the database just created. 9. In Database Role Membership, select the db_owner role. 10. Do the same for Domain Admins. 11. Add the account that is going to create the database tables and add the role "dbo". 12. Alternatively, when using accounts from another domain:  Add Domain Admins (or any other group of RES Automation Manager administrators that use the RES Automation Manager Console) and the service account group to a domain local group.  In Microsoft SQL Server Management studio, add the domain local group to the database as db_owner. 13. Install RES Automation Manager with the installation .MSI with a user that has the role "dbo". 14. After installation, start the RES Automation Manager Console. 15. When prompted, do NOT create a new database, but connect to the one that you just created. 16. Provide the required information and select Windows Authentication. 17. Specify the Service Account in the format: DOMAIN\username. 18. Click OK. 19. When connecting to the database, RES Automation Manager will ask for confirmation first. When confirmed, RES Automation Manager will create the required tables.

2 0 1 4 0 3 0 4 g t

16

Existing installations using SQL Server Authentication 1. On the Microsoft SQL Server, switch the authentication mode for the RES Automation Manager Datastore from mixed mode authentication to Windows Authentication. 2. Follow the steps as described above until step 13. Skip the step where you create a new database. 3. Start the RES Automation Manager Console and at Infrastructure > Datastore > Setup > Database change Database authentication to Windows Authentication. 4. Provide the service account credentials and click Connect. The Console will now restart. 5. Repair all Consoles and Dispatchers in the RES Automation Manager environment. Every new Console and Dispatcher that you deploy will run using the provided service account credentials. Other prerequisites for Microsoft SQL Server Consoles and Dispatchers  Microsoft SQL Native Client if you want to use encrypted communication between the Datastore and the Consoles and Dispatchers or if WMC.exe needs to be started from the command line Agents Microsoft SQL Server client (pre-installed with Microsoft Windows)

2 0 1 4 0 3 0 4 g t

17

MySQL and Oracle Database type

Prerequisites

MySQL (5.0 and later)

Database MySQL DBA credentials Consoles and Dispatchers MYSQL ODBC Driver 3.51 or higher (x64/x86)

Oracle (9i and later)

Database Oracle DBA credentials Consoles and Dispatchers Oracle OLEDB provider Oracle win32_11gR2_client with Patch 10245350 or higher (x86) Oracle win64_11gR2_client with Patch 10245351 or higher (x64)

2 0 1 4 0 3 0 4 g t

18

IBM DB2 Database type

Prerequisites

IBM DB2 (8.1 and later)

Database An existing database and database user. The database user must be able to access a table space with a page size of at least 8k Consoles and Dispatchers IBM DB2 OLEDB provider (x64/x86)

Preparations for creating a Datastore on DB2 1. Create a local user on the DB2 Server, for example: AutomationManager. This account will be used to connect to the RES Automation Manager Datastore. 2. Manually create a database on the DB2 Server, for example: AMDB. 3. Create a Table Space for the user AutomationManager in the new AMDB database. Specify a Buffer pool of 8KB. 4. Create a schema in the new AMDB database, for example: am. 5. Add the user you created in step 1 to the database AMDB. 6. Assign the applicable authorities, and add the schema and Table Space you created in steps 3 and 4 to this user. Make sure you assign the proper privileges.

2 0 1 4 0 3 0 4 g t

19

Installing drivers using RES Automation Manager Consoles and Dispatchers require the installation of certain database drivers on the computers on which they are deployed. You can do this using RES Automation Manager: 1. 2. 3. 4.

Manually install the appropriate database driver on a computer. Deploy a Dispatcher on this computer. Deploy an Agent on all computers on which you want to deploy a Console or a Dispatcher. Install the database driver on the target computers using the Task Invoke Windows Installer or Perform Unattended Installation. 5. Deploy a Dispatcher on these computers. 6. Optionally, remove the Agent from these computers. You can also use this method to migrate an existing RES Automation Manager environment from a Microsoft SQL database to a MySQL, Oracle or IBM DB2 database. Before you do this, create a Building Block of your Repository as a backup.

2 0 1 4 0 3 0 4 g t

20

Architecture Components Datastore The Datastore contains all the settings and Resources of your RES Automation Manager environment. It contains the following sections: Security: Configure different levels of access to the Console. Settings: Configure global settings, configure Variable of Agents and Teams, and view the Audit Trail. Setup: Configure and create Datastore connections, view Datastore information, view and update RES Automation Manager components, configure RES Automation Manager licensing and manage connectors. For environments with 1000+ agents a dedicated database server is recommended.

Consoles The Console is the application from which RES Automation Manager is configured and used, from setting up the RES Automation Manager environment to the execution of Tasks. A RES Automation Manager environment can contain several Consoles. Each Console can connect to different RES Automation Manager sites, but not simultaneously.

Engines At Engines, you can set up and manage Dispatchers. Dispatchers communicate information from the Datastore to Agents. Dispatchers contact the Datastore at regular intervals. If new Jobs are available for Agents to which it connects, the Dispatcher will download all necessary data from the Datastore and store it. The Agents will use this data to execute the Jobs. 

   

An RES Automation Manager environment can contain several Dispatchers. The size of your RES Automation Manager environment determines the number of Dispatchers needed: in test situations, a number of 9,000 concurrent connections was reached. However, the actual maximum number of concurrent connections depends on the type of Jobs that are executed and on the hardware properties of the machine on which the Dispatcher is running. Before you deploy new Dispatchers, ensure that the target computers meet the prerequisites. You can also deploy Dispatchers manually or unattended. The column Connections shows the current number of connected Agents, and the column Peak shows the maximum number of Agents that have ever connected concurrently to each Dispatcher. This number is updated approximately every thirty seconds. If Dispatchers are identified by MAC address or by Domain name/NetBIOS name, this information will be shown in the Dispatcher Properties, in the field Identified by. This field is not shown if components are identified by their GUID. You can change the way in which components are identified in the Global Settings. The availability of a Web API provides full support for building and deploying RESTful and SOAP web services. This allows you to integrate Job scheduling in external systems.

Agents An Agent is a service running on a computer, and can execute Tasks on networked Microsoft Windows desktops and servers. This can be on the same computer on which the Agent runs, but also on another computer (for example, when executing a Task Execute Secure Shell (SSH) Commands or a Task Create Exchange Mailbox. Before you deploy new Agents, ensure that the target computers meet the prerequisites. You can also deploy Agents manually or unattended.  If Agents are identified by MAC address or by Domain name/NetBIOS name, this information will be shown in the Agent Properties, in the field Identified by. This field is not shown if components are identified by their GUID. You can change the way in which components are identified in the Global Settings.  If an Agent is offline because the computer on which it is installed is turned off, you can use wake-on-LAN to turn on the computer and bring the Agent online. To use wake-on-LAN, right-click the Agent and choose Wake-onLAN. Please note that this feature only works if the Agent and your network infrastructure support wake-on-LAN.

2 0 1 4 0 3 0 4 g t

21

Enterprise Considerations RES Automation Manager Network Load Network Traffic of an Idle RES Automation Manager Agent We regard a RES Automation Manager Agent as idle when:  There are no jobs scheduled for the Agent  The RES Automation Manager Agent service (RESWAS) is up and running.  There are and will be no pending configuration changes in the database.  The RES Automation Manager Console service is not installed on the system with the Agent.

Packets

bytes

320 47,556 Expected idle traffic (further data on how expectation is calculated is available on request under NDA) Capture taken over a 5 minute period (approx. 300 seconds) Packets

bytes

320 47,370 Actual idle traffic based on capture Network Traffic of an Idle RES Automation Manager Dispatcher We regard a RES Automation Manager Dispatcher as idle when:  Agents don’t request anything other than idle traffic  The RES Automation Manager Dispatcher service (RESWDS) is up and running.  There are and will be no pending configuration changes in the Database.  The RES Automation Manager Console service is not installed on the system with the Dispatcher. In any given RES Automation Manager topology, one Dispatcher is dynamically assigned the role of garbage collector. This role is responsible for doing housekeeping on the database. Connected Agents 0

Garbage Collector No

0

Yes

Packets

Bytes

1,701

616,086

2,526

831,726

1 No 1,773 638,862 Expected idle traffic (further data on how expectation is calculated is available on request under NDA)

Connected Agents 0

Garbage Collector No

0

Yes

1

2 0 1 4 0 3 0 4 g t

Packets

Bytes

1,734

619,386

2,846

847,905

No 1,837 646,424 Actual idle traffic based on capture

22

Invocation of a Project A RES Automation Manager Dispatcher can operate in 3 configurations:  Not configured for connecting to a master cache dispatcher in case of a resource download and the resource is not cached (the default): Table 1  Configured to connect to a master-cache-dispatcher in case of a resource download, and the resource is not cached: Table 2  Configured to listen on an IP port other than the default 3164, which means that Agents cannot connect this Dispatcher: Table 3 The theory behind the configuration depicted in table 3 is to act as a Resource (AM resource file, AM resource package) cache of multiple local Dispatchers similar to that illustrated in table 2 but is the only dispatcher for that specific local network to access the database for downloading Resource files or Resource packages. Invoking a project type job an AM Agent with a 5.5MB resource, where the resource has not been download before, causes the following network load. Table 1 Between Agent (A) and Dispatcher (B): Packets

Bytes

Packets A→B

Bytes A→B

Packets A←B

Bytes A←B

6,119

625,5617

2,062

181,488

4,057

6,074,129

Table 2 Between non master cache dispatcher (A) and the Datastore (B): Packets

Bytes

Packets A→B

Bytes A→B

Packets A←B

Bytes A←B

319

246,684

199

101,406

120

145,278

Table 3 Between the master cache dispatcher (A) and the Datastore (B): Packets

Bytes

Packets A→B

Bytes A→B

Packets A←B

Bytes A←B

3,367

6,031,261

2323

143,373

1,044

5,887,888

2 0 1 4 0 3 0 4 g t

23

Compatibility Matrix Microsoft Operating Systems

Platform

Microsoft Windows Server 2003

x86/x64

Microsoft Windows Server 2003 R2

x86/x64

Microsoft Windows Server 2008

x86/x64

Microsoft Windows Server 2008 Core ed. Microsoft Windows Server 2008 R2

x64

Microsoft Windows Server 2008 R2 Core ed. Microsoft Windows Server 2012 Microsoft Windows Server 2012 Core ed. Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 R2 Core Edition Microsoft Windows XP

x86/x64

Microsoft Windows Vista

x86/x64

Microsoft Windows 7

x86/x64

Microsoft Windows 8

x86/x64

Other Operating Systems

Platform

Red Hat Enterprise Linux release 4: 4.5 and higher versions of release 4 Red Hat Enterprise Linux release 5: 5.3 and higher versions of release 5 Red Hat Enterprise Linux release 6: 6.0 SUSE Linux Enterprise Server release 10 SUSE Linux Enterprise Server release 11 Ubuntu release 12 IBM AIX 5L: version 5.3 (technical level 4 and higher) IBM AIX 6: version 6.1 (technical level 7 and higher) IBM AIX 6: version 7.1 Sun Solaris 10 for SPARC (update 6 and higher) Citrix XenServer 5.6

install Agents for Linux based on 32-bit versions of Red Hat Enterprise Linux release 5 (i386) only

Citrix XenServer 6.0

install Agents for Linux based on 32-bit versions of Red Hat Enterprise Linux release 5 (i386) only

Citrix XenServer 6.1

install Agents for Linux based on 32-bit versions of Red Hat Enterprise Linux release 5 (i386) only

2 0 1 4 0 3 0 4 g t

24

Directory Services

Platform

Microsoft Windows 2000 Microsoft Windows 2003 Microsoft Windows 2008 Microsoft Windows 2008 R2 Microsoft Windows 2012

Database

Platform

Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008

x86/x64

Microsoft SQL Server 2008 R2 Microsoft SQL Server 2012 Microsoft SQL Azure IBM DB2 9.1 IBM DB2 9.5 IBM DB2 9.7 MySQL 5.0 and higher

x86/x64

Oracle 10.1 Oracle 10.2 Oracle 11.1 Oracle 11.2

Mail Servers Microsoft Exchange Server 2000 Microsoft Exchange Server 2003 Microsoft Exchange Server 2007 Microsoft Exchange Server 2010 Microsoft Exchange Server 2010 SP1 Microsoft Exchange Server 2013

Application Virtualization Softricity SoftGrid Client 3.1 Microsoft App-V 4.5 Microsoft App-V 4.6 Microsoft App-V 5.0

2 0 1 4 0 3 0 4 g t

25

Microsoft System Center Configuration Manager System Center 2007 System Center 2012 System Center 2012 SP1

Microsoft PowerShell PowerShell 1.0 PowerShell 2.0 PowerShell 3.0

Citrix Citrix Workflow Studio 2.5 Citrix XenApp 4.5 (Presentation Server) Citrix XenApp 5.0 Citrix XenApp 6.0 Citrix XenApp 6.5 Citrix XenDesktop 4 Citrix XenDesktop 5.5 Citrix XenServer 5.5

VMware VMware ESX 3.x VMware vSphere 4.x

RES HyperDrive Agent for RES HyperDrive Virtual Appliance

RES Workspace Manager RES Workspace Manager Relay Server support in Task Install Windows Installer Package

2 0 1 4 0 3 0 4 g t

26

Citrix Ready certified for

Platform

Citrix XenApp 4.5 (Presentation Server)

x86/x64

Citrix XenApp 5.0

x86/x64

Citrix XenApp 6.5 Citrix XenDesktop 4 Citrix XenDesktop 5.5 Citrix XenServer 5.0 Citrix XenServer 5.5

2 0 1 4 0 3 0 4 g t

27

Conclusion Hopefully this document has provided you with some useful information that can be used when you are designing your next RES Automation Manger implementation. There are a network of highly skilled partners that can assist you with your requirements – please check the RES Software website for more information.

Click Here for the Getting started with RES Automation Manager 2014 Guide Click Here for the Getting Started with the RES Automation Manager Agent for Linux Guide Click Here for the RES Automation Manager 2014 Administration Guide Also be sure to keep an eye on our Blog site at http://blog.ressoftware.com/ where you will find regular technical articles from the RES Software team. Finally, RES Software customers can always contact our Support Department who are here to assist you with any technical concerns you may have.

2 0 1 4 0 3 0 4 g t

28