Network Security

[Louise McGillis]

We have a computer lab in our library running on Windows NT.  I found 
your comments about having to update individual workstations very 
interesting - we also have our software loaded on individual machines. 

My problem is that preferences are connected to accounts, not machines.  
This is really a problem with something like Netscape.  Does anyone know 
how to set prefences (default home page) and apps (telnet) so that they 
are retained by different users.  Any help would be greatly appreciated.

----------------------------------------------------------------------------
Louise McGillis
Librarian, Ferriss Hodgett Library      phone:  (709) 637-6236
Sir Wilfred Grenfell College            fax:    (709) 639-8125
Memorial University of Newfoundland     email:  mcgillis at beothuk.swgc.mun.ca
Corner Brook, Newfoundland
A2H 6P9
----------------------------------------------------------------------------
   

On Tue, 22 Oct 1996, Timothy G. Kambitsch wrote:

> I am curious as to which applications people launching from the SERVER when
> they user Windows NT clients for public workstations. We are currently
> loading all the apps onto the client workstation partly so that our public
> Win95 workstations don't have to
> log-on to a server.  This has been okay as we have just started deploying
> our first systems, but I worry about how we
> are going to upgrade hundreds of workstations in the future.
> 
> Ideally I would like all of our public machines to be void of user
> applications and once connected to the network all applications are loaded
> from our NT Server's diskspace.
> 
> We use:
> 	Netscape 3.0
> 		Adobe Acrobat
> 		Real Audio
> 	CRT (terminal emulation)
> 	Electric Library
> 	NoveList
> 	Everybody's menu
> 
> 
> As to connecting to a server. I would like to find a way to have
> NT clients or even Win95 clients automatically login to a "guest"
> or "public" account on the server without the user seeing a
> network login dialog box.  Back in my Win 3.11/Novell days we used
> to script it into the autoexec.bat file, but noone here can seem
> to figure out a similar technique with an NT server.
> 
> >When last we looked at the question of securing public access
> >workstations, we concluded that Windows 95 was too difficult
> >and uncertain to secure.  We have thus decided to use Windows NT
> >for such locations.
> >
> >- Daniel
> 
> Tim Kambitsch <mailto://kambitsch@dayton.lib.oh.us>
> Dayton and Montgomery County Public Library                   513-227-9560
> 215 East Third Street Dayton OH 45402                   fax:  513-227-9524
> 
> 
>