One cannot use the netdom switch unless they are a domain admin??

[Spin]

One cannot use the netdom switch unless they are a domain admin. Is there a
workaround? Because I have my helpdesk re-ghosting machines a lot and they
are winding up in the default computers OU again. The reason for that is
below.

Computers will be added to the default computers OU unless they are joined
to the domain with netdom.exe and use the /OU switch:
http://support.microsoft.com/default.aspx?scid=kb;en-us;266651

 

[Charles McMillan]

If they create the computer account in the correct OU
prior to joining the domain they won't need to use the
netdom command.

 

[Spin]

How exactly does one do that?

Have them create the computer account in the proper OU
before they join the workstation to the domain.

 

[Charles McMillan]

Have them right click on the OU and select all tasks then
add a computer. Make sure the type the name of the
computer correctly. Not sure of the exact context OU|all
tasks|add computer but once they right click it will be
evident what to do. I don't have access to my DCs or I
would give you the exaxt context so I have to do it by
memory, sorry.

 

[Spin]

And after they do this, the computer, if it is re-ghosted, when added back
into the domain it will automatically go into the correct OU? Sounds too
good to be true!

 

[Charles McMillan]

I may be misunderstanding your question.
If the help desk is going to re-use a computer name then
they need to right click the computer account in the OU
and select reset account.

If the computer name has never been used then just create
the computer account in the proper ou and you should be
good to go.

 

[Spin]

The problem is the helpdesk re-ghosts machines a lot. The machines, once
re-ghosted, then go back by default into the default "Computers" OU after
the re-ghosting. I want them to be able to put the computers back in the
correct OU (which by the way, isn't the default), but I do not want to give
them administrator privileges. I hope this makes it more clear.
--

 

[Charles McMillan]

Resetting the computer accounts prior to re-ghosting
should solve the problem.