I'm going to work with him on this some more on Monday - we have 8
more machines to do. I'll (dis)confirm the behavior, and let the list
know.

Thanks,

Kurt

On Sat, Apr 10, 2010 at 14:20, Brian Desmond <[email protected]> wrote:
> They should call the same API (I can confirm if need be). I have a bunch of 
> quick and dirty cmdline apps I wrote for some of these tasks that my build 
> tools call.
>
> Thanks,
> Brian Desmond
> [email protected]
>
> c   – 312.731.3132
>
>
> -----Original Message-----
> From: Kurt Buff [mailto:[email protected]]
> Sent: Saturday, April 10, 2010 4:18 PM
> To: NT System Admin Issues
> Subject: Re: Windows 7 - problems with renaming computer and joining to domain
>
> The minion was able to add via the powershell script.
>
> Don't know why, but would like to, he couldn't add the Win7 machine via the 
> control panel.
>
> Weird.
>
> On Sat, Apr 10, 2010 at 10:07, Brian Desmond <[email protected]> wrote:
>> Default quota isten machines in 2003 I have qnd rename tool if you
>> need it
>>
>> Brian Desmond from my phone
>>
>> On Apr 9, 2010, at 5:05 PM, "Kurt Buff" <[email protected]> wrote:
>>
>>> 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/>  ~
>
>
>
> ~ 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/>  ~

Reply via email to