Re: Admin Priveleges Not Working

From: Jim Behning (jimbehningmvp_at_atl.mindspring.com)
Date: 06/04/04


Date: Fri, 04 Jun 2004 13:34:26 GMT

When I add a computer to the domain from the workstation I go through
the wizard and I enter the server administrator name, administrator
password and domain name. I do this for all the times the wizard has
fill in the blanks questions related to a domain user. Is that where
you are having problems? The workstation is part of the workgroup
Workgroup when you start the Network wizard? You do not use local
workstation admin accounts to join a domain. Only the domain
administrator (s) accounts.

"Gary" <anonymous@discussions.microsoft.com> wrote:

>Hi Jeff - thanks for your reply. I deleted one of the
>accounts & ensured it wasn't part of the domain. When I
>then tried to add it to the domain I get "Access rights
>to create & delete computer objects are required to use
>the Setup Computer Wizard" - on the SBS box. I now have a
>client that can't be logged into as it isn't part of the
>domain & doesn't have a local admin account to try & join
>it to the domain. Any more suggestions? This is obviously
>a pain & i'm starting to get worried.
>
>Cheers
>
>Gary
>>-----Original Message-----
>>Try deleting the computer account and rejoining it to
>the domain.
>>"Gary" <anonymous@discussions.microsoft.com> wrote in
>message
>>news:17d9101c4497f$57dcaa10$a101280a@phx.gbl...
>>> Hi All,
>>> After having to use System Restore on a client,
>>> I've noticed that our XP Pro workstations have all lost
>>> Administrator Priveleges. All local admin accounts have
>>> been disabled and the SBS admin is the only member of
>>> the "administrators" group. The workstations log into
>the
>>> SBS server under the admin account but i can't System
>>> Restore, Windows Update, Add/ Remove software etc.
>These
>>> workstations are fully patched but I checked 3 others
>>> that haven't been used the last month & weren't patched
>>> last month. They all have Admin account full priveleges
>>> therefore I'm assuming it was one of last months
>>> hotfixes. I can't remove the relevant hotfixes as I
>don't
>>> have the privelege & all I could find Googling was Kb
>>> 313222. Has anyone come across this problem recently?
>>> Does anyone have any suggestions as to how to rectify
>>> this situation. As you can imagine this is annoying &
>>> next Tues is Windows Update time!
>>>
>>> TIA
>>>
>>> Gary
>>
>>
>>.
>>

Jim B. SBS MVP
remove the mvp to send email



Relevant Pages

  • Re: Admin Priveleges Not Working
    ... you must be signed onto the workstation under an account which has local ... admin rights to change from a wg to a domain. ... it's probably a bit late now, but I always change the local administrator ... > workstation admin accounts to join a domain. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Admin Priveleges Not Working
    ... the "administrator group" but that didn't work. ... >you must be signed onto the workstation under an account ... >> the wizard and I enter the server administrator name, ... >> workstation admin accounts to join a domain. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Must all users be administrators?
    ... Why would the owner of a business decide to renovate a cubicle for each ... > group on the local workstation. ... Unless the end user is an administrator, ... making a user a member of Domain Admins has the ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 6032
    ... So are these files actually on the SBS box, or on the workstation? ... The Recovery Agent does not need ownership, but it has to be the ... Administrator account by default, but it would not have to be. ... decrypt the files by reversing the process in which you encrypted them. ...
    (microsoft.public.windows.server.sbs)
  • Re: "Classic logon" screen in XP does not remeber the user name
    ... not use the default (Administrator) user profile, as a precaution to not mess ... John N ... When I am at the server, ... and log onto a workstation, that workstation immediately goes to a locked ...
    (microsoft.public.windowsxp.security_admin)