Re: Domain or Workgroup
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Thu, 27 Jul 2006 07:24:36 -0700
Actually, when properly installed, Domains are more robust and provide a
'simpler' set of maintenance issues, with a concomitant higher level of
security. But it may require having someone with more expertise available to
get it set up and staff 'trained' on the differences. I have clients with
both small and large domains, and the total maintenance for all computers on
the network dropped significantly after converting from Peer-Peer to a
Domain infrastructure.
The "...SSPI context" message is probably due to an application attempting
to connect to a server and not being properly configured.
About moving 'things' over... There is an issue around keeping user
profiles -but there are tools that will take care of that for us. Normally,
there is nothing to 'move over'. Sometimes, however, when a domain is
installed, since better security is now available, file storage may be
revised in order to take advantage of the increased security and possibly
even centralized backup.
Robert, I guess the key question is: "Do you have someone available to
assist with the proper installation, configuration, and training, and that
could be 'on call' for ongoing assistance?"
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Mernick" <Mernick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A900BED2-959A-4750-932F-542C62E3E8EB@xxxxxxxxxxxxxxxx
Thank you so much for the quick reply.
I was hoping to keep the users in the workgroup rather than as domain
members because this is a fairly mature system and they have two years
worth
of work under there current user name setup. Contacts, word processor
documents, etc.. Moving everything over seems like quite a job.
Also during our testing I was getting a fair amount of sporatic system
type
error messages if we went a couple of hours without using a work station.
Something like "Could not generate a SPSI context". It required rebooting
to
reconnect to the domain.
I have a friend who has a system with 120 users, and he strongly
recommends
staying away from enrolling everyone in the domain, since it will add so
much
complexity to the system.
You thoughts would be greatly appreciated.
Thanks again,
Robert Mernick
"Arnie Rowland" wrote:
As far as SQL Server 2000 is concerned, Domain users are the way to go.
Windows authentication provides better security, better password control,
less 'user' maintenance for the DBA, etc..
It really is a 'no-brainer'.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Mernick" <Mernick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A762C88-472D-4094-B560-14C5D6C972D3@xxxxxxxxxxxxxxxx
We recently moved our main application from a work group environment,
to a
server environment.
What are the trade offs in having our users becoming part of our new
domain
or to remain in their work group and access SQL Server through Server
Authentication?
Hope to hear from you soon
Robert Mernick
.
- Follow-Ups:
- Re: Domain or Workgroup
- From: 10001110101
- Re: Domain or Workgroup
- References:
- Re: Domain or Workgroup
- From: Arnie Rowland
- Re: Domain or Workgroup
- Prev by Date: Re: Domain or Workgroup
- Next by Date: Re: Domain or Workgroup
- Previous by thread: Re: Domain or Workgroup
- Next by thread: Re: Domain or Workgroup
- Index(es):
Relevant Pages
|
