CCH Tax and Accounting. A WoltersKluwer Company ProSystem fx Engagement

Views: 1.4k  |  Created: 05/12/2011

Average Rating: 0
ProSystem fx Engagement has 1 inventory records, 0 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (2)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 0 / 5 (Not Rated) based on 0 ratings
Most Commonly Reported Deployment Method
Not Determined
or cancel
0
Note
Information pulled from "Administrator's Guide to Pushing Engagement MSI Installation v 6.5.pdf"

Deploying ProSystem fx Engagement across computers in a domain
Overview

This document will help you deploy (or push) ProSystem fx Engagement across multiple computers in a
network using Active Directory. A Microsoft Windows Server, with Microsoft Active Directory, may be used
to push the SQL Express 2005 instance and the Engagement installation package to computers in a domain.

When these computers are rebooted, SQL Express 2005 and Engagement Workpaper Management will be
installed automatically. (Note: For additional information on Active Directory, please refer to your Microsoft
operating system documentation.)

For computers that have a prior version of ProSystem fx Engagement installed, pushing SQL Express 2005 is
not required, since those machines already have the Engagement SQL database instance. ProSystem fx
Engagement version 5.5 and higher are supported when upgrading the program.

Preparation

Before starting, please make sure that all computers to which Engagement will be deployed meet the following
requirements and have the following components installed:

1) Must be part of the Windows domain
2) Microsoft .NET Framework version 3.5 SP 1
3) SQLXML 3.0 SP3 for computers running Engagement Admin and WM
4) SQLXML 4.0 SP1 for computers running Engagement WM
5) Microsoft Windows Installer Version 3.1 for SQL 2005
6) Microsoft SQL Server System CLR Types (32 bit)
7) Microsoft SQL Server 2008 Management Objects (32 bit)
8) Microsoft SQL Server 2008 Native Client (32 or 64 bit, depending on the operating system)
9) Microsoft Visual C++ 2008 Redistributable x86 9.0.30729.17
10) Microsoft Visual C++ 2008 Redistributable x86 9.0.30729.4148
11) If Office 2003 SP 1 or higher is installed, then install the following which is located on the CD:
a. Visual Studio 2005 Tools for Office Second Edition Runtime (VSTOR)
Note: This component may be installed from the Applications\Knowledge Tools Prerequisites
folder on the installation CD. However, it may not be pushed to machines.
12) If Office 2007 is installed, then install the following which are located on the CD:
a. Office 2007 Primary Interop Assemblies (PIA)
b. Visual Studio Tools for the Office System Runtime version 3.0
c. Visual Studio Tools for the Office System 3.0 Runtime SP1
13) Knowledge Tools requirements:
a. Microsoft Office 2003 Professional with Service Pack 2
i. Microsoft Office 2003 Primary Interop Assemblies (PIA)
ii. Visual Studio 2005 Tools for Office Second Edition Runtime (VSTOR)
Note: These two components may be installed from the Applications\Knowledge Tools
Prerequisites folder on the installation CD. However, they may not be pushed to machines.
b. Microsoft Office 2007
i. Microsoft Office 2007 Primary Interop Assemblies (PIA)
ii. Visual Studio 2005 Tools for Office Second Edition Runtime (VSTOR)
Note: These two components may be installed from the Applications\Knowledge Tools
Prerequisites folder on the installation CD. However, they may not be pushed to machines.
14) Knowledge Coach requirements:
a. Microsoft Windows Vista with Service Pack 2.
b. Microsoft Windows Server 2008 with Service Pack 2.
c. Microsoft Office 2007
i. Microsoft Office 2007 Primary Interop Assemblies (PIA)
ii. Visual Studio Tools for the Office System Runtime version 3.0
iii. Visual Studio Tools for the Office System 3.0 Runtime SP1
Note: These components may be installed from the Applications\KC folder on the installation
CD. However, they may not be pushed to machines.
6
15) Machines must also meet the minimum requirements for ProSystem fx Engagement installation. Please
refer to the Installation Guide for these requirements located on the installation CD in the Documents
folder.



Important Notes

? Deployment of ProSystem fx Engagement using Active Directory is supported for
all international versions.

? Deploying ProSystem fx Engagement across computers in a domain is a two step
process that may require two separate pushes. For new installations, a separate
push will be required to install a new SQL Express 2005 instance. The second
push will be to install ProSystem fx Engagement Workpaper Management.

? Although an MSI file is provided which can be used to push the installation of
SQL Express 2005, Microsoft does not support this method. The Microsoft SQL
Express 2005 setup itself consists of multiple MSI installation files. Due to
limitations with the Windows Installer, only one MSI file can be active at a time on
a machine. The Active Directory deployment process cannot properly detect the
processing status of the SQL Express 2005 MSI files, so its behavior is
unpredictable. The only way to avoid this issue is to deploy the SQL Express 2005
installation, and wait until all processing has completed on all machines before
deploying the Engagement Workpaper Management installation. This may take
30 minutes or more.

? ProSystem fx Engagement supports either SQL Express 2005 or SQL Express
2008. Due to new limitations of the Microsoft SQL Express 2008 installer, it is not
possible to use Active Directory to push the installation of SQL Express 2008. You
may continue to install and use SQL Express 2005 with the steps provided in this
document.


Pushing SQL 2005 Express and ProSystem fx Engagement

Once all of the above requirements have been met, follow the instructions below to push SQL Express 2005 and
ProSystem fx Engagement Workpaper Management across computers in a network, which are part of the
domain, using Active Directory.


1) Log into a Microsoft Windows Server 2003 or Windows Server 2008.

2) Copy the ProSystem fx SQL 2005 Instance Installer.msi package from the installation CD to a shared
folder on the server?s local drive. Make sure the security settings for this folder list Domain Computers with
Full Control.

3) Copy the ProSystem fx Engagement.msi package from the installation CD to a shared folder on the
server?s local drive. Make sure the security settings for this folder list Domain Computers with Full Control.

4) From the server, select Start, then All Programs, Administrative Tools and Active Directory Users and
Computers.

5) Active Directory Users and Computers screen is displayed.

6) Right-click on the domain and select New, followed by Organizational Unit (Note: If you already have an
Organizational Unit created under your domain which you will use here, skip to step 8.)

7) Enter a name for your Organizational Unit and click OK.

8) Under your domain, there is a folder called „Computers?. Highlight this folder which will display the list of
all computers in this domain.

9) Highlight the computer(s) that you wish to deploy SQL Express and Engagement installation package to.

10) Right-click and select Move

11) In the screen displayed, select the Organizational Unit that you had created in Step 7 and click OK. This
will move all of the selected computers to your Organizational Unit.

12) Right-click on your Organizational Unit and select Properties.

13) In the Properties dialog, select the Group Policy tab.

14) Click New which will add an entry in the Group Policy Object Links pane. You may rename the new entry
or use the default name.

15) With this entry highlighted, click Edit. This will display the Group Policy Object Editor screen.

16) Under Computer Configuration, expand the Software Settings folder by clicking on the + icon. Under
Software Settings folder, right-click on Software installation and select New followed by Package.

17) Browse to the location of the ProSystem fx SQL 2005 Instance Installer.msi package that was copied to
the server?s local drive. Highlight the file and click Open. (Note: When browsing to the location of the
installation package, you must use a UNC path.)

18) In the next screen, select the Assigned option if not already selected. Click OK to continue.

19) Wait a few seconds until the ProSystem fx SQL2005 Instance Installer.msi package displays under
Software installation. The SQL Express installation package has now been assigned to all the computers
that were selected earlier.

20) Wait a few minutes and then reboot all computers that were selected for installation. SQL 2005Express will
be installed automatically on these machines at start-up. A screen will display showing the message
”Installing managed software Engagement SQL Express Instance”. On Vista operating systems ”Please
Wait” will display while the application is being installed.

Note: Once the SQL 2005 Express instance push has started, verify that the installation is complete before
proceeding with the ProSystem fx Engagement push. You may verify the installation of SQL Express with
the following steps:

a. Select Start / Run
b. Type “services.msc” and click OK
c. In the list of services, look for an item called “SQL Server (PROFXENGAGEMENT)”
d. Confirm that the Status column shows “Started”

Note: Some computers may take longer than others to receive the SQL Express and ProSystem fx
Engagement packages. If rebooting the computer does not install the application, reboot the computer again
after a few more minutes.

21) After verifying that the SQL 2005 Express instance install has completed, open the Group Policy created for
the SQL 2005 Express installation.

22) In the Group Policy Object Editor under Computer Configuration, expand the Software Settings folder by
clicking on the + icon. Under Software Settings folder, right-click on Software installation and select New
followed by Package.

23) Browse to the location of ProSystem fx Engagement.msi package that was copied to the server?s local
drive. Highlight the file and click Open. (Note: When browsing to the location of the installation package, you
must use a UNC path.)

24) On the next screen select the Assigned option if not checked by default.

25) Wait a few seconds until the ProSystem fx Engagement.msi package displays under Software
Installation. The ProSystem fx Engagement package has now been assigned to all the computers that were
selected earlier.

26) Wait a few minutes and then reboot all computers that were selected for installation. ProSystem fx
Engagement will be installed automatically on these machines at start-up; a screen will display showing the
message „Installing managed software ProSystem fx Engagement’. On Vista operating systems ‘Please Wait’
will display while the application is being installed.

If you have a previous version of Engagement installed on any of these computers and are upgrading, all
Engagement modules will be upgraded simultaneously. In addition, SQL databases will be converted by the
Engagement upgrade installation. Converting Trial Balances is a separate process. Please see the ProSystem
fx Engagement Conversion Guide for additional details.


If no prior version of Engagement exists on a computer, then ONLY the SQL Express 2005 instance and
ProSystem fx Engagement Workpaper Management module (including Trial Balance) with knowledge Tools
will be installed.

Note: It is possible to use the push installation to modify an existing installation to include the newly released
Knowledge Coach components. Please contact technical support for the appropriate MSI transform file if you
have a need to push the Knowledge Coach installation.

Note: The SQL 2005 Express instance must be pushed separately as the SQL instance must be installed prior to
the ProSystem fx Engagement installation.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note
Information pulled from "Administrator's Guide to Pushing Engagement MSI Installation v 6.5.pdf"

Deploying ProSystem fx Engagement across computers in a domain
Overview

This document will help you deploy (or push) ProSystem fx Engagement across multiple computers in a
network using Active Directory. A Microsoft Windows Server, with Microsoft Active Directory, may be used
to push the SQL Express 2005 instance and the Engagement installation package to computers in a domain.

When these computers are rebooted, SQL Express 2005 and Engagement Workpaper Management will be
installed automatically. (Note: For additional information on Active Directory, please refer to your Microsoft
operating system documentation.)

For computers that have a prior version of ProSystem fx Engagement installed, pushing SQL Express 2005 is
not required, since those machines already have the Engagement SQL database instance. ProSystem fx
Engagement version 5.5 and higher are supported when upgrading the program.

Preparation

Before starting, please make sure that all computers to which Engagement will be deployed meet the following
requirements and have the following components installed:

1) Must be part of the Windows domain
2) Microsoft .NET Framework version 3.5 SP 1
3) SQLXML 3.0 SP3 for computers running Engagement Admin and WM
4) SQLXML 4.0 SP1 for computers running Engagement WM
5) Microsoft Windows Installer Version 3.1 for SQL 2005
6) Microsoft SQL Server System CLR Types (32 bit)
7) Microsoft SQL Server 2008 Management Objects (32 bit)
8) Microsoft SQL Server 2008 Native Client (32 or 64 bit, depending on the operating system)
9) Microsoft Visual C++ 2008 Redistributable x86 9.0.30729.17
10) Microsoft Visual C++ 2008 Redistributable x86 9.0.30729.4148
11) If Office 2003 SP 1 or higher is installed, then install the following which is located on the CD:
a. Visual Studio 2005 Tools for Office Second Edition Runtime (VSTOR)
Note: This component may be installed from the Applications\Knowledge Tools Prerequisites
folder on the installation CD. However, it may not be pushed to machines.
12) If Office 2007 is installed, then install the following which are located on the CD:
a. Office 2007 Primary Interop Assemblies (PIA)
b. Visual Studio Tools for the Office System Runtime version 3.0
c. Visual Studio Tools for the Office System 3.0 Runtime SP1
13) Knowledge Tools requirements:
a. Microsoft Office 2003 Professional with Service Pack 2
i. Microsoft Office 2003 Primary Interop Assemblies (PIA)
ii. Visual Studio 2005 Tools for Office Second Edition Runtime (VSTOR)
Note: These two components may be installed from the Applications\Knowledge Tools
Prerequisites folder on the installation CD. However, they may not be pushed to machines.
b. Microsoft Office 2007
i. Microsoft Office 2007 Primary Interop Assemblies (PIA)
ii. Visual Studio 2005 Tools for Office Second Edition Runtime (VSTOR)
Note: These two components may be installed from the Applications\Knowledge Tools
Prerequisites folder on the installation CD. However, they may not be pushed to machines.
14) Knowledge Coach requirements:
a. Microsoft Windows Vista with Service Pack 2.
b. Microsoft Windows Server 2008 with Service Pack 2.
c. Microsoft Office 2007
i. Microsoft Office 2007 Primary Interop Assemblies (PIA)
ii. Visual Studio Tools for the Office System Runtime version 3.0
iii. Visual Studio Tools for the Office System 3.0 Runtime SP1
Note: These components may be installed from the Applications\KC folder on the installation
CD. However, they may not be pushed to machines.
6
15) Machines must also meet the minimum requirements for ProSystem fx Engagement installation. Please
refer to the Installation Guide for these requirements located on the installation CD in the Documents
folder.



Important Notes

? Deployment of ProSystem fx Engagement using Active Directory is supported for
all international versions.

? Deploying ProSystem fx Engagement across computers in a domain is a two step
process that may require two separate pushes. For new installations, a separate
push will be required to install a new SQL Express 2005 instance. The second
push will be to install ProSystem fx Engagement Workpaper Management.

? Although an MSI file is provided which can be used to push the installation of
SQL Express 2005, Microsoft does not support this method. The Microsoft SQL
Express 2005 setup itself consists of multiple MSI installation files. Due to
limitations with the Windows Installer, only one MSI file can be active at a time on
a machine. The Active Directory deployment process cannot properly detect the
processing status of the SQL Express 2005 MSI files, so its behavior is
unpredictable. The only way to avoid this issue is to deploy the SQL Express 2005
installation, and wait until all processing has completed on all machines before
deploying the Engagement Workpaper Management installation. This may take
30 minutes or more.

? ProSystem fx Engagement supports either SQL Express 2005 or SQL Express
2008. Due to new limitations of the Microsoft SQL Express 2008 installer, it is not
possible to use Active Directory to push the installation of SQL Express 2008. You
may continue to install and use SQL Express 2005 with the steps provided in this
document.


Pushing SQL 2005 Express and ProSystem fx Engagement

Once all of the above requirements have been met, follow the instructions below to push SQL Express 2005 and
ProSystem fx Engagement Workpaper Management across computers in a network, which are part of the
domain, using Active Directory.


1) Log into a Microsoft Windows Server 2003 or Windows Server 2008.

2) Copy the ProSystem fx SQL 2005 Instance Installer.msi package from the installation CD to a shared
folder on the server?s local drive. Make sure the security settings for this folder list Domain Computers with
Full Control.

3) Copy the ProSystem fx Engagement.msi package from the installation CD to a shared folder on the
server?s local drive. Make sure the security settings for this folder list Domain Computers with Full Control.

4) From the server, select Start, then All Programs, Administrative Tools and Active Directory Users and
Computers.

5) Active Directory Users and Computers screen is displayed.

6) Right-click on the domain and select New, followed by Organizational Unit (Note: If you already have an
Organizational Unit created under your domain which you will use here, skip to step 8.)

7) Enter a name for your Organizational Unit and click OK.

8) Under your domain, there is a folder called „Computers?. Highlight this folder which will display the list of
all computers in this domain.

9) Highlight the computer(s) that you wish to deploy SQL Express and Engagement installation package to.

10) Right-click and select Move

11) In the screen displayed, select the Organizational Unit that you had created in Step 7 and click OK. This
will move all of the selected computers to your Organizational Unit.

12) Right-click on your Organizational Unit and select Properties.

13) In the Properties dialog, select the Group Policy tab.

14) Click New which will add an entry in the Group Policy Object Links pane. You may rename the new entry
or use the default name.

15) With this entry highlighted, click Edit. This will display the Group Policy Object Editor screen.

16) Under Computer Configuration, expand the Software Settings folder by clicking on the + icon. Under
Software Settings folder, right-click on Software installation and select New followed by Package.

17) Browse to the location of the ProSystem fx SQL 2005 Instance Installer.msi package that was copied to
the server?s local drive. Highlight the file and click Open. (Note: When browsing to the location of the
installation package, you must use a UNC path.)

18) In the next screen, select the Assigned option if not already selected. Click OK to continue.

19) Wait a few seconds until the ProSystem fx SQL2005 Instance Installer.msi package displays under
Software installation. The SQL Express installation package has now been assigned to all the computers
that were selected earlier.

20) Wait a few minutes and then reboot all computers that were selected for installation. SQL 2005Express will
be installed automatically on these machines at start-up. A screen will display showing the message
”Installing managed software Engagement SQL Express Instance”. On Vista operating systems ”Please
Wait” will display while the application is being installed.

Note: Once the SQL 2005 Express instance push has started, verify that the installation is complete before
proceeding with the ProSystem fx Engagement push. You may verify the installation of SQL Express with
the following steps:

a. Select Start / Run
b. Type “services.msc” and click OK
c. In the list of services, look for an item called “SQL Server (PROFXENGAGEMENT)”
d. Confirm that the Status column shows “Started”

Note: Some computers may take longer than others to receive the SQL Express and ProSystem fx
Engagement packages. If rebooting the computer does not install the application, reboot the computer again
after a few more minutes.

21) After verifying that the SQL 2005 Express instance install has completed, open the Group Policy created for
the SQL 2005 Express installation.

22) In the Group Policy Object Editor under Computer Configuration, expand the Software Settings folder by
clicking on the + icon. Under Software Settings folder, right-click on Software installation and select New
followed by Package.

23) Browse to the location of ProSystem fx Engagement.msi package that was copied to the server?s local
drive. Highlight the file and click Open. (Note: When browsing to the location of the installation package, you
must use a UNC path.)

24) On the next screen select the Assigned option if not checked by default.

25) Wait a few seconds until the ProSystem fx Engagement.msi package displays under Software
Installation. The ProSystem fx Engagement package has now been assigned to all the computers that were
selected earlier.

26) Wait a few minutes and then reboot all computers that were selected for installation. ProSystem fx
Engagement will be installed automatically on these machines at start-up; a screen will display showing the
message „Installing managed software ProSystem fx Engagement’. On Vista operating systems ‘Please Wait’
will display while the application is being installed.

If you have a previous version of Engagement installed on any of these computers and are upgrading, all
Engagement modules will be upgraded simultaneously. In addition, SQL databases will be converted by the
Engagement upgrade installation. Converting Trial Balances is a separate process. Please see the ProSystem
fx Engagement Conversion Guide for additional details.


If no prior version of Engagement exists on a computer, then ONLY the SQL Express 2005 instance and
ProSystem fx Engagement Workpaper Management module (including Trial Balance) with knowledge Tools
will be installed.

Note: It is possible to use the push installation to modify an existing installation to include the newly released
Knowledge Coach components. Please contact technical support for the appropriate MSI transform file if you
have a need to push the Knowledge Coach installation.

Note: The SQL 2005 Express instance must be pushed separately as the SQL instance must be installed prior to
the ProSystem fx Engagement installation.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

ProSystem fx Engagement

Version

6.5

Uninstall String

MsiExec.exe /I{21E3A0C7-DC15-4329-B58A-7A46B51B5A0A}

Questions & Answers (0)

Questions & Answers related to CCH Tax and Accounting. A WoltersKluwer Company ProSystem fx Engagement

Blogs (0)

Blog posts related to CCH Tax and Accounting. A WoltersKluwer Company ProSystem fx Engagement

Reviews (0)

Reviews related to CCH Tax and Accounting. A WoltersKluwer Company ProSystem fx Engagement