- Message Boards
- Package KB
- Software KB
- Free Videos
- MSI Errors
- Tools
- Tech Home Pages
- Reviews
- Downloads
- Articles
- FAQs
- Tips & Tricks
- Services
- News
- Newsletter
Search AppDeploy
Arc Connect Console Operator 5.x
| Company: | Arc Solutions |
| Setup Type: | Native Windows Installer setup (MSI) |
| Package Difficulty Rating: | TBD [ Rate It or View Ratings ] |
| Most Commonly Reported Method: | not yet established |
| Record Created On: | 3/1/2010 |
| Number of Views: | 562 |
Software Knowledge Base: The software knowledge base contains details on over 60,000. The closest record matching this software package is displayed here. Browse the Software KB directly to find similar records.
Software Knowledge Base
Software Knowledge BaseNo record in the Software KB was found to match this package.
Command Lines: Command line details for installation and removal of this software. Details may include available command line arguments and/or public properties.
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.
| Clear out your %temp% directory, and keep it open so you can see any newly created directories. Grab OPR_Setup.exe and double-click it. Copy out the following files as soon as you see them created: Arc Console Operator 5.1 for CUCM.msi (this will be in the first directory created) BDE Utility.msi < this file will automatically install itself (it's the Borland Database Engine Utility). You'll be able to grab this from the third directory that gets created - the second directory is BDE Utility.exe, which then extracts into a third containing the msi. If you're not quick enough, you will need to uninstall BDEUtility.exe, run it again, and it'll uninstall. Run it again, and monitor temp so you can grab it. Once you have that, you can use AdminStudio to create response transforms for both files, but make sure you pass ISSETUPDRIVEN=1 as a property or it'll complain. Once that is done, install the BDEUtility first, and ARCConsole next, using the following: start /w msiexec /i %installsourcepath%\%MSIMSI%.msi ISSETUPDRIVEN=1 ALLUSERS=2 TRANSFORMS=%installsourcepath%\%MSIMSI%.mst REBOOT=ReallySuppress /qn I then use regini.exe to grant permissions to these directories: \Registry\Machine\Software\Arc Solutions\Call Connect [1 5 7 17] \Registry\Machine\Software\Arc Solutions\Call Connect\Defaults [1 5 7 17] \Registry\Machine\Software\Arc Solutions\Call Connect\Operator [1 5 7 17] \Registry\Machine\Software\Arc Solutions\Call Connect\Operator\Defaults [1 5 7 17] \Registry\Machine\Software\Arc Solutions\Call Connect\Operator\Logging [1 5 7 17] \Registry\Machine\Software\Arc Solutions\Call Connect\Operator\Preferences [1 5 7 17] \Registry\Machine\Software\Arc Solutions\Call Connect\Operator\Version [1 5 7 17] And finally, create the ODBC connection: [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Call Connect Cfg DB] "Driver"="C:\\WINNT\\system32\\SQLSRV32.dll" "Server"="NAMEOFARCSERVERGOESHERE" "Database"="ArcConfigDB" "LastUser"="arcserviceaccountnamegoesherebutmaynotevenbenecessary" [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources] "Call Connect Cfg DB"="SQL Server" | ||||
| Above Entry Provided on 3/2/2010 by nzdude | Rate It | Rating 0 | ||
Virtualization: Information regarding how to work with this software in creating a virtual deployment package for products like Altiris SVS and Microsoft SoftGrid.
Terminal Services: Notes on how to address problems working with this software in a Terminal Services session as with Citrix shared environments.
Related Links: Additional resources to reference in regards to the deployment and configuration of this software.
Security Information: Details covering which files, directories and/or registry entries must be opened to standard users for operation in a locked down environment.
Discussion threads: Discussion topics in the AppDeploy message boards that have been linked as relevant information to this entry.
