RE: Workaround for 0x8007045A (!)
From: Tony Vaughan (TonyVaughan_at_discussions.microsoft.com)
Date: 09/17/04
- Next message: dai wee b: "RE: Error code 8024402C"
- Previous message: Ard: "Re: Error number: 0x80070002]"
- In reply to: Doug: "RE: Workaround for 0x8007045A (!)"
- Next in thread: Torgeir Bakken \(MVP\): "Re: Workaround for 0x8007045A (!)"
- Reply: Torgeir Bakken \(MVP\): "Re: Workaround for 0x8007045A (!)"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 17 Sep 2004 13:41:10 -0700
Hi Doug
I've just been chatting to a mate of mine who really knows what he is doing
when it comes to network configuration. Now, if you used to use SBS under NT4
and you created a domain user for a workstation as an administrator, the
domain user would have full administration rights to the local machine. My
mistake was to think that SBS 2000 and SBS 2003 did the same even though you
will notice that they introduced templates. It would now seem that when you
create a user as a template administrator you are giving that user
administrative rights to the domain but not the local machine, as your
observation proved.
So, what is the solution? I tried to give the domain user access rights to
the local machine by going into Computer Management and selecting 'Local
Users and Groups' and adding Domain Users to the list. However, under SP2
this didn't work so I am about to test this with a machine that doesn't have
SP2 installed. I'll let you know how that goes.
Anyway, you've found the cause of this problem, Well done!!!
We only need to find the solution so that domain users can use WU5.
And we have to ask why nobody from Microsoft told us about this earlier.
Speak to you soon.
Tony
"Doug" wrote:
> Yes I have SBS2003. You are right that all of us seem to have that.
>
> Im not sure about a policy problem because I have some PCs on the domain
> that don't exhibit any problems. Same version of windows, same domain
> accounts, but some PCs just stubbornly refuse to download updates.
>
- Next message: dai wee b: "RE: Error code 8024402C"
- Previous message: Ard: "Re: Error number: 0x80070002]"
- In reply to: Doug: "RE: Workaround for 0x8007045A (!)"
- Next in thread: Torgeir Bakken \(MVP\): "Re: Workaround for 0x8007045A (!)"
- Reply: Torgeir Bakken \(MVP\): "Re: Workaround for 0x8007045A (!)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|