Re: Domain or Workgroup?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 12/17/04 

Date: Fri, 17 Dec 2004 12:36:38 -0500

m.marien wrote:
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
> message news:e3quxh94EHA.1400@TK2MSFTNGP11.phx.gbl...
>> m.marien wrote:
>>> "Lanwench [MVP - Exchange]"
>>> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
>>> message news:ub2Eutw4EHA.1564@TK2MSFTNGP09.phx.gbl...
>>>> Eric Foreman wrote:
>>>>> I'm installing a new server for a small law firm with 9 users.
>>>>> They are very loose and unsecured ( no passwords) and prefer it
>>>>> that way. Should I rollout the new server using AD or an old
>>>>> fashioned Workgroup? What are the advantages to using AD for a
>>>>> small group? They will also never do any roaming. Any advice
>>>>> would be appreciated.
>>>>
>>>> I would always go for a domain if it isn't a very small home
>>>> network. You can control security centrally, store all data
>>>> centrally, etc - workgroups do not scale well and I don't think
>>>> they have any place on a business network.
>>>>
>>>
>>> Nice try. Except for the centrally managed user accounts, peer
>>> workgroups do everything a domain does.
>>
>> Except for AD-integrated DNS, WINS, and roaming profiles, and
>> centralized group policy and all that.
>>>
>
> DNS has been around a little longer then AD and WINS works just fine
> on peer workgroups. He also specifically stated they don't do
> roaming. As far as centralized goup policy, it seems that they don't
> have a policy and prefer it that way.
>
> I can understand all the good things about domains, but I think you're
> trying to sell a hummer to somebody that doesn't really need it.

I ask people what they need, and then we figure it out from there. It's
always up to them to do it or not.
>
> [snip]
>
>>
>> That's a shame, but passwords are a fact of life. If I were engaged
>> as a consultant somewhere and were asked to bypass this, I'd say no
>> - if they didn't want to continue with my services, I'd shake their
>> hand and walk away.
>>
>
> May be the best thing that happened to them.

My goodness, you seem cranky.
>
>>
>> That is true, and as in everything, one's mileage may vary. I offer
>> only my
>> own opinions. I don't want the support nightmare of supporting
>> workgroups beyond a handful of PCs. Pax!
>>
>
> Hello, they have a handful of of PC's here.

I can't hold 9 PCs in one hand. As I said, one's mileage may vary. I have my
ways, you have yours, and we can all be happy with our choices.

Relevant Pages

  • Re: Domain or Workgroup?
    ... >> centralized group policy and all that. ... As far as centralized goup policy, ... they have a handful of of PC's here. ... I can't hold 9 PCs in one hand. ...
    (microsoft.public.windows.server.setup)
  • Re: Need Troubleshooting tips for GP deployment failure
    ... it indicates that the correct Policies are ... >> run into a hitch with Port exceptions to the firewall that are needed ... >> being delivered via Group Policy to some but not all PCs. ...
    (microsoft.public.win2000.group_policy)
  • Re: Rolling back GPO changes
    ... Simplify Group Policy Troubleshooting with the NEW GPExpert Troubleshooting Pak 1.0 at http://www.sdmsoftware.com/products.php ... WOULD STILL ALLOW DOMAIN USERS TO LOG ON TO THEIR pcs AND ALSO THIS NEW GROUP ...
    (microsoft.public.windows.group_policy)
  • Re: Applying user GPO to computers
    ... > to specific COMPUTERS, rather than ... > USERS (there are several PCs which are exempt from this policy)" ie I'd ... Mike Brannigan ...
    (microsoft.public.windows.server.active_directory)
  • Group policy not taking effect on some users
    ... Our DC is in our office and we have a few PCs that connect remotely through ... If a user logs in as a local admin on those PCs they are able to ... However, when a user logs into the system it lets them in, but only ... I have a mapped drive policy in Group policy ...
    (microsoft.public.windows.group_policy)