|
| | | Forum Newbie
Group: Forum Members
Last Login: 1/3/2008 5:36:58 AM
Posts: 2, Visits: 3 |
| | I am in an environment that cannot allow end users local admin rights so I need a silent installation that can be delivered via SMS. I have created a setup.iss file using the record switch, after installing the package using the iss file when I attempt to launch Point I get an error indicating that saxcom32.dll is missing. I have verified that it does in fact exists in the source cab files. If I manually click through the exact same options that the setup.iss was created with it works fine. So either the iss file is either missing an entry or there may be logic that actually utilizes a variable set by the UI that is not being addressed within the iss file entries. I have pulled the saxcom32.dll out of the cab file and applied it separately after the install and appear to get further but have addional errors that indicate additional files are required. I am looking for someone that may have already encountered this issue to properly adjust the iss file. |
| |
| | | 
Sepal
Group: Moderators
Last Login: Today @ 10:28:02 AM
Posts: 1,183, Visits: 9,260 |
| In the current versions of point we don't support a silent mode install we use that for the netsetup option. The next release will be msi so it will offer a few more options.
Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.  |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 1/3/2008 5:36:58 AM
Posts: 2, Visits: 3 |
| | Thank you for your swift reply. I realize that silent installaions outside of the netsetup process is not supported at this time, but my current situation is as follows I have approx 300+ users scattered throughout the US that have had Point installed with subsequient upgrades all of which are locked down via GP making the netsetup not a choice. Our intent is to provide new systems clean installations through our configuration group until the MSI version is supplied, but have to address the current install base. If I could get enough informational assistance to get the iss file operational enough at minimum to allow scripting the configuration portion this would allow us to update the field until the next release comes out or they are replaced through attrition by the configuration group. Do you know what feature, ini setting, or UI response triggers the installation component that supplies the saxcom32.dll? Thank You |
| |
| | |
Sepal
Group: Moderators
Last Login: Today @ 10:28:02 AM
Posts: 1,183, Visits: 9,260 |
| Point's install will flip it out of silent mode( this is for netadmin client install mode reasons). I don't think it will read the iss file. You can configure a network admin install. and leave the config.ini file in the same directory as setup.exe( installer) then when you run it it will install based on those settings, If this is done in a local location the client(Point) will think it has a server were the config file is located, but that should not affect the end user.
Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post. |
| |
|
|