SB and network/workstation installs

[NewsArchive]

Reading the help files seems to imply that there is a script that can handle
both server/workstation installs and standalone installs. The documentation
says that standalone machines can also benefit from a server/workstation
install.

Can someone please tell me if there is an example of this anywhere and if I
can convert an existing standalone install to a server/workstation script?

TIA

John Fligg

[NewsArchive]

Hi John,

It just means that SB does have the power and functionality to create both
server/workstation (even in a single) installation.

But only the developer can decide what to do. For example, display a dialog
so the user can select a Server or Workstation option. Then, in the script
code, do whatever has to be done for a Server and Workstation installation.
For example, only create Shortcuts to files on the server for Workstation
installations, etc. Or, don't install server files for a Workstation
installation.

But there is no general design rule for a workstation/server installation.
It depends on the application type.

Friedrich

[NewsArchive]

Thanks Friedrich.

I see what you are saying but is there any general rule to be aware of? I
would imagine that the application files go onto the workstation (and maybe
the server) and of course data goes to the server.

OCX's etc. go to the workstation.

Are there any more general rules to be aware of in terms of networking
requirements? I know ini files need to be considered carefully as to whether
they go to a server or worksation.

Finally, as Jane was saying in another thread, how do you go about detecting
whether the app is running on a worksation or server as I understand that
using CSIDL on a Vista server is unreliable and you may have to use UNC
pathnames on a workstation.

I think that this last paragraph is probably more of the "general rules"
that I am thinking of.

Hope that makes sense.

And just when I thought I had my install script nicely finished <g>

Many thanks

John

[NewsArchive]

Hi John,

First of all, there is no reliable way to detect whether the app is running
on a workstation or server. You can even use a Win95 machine as a server
<g>. Does running your app on Windows Server 2003 or Windows Server 2008
mean the machine is acting as server? No.

So it all depends on the application. Server installation just means that
the install for this machine will act as the host computer for your system.
Client installation means that the install for this machine will act as a
client computer, connecting to a host. So do whatever has to be done for a
Server Installation and for a Client Installation.

In most cases, a Server Installation does not create Shortcuts, it does
self-register files, it does not create file associations, and much more.
And of course, it should not reboot the server! So making sure that all
files can be written is vital in a server installation environment (see
Check In-Use Files function). The Client Installation will create
shortcuts, self-register files, create file associations, perhaps it needs
the host name, the path to the database, or the installation has to map
network drives or share or remove a server resource.

Does this help?

Friedrich

Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.6
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

> Does this help?
>

Perhaps <g>

I have asked Jane Fleming a question about all this too as she very kindly
helped out on another matter by private email. Once I hear back from here
(she is busy right now) I can sit down and plan all this out perhaps.

It seems I have got into a scenario where quite frankly I am not quite sure
what I am doing. A case of a little knowledge is perhaps dangerous!

All I know is that some clients will now be wanting to install my app in a
network environment over which I have absolutely no control (server only,
server/workstation) and then there is the frightning issue that they may
want to use roving laptops to connect to whatever is running in the office.

So all in all one heck of a nightmare.

John

[NewsArchive]

Hi John,

Okay, I see. So as I understand it, you are at an early state of the setup
planning process.

First of all, you have to make sure that your application really works in
such a "server environment". After that you can plan your installation
procedure.

It's always a good idea to have only one installation that can handle both
Server and Workstation setup. Display the "Welcome" dialog, then the
"Readme" and/or "License Agreement" dialog. Next display a dialog that
enables the user to select "Server Installation" or "Workstation
Installation" options (with the default set to Workstation). Now comes the
tricky part. Some dialogs/functions are no required in a Server
installations, other dialogs/functions are only required if you do a
Workstation installation. SetupBuilder can handle this without any problem.
But you have to know what is required and what not.

Please keep us posted.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.6
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

This topic could make for a good ClarionMag article.

Greg Fasolt

[NewsArchive]

Absolutely!!! Good idea.

Friedrich

[NewsArchive]

Well I'm not writing it <vbg>

Seriously - thanks to ALL. Things are becoming a little clearer. I ahve my
paper and pencil at the ready. Just need a few spare days now.

John

[NewsArchive]

John,

The first thing you have to know about clients/server setup for your app is
that it will enable to be run :
as a stand alone one machine for clients with only one machine - use server
installation
your app will be "able" to work like this because all files (app-dll's-data
etc are on the machine)

I am not quite as categorical as Friederich is about registering files or
shortcuts on a "server" machine as this enables the one machine clients to
use the same installer if all is done on the "server" machine

Now imagine you have a one machine client - he needs all shortcuts etc
Now imagine you do a real server install, why refuse any user to work on
that machine if no shortcuts etc ?

THE difference is in size of companies and on definition of "server" - as
Friederich said you can call a server a W95 machine.

In small lans - I presume there will be one machine dedicated to Internet
and your application and data files - client machines will connect to this
machine to access Internet (before you jumped in) and they will also connect
to your app same way

Now - nothing prohibits anyone from using that machine to access your app
exccept some rules written in golden sand in the desert of computing world
IF they know what they are doing (they generally do not)

So I would suggest in your installer "server" side to add a checkbox for
shortcuts etc .... like this give users with two machines the possibility
not to have to buy a third one just because some people will say : never
work on a server! stupid !

For many small apps a "server" is simply a machine were app and data is
stored and accessible on the lan - point.(wether it is a W95 or a W2008 ent
machine with 4 quad core cpus and 32 Gb Ram) so go for the full install
possibility on the servers

Then on client machines all you need is to have shortcuts pointing to the
server installation - DONE BEFORE any CLIENT one of course
So in client install all you need is to get the user to go on the lan and
pick out the correct directory on the "server" machine were YOUR exe has
already been installed
Then to create all shortcuts etc...locally using SB_INSTALLDIR as reference
(server directory) - abit tricky but some try and try will get you what you
need

Prohibit any installation client side if there is no server side install
(allow selection ONLY of YOUR exe over the lan)
Write on client machine in registry the lan directory (user selected it so
it exists) and you might need it "locally"

You can - at this stage do any registry setups also for usernames on the lan
(or do it from your app if left(path,2)='\\' ) - this means UNC dir so lan

Attached is my sebup builder I use for both installs (I do not use checkbox
possibility for server shortcuts - I just install them)

ALL depends on your clients and your app : either go for such a small mixed
installer giving you possibility to do all in one or go for a real server
client install but then you will have the funds available to pay Bill Gates
himself to come and do it for you no ? <BG>

JP





--
Merci - Thank you

JP