Re: How do manage your workstations?



Amartyr1 wrote:
It is ideal for network administrators to have all workstation setup so that users are logon as regular users (not power user, not administrator). The main problem I have when doing this is when it is time to upgrade an application programs, or a device (such a network printer) needs to be added. For the most part these functions require a local administrator rights. Therefore I have to logoff the regular user, then I logon as local administrator so I can update programs or add-in devices. That’s no big deal if I’m just doing a handful of workstations. However, if there are hundreds of workstations involved, it’s really time consuming!



I find it awfully hard to believe that you have hundreds of computers in a workgroup. That must be an excrutiatingly slow network, as the optimum workgroup size is 10 to 12 workstations. Why does your employer's IT department not create a domain? Among other things, a centrally controlled domain would greatly facilitate the installation and upgrade of member workstations. Your IT department should be able to explain this to you.


For now, I just make everybody a local administrator on their own workstation. That way the users can do program updates, add devices, etc.


Ouch...


However this presents a serious problem when users begin to play around and install authorized programs and altering system settings.



Too true. Only grant users local admin privileges if your employer can afford to double the support staff.


I just wonder what other IT professionals are doing to mitigate this problem. Maybe there is remote installation system that push program updates (or installation) to the workstation and that system logons on as domain admin (which is local admin by default).



Well, let's see. There's SMS, WUSS, RIS, DameWare, Novell's ZenWorks, Altiris, etc. Again, your IT department will have professionals trained in these matters; consult them.


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin

Is life so dear or peace so sweet as to be purchased at the price of chains and slavery? .... I know not what course others may take, but as for me, give me liberty, or give me death! -Patrick Henry
.



Relevant Pages

  • Re: Slow logon as administrator
    ... Are you redirecting the Administrator desktop (or using a roaming ... Sever IP is entered in DNS network settings and they all logon quickly ... enough when loggin on as domain users, but when I have to logon as the ... All workstations have same problem, ...
    (microsoft.public.windows.server.sbs)
  • New users cannot access shared programs
    ... I have installed MS Office 2000 and Adobe Reader 6.0 ... under WinXP Pro using Administrator status. ... when I logon with another user name, ... insert installation disc or show that a ...
    (microsoft.public.windowsxp.security_admin)
  • Problems in access problems by different users
    ... I have installed MS Office 2000 and Adobe Reader 6.0 ... However, when I logon ... Administrator), the "User" cannot access to the above ... installation disc or show that a ...
    (microsoft.public.windowsxp.accessibility)
  • Re: Setting User Name to ADMINISTRATOR
    ... because I just put a single letter during XP installation process. ... when XP was installed I went and changed the user account ... start with after installing XP) to the name of ADMINISTRATOR? ... In Windows XP Professional with the Welcome Screen logon still enabled, ...
    (microsoft.public.windowsxp.security_admin)
  • RE: Event ID 529
    ... The source is clear - workstations that are not part of my ... SBS2003 domain share the same local network (it's a shared local network in ... This kind of issue may be caused by Application logon such as while Outlook ... is connecting to Exchange Server, or this is an automated dictionary attack ...
    (microsoft.public.windows.server.sbs)