I'm trying to figure out an intelligent way to install apps on the network server, and be able to install once and have all the clients use this. However, it seems like most installations modify the registry and seem to demand a client-by-client installation. Am I missing something on this? Can someone provide me some hints or references to help this? (And is anyone thinking about a SMS/ZEN type package for Samba/Unix?) Thanks, Bill -- Bill Eldridge Radio Free Asia bill@rfa.org
Bill Eldridge wrote:> > I'm trying to figure out an > intelligent way to install > apps on the network server, > and be able to install once > and have all the clients use > this. However, it seems > like most installations modify > the registry and seem to > demand a client-by-client installation. > > Am I missing something on this? > Can someone provide me some hints > or references to help this?Welcome to the bane of my life! You aren't missing anything. Most applications are written on the basis that you will install them on every machine. Some are written so you can install on a network server and then do a client install on every machine. Very few are written such that you can install them on a network server and they will just work on a client. For the usual sorts if you want them to just work you have to either copy the DLLs that sneak into the windows dirs back to the program dirs on the server or do a script in kix32, batsh or winbatch or whatever to copy them to each machine and also work out what registry entries or ini files are needed. There are tools like wininstall (symantec?) or inctrl (on the ziif davis archive) to help but a lot of it is trial and error in my experience! Cheers Martin -- Martin Sapsed Tel: +44 (0)1248 382409 Computing Lab Fax: +44 (0)1248 383826 University of Wales, Bangor m.sapsed@bangor.ac.uk North Wales, LL57 2DG Press any key to continue or any other key to quit...
On Wed, 5 May 1999, Bill Eldridge wrote:
Although this may be closing the door afterwards in your case, the typical
method at my place of employ is to create an image with all the network
apps already installed and then remove the the binary package and data
files. This will leave an image with .dll's and registry entries ready to
run although it may require some tweaking of file associations especially
to avoid calling the nonexistent app from the local drive. This image is
then deployed either via a ghosted CD or a network install to all client
computers. When the app is called from the network it then has all the
resources available locally with a minimum of clutter. This can also be
deployed via a case by case basis using a script that installs and then
deletes the app via the network the first time the netapp is called from
the client - although this a slightly messier method it does allow on the
fly implementation of new applications - it also requires fairly extensive
testing and a lot of bandwidth...
+>I'm trying to figure out an
+>intelligent way to install
+>apps on the network server,
+>and be able to install once
+>and have all the clients use
+>this. However, it seems
+>like most installations modify
+>the registry and seem to
+>demand a client-by-client installation.
+>
+>Bill Eldridge
+>Radio Free Asia
+>bill@rfa.org
+>
Gregory Lee Jones skripto@io.com
liscglj@tlc.state.tx.us
http://www.io.com/~skripto
'Fewer Insect Parts By Weight than the Leading Brand'
Take a look at the smb.conf manpage ( announce as and announce version
):
announce as (G)
This specifies what type of server nmbd will announce
itself as, to a network neighborhood browse list. By
default this is set to Windows NT. The valid options
are : "NT", which is a synonym for "NT
Server", "NT
Server", "NT Workstation", "Win95" or
"WfW" meaning
Windows NT Server, Windows NT Workstation, Windows 95
and Windows for Workgroups respectively. Do not change
this parameter unless you have a specific need to stop
Samba appearing as an NT server as this may prevent
Samba servers from participating as browser servers
correctly.
Default: announce as = NT Server
Example announce as = Win95
announce version (G)
This specifies the major and minor version numbers that
nmbd will use when announcing itself as a server. The
default is 4.2. Do not change this parameter unless
you have a specific need to set a Samba server to be a
downlevel server.
Default: announce version = 4.2
Example: announce version = 2.0
>
> Date: Thu, 6 May 1999 10:56:35 +0800 (MYT)
> From: Admin-Eng <langzhi@sak.upm.edu.my>
> To: samba@samba.org
> Subject: Linux seen as Win NT 4.2 Backup
> Message-ID: <Pine.LNX.3.96.990506105337.19338A-100000@sak.upm.edu.my>
>
> Why is my Linux (samba 1.98-RedHat 5.2) is seen as WinNT 4.2 Backup from
> my Domain Controler Service Manager ?
>
> How to make it so that its only seen as normal Win95 or winNT workstation
> ?
>
> thanks
>
> --- ---
> -_- -_-
> **~* **~*
> F /-/ LangZhi UPM <langzhi@sak.upm.edu.my>
/-/F
> R /-/ whois ? Chan Kien Eng <b41548@kosass.upm.edu.my>
/-/ R
> E/-/ " We grow strong by pains,grow great by dreams - Dave Wang
" /-/ E
> E - - - ^ When do you wanna cra$h today ?? ^ - - - E
>
--
Regards Per \|/
(o *)
---------------------------------------------------oOOO--(_)-
| Per Kofod / Systems Engineer Email: per@sgi.com |
| Silicon Graphics Denmark Fax: (+45) 43270481 O
| Stationsparken 25 Phone: (+45) 43438600 O
| 2600 Glostrup VNET 540-0431 O
| DENMARK URL: http://www.sgi.com o
-------------------------------------------------------------
* Gravity never loses! The best you can hope for is a draw! *
> Date: Wed, 5 May 1999 15:31:45 -0400 > From: "LeScoezec, Mark" <mark_lescoezec@sfmny.com> > To: "'samba@samba.anu.edu.au'" <samba@samba.anu.edu.au> > Subject: SAMBA 2.0.3 with HP WebJetadmin > Message-ID: <8164200C6DC4D21193AB0008C709B2C0264634@sfmexch1.sfmny.com> > > Has anybody setup Samba in conjunction with HP WebJetadmin software? > Seems that this would be a good combo if they worked together. > > thanks in advance > Mark LeScoezec > SA/DBA > Soros Fund Management > 212-397-5597I have both Samba and WebJetAdmin running on the same server and have not had any trouble. Both are great programs. BRG
When the world was young, Brian Servis <servis@purdue.edu> carved some runes like this:> *- On 6 May, robert wrote about "printing through a workstation" > > > hello, Is there a way to get samba to allow you to print from the unix > > side of the fence to a shared printer on a win95 workstation? This would > > be very useful for faxing etc... any suggestions?? thanks Robert > > > > Look for the smbprint script that is part of the examples section in > the source, In the Debian GNU/Linux distro it is contained in the > samba-doc package. It has info on setting up a unix print filter to > send to a windows shared printer. I have never used it, but the info is > there.With redhat it's even easier (not sure about other distributions or unix flavors) - just use the printtool widget under X and specify SMB network printer. It uses the standard redhat print filters (nenscript and ghostscript) and the following basic samba settings: in the global section: printcap name = /etc/printcap load printers = yes (printing style is not specified) the printer share definition: [printers] comment = All Printers path = /var/spool/samba browseable = no # Set public = yes to allow user 'guest account' to print guest ok = no writable = no printable = yes It seems to work fine, ie, even though the printers are hanging on a win95 print server, I can even print through the samba print shares from another win95 client (as well as direct from win95 and from the linux side). The linux printing HOWTOs can be helpful (even if you're running a commercial unix flavor). Also, lprng is supposed to be pretty slick too (check the docs for more info). Don't forget, you can always look at the source code too... **************************************************************** Stephen L. Arnold Senior Systems Engineer ENSCO Inc. email: arnold.steve@ensco.com P.O. Box 5488 www: http://www.ensco.com Vandenberg AFB, CA 93437 voice: 805.606.8838 fax: 805.734.4779 #include <std_disclaimer.h> ****************************************************************
Sending Winpopup messages is possible by issuing the command smbclient -M <host>. How do I send a winpopup message to a user, or a workgroup. If I type smbclient -M <workgroup> I get 'Unknown Host'. I have tried various methods, but no success. I wish to cause winpopup messages to be broadcast when the server is shutting down, automatically. What am I doing wrong???! Gareth.