|
| | | Forum Newbie
Group: Forum Members
Last Login: 9/8/2008 4:49:37 PM
Posts: 4, Visits: 12 |
| | Has the .msi installer package been fixed for Point 6.2? It failed validation in 6.1 and 6.1a. Naturally, this meant that I either supply all users with local admin rights to install the updates or (which is what we did), roll it out one-by-one, taking about 3 hours to roll out the latest updates. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 10/1/2008 12:43:12 PM
Posts: 3, Visits: 17 |
| The MSI does appear to function properly when run by itself. The only issue is that, as supplied, I have not yet been able to automate a deployment. If you are to try an install using MSIExec, with the /qb or /qn arguments, the installer errors and states the Account ID is missing. Looking at the MSI in Installshield AdminStudio I haven't found a property that appears to be the Account ID.
To make it a true silent install we need to find a way to specify the Account ID at runtime; Either through the use of an MST, or a command line switch.
Has anyone had any luck using either of these methods?
|
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 10/1/2008 12:43:12 PM
Posts: 3, Visits: 17 |
| After talking to a few people in Calyx support, I believe we've found a solution.
First add the following String values to the "HKLM\SOFTWARE\Calyx Software\Point\User Information" key in registry
Value / Data
User / User Name
Company / Company Name
AccountID / Account ID
After these values are on your workstations, continue your chosen deployment method in which you use a Basic UI or silent install of the MSI.
For example, we've chosen to deploy the MSI through group policy. The same would work for using SMS, Zenworks, etc. |
| |
|
|