Unzipping an autounzip.exe to numerous workstations at once

Also forgot, you'll need to create a Server Ini for this to work, in the example above I used SVRUPDATE.INI this can be placed in the same directory as the autozip executables.

Just need the following two lines included in the ini
[Version]
Version = 1.0

When an update is released, update the executables and change the Version number to 2.0 or 1.1 etc..

Cheers

Hi there

Basically the script above is like the Java Update, except we just use the Servers Shared folder rather than a web address,
So here's a scenario

The Script above once compiled to an .exe will be saved to a folder on the users machine for example
C:\Program Files\SQLUpdater
A reference to the file is placed within HKLM\Software\Microsoft\Windows\CurrentVersion\Run\ with a value of SQLUpdater pointing to C:\Program Files\SQLUpdater\SQLUpdate.exe

Every time a user logs in, the program will run, it will look for the \\Server\Share\SQLUpdate.ini file, if it exists it will then do a version comparison, of the Server against the Computer ini held in C:\Program Files\SQLUpdater\ if the version is the same it quits, if the Server is higher, or the Computers version is lower inside the ini file it will then run your four autounzip.exe files.

I'll write you a small program if you like that you can install this on each pc, we could even put an icon under Start | All Programs if you like, it will also be added to Add/Remove Programs so that if you need to uninstall you can do so.

Write back soon.

Cheers

Just a couple of things

What are the names of the four autounzip.exe files?
Do they require switches appended or can they just be run directly without any prompting?
Do the users have Administrator Rights on the Computer?  If not I'll need to setup permissions on the C:\Program Files\SQLUpdater directory
Do the users have Rights to the SQL Directories where the autounzip.exe files unzip to?

I've already finished the setup.exe for the workstations, but need to touch up the first script above to ensure that the files have updated correctly before changing the local ini version information.

Cheers

Not sure why but the exe didn't get included, I don't thing EE accepts exe as attachments.

Can you tell me what program was used to zip these files, because hopefully there are switches I can use to unpack them silently.

"Could you allow access to those paths in this?"
Yep, but an administrator would initially need to install the programs so that the permissions can be given to these folders.

"Do I need to setup a shared folder on my server to store the originating autounzip.exe files, for this to work?"
Yes, basically rather than use version numbers on the zip files we would use the SVRUpdate.ini file held in the same folder as the autounzip.exe files.

So on the Server you would have

\\Server\Share\SQLUpdates for example, you will then have the following files in this directory.
Crystal.exe
Help.exe
Prophet.exe
MDF.exe
SQLUpdate.ini

The SQLUpdate.ini we would have
[Version]
Version = 11.5.687.007

Note that I used the version number of the file inside the ini file.

Cheers

"Would I change the ini everytime I ran an update. (That isn't a problem, just trying to understand)"
That's correct, so for the next update, you'd rename your files to:
Crystal.exe
Help.exe
Prophet.exe
MDF.exe

Change the Version of SQLUpdate.ini on the Server to whatever the new Version is.

Can you try something with one of your autounzip.exe files just as a test, can you run:
Crystal_11.5.687.007.exe /Auto "C:\Program Files\Activant\Prophet 21 11.0\Reports"

Can you tell me if it extracts silently?

You could try and send it to my email, matrixnz at 321.co.nz but it may or maynot work.

Cheers

No unfortunately, did you try the switch, I've finised both scripts, but just really need to know if the silent switches work or not so that I can write the command in.  Is it possible to use something like 7zip or just compress the file with zip then use commandline to extract?

Cheers

Alright I'm back, sorry for the delay

Here are the instructions:
Download and install AutoITv3 and AutoIT Script Editor found here http://www.autoitscript.com/autoit3/downloads.shtml (if you haven't already done so)
Download and install Innosetup QuickStart Pack found here http://www.jrsoftware.org/isdl.php#qsp
Download and Extract SQLUpdate.zip (attached) to C:\Scripts (for example)

Experts exchange wouldn't allow my extensions to upload so I renamed the all with a .txt extension, so please:
Rename C:\Scripts\AutoSQLUpdate.au3.txt to AutoSQLUpdate.au3
Rename C:\Scripts\SQLUpdate.au3.txt to SQLUpdate.au3
Rename C:\Scripts\SQLUpdate.ico.txt to SQLUpdate.ico
Rename C:\Scripts\SVRUPDATE.INI.txt to SVRUPDATE.INI
Rename C:\Scripts\Setup.iss.txt

Now for the setup:
Copy C:\Scripts\SVRUPDATE.INI to \\Your Server\Share\SQLUpdate\ Folder
Note: \\Your Server\Share\SQLUpdate\ should contain your autounzip.exe files and they should be named:
   Crystal.exe
   Help.exe
   Prophet.exe
   MDF.exe
If you want to change these names you'll need to update the "$SVR_ZPFILEx" variables within the SQLUpdate.au3 and AutoSQLUpdate.au3 scripts

Now for the script changes:
Open Scite found in: .>Start > All Programs > AutoIT v3 > Scite > Scite
Open the two files SQLUpdate.au3 and AutoSQLUpdate.au3
In SQLUpdate.au3 and AutoSQLUpdate.au3 you should only need to change the following line:

$SVR_SRCPATH = @ScriptDir ;Path to Server Updates; example: '\\Server\Share' Note: No following '\'

You will need to change it to something like:
$SVR_SRCPATH = '\\Your Server\Share\SQLUpdate'

Once completed and within Scite click Tools > Build or press F7 on your keyboard, the files should now compile to executables within the same folder as the Scripts, you should see SQLUpdate.exe and AutoSQLUpdate.exe

Open ISTool found in .> Start > All Programs > Inno Setup 5 > ISTool > ISTool
Open Setup.iss
You can change any of the following variables
#define PKGNAME "SQL Update Wizard";
#define PKGVERS "1.0"
#define PKGFOLD "SQL Update Wizard";
#define PKGCOMP "My Company Name"

PKGNAME is the name of the application.
PKGVERS is the version of the application.
PKGFOLD is the folder of the application i.e. default is C:\Program Files\SQL Update Wizard
PKGCOMP is the name of your company

Once completed click Project > Compile Setup or Press Ctrl + F9 on your keyboard, the file should now compile to an executable within the same folder as the Scripts, you should see Setup.exe.  This file contains the two files SQLUpdate.exe and AutoSQLUpdate.exe.

That's it your done.

Now all you need to do is test and install on a computer.  Note: To run Setup.exe you must be a member of the local administrators group.  The Setup.exe will install SQLUpdate.exe and AutoSQLUpdate.exe to C:\Program Files\SQL Update Wizard\ it will also set the permission authenticated users, modify rights on the following folders:
C:\Program Files\SQL Update Wizard\
C:\Program Files\Activant\Prophet 21 11.0\Reports
C:\Program Files\Activant\Prophet 21 11.0
C:\jfsrvr\forms
That way users can update themselves in future without any permissions.

A registry key is also created in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, the name of the Value is SQL Update Wizard and it runs the AutoSQLUpdate.exe everytime the user logs in.

A shortcut to SQLUpdate is added to the users Start Menu this is a Gui based version of the AutoSQLUpdate.exe this allows users to update manually if they need to.

If you need to remove the files, you can do this directly from Add/Remove Programs like any other program, it will only remove the files that we've installed nothing else.

If you wish to run the setup.exe silently you can do so by using the /verysilent switch if you wish to run it with a progress bar then you could just use /silent for example Setup.exe /Silent

Anyhow hope that helps and I haven't confused you.

Cheers

Actually all the downloads can be local, so just install them on your machine, as I mentioned the only thing that needs to be up on the server is in the same folder.
   SVRUPDATE.INI
   Crystal.exe
   Help.exe
   Prophet.exe
   MDF.exe

Do all your machines use D:\Program Files by default? either way, the script is actually setup to read from the registry where Program Files is so if the machine was setup to have D:\Program Files than by default it will install there.  It uses the same variable as %ProgramFiles%

Cheers

Hi Laustandphound

Sorry was away today, glad you got it all sorted, did you get the correct Server Variable because it should of been

$SVR_SRCPATH = '\\192.168.1.4\SQLUpdate'

not

$SVR_SRCPATH = @ScriptDir '\\192.168.1.4\SQLUpdate'

Cheers