AssetWise Performance Management. APM Remote Upgrade Guide

Transcription

1 AssetWise Performance Management APM Remote Upgrade Guide

2 Trademark Notice Bentley, the B Bentley logo, AssetWise, Ivara, the Ivara EXP logo, Ivara Work Smart, Aladon and RCM2 are either registered or unregistered trademarks or service marks of Bentley Systems, Incorporated or one of its direct or indirect wholly owned subsidiaries. All other brands and product names are trademarks of their respective owners. Copyright Notice Copyright 2014, Bentley Systems, Incorporated. All Rights Reserved. Including software, file formats, and audiovisual displays; may only be used pursuant to applicable software license agreement; contains confidential and proprietary information of Bentley Systems, Incorporated and/or third parties which is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization. For reference, a copy of the End User License Agreement named EULA.pdf is installed in the same folder as the product. Corporate Headquarters Bentley Systems, Incorporated 685 Stockton Drive Exton, PA USA Phone: (1) Fax: (1) International Headquarters Bentley Systems International Limited Second Floor, Block 2, Park Place Upper Hatch Street Dublin 2 Ireland Phone: Fax: Asia Headquarters Bentley Engineering Software Systems Unit , Tower 1 China Central Place, Beijing China Phone: (86) Fax: (86) APM Remote Upgrade Guide Published April 2014 APM Release APM Remote Upgrade Guide

3 Contents Upgrading APM Remote Introduction to Upgrading APM Remote APM Remote Client Prerequisites Generate SQL Statements for Download Packages Upgrade APM Remote Software Upgrade the Master APM Remote Database Upgrade an Instance or a Database? Upgrade Wizard Log Files Using the APM Upgrade Wizard Package the APM Remote Software and Database APM Remote Packager: Input and Output Deployment Options Automatic Updates Setting up Access on a Shared Folder Creating an APM Remote Installer Using Uninstall.exe to Remove the APM Remote Software APM Remote Upgrade Guide 3

4 Contents 4 APM Remote Upgrade Guide

5 This guide explains how to upgrade to version 7.2 of APM Remote. Note: You can upgrade to APM Remote 7.2 from version or 7.1. If you are running an earlier version, you must upgrade to one of these before moving to 7.2. See the APM Readme file and APM Remote Upgrade Guide for the version that you are upgrading to. APM Remote Upgrade Guide 5

6 Introduction to Upgrading APM Remote Note: Before proceeding with an upgrade to APM and APM Remote, we recommend that you upload all outstanding transactions for all APM Remote clients. This will prevent problems that can occur if you upload transactions from an older version of an APM Remote client to an upgraded APM master database. As of version 7, all custom attributes on APM Remote are truncated to 2000 characters. This change was driven by the conversion of the APM Remote database to Unicode. Before upgrading, analyze your APM customizations to identify string attributes with lengths over The previous limit was If any of these attributes are downloaded to APM Remote, they will have to be either truncated or converted to an HTML string data type. If you need assistance, contact APM Technical Services or Support. Before beginning the upgrade process for APM Remote, upgrade APM and the APM database on the computer that hosts the synchronization service provider. For complete instructions, as well as information about upgrading customizations, see APM Upgrade Guide. Upgrading APM Remote involves these steps: Generate SQL Statements for Download Packages on page 8 In APM, generate the SQL statements for all download packages to ensure that they are ready to download. Upgrade APM Remote Software on page 8 Upgrade your master copy of the APM Remote software. Upgrade the Master APM Remote Database on page 10 Use the APM Upgrade Wizard to upgrade your database to the current version. You can then create a backup of the master database to include in the package for deployment to client computers. Package the APM Remote Software and Database on page 18 When you have tested and are satisfied with the master configuration, you can create an installation utility and deploy the upgrade to client computers. When you install the APM Remote software, reports are included that list the object model and user interface differences between the current version of the base product and all previous versions that you can 6 APM Remote Upgrade Guide

7 upgrade from. The reports take the form of text files located in the directory <InstallDirectory>Bentley\AssetWise Performance Management Remote\Upgrade Difference Reports. For information about using the APM Database Difference Tool to compare customizations in two databases, see APM Upgrade Guide. APM Remote Client Prerequisites Laptop or tablet computers running APM Remote require the following. Minimum Recommended CPU Multi-core Memory 1 GHz or better 1 GB Display Resolution 1024 x 728 Operating System Windows 7 Database Software 1 Microsoft SQL Server 2008 R2 Express or Microsoft SQL Server 2012 Express Other Software Microsoft.NET Framework 4.5 (plus the latest patches) is required for client computers 2 Microsoft Excel 2007 or 2010 is required for exporting checksheets, tables, and so on 1. If supported database software is not present on the computer, the APM Remote install utility prompts the user. With the user s confirmation, the utility downloads and installs Microsoft SQL Server 2012 Express. 2. If Microsoft.NET is not present on the computer, the APM Remote install utility prompts the user. With the user s confirmation, the utility downloads and installs Microsoft.NET. APM Remote Upgrade Guide 7

8 Generate SQL Statements for Download Packages After you have upgraded APM and the APM database on the computer that hosts the synchronization service provider, generate the SQL statements for all download packages. To Generate SQL Statements for Download Packages 1. Open APM and the site window. Select the Mobile Computing view and the Remote Computing tab. 2. Select the Download Packages tab. 3. Select all of the download packages in the list and click Generate SQL. The SQL statements for the download packages are refreshed, ready to be downloaded. Upgrade APM Remote Software Once APM has been upgraded on the computer hosting the synchronization service provider, you are ready to upgrade the master copy of APM Remote software, which will be packaged and deployed to client computers. APM includes a single installation package for both upgrades and new installations. The APM installation zip file contains a Setup executable that takes you through the process of upgrading or installing the APM Remote software. It also places the Remote Install database on the computer. Note: When you are installing APM Remote, you must be logged on to the computer as an administrator. To Upgrade APM Remote Software 1. Make a backup copy of your current APM Remote master database. 2. Download the AssetWise Performance Management Remote product from Bentley SELECTservices. 3. Double-click the downloaded.exe file to extract the files to a temporary folder, for example, in C:\BentleyDownloads. The extraction wizard launches the Setup.exe and the InstallShield Wizard appears. 4. In the Welcome window, click Next. The License Agreement page appears. When you have accepted the terms of the license agreement, the Next button is available. 8 APM Remote Upgrade Guide

9 5. Click Next. The Destination Folder page appears. 6. If you wish to change the directory in which APM Remote will be installed, click Change. Select a new location and click OK. 7. Click Next. The Ready to Install page appears. 8. Click Install. The Installing APM Remote page appears, showing a progress bar and naming the components as they are copied to the destination. Note: If Remote Auto Synchronize is enabled and detects updates to be installed, a window will appear informing the user that the updates are being installed. 9. When the installation is finished, the Completed page appears. APM Remote Upgrade Guide 9

10 10. Click Finish. Upgrade the Master APM Remote Database The APM Upgrade Wizard allows you to select a target to upgrade and provides a list of the steps in the upgrade process, as well as a description of each step. Some steps are optional, such as cleaning up obsolete columns, and you can select or deselect them as required. The upgrade target can be an instance (and the database it references) or a database alone. Note: The target instance or database must have a valid ODBC data source so that the Upgrade Wizard can access the database. As the upgrade process executes, the wizard displays the progress and results. You can pause and resume the upgrade as required. You can also save the upgrade project to an APM Upgrade Results file (with the suffix *.ivup). The project can then be re-opened in the Upgrade Wizard (on the File menu, click Open Upgrade Results) so that you can review the results or complete an unfinished upgrade. You can also save the results page from the wizard to a file or copy it to the clipboard and paste it into a document of your choice. Upgrade an Instance or a Database? Note: The Upgrade Wizard converts databases that use ANSI encoding to Unicode. The Prepare String Columns for Unicode step in the wizard detects and truncates large string columns down to a maximum of 2000 characters for Unicode implementation. Any data that is truncated as a result of this step is reported in the wizard and the log file. You can use the APM Upgrade Wizard to update a remote instance and its database, or to update a database alone. We advise upgrading an instance so that the following upgrade steps are available: Delete Custom Cache This step removes the CustomerData and Package folders located in the cache folder. Test the Instance This step performs several tests on the target instance and provides the option of launching APM Configuration, if you need to modify the instance and retry the test. 10 APM Remote Upgrade Guide

11 Upgrade Wizard Log Files From the Upgrade Wizard, you can open APM Configuration to create or modify an instance, which you can then select to upgrade. At minimum, the instance must identify the data source name (DSN) and the path to the cache files. The Upgrade Wizard generates a log file, as well as showing information about the upgrade on the Summary page. To view the log files, select the Help menu and click Log File Location(s). Windows Explorer opens to the directory where the log files are stored. Using the APM Upgrade Wizard When you have updated your database, backed up your data, and installed the APM Remote software, you are ready to upgrade the database to the new version. The Upgrade Wizard steps you through this process. To Upgrade Your Database 1. On the Start menu, click Bentley, APM Remote, and then APM Upgrade Wizard. The Upgrade Wizard window appears. Tip: You can also start the Upgrade Wizard from APM Configuration. Select the instance that you wish to upgrade, click the Installation list, and then click Upgrade Wizard. The wizard opens to the Select Instance to Upgrade page and displays the instance you selected in APM Configuration. APM Remote Upgrade Guide 11

12 2. Select a target type. If you select an instance, its settings and the database it references are both updated. Note: The target instance or database must have a valid ODBC data source so that the Upgrade Wizard can access the database. You can click Configure APM Remote to create or check an instance. 3. Click. Do one of the following, depending on your previous choice: If you are upgrading an instance, the Select Instance to Upgrade page appears. In the Type list, select Remote. Select the instance name. Information is added to the page about the source, database type, version, target instance, and data source name, and encoding. For example: 12 APM Remote Upgrade Guide

13 If you are upgrading a database, the Select Database to Upgrade page appears. Select the data source name and enter the user name and password to access the database. Click Connect. Information is added to the page about the source, database type, and version. For example: 4. Click. Note: If the user does not have SysAdmin server role, a page appears asking you for an account with elevated credentials. Enter the user and password and click Connect. Alternatively, the SA login can be used to perform the upgrade. These elevated credentials are required to run the init_remote.sql script. 5. Click. The next page shows the upgrade steps. Click a step to view a description of it at the bottom of the page. For example: APM Remote Upgrade Guide 13

14 Note: If you are upgrading a database alone, some steps are not available to you such as testing the selected instance. The icons indicate whether a step is mandatory (grey) or optional and whether it is selected or un-selected: Icon Description Mandatory, selected (cannot be un-selected) Mandatory, not selected (cannot be selected) Optional, selected 14 APM Remote Upgrade Guide

15 Icon Description Optional, not selected 6. Review and change the selections, as required. 7. Click. The next page shows the upgrade steps. Once the upgrade process begins, progress is shown on this page. 8. Click Begin Upgrade. A message appears to remind you that the target database should be backed up before upgrading. Click Yes. As the upgrade progresses, completed steps are marked and the results shown. For example: Tip: You can click Pause to stop the process temporarily. In some cases, the current step must be completed before the upgrade can be paused. When the upgrade stops, a message appears to inform you that the upgrade has been paused. To resume, click Begin Upgrade. APM Remote Upgrade Guide 15

16 9. If you selected the Pause upgrade step, the process stops when it gets to that step. Click. The Upgrade Results Summary page appears, showing the status Paused by Step. When you are ready to resume, return to the Results page and click Continue Upgrade. Note: If an error occurs during the upgrade process, the upgrade might stop automatically, depending on the step that is executing. In some cases, a message appears asking whether you wish to continue or stop the upgrade. If you choose to continue, the process resumes. When it is completed, the Results Summary page shows the status Completed with Error. If you choose to stop the upgrade process or it stops automatically, no additional steps are processed. The Results Summary page shows the status Failed with Error. You can click the Help menu and then Log File Location(s) to open Windows Explorer to the directory where log files are stored. 10. If you selected Test the selected instance, while testing is in progress, the Results column displays any warnings or errors that occur. A message might appear offering to launch APM Configuration. You can make changes to the instance and resume testing. 11. When the upgrade process completes, a message informs you. Click. The Upgrade Wizard Summary page appears. For example: 16 APM Remote Upgrade Guide

17 This example shows that the upgrade of an instance completed with one or more warnings. After reviewing the results summary, you can return to the previous page and click Retry Unsuccessful Steps. 12. You can save the results in these ways: Click Save As to save the results summary as a text or html file. Click Copy to Clipboard to select the results summary and copy it to the clipboard. You can then paste the text into the document of your choice. 13. When you are finished, save the upgrade project. Click to open the Save As window, where you can select a location and enter a name for the project. The APM Upgrade Project file is saved with the suffix.ivup. APM Remote Upgrade Guide 17

18 Tip: To reopen the project in the wizard, click the File menu and then Open Upgrade Results. 14. Close the APM Upgrade Wizard window. When you have finished upgrading your database, create a backup of it. Package the APM Remote Software and Database This section explains how to use the APM Remote Packager to create an installer for deploying the APM Remote software and database to client computers. It also describes the update process and the files involved. Before packaging the master APM Remote configuration, ensure that: All customizations are complete and tested and cache files have been generated. Default window positions, banners, and so on have been set as required in the master APM Remote software. Remote users and employee records are set up in the master Remote database. APM Remote Packager: Input and Output The APM Remote Packager gathers the following components: Binary files APM Remote database Cache files Any custom components Prerequisites required to run APM Remote: Microsoft Visual C Redistributable Package (x86) Microsoft SQL Server 2008 R2 Express Microsoft SQL Server 2012 Express Microsoft.NET Framework 4.5 The prerequisite software is installed and configured automatically if any of the components are missing on the client computer. Note: For SQL 2008 R2 Express installations, the packaged installer will automatically install SQL Server 2008 R2 Express if not previously installed on the remote computer. 18 APM Remote Upgrade Guide

19 Deployment Options Note: For installations where SQL Server 2008 R2 Express or SQL Server 2012 Express is already installed, the server s SQL authentication must be in SQL Server and Windows authentication mixed mode otherwise an error will occur. Note: If SQL Server 2012 Express has been installed on the remote computer (not by the packaged installer), SQL authentication must be used for the installation, and the Named instance setting must be defined as SQLExpress. Otherwise, the installer will attempt to re-install 2012 Express and an error will occur. Note: If some remote computers have SQL Server 2008 R2 Express installed and some have 2012 Express, make sure that your master database is 2008 R2 Express. The installer will replace the existing database on the client with the same version of SQL Server Express. The APM Remote Packager creates the following files: IvaraRemoteSetup.exe executable that the user double-clicks to extract and install the software. IvaraRemoteVersion.xml record of the version number. A copy of this file is included in the install and compared to the copy on the update server. If the version on the server contains a more recent version number, an update is available. index.htm simple web page that points to the installer. The user clicks Download to run the installer or to save it to a specified location. Use this file if the install is hosted on a web server. To make the installer available to users, you can have the packager place the IvaraRemoteSetup.exe and IvaraRemoteVersion.xml files on a deployment web server, hosted by the application server. Two settings control the deployment server set up. For the application server instance, the Settings Editor has advanced settings in the Mandatory Settings node: Deployment Folder identifies the location where the deployment server stores deployment files. By default, this option is set to: %programdata%\bentley\ivaraexp\deployment Deployment Port is the port used by the deployment server. By default, the port for the first instance is Alternatively, you can copy the IvaraRemoteSetup.exe and IvaraVersion.xml files to a network file share or your own web server. If you are using a web server, include the index.htm file. APM Remote Upgrade Guide 19

20 Automatic Updates An APM Remote installer includes information that allows updates to be downloaded and installed on client computers. APM Remote checks for updates and, if found, downloads the installer automatically. APM Remote checks for updates in the following situations: Before APM Remote is initialized Before a download when download-only is selected After an upload, when upload-only is selected After an upload when a full synchronization is selected The installer is run in the following situations: Automatically if the APM Remote Synchronization Monitor is running immediately after the update is downloaded Automatically if the user runs the synchronization process immediately after the update is downloaded Among the files that the installer copies is uninstall.exe, an application that removes the APM Remote software. Users can also uninstall the application from the Windows Control Panel, using the uninstall feature. When creating the installer, the URLs for the IvaraRemoteSetup.exe (the installer) and the IvaraRemoteVersion.xml file to enable automatic updating are populated automatically from the chosen server instance. You can also create a client installer for environments with mounted network drives or for network shares. The network path is specified instead of a URL. The IvaraRemoteVersion.xml file contains the version number that is compared to the user s current software. If the user s version is older, the update is triggered. Setting up Access on a Shared Folder IvaraRemoteVersion.xml, IvaraRemoteSetup.exe, and related components can be accessed by client computers from a shared folder. Two scenarios are possible: Remote device is on the domain. This involves sharing a folder and ensuring that the APM Remote domain user has access to the folder. No changes are needed on the device. Remote device is not on the domain. This is more complex because non-domain devices do not have access to domain resources. Even opening the folder s access to everyone will not be sufficient to grant access. The most secure way to achieve this is to set up a restricted user account on the upgrade server that will have read-access to this 20 APM Remote Upgrade Guide

21 folder (and nothing else). Then on each remote computer, you need to set the credentials and make sure they are saved. This can be achieved by either: Browsing to the shared folder, filling in the restricted user name and password and selecting the Save credentials option. Or by running the command below on each unit: cmdkey /add:nameofserver /user:nameofserver\localusername / pass:userspassword For example: Creating an APM Remote Installer cmdkey /add:serverabc /user: serverabc\restrictedivara / pass:restrictedivarapass Note: On the client computer where APM Remote has been installed, a different user can install the RemoteAutoSync service, if required. This user must enter <domain name>\<windows user name> in the Set Service Login dialog and be defined in the APM Remote database on the client computer. After you have created a backup of the database, start the APM Remote Packager tool and select options on each page. You can create client packager projects, save them (with the extension.exprpkg), and reopen them. This makes it easier when you need to update installers. To Create a Client Software Installer 1. Back up the master APM Remote database. Place the remoteinstall.bak file in the following folder: Bentley\AssetWise Performance Management Remote\SQL Server The packager looks in this folder when it adds the database to the install. 2. On the Start menu, click All Programs, Bentley, APM Remote, and then APM Remote Packager. The Remote Packager wizard appears. APM Remote Upgrade Guide 21

22 3. Select the remote instance from the list. This loads the default settings, assigns port numbers, updates URLs, and sets local deployment paths. 4. Click. The Install Information page appears. 22 APM Remote Upgrade Guide

23 5. If necessary, change the default name (APM Remote) in the Install Name box. This name is used as the directory name when installing the software and it is used when creating the folder in the user s Start menu for the icons. The name cannot contain the characters \, /, :, *,?,, <, >, or. Tip: It is good policy to use the same project when packaging the software for an upgrade. When users install the update, the previous version is uninstalled automatically, even if the Install Name has changed. 6. In the Install options, Check Prerequisites is set to True. The packager downloads the software from the Microsoft web site and places them in the deployment folder. The installer gets them from the deployment folder when installing APM Remote on the client computer. Prerequisites include: Microsoft VC++ redistributable file, which installs the runtime components of Visual C++ libraries Microsoft SQL Express Microsoft.NET Framework APM Remote Upgrade Guide 23

24 7. You can specify the shortcuts included in the install. Select Shortcuts and click the browse button to view the collection of shortcuts that are included by default. 8. Select a shortcut to view and set the Shortcut Folder to SetupAnd- Desktop. 9. You can view and adjust other default properties as needed. You can also add, remove, and reorder shortcuts. 10. When you are finished, close the dialog. 11. In the Post-Install settings, the Run Initial Download option is set to True by default to have a download performed as soon as APM Remote is installed on the client computer. Tip: Run Initial Download should be set to True unless the package will be deployed in a situation where the download server will not be accessible. Note: Installation will fail if Run Initial Download is set to True and the auto initialize option Use Machine Name (in the Record Settings window) is set to False. It will also fail if Run Initial Download and Use Machine Name are set to True and the virtual remote computer has not been added in APM with a default download package. 12. In the Services settings, the Install Service option is set to True by default so that the Remote Auto Synchronize service is installed automatically on the client computer. You can either set the option to False or provide the correct user domain, name, and password to run the service on the client computer. The service should be installed using the user name and password of the user that will be running APM Remote interactively. 24 APM Remote Upgrade Guide

25 Note: The rights on the client computer must allow this user to install and run the service. The final packaged APM Remote installer will attempt to add Run As Service permission to the user automatically. 13. Click to open the Record Settings window to adjust and save settings for the instance. Tip: Under Server, the Mandatory Settings contain the Globalization option. Language is set to the language used by the remote instance. You can change this setting for the remote computer by selecting another option in the Language list. 14. Under Remote, click Remote Settings. 15. In the Auto Initialize area, Use Machine Name is set to True by default. This means that, when automatic synchronization is active, the first time that the client computer is docked, the utility attempts to initialize APM Remote and assign it to the remote computer registered in APM that matches the machine name of the client computer. Note: The initial user must have been created in the database for automatic initialization to be successful. APM Remote Upgrade Guide 25

26 Warning: When using the Record Settings window with Advanced options, never enter anything in the Assigned Computer field. If you do, all of your remote computers will be assigned to the same remote computer registered in APM, and unexpected behavior will result. If you blank out this field, all of your previously initialized mobile computers will become un-initialized when the update is installed. You will have to manually re-initialize them. To disable automatic initialization, change Use Machine Name to False. The client computer must be manually initialized before synchronization can occur. Even when the Auto Initialize option is enabled, you can initialize the remote computer manually. The Select Computer dialog appears, and you can choose the mobile computer from the list of those available. 16. Under Mandatory, if the remote instance is using a working APM Server Manager, the Broker Address and Broker Port values are displayed by default. If the Server Manager has not been set up yet, you can enter the information here. 17. Under Mandatory, in the Server URL box, review the path to the synchronization service and the endpoint Synchronize. For example: where <ComputerName> is the name of the computer hosting the synchronization service. Tip: You will find the path in the Settings Editor on the computer hosting the synchronization service. Select the Service Providers node in the Settings tree. In the Remote Web Service settings, the path is shown in the Base Uri of the hosted service box. If the synchronization service does not use the default port (13401), include the port number is included in the path. For example: #>/RemoteService/Synchronize 18. If automatic synchronization is enabled, you can also activate the Force Synchronization feature. When the client computer is connected and idle, the utility attempts to synchronize with the service at the specified interval. For the Force Synchronize Every setting, specify a time span in the format hours:minutes:seconds. 19. Under Client in the Settings pane, click User Interface to define text, color, angle, and font options for the banner. 26 APM Remote Upgrade Guide

27 20. When you are finished, click Save to close the Record Settings window. 21. In the Remote Packager window, click. The Add Files page appears. 22. Use this page to review the files that will be included in the package and to add others if needed. For example, if you have customized APM Remote and generated cache files, add the CustomerData cache folder. You can cancel the selection for optional files that you do not wish to include in the package. Mandatory files, like those in the Core node, cannot be cleared. 23. Use the following methods to add items to the package: To add a child to a node in the tree, right-click the node and click Add Child Component. The Add Component dialog appears, where you can enter a name and click OK. APM Remote Upgrade Guide 27

28 The child node is added to the tree. Tip: To delete any item that you added to the tree, right-click it and select Delete. To add the contents of a folder to a node in the tree, right-click the node and select Add Folder. The Browse for Folder dialog appears. Navigate to and select the folder. When you click OK, the contents of the folder are added to the tree. To add one or more files to a node in the tree, right-click the node and select Add Files. The Open dialog appears, which contains filters for binary files, cache files, and all files. Navigate to the file(s) and select them. When you click OK, the files are added to the tree. 24. Click. The Automatic Update Information page appears. For example: Whenever APM Remote starts up, it checks IvaraRemoteVersion.xml on the server to see if updates are available. The Automatic Update Information page is for creating that file. 28 APM Remote Upgrade Guide

29 25. When an update is available, the client displays a message to inform the user. If you want to change the title of that message box or the message that is displayed, edit the values in the Update Title, Update Text, or both boxes. 26. Select the deployment type: APM Deployment Server The IvaraRemoteSetup.exe and IvaraRemoteVersion.xml files are placed on a standard APM deployment web server hosted by the application server. UNC File Share The IvaraRemoteSetup.exe and IvaraVersion.xml files are placed on a network file share or web server. 27. The Deployment path is the location of the IvaraRemoteVersion.xml and IvaraRemoteSetup.exe files. This tells the client where to look for updates after it is installed. If you are using the APM deployment server, the URL and the local file path are provided in read-only format. If you are using a network share, enter the UNC path in the following format: \\<machine name>\<share name>\ Note: The software version and publish date are entered for you automatically. 28. Click. The next page is blank, but Create Installer is enabled. 29. Click Create Installer. This process can be time-consuming, especially the compression of the image that occurs near the end of the process. The progress is shown in the page and when the process is complete, a message appears. For example: APM Remote Upgrade Guide 29

30 30. Do one of the following: Click Yes to copy the files to the deployment path that you specified in the wizard. If you are using a file share, the Deploy complete message appears. If you are using the deployment server, your web browser opens showing the Install page. For example: 30 APM Remote Upgrade Guide

31 Click No if you are using a different location. A Windows Explorer window opens showing the location of IvaraRemoteSetup.exe in the output folder. You can copy IvaraRemoteSetup.exe and Ivara- RemoteVersion.xml to a network file share. If you are using a web server, copy the contents of the output folder. If errors occurred during the build, they appear in the log window. 31. In the Remote Packager window, click to save the project for the next time that you need to package the client software. In the Save Project File window, navigate to the folder where you wish to store the project and provide a name. The projects are saved with the.exprpkg extension. The next time that you start the Remote Packager, you can open this project. Tip: To view log files generated by the packager, click the Help menu and then Log File Location. The Log File Location window shows the path to the Logs folder. The file name is IvaraRemotePackager_instance.txt, where instance is the name of the instance that you packaged. 32. Close the Remote Packager window. Using Uninstall.exe to Remove the APM Remote Software On the client computer, you can uninstall APM Remote using the uninstall.exe program. APM Remote Upgrade Guide 31

32 To Uninstall APM Remote Software 1. Log off and exit APM Remote. 2. On the Start menu, click All Programs, Bentley, <Install Name>, and then Uninstall APM Remote Client, where <Install Name> is the name specified in the packager. The Uninstall window appears and shows the progress of the uninstall process. For example: 3. Click Close when the process has completed. Note: If you do not log off and exit APM before uninstalling, the utility must reboot the computer to remove locked files. The following message appears: Click Yes to reboot the computer and complete the uninstall process. 32 APM Remote Upgrade Guide