Deploy aspenONE V8.

8 with SCCM 2012

Best Practices
Version Number: V8.8
May 2015
Copyright (c) 2015 by Aspen Technology, Inc. All rights reserved.

The Aspen leaf logo is a trademark of Aspen Technology, Inc., Bedford, MA.

All other brand and product names are trademarks or registered trademarks of their respective companies.

This document is intended as a guide to using AspenTech's software. This documentation contains AspenTech
proprietary and confidential information and may not be disclosed, used, or copied without the prior consent of
AspenTech or as set forth in the applicable license agreement. Users are solely responsible for the proper use of
the software and the application of the results obtained.

Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software
may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO
WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS DOCUMENTATION,
ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Aspen Technology, Inc.

20 Crosby Drive,
Bedford, MA 01730
USA
Phone: (1) (781) 221-6400
Toll Free: (888) 996-7100
URL: http://www.aspentech.com
Contents
1 Introduction .........................................................................................................5
About this Document ........................................................................................5
Silent Install and SCCM 2012.............................................................................6
System Configuration .............................................................................7
Client Virtual Machines............................................................................7

2 Third-Party Pre-requisites for SCCM Deployment .................................................9

Preparing .NET 3.5 SP1 and .NET 4.5.1 ...............................................................9
Create SCCM Application for .NET 3.5 SP1......................................................... 10
Create SCCM Application for .NET 4.5.1 ............................................................ 15

3 Aspen Technology Products SCCM Deployment ..................................................21

Aspen Plus: Create a Silent Install Package ....................................................... 21
Create SCCM Application for Aspen Plus ............................................................ 31
Create Deployment for Windows 7 x86 ................................................... 38
Aspen HYSYS: Create a Silent Install Package.................................................... 40
Create SCCM Application for Aspen HYSYS ........................................................ 49
Create Deployment for Windows 7 x86 ................................................... 56

4 Additional Information .......................................................................................59

Reboots .............................................................................................. 59
Pre-staging.......................................................................................... 59
Cache size........................................................................................... 60
Stream vs. Download Content Locally ..................................................... 60
SQL Server.......................................................................................... 60
Logging............................................................................................... 61

Index ....................................................................................................................63

Contents iii
iv Contents
1 Introduction

About this Document

The Deploy aspenONE V8.8 with SCCM 2012 Best Practices guide details the
processes applicable to the SCCM System Administrator for creating Aspen
Technology applications in a Microsoft SCCM 2012 environment. This
document will go over Windows 7 (32 and 64-bit) platforms.
The Deploy aspenONE V8.8 with SCCM 2012 Best Practices document:
 Is for use by an experienced Microsoft System Center 2012 administrator
with previous expertise packaging and deploying applications in the SCCM
2012 environment.
 Provides instructions at a high level assuming the target audience will
have the prerequisite knowledge base mentioned in the Deploy aspenONE
V8.8 with SCCM 2012 Best Practices document.
 Eliminates a large part of the trial and error involved in packaging an
Aspen Technology V8.8 AES product for distribution with a SCCM 2012
environment.
 Describes the creation of silent installation source files using Aspen
Technology silent deployment tools, and the best practices for creating
SCCM 2012 applications with these source files.
 Will cover, and is limited to, the silent packaging of the third-party
(Microsoft) prerequisites that Aspen Technology distributes with V8.8
media that include, .Net 3.5 SP1 and .Net 4.5.1.

Notes:
 The Deploy aspenONE V8.8 with SCCM 2012 Best Practices’ proof of
concept is one of many ways to package the applications.
 Aspen Technology is not responsible for support of packaging or
deployment of third-party software and the associated documentation
provided is a proof of concept.
 Due to differing corporate regulations and policies we cannot provide an
instruction set that will apply to all deployment scenarios.
 It is the responsibility of the SCCM 2012 System Administrator to interpret
the instructions provided in the Deploy aspenONE V8.8 with SCCM 2012
Best Practices document, and to make appropriate changes based on
his/her enterprise environment.
For supported best practices regarding the silent installation and SCCM
packaging of these redistributable components please consult the appropriate
software provider, in this case, Microsoft.

1 Introduction 5
 Silent Install and SCCM 2012
Microsoft’s System Center Configuration Manager 2012 can be utilized to
facilitate pushing silent installations from a central IT system to computers in
an enterprise deployment environment.
Aspen Silent Install is a collection of tools that will allow for creation of .msi
packages and scripts for silent installations. Aspen Tech Silent Install tools,
starting in V8.0, are now gathered under Prepare Deployment Workflow in the
new V8.8 Installer.
Aspen Tech Silent install in a combination with SCCM 2012 will allow the
SCCM System Administrator to:
 Create a Third-Party Prerequisite Silent Install Package.
 Utilize a Third-Party Prerequisite Silent Installation package to create a
SCCM 2012 application.
 Create an Aspen Silent Install Package.
 Utilize an Aspen Silent Install package to create a SCCM 2012 application.
 Install and trouble-shoot Aspen products.
The end result of this document will be four SCCM 2012 Applications:
 .NET 3.5 SP1
 .NET 4.5.1
 Aspen Plus
 Aspen HYSYS
The SCCM 2012 Applications allow the end user to have the ability to
deploy an Aspen Plus installation and an Aspen HYSYS installation to 64-bit
and 32-bit client systems.
The instructions regarding the use of Aspen Technology silent deployment
tools are applicable to all client-side products within the AES product family,
excluding the following: aspenONE, Process Explorer, ABE Server, Process
Manual, Online Deployment, and Aspen Mobile Server.

Notes:
 Aspen Technology assumes responsibility and supports only the creation
of silent installation source files and SCCM 2012 Applications for Aspen
Technology products.
 If it is determined that a failed SCCM 2012 deployment of Aspen
Technology products is due to the packaging or deployment of Microsoft
third-party redistributable dependencies or the SCCM 2012 system itself,
it will be the responsibility of the end user to consult with Microsoft to
resolve these issues.

6 1 Introduction
 System Configuration
The procedures described in the Deploy aspenONE V8.8 with SCCM 2012 Best
Practices document were performed on a virtual SCCM 2012 environment with
the following platform specifications:
SCCM Infrastructure Virtual Machines
Active Directory (Cambridge, MA): Windows Server 2008 R2 SP1
SCCM SQL Server (Cambridge, MA): Windows Server 2008 R2 SP1
with SQL Server
SCCM Primary Site (Cambridge, MA): Windows Server 2008 R2 SP1
Distribution Point (Cambridge, MA): Windows Server 2008 R2 SP1
Distribution Point (Houston, TX): Windows Server 2008 R2 SP1

Client Virtual Machines

 Cambridge, MA
o Windows 7 Enterprise x64
o Windows 7 Enterprise x86
 Bedford, MA
o Windows 7 Enterprise x64
o Windows 7 Enterprise x86
 Houston, TX
o Windows 7 Enterprise x64
o Windows 7 Enterprise x86

1 Introduction 7
8 1 Introduction
2 Third-Party Pre-requisites
for SCCM Deployment

This chapter describes the prerequisites needed for the Deploy aspenONE
V8.8 with SCCM 2012 Best Practices configuration of the Aspen Technology
example products packaged in this document.

Preparing .NET 3.5 SP1 and

.NET 4.5.1
These .NET executables work with both x86 and x64 architectures and are the
only inputs needed for SCCM to package the .NET prerequisites
Within AspenTech media, navigate to the 3rd Party Redistributables folder.
You will see directories for:
 Microsoft .NET Framework 3.5 SP1
Contents: dotNetFx35.exe
 Microsoft .NET Framework 4.5.1
Contents: NDP451-KB2858728-x86-x64-AIIOS-ENU.exe
Create two folders at an appropriate location in your SCCM 2012 source
directory and copy the executable files into them.

Note: Copy and paste the entire folder from the redistributables; there are no
extra files.

2 Third-Party Pre-requisites for SCCM Deployment 9

 Create SCCM Application for
.NET 3.5 SP1
 Click Create Application from the SCCM application ribbon.
 Choose Manually specify.
 Fill out the general information under Specify information about this
application.
 Set application catalog properties.
 Add Deployment Type:
Specify general information for this deployment type.
Select type: Script Installer.

10 2 Third-Party Pre-requisites for SCCM Deployment

 Content
 Location:
\\<sccm host>\<sccm source directory>\...\<.net 3.5 sp1>
Browse to the directory you created during the preparation of the .NET 3.5
SP1 package.

Example: \\sccm-primary\Media\Microsoft .NET 3.5 SP1

 Installation Program:
dotNetFx35.exe /q /norestart
o /q = Quiet installation
o /norestart = suppresses restart for this installation (will handle with
SCCM)

2 Third-Party Pre-requisites for SCCM Deployment 11

 Detection Method
Select Add Clause, then add the two registry clauses:
 Clause 1: Valid installation of .NET 3.5

12 2 Third-Party Pre-requisites for SCCM Deployment

  Clause 2: Valid install of SP1

Note: The two detection methods should be connected with and, because
both are necessary.

2 Third-Party Pre-requisites for SCCM Deployment 13

 User Experience
 In the Installation Behavior field, Install for system is required.
 In the Logon requirement field, select: Whether or not a user is
logged on.
 In the Installation Program Visibility field, select Normal (installation
scripts will suppress interaction.)

Notes:
 In the example system we have chosen these values.
 Please select values based on your deployment methodologies and
organizational standards.

 .NET 3.5 SP1 is packaged with no requirements.

 .NET 3.5 SP1 is packaged with no dependencies.
Complete the wizard by reviewing summary and proceeding.

14 2 Third-Party Pre-requisites for SCCM Deployment

 Create SCCM Application for
.NET 4.5.1
 Click Create Application from the SCCM application ribbon
 Select Manually Specify.
 Enter the general information, Specify information about this
application.
 Set application catalog properties.
 Add Deployment Type:
Specify general information for this deployment type.
Type: Script Installer.

2 Third-Party Pre-requisites for SCCM Deployment 15

 Content
 Location: \\<sccm host>\<sccm source directory>\...\<.net 4.5.>
Browse to the directory you created during the preparation of the .NET 4.5.1
package.

Example: \\sccm-primary\Media\Microsoft .NET 4.5.1

 Installation script:
NDP451-KB2858728-x86-x64-AIIOS-ENU.exe /q /norestart
o /q = Quiet installation
o /norestart = suppresses restart for this installation (will handle with
SCCM)

16 2 Third-Party Pre-requisites for SCCM Deployment

 Detection Method
There are two registry keys to check here to make sure that .NET 4.5.1 has
installed both the “client” and “full” framework, and that the right version is
used.

 Clause 1: Client
o Make sure the Version is greater than or equal to 4.5.50938

2 Third-Party Pre-requisites for SCCM Deployment 17

  Clause 2: Full
o Make sure the Version is greater than or equal to 4.5.50938

Note: These two detection methods should be connected with and, because
both are necessary.

18 2 Third-Party Pre-requisites for SCCM Deployment

 User Experience
 In the Installation Behavior field, Install for system is required and
must be selected.
 In the Logon requirement field, select: Whether or not a user is
logged on.
 In the Visibility field, Normal (installation scripts will suppress
interaction), is optional.

Notes:
 In the example system we have chosen these values.
 Please select values based on your deployment methodologies and
organizational standards.

 .NET 4.5.1 is packaged with no requirements.

 .NET 4.5.1 is packaged with no dependencies.
Complete the wizard by reviewing summary and proceeding.

2 Third-Party Pre-requisites for SCCM Deployment 19

20 2 Third-Party Pre-requisites for SCCM Deployment
3 Aspen Technology Products
SCCM Deployment

Aspen Plus: Create a Silent

Install Package
The creation for the silent installation .xml file is written assuming that the
end goal is an SCCM package. You will need to make a separate .xml file for
x86 and x64 machines.
The Deploy aspenONE V8.8 with SCCM 2012 Best Practices document will
outline only one such workflow.
On Windows 7 or greater client platforms, the Aspen Tech installer
implements an installation of LocalDB for use by the products.

3 Aspen Technology Products SCCM Deployment 21

 Aspen Technology Prepare Deployment Workflow
Insert AspenTech DVD, or browse to a media location on the network share
on a clean Windows 7 x64 machine with .NET 3.5 and .NET 4.5.1 installed.

Note: If you only plan to install the product on Windows 7 x86 machines, you
can use a clean Windows x86 machine.

If AUTORUN has not been invoked by the DVD, double click, Setup.exe

In the aspenONE Installer, choose Prepare Deployment

 Create a directory that will be used for your package of Aspen Tech
silent installation files for an Aspen Plus installation.

Note: In the example, the folder will be C:\Media\AspenPlus

22 3 Aspen Technology Products SCCM Deployment

 Select Record installation script
 Response file name: select a file name of your choice, you may leave
the default name or enter something more descriptive.
Note: In the example, we renamed it to Aspen Plus V8.8 (x64).xml

 Record to folder: enter or browse to the directory that you created to

store these installation files.
 Record User Changes only: records any changes you make from the
default installation values and results in the silent installation .xml file
being shorter and more manageable.
 Install media location: specify the location, C:\ as filler.
Notes:
 This location is used during silent installation with a batch file.
 The batch file will not be used during SCCM deployment; however, the
field must contain a value of your choice.

 Install log file: Creates a log file on the client machine, the application is
being packaged on, used to troubleshoot product installation.
 Select Copy installation files for selected products.
o Browse to the directory that you created to store these
installation files.

Note: Copy installation files for selected products will copy the
necessary installation files from the AspenTech media to the directory of your
silent installation package. This will keep SCCM packages distributed across
your infrastructure as lean as possible.

3 Aspen Technology Products SCCM Deployment 23

 Select, Process Modeling (Aspen Plus)
 Aspen Exchanger Design & Rating and Economic Evaluation are included
within the Aspen Plus product group and are unavailable for removal.

24 3 Aspen Technology Products SCCM Deployment

 (OPTIONAL) Select the File Location tab to install the AspenTech products
in your desired location.
 The default value is C:\Program Files (X86) on a x64 machine, and
C:\Program Files on a x86 machine. If this is how you want it installed,
skip this step.

3 Aspen Technology Products SCCM Deployment 25

 Enter the information for your AspenTech license server, or a standalone
license:

26 3 Aspen Technology Products SCCM Deployment

 Review your installation settings before recording the .xml file, then select
Record Now to create the configuration files and copy the necessary media
to the proper location.

3 Aspen Technology Products SCCM Deployment 27

 Aspen Tech silent installation tool creates the following silent installation files
for an installation of Aspen Plus:

 Aspen Plus Installation includes 12 products and a corresponding .MST file

for each product.
 Aspen Plus V8.8 (x64).xml is the configuration file for the silent
installation, and was specified during the recording step of the AspenTech
prepare deployment tool.
 Aspen Plus V8.8 (x64).bat is a batch file that can be used for silent
deployment, however will not be using this file for deployment with SCCM.
 The aspenoneengdvd directory contains the .MSI and any other
necessary installation files for each AspenTech product associated with the
Aspen Plus installation. Within this folder, there will be a directory for each
.MST file seen above.

Copy the file, ATRunUnattended.exe from the AspenTech DVD Tools folder
to the directory where the installation files just created are stored.

Then copy the Aspen Plus Installation directory to an appropriate location in

your SCCM source directory.

Note: Check for updates of ATRunUnattended.exe, at the AspenTech support

website for enhanced features and bug fixes.

28 3 Aspen Technology Products SCCM Deployment

 Create .XML for Window 7 x86
Alterations to the silent install .xml file are needed to prepare for an x86
machine architecture.

 Run through the process above again on a clean Windows x86 machine.

 Rename the .XML configuration file to Aspen Plus (x86).xml, or any

other name to differentiate it from the x64 file.

 If you already created an x64 installation package, you do not have to

check Copy installation files for selected products, as you will be using the
files created from the x64 installation package.

Copy over only the .XML configuration file created for the x86 machine
to the SCCM source directory where the x64 installation package was placed.

3 Aspen Technology Products SCCM Deployment 29

 The final contents of the SCCM source directory for the Aspen Plus product
should look similar to below:

30 3 Aspen Technology Products SCCM Deployment

 Create SCCM Application for
Aspen Plus
Select Create Application from the SCCM application ribbon.
 Select Manually Specify.
 Fill out general information under Specify information about this
application.
 Set the application catalog properties.

Differing dependencies and folder structures across the two example systems
result in two different deployment types:
 Windows 7 x64
 Windows 7 x86

Add Deployment Type, in the General Information pane; name your

application and reference the system and architecture that the deployment
applies to. Type: Script Installer.

3 Aspen Technology Products SCCM Deployment 31

 Content
 location:
\\<sccm host>\<sccm source directory>\...\<Aspen Plus>
Browse to the directory you created during the preparation of the Aspen Plus
package:

Example: \\sccm-primary\Media\AspenPlus

32 3 Aspen Technology Products SCCM Deployment

  Installation program:
AtRunUnattended.exe "Aspen Plus V8.8 (x64).xml"
altsource="aspenoneengdvd" /L /noreboot
o Altsource: specifies that AtRunUnattended.exe should use the media
location in its local folder
o /L: enables verbose logging. This flag will produce detailed MSI logs
for each product installation to help with troubleshooting. A custom file
location and name can be specified using /L logfile = [path\name.log].
For more information, see the Logging section within the Additional
Information section of this document for system specific log location.
Note: This option increases the installation time by a factor of at least 2.
o /noReboot - to suppress a reboot

Individual product uninstalling through SCCM system is not supported.

 To silently uninstall all Aspen Tech products from a system run
AtRunUnattended.exe /removeall

Note: The example does not include the use of an uninstallation program.
CAUTION: This will uninstall all versions of all AspenTech products from
your system.

3 Aspen Technology Products SCCM Deployment 33

 Detection Method
There are 12 detection rules for this Application.
A Windows Installer detection method will be used for each. To find the
product codes, choose Windows Installer as a detection rule and browse to
each MSI. Each directory within the aspenoneengdvd directory represents a
particular product that will have its own MSI. Browse to each location to
import the product code straight from the MSI.

 Aspen Batch Process Developer V8.8: {EC914A19-AA5B-492B-9BC8-

D266D9B1949C}
 Aspen Energy Analyzer V8.8: {D3357268-FB27-4D5B-963A-
575667243F7E}
 Aspen Flare System Analyzer V8.8: {D2EE16BA-D766-4F9A-B29E-
3704112B8B14}
 Aspen OTS Framework V8.8: {E6C78967-D64B-410D-8AE8-
F5BB4FC1555F1}
 Aspen Plus Refinery V8.8: {3377D21F-90DA-4AD9-9F72-0BBF198BE665}
 Aspen Properties V8.8: {AA662CC2-7762-4953-8000-FF83DB90E687}
 Aspen Simulation Workbook V8.8: {FAAC374E-E9B4-4755-ABB1-
F28319E3C84D}
 Aspen Utilities Planner V8.8: {C82F5EE2-A2FE-4C91-8636-
8DA223130943}
 Aspen Version Comparison Assistant V8.8: {C5A56564-1C6E-4E91-ACBC-
9A7FE76B6EEA}
 Economic Evaluation V8.7.1: {57D61C8E-4BE3-43E1-B2DD-
935540F11CA2}
 Exchanger Design and Rating V8.8: {BB6751F8-D9B5-4AD8-BC8F-
76D8286B7790}
 Process Modeling (Aspen Plus) V8.8: {7B8EE77E-B26B-48C6-B290-
295A0B6F3866}
Include a Windows Installer Detection Rule for each product, connecting them
with “And” clauses as they are all required.

34 3 Aspen Technology Products SCCM Deployment

 User Experience
Select values based on your deployment methodologies and organizational
standards.
 In the Installation behavior field, Install for system is required and
must be selected.
 In the Logon requirement field, select: Whether or not a user is
logged on, is optional
 In the Installation Program Visibility field, Normal (installation scripts
will suppress interaction), is optional.

3 Aspen Technology Products SCCM Deployment 35

 Requirements
When targeting only Windows 7 x64 systems, add this operating system
specification as a requirement.

36 3 Aspen Technology Products SCCM Deployment

 Dependencies
The dependencies for Windows 7 x64 system are the .NET 3.5 SP1 and .NET
4.5.1; packaging details are outlined previously in this document.

Note: Installation of AspenTech products runs more smoothly if the

dependencies are already installed on the client machines. Having them install
automatically with the Aspen Plus installation packet increases the chance of
initial failure to install as the dependencies may need to restart first.

Proceed through the Create Deployment Wizard, until you return to the
Deployment Types pane of the Create Application Wizard.

3 Aspen Technology Products SCCM Deployment 37

 Create Deployment for Windows 7 x86
Select your x64 deployment and make a copy of it using Copy.

 Edit the new deployment that you just copied.

 Rename this new deployment type with some reference to Windows 7 x86
as this will be the target system.
 In the Programs tab:
o Change the installation program to: ATRunUnattended.exe "Aspen
Plus V8.8 (x86).xml" altsource="aspenoneengdvd" /L
/noreboot

Note: “Aspen Plus V8.8 (x86).xml” references the x86 version of the .xml
configuration file that was created earlier.

38 3 Aspen Technology Products SCCM Deployment

  In the Requirements tab:
o Edit the present requirement.
o Change the machine requirement to target All Windows 7 (32-bit)
operating systems.

 Select Ok at the properties window to save changes.

Proceed through the rest of the Create Application Wizard. The Aspen Plus
SCCM Application is now created.

3 Aspen Technology Products SCCM Deployment 39

 Aspen HYSYS: Create a Silent
Install Package
The creation for the silent installation .xml file is written assuming that the
end goal is an SCCM package. You will need to make a separate .xml file for
x86 and x64 machines.
This document outlines only one such workflow.
On Windows 7 or greater client platforms, the Aspen Tech installer
implements an installation of LocalDB for use by the products.

Aspen Technology Prepare Deployment Workflow

Insert an AspenTech DVD, or browse to media location on network share on a
clean Windows 7 x64 machine with .NET 3.5 SP1 and .NET 4.5.1 installed.

Note: If you only plan to install the product on Windows 7 x86 machines, you
can use a clean Windows 7 x86 machine.

If AUTORUN has not been invoked by the DVD, double-click Setup.exe

In the aspenONE Installer, choose Prepare Deployments.

 Create a directory that will be used for your package of AspenTech
silent installation files for an Aspen HYSYS installation.
Note: In the example, the folder will be C:\Media\HYSYS.

40 3 Aspen Technology Products SCCM Deployment

 Select, Record installation script
 Response file name: select a file name of your choice; you may leave
the default name or enter something more descriptive.
Note: In this example, the file is renamed to HYSYS V8.8 (x64).xml.

 Record to folder: enter or browse to the directory that you created to

store these installation files.
 Record User Changes only: records any changes you make from the
default installation values and results in the silent installation .xml file
being shorter and more manageable.
 Install media location: specify the location, C:\ as filler.
Notes:
 This location is used during silent installation with a batch file.
 The batch file will not be used during SCCM deployment; however, the
field must contain a value of your choice.

 Install log file: Creates a log file on the client machine that the
application is being packaged on, used to troubleshoot product
installation.

 Select Copy installation files for selected products.

o Browse to the directory that you created to store these
installation files.

Note: Copy installation files for selected products will copy the
necessary installation files from the AspenTech media to the directory of your
silent installation package; to keep SCCM packages distributed across your
infrastructure as lean as possible.

3 Aspen Technology Products SCCM Deployment 41

 Select Process Modeling (Aspen HYSYS)
 Process Modeling (Aspen Plus), Aspen Exchanger Design & Rating, and
Economic Evaluation are included within the Aspen HYSYS product group
and are unavailable for removal.

42 3 Aspen Technology Products SCCM Deployment

 (OPTIONAL) Select the File Location tab to install the AspenTech products
in your desired location.
 The default value is C:\Program Files (X86) on an x64 machine, and
C:\Program Files on an x86 machine. If this is how you want it installed,
skip this step.

3 Aspen Technology Products SCCM Deployment 43

 Enter the information for your AspenTech license server, or a standalone
license:

44 3 Aspen Technology Products SCCM Deployment

 Review your installation settings before recording the .xml file, then Select,
Record Now to create the configuration files and copy the necessary media
to the proper location.

3 Aspen Technology Products SCCM Deployment 45

 Aspen Tech silent installation tool creates the following silent installation files
for an installation of Aspen HYSYS:

Aspen HYSYS Installation includes 13 products and a corresponding .MST file

for each product.
 HYSYS V8.8 (x64).xml is the configuration file for the silent installation,
and was specified during the recording step of the Aspen Tech prepare
deployment tool.
 HYSYS V8.8 (x64).bat is a batch file that can be used for silent
deployment, however will not be using this file for deployment with SCCM.
 The aspenoneengdvd directory contains the .MSI and any other
necessary installation files for each Aspen Tech product associated with
the Aspen Plus installation. Within this folder, there will be a directory for
each .MST file seen above.

Copy the file, ATRunUnattended.exe from the AspenTech DVD Tools folder
to the directory where the installation files just created are stored.

Then copy the entire directory to an appropriate location in your SCCM source
directory.

Note: Check for updates of ATRunUnattended.exe, at the AspenTech support

website for enhanced features and bug fixes.

46 3 Aspen Technology Products SCCM Deployment

 Create .XML for Window 7 x86
Alterations to the silent install .xml file are needed to prepare for an x86
machine architecture.
 Run through the process above again on a clean Windows x86 machine.
 Rename the .XML configuration file to HYSYS V8.8 (x86).xml, or any
other name to differentiate it from the x64 file.

 If you already created an x64 installation package, you do not have to

check Copy installation files for selected products as you will be
using the files created from the x64 installation package.

Copy over only the .XML configuration file created for the x86 machine
to the SCCM source directory where the x64 installation package was placed.

3 Aspen Technology Products SCCM Deployment 47

 The final contents of the SCCM source directory for the Aspen HYSYS product
should look similar to below:

48 3 Aspen Technology Products SCCM Deployment

 Create SCCM Application for
Aspen HYSYS
Select Create Application from the SCCM application ribbon.
 Select Manually specify.
 Fill out general information under Specify information about this
application.
 Set the application catalog properties.
Differing dependencies and folder structures across the two example systems
result in two different deployment types:
 Windows 7 x64
 Windows 7 x86
Add Deployment Type, in the General Information pane; name your
application, and reference the system and architecture that the deployment
applies to; Type: Script Installer.

3 Aspen Technology Products SCCM Deployment 49

 Content
 Location:
\\<sccm host>\<sccm source directory>\...\<Aspen HYSYS>

Browse to the directory you created during the preparation of the Aspen
HYSYS Custom:

Example: \\sccm-primary\Media\HYSYS

50 3 Aspen Technology Products SCCM Deployment

  Installation program:
AtRunUnattended.exe “HYSYS V8.8 (x64).xml"
altsource="aspenoneengdvd" /L /noreboot
o Altsource: specifies that AtRunUnattended.exe should use the media
location in its local folder.
o /L: enables verbose logging. This flag will produce detailed MSI logs
for each product installation to help with troubleshooting. .A custom
file location and name can be specified using /L logfile =
[path\name.log]. For more information, see the Logging section
within the Additional Information section of this document for system
specific log location.
Note: This option increases the installation time by a factor of at least 2.
o /noReboot, suppress rebooting.
Individual product uninstallation through the SCCM system is not supported.
 To silently uninstall all Aspen Tech products from a system run
AtRunUnattended.exe/removeall

Note: The example does not include the use of an uninstallation program.
CAUTION: This will uninstall all versions of all AspenTech products from
your system.

3 Aspen Technology Products SCCM Deployment 51

 Detection Method
There are 13 detection rules for this Application.
A Windows Installer detection method will be used for each. To find the
product codes, choose Windows Installer as a detection rule and browse to
each MSI. Each directory within the aspenoneengdvd directory represents a
particular product that will have its own MSI. Browse to the location to
import the product code straight from the MSI.

 Aspen Batch Process Developer V8.8: {EC914A19-AA5B-492B-9BC8-

D266D9B1949C}
 Aspen Energy Analyzer V8.8: {D3357268-FB27-4D5B-963A-
575667243F7E}
 Aspen Flare System Analyzer V8.8: {D2EE16BA-D766-4F9A-B29E-
3704112B8B14}
 Aspen OTS Framework V8.8: {E6C78967-D64B-410D-8AE8-
F5BB4FC1555F1}
 Aspen Plus Refinery V8.8: {3377D21F-90DA-4AD9-9F72-0BBF198BE665}
 Aspen Properties V8.8: {AA662CC2-7762-4953-8000-FF83DB90E687}
 Aspen Simulation Workbook V8.8: {FAAC374E-E9B4-4755-ABB1-
F28319E3C84D}
 Aspen Utilities Planner V8.8: {C82F5EE2-A2FE-4C91-8636-
8DA223130943}
 Aspen Version Comparison Assistant V8.8: {C5A56564-1C6E-4E91-ACBC-
9A7FE76B6EEA}
 Economic Evaluation V8.7.1: {57D61C8E-4BE3-43E1-B2DD-
935540F11CA2}
 Exchanger Design and Rating V8.8: {BB6751F8-D9B5-4AD8-BC8F-
76D8286B7790}
 Process Modeling (Aspen Plus) V8.8: {7B8EE77E-B26B-48C6-B290-
295A0B6F3866}
 Process Modeling (HYSYS) V8.8: {E291BF53-6583-4BBB-A6E2-
C563364FBC41}

Include a Windows Installer Detection Rule for each product, connecting them
with “And” clauses as they are all required.

52 3 Aspen Technology Products SCCM Deployment

 User Experience
Select values based on your deployment methodologies and organizational
standards.
 In the Installation Behavior field, Install for system is required.
 In the Logon requirement field, select Whether or not a user is logged
on.
 In the Visibility field, Normal (installation scripts will suppress
interaction.) is optional.

3 Aspen Technology Products SCCM Deployment 53

 Requirements
When targeting only Windows 7 x64 systems, add this operating system
specification as a requirement.

54 3 Aspen Technology Products SCCM Deployment

 Dependencies
The dependencies for Windows 7 x64 system are the .NET 3.5 SP1 and .NET
4.5.1; packaging details outlined previously in this document.

Note: Installation of AspenTech products runs more smoothly if the

dependencies are already installed on the client machines. Having them install
automatically with the Aspen Plus installation packet increases the chance of
initial failure to install as the dependencies may need to restart first.

Proceed through the Create Deployment Wizard, until you return to the
Deployment Types pane of the Create Application Wizard.

3 Aspen Technology Products SCCM Deployment 55

 Create Deployment for Windows 7 x86
Select your x64 deployment and make a copy of it using the Copy button.

 Edit the new deployment that you just copied.

 Rename this new deployment type with some reference to Windows 7 x86
as this will be the target system
 In the Programs tab:
o Change the installation program to: ATRunUnattended.exe "HYSYS
V8.8 (x86).xml" altsource="aspenoneengdvd" /L /noreboot

Note: “HYSYS V8.8 (x86).xml” references the x86 version of the .xml
configuration file that was created earlier.

56 3 Aspen Technology Products SCCM Deployment

  In the Requirements tab:
o Edit the present requirement.
o Change the machine requirement to target All Windows 7 (32-bit)
operating systems.

 Select Ok at the properties window to save changes.

Proceed through the rest of the Create Application Wizard. The Aspen
HYSYS SCCM Application is now created.

3 Aspen Technology Products SCCM Deployment 57

58 3 Aspen Technology Products SCCM Deployment
4 Additional Information

Reboots
The packages contained within the Deploy aspenONE V8.8 with SCCM 2012
Best Practices document are written to initiate a soft reboot only. Aspen
Technology is under the assumption that the packages may be deployed when
the end user is actively logged into the client system and suggest that a
reboot is not forced by the system even if necessary. Depending on corporate
policies, rebooting of user systems by SCCM 2012 may be handled differently,
especially if the deployment is scheduled to take place when the user will not
be at the device. It is recommended that the prerequisites be installed first on
the client machines, and then rebooted before installing the AspenTech
products.

Notes:
 The /noreboot flag for the Aspen Technology silent installation tool,
ATRunUnattended.exe, flips the /REALLYSUPRESS switch on
MSIEXEC.exe; if the installation exits with a reboot required it will issue
the 3010 return code upon completion.
 In the default settings of an SCCM 2012 Deployment Type, 3010 is
mapped to a soft reboot and will be triggered by the SCCM 2012 system.

Pre-staging
When deploying Aspen Technology products in locations a great distance (or
over a slow link) from the SCCM Primary site, it is useful to pre-stage content
on the remote distribution points. When pushing content over a great
distance, issues with failed deployments and difficulty syncing content
updates across all DPs have occurred.

Note: For more information regarding how to pre-stage content please refer
to: http://technet.microsoft.com/en-
us/library/gg712694.aspx#BKMK_DistributeContent

4 Additional Information 59
 Cache size
Ensure that SCCM client caches on machines that Aspen Technology
applications deploys to are sufficiently large enough to support deployment of
large products. The Aspen HYSYS installation application is approximately
5GB, and the Aspen Plus Typical installation is approximately 3GB in size.
In the test environment, client cache size is set to 8GB and deployments
execute without issue.

Note: If SCCM is used heavily for application deployment within your

enterprise, with the potential for multiple applications to be cached on a client
system simultaneously, it may be necessary to adjust this value upwards
from 8GB as deemed appropriate.

Stream vs. Download Content Locally

If Aspen Technology products are being deployed to laptop systems it is
recommend that the content be downloaded locally and then installed to
lower the risk of failed installation because of the large size of the
applications. When the application is set to download locally, after the files
are downloaded to the local machine the application will become available.
This removes any networking issues that may negatively impact the
installation.

SQL Server
On Windows 7 x86 and x64 applicable Aspen Technology products will install
a version of SQL 2012, localDB, on the client system which will be used to
store AspenTech application data. Windows Server platforms are not
compatible with localDB and these systems require SQL Server be installed.
AspenTech products support SQL Server 2005 or newer databases,
including, express. An installer for SQL Server Express 2012 SP1 is
distributed with the Aspen Technology V8.8 media, and can be found in the
3rd Party Redistributables folder.
If only one database instance is installed on the machine, the AspenTech
installer will automatically detect and use that instance. However, if there are
multiple instances, the appropriate instance will need to be specified within
the .XML file; or the database will need to be manually restored on the client
system before AspenTech products will function.

60 4 Additional Information
 Logging
To help diagnose a failed Aspen Technology product installation there are two
different types of log files created on the client system, if the /L flag is used
with ATRunUnattended.exe in the deployment.
The first, and generally most useful with SCCM, is the silent installation log.
This file will be named, ATRunUnattended [date and time].log, and
contains the calls to msiexec.exe being made by the Aspen Technology
silent installation tool. This log file will be generated every time the
ATRunUnattended.exe tool is run, whether or not the /L parameter is used.
Second are the individual product installation logs, one log file for each
product installed. These verbose log files contain every command executed by
MSIExec.exe during the installation

Example: Process Modeling (Aspen Plus) V8.8.log.

SCCM runs the installation under a System account and creates the log files in
the following locations for each operating system:
Windows 7 (x86 and x64):
C:\Windows\Temp

4 Additional Information 61
62 4 Additional Information
Index

A
About this Document, 5 I
Additional Information, 59 Introduction, 5
Aspen HYSYS: Create a Silent
Install Package, 40
L
Aspen Plus: Create Silent Install
Package, 21 Logging, 61
Aspen Technology Products SCCM
Deployment, 21 P
Preparing .NET 3.5 SP1 and .NET
C
4.5.1, 9
Cache size, 60 Prestaging, 59
Client Virtual Machines, 7
Create Deployment for Windows 7 R
x86, 38, 56
Create SCCM Application for .NET Reboots, 59
3.5 SP1, 10
Create SCCM Application for .NET S
4.5.1, 15
SCCM Infrastructure Virtual
Create SCCM Application for Aspen
Machines, 7
HYSYS, 49
Silent Install and SCCM 2012, 6
Create SCCM Application for Aspen
SQL Server, 60
Plus, 31
Stream vs. Download Content
Locally, 60
System Configuration, 7

Index 63