Re: Best practice post-install of sbs clients
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 10 May 2007 12:54:42 -0400
I'm not sure that Microsoft makes a specific recommendation in this regard.
The admin rights are needed to install software, and for some configuration
tasks.
What I do with new PCs, which I think is a common practice, is to do all the
config and installation work while the user is a local admin, then knock
them back to standard user rights. I'd actually use restricted, but our
accounting app won't run unless users have "standard" user rights.
"Keith Lawrence MCP" <KeithLawrenceMCP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:C12A4FAF-E54B-49DE-B618-19CE3EB28AB8@xxxxxxxxxxxxxxxx
Anyone who has done an install of SBS2003 and XP clients will know that
during the Connect Computer phase, the designated user of the PC gets set
up
as a local admin on the computer.
Now, it is my understanding that you should only have users as local
admins
if it is ABSOLUTELY necessary, due to the increased rick of malware,
spyware
and people generally messing up their workstations. Some examples of
unavoidable situations include archaic accounting software, dos programs
etc.
With vista, the push has been away from any notion of a local admin,
bringing in UAC to provide a level of nix-esque control over elevated
priviledges.
My question is, does Microsoft recommend the designated user is left to be
a
local admin or not? if not, why is there no mention (in install/migration
guidlines) of bumping the user back down to domain user after the setup
phase?
Also, in real-life situations, what do other sysadmins out there do?
.
- Prev by Date: RE: Remote Web Workplace not working
- Next by Date: Re: Outlook2003 e-mail accounts order
- Previous by thread: Re: Running out of Disk Space
- Next by thread: Re: Can't Access HTTP Sites from SBS Network
- Index(es):
Relevant Pages
|
