/build/static/layout/Breadcrumb_cap_w.png

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 7.1k  |  Created: 05/12/2011

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

Deployment Tips (3)

Most Common Setup Type
Legacy Setup with command line support
Average Package Difficulty Rating
Rated 5 / 5 (Very Difficult) based on 1 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (answer file driven)
6
Note
This is my approach to the silent install of the Sage 50 Accounts 2011 application. I am sure that this can be done in a different way, but this approach works for me.

***************************************************
The Main Application Installation and configuration
***************************************************

Create a .vbs script (install.vbs) to install the main application. The legacy setup.exe requires an .iss response file for the installation. Another .iss response file is required for uninstall.

Search the appdeploy.com forum if you are not sure how to create the .iss response file.

Sage requires configuration on first launch (company information, licensing information, RSS feeds message box, automatic updates message box). Create a snapshot and configure the application. This is the Customization MSI. This MSI should be installed by the install.vbs script.

How to disable automatic updates.
Don’t use the application GUI to disable the automatic updates. This is very hard to snapshot and may break the application. Rename the "C:\Program Files\Common Files\Sage SBD\Sage.SBD.Platform.Installation.SoftwareUpdates.UI.exe" file to Sage.SBD.Platform.Installation.SoftwareUpdates.UI.exe- or simply remove this file. This can be done in the Customization MSI or in install.vbs.
Remove the KeyPath from the AutoUpdateService(…) component, otherwise this file will be repaired. This should be done in the main Accounts.msi file. Use .mst to do it.
Tip: Use the following command in your install.vbs script to install the main application using the .iss response file and the .mst file
"""" & CurrentDir & "Install\InstallV.exe" & """" & "/s /f1" & """" & CurrentDir & "Install\install.iss" & """" & " /v" & """" & "transforms=\" & """" & CurrentDir &"Install\customization.mst\" & """" & """"
When the above is done, try to click the Help >> Updates -nothing will happen.

You can also edit the “C:\Program Files\Sage\AccountsApplication.config” file to disable automatic updates. The following lines should be changed (use 127.0.0.1 or any other IP which will not point to the Sage updates server)
<NAME>Sage Software Updates</NAME>
http://127.0.0.1


***************************************************
The updates installation
***************************************************

There is a number of updates for the Sage application. Some are vendor supplied MSI’s, some are in the legacy setup.exe format. In case of the legacy setup.exe format use the AutoIT (easy stuff, may be more complex when you have to script the Tree View control) tool to create an .exe which will install the update. The AutoIT .exe should be launched from within the install.vbs script.

/Tomasz
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • serpiente
  • 06/06/2011  
  • Show Comments   ( 1 )

  • You state that a snapshot must be created first. I have created my snapshot but where can I find the files needed now for an unattend install.

    Thanks - Rocket Man 12 years ago
4
Note
This is my approach to the silent install of the Sage 50 Accounts 2011 application. I am sure that this can be done in a different way, but this approach works for me.

***************************************************
The Main Application Installation and configuration
***************************************************

Create a .vbs script (install.vbs) to install the main application. The legacy setup.exe requires an .iss response file for the installation. Another .iss response file is required for uninstall.

Search the appdeploy.com forum if you are not sure how to create the .iss response file.

Sage requires configuration on first launch (company information, licensing information, RSS feeds message box, automatic updates message box). Create a snapshot and configure the application. This is the Customization MSI. This MSI should be installed by the install.vbs script.

How to disable automatic updates.
Don’t use the application GUI to disable the automatic updates. This is very hard to snapshot and may break the application. Rename the "C:\Program Files\Common Files\Sage SBD\Sage.SBD.Platform.Installation.SoftwareUpdates.UI.exe" file to Sage.SBD.Platform.Installation.SoftwareUpdates.UI.exe- or simply remove this file. This can be done in the Customization MSI or in install.vbs.
Remove the KeyPath from the AutoUpdateService(…) component, otherwise this file will be repaired. This should be done in the main Accounts.msi file. Use .mst to do it.
Tip: Use the following command in your install.vbs script to install the main application using the .iss response file and the .mst file
"""" & CurrentDir & "Install\InstallV.exe" & """" & "/s /f1" & """" & CurrentDir & "Install\install.iss" & """" & " /v" & """" & "transforms=\" & """" & CurrentDir &"Install\customization.mst\" & """" & """"
When the above is done, try to click the Help >> Updates -nothing will happen.

You can also edit the “C:\Program Files\Sage\AccountsApplication.config” file to disable automatic updates. The following lines should be changed (use 127.0.0.1 or any other IP which will not point to the Sage updates server)
<NAME>Sage Software Updates</NAME>
http://127.0.0.1


***************************************************
The updates installation
***************************************************

There is a number of updates for the Sage application. Some are vendor supplied MSI’s, some are in the legacy setup.exe format. In case of the legacy setup.exe format use the AutoIT (easy stuff, may be more complex when you have to script the Tree View control) tool to create an .exe which will install the update. The AutoIT .exe should be launched from within the install.vbs script.

/Tomasz
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
  • serpiente
  • 06/06/2011  
  • Show Comments   ( 1 )

  • After creating the snapshot of the application where are the files located with the specifics entered to install the application fully unattended - Rocket Man 12 years ago
2
Note

If it helps anyone here is the "setup.iss" that I finally managed to get the install.exe of Sage 50 Accounts 2013 to spit out.  I would love some help with packaging this up for silent GP deployment if anyone is familiar.

 

With this setup.iss I can get a silent install done with the command:
install.exe /s /sms

However this is only half the battle as I need to insert the network path so the company data and product key are picked up.


Setup.iss:


[{45ECE61A-C8EE-4847-852C-6E8A8192D424}-DlgOrder]
Dlg0={45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdLicense-0
Count=4
Dlg1={45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdOptionsButtons-0
Dlg2={45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdStartCopy-0
Dlg3={45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdFinish-0
[{45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdLicense-0]
Result=1
[{45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdOptionsButtons-0]
Result=101
[{45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdStartCopy-0]
Result=1
[Application]
Name=Accounts 2013
Version=19.00
Company=Sage
Lang=0409
[{45ECE61A-C8EE-4847-852C-6E8A8192D424}-SdFinish-0]
Result=1
bOpt1=0
bOpt2=0



Thanks in advance for any help, I see ALOT of people are really struggling with packaging Sage 50 Accounts and what with me being a newbie and all . . .

Best,


Evil
Setup Information:
Setup Type: Legacy Setup with command line support
Deployment Method Used: Vendor Provided Command Line (answer file driven)
Deployment Difficulty: Very Difficult
Platform(s): Windows
  • DrEvil
  • 04/29/2013  
  • Show Comments   ( 0 )

Inventory Records (1)

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

Versions

Sage

Version

17.0.12.196

Contact

Customer Support Department

Comments

If you wish to contact technical support please have your serial number and activation key ready.

Readme

C:\Program Files\Sage\Accounts\Readme.rtf

Uninstall String

C:\PROGRA~1\COMMON~1\INSTAL~1\Driver\1150\INTEL3~1\IDriver.exe /M{4D21F997-85AD-42D2-986F-D91C4836438D} C:\PROGRA~2\COMMON~1\INSTAL~1\Driver\1150\INTEL3~1\IDriver.exe /M{4D21F997-85AD-42D2-986F-D91C4836438D}

Questions & Answers (0)

Questions & Answers related to Sage UK Sage

Blogs (0)

Blog posts related to Sage UK Sage

Reviews (0)

Reviews related to Sage UK Sage

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ