I've seen that problem before, and I turned off the ability of standard users to join machines to the domain long ago. That's why I created the Add2Domain group and added him to it - with either the script I gave him or manually he's successful with joining XP, it this first Win7 box that's stumped me.
Ahhh... I wonder - I'll have him try the powershell script with the correct OU on it on the next machine he sets up. It shouldn't matter, as he's joined over 100 machines already, but perhaps there's something funky with Win7. Kurt On Fri, Apr 9, 2010 at 15:12, Steven M. Caesare <[email protected]> wrote: > We ran in to this as well... this article references Win2K domains, but I > think it may affect Win2K3 domains if they had been upgraded from Win2K: > > http://support.microsoft.com/kb/251335 > > We now pre-create the computer objects for the most part. > > -sc > > -----Original Message----- > From: Kurt Buff [mailto:[email protected]] > Sent: Friday, April 09, 2010 6:05 PM > To: NT System Admin Issues > Subject: Windows 7 - problems with renaming computer and joining to domain > > All, > > We have a Win2k3 SP2 R2 domain. > > We're getting small number of machines with Win7 Pro pre-installed from a > local whitebox vendor (this is a temporary condition, I > hope...) > > I've run into two problems: > > 1) minion can't join machine to domain manually He's not a Domain Admin, and > it says he's exceeded his quota for adding machines. This surprises me, since > he doesn't have this issue with XP machines - I long ago added him to a group > that is allowed add machines to the domain. My credentials worked. > > 2) I cruised the Information Super Highway and found that the PS cmdlet > rename-computer has been removed from PS. This puts a kink in things, as we > want to rename the computer and join it to the domain in the same script. > > My google-fu is failing me - I can't seem to find any links that address > these problems. > > I'm not going to go down the path of crying about netdom being removed. > PowerShell is just fine by me, though the method required to start an > elevated instance is a bit annoying. > > Anyone have some hints for me? > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
