user permissions to add computer acct to domain

[Guest]

I have used an acct for the past year to RIS computers and had no problems
with the user acct adding the newly RIS computer to the domain. I have W2k
servers and use RIS for deploying images. Yesterday I made a new image and
then used the same acct to test the new image out and I received an error
message during the restart that the acct used does not have permission to add
the computer to the domain and would I like to do that now or later?
I am mystified by this sudden change. It really will create more work for
me if I have to go to any computers that RISed and have to manually add them
to the domain.
Only thing that I can think of that has changed is I added XP *.adm files to
be able to manage XP computers and applied the hotfix to W2k to be able to
read the new *.adm files for XP. I then installed the necessary files to RIS
to be able to deploy XP from our W2K server.
Would this change permissions?? I would think not. I have checked the
advanced security settings on the appropriate OUs nad the acct has create
computer objects.
I am at a loss of where or what else to look for?
Any suggestions on where or what to look for.

 

[Andrei Ungureanu]

but if you create the computer objects manually, it's working?

Andrei Ungureanu
www.eventid.net

 

[Guest]

I manually joined the computer to the domain by logging on as admin. I am
working on more tests today. I used the user acct this morning and it
worked. I think if the computer was previously a member of the domain, then
reimaged, it seems to work. This is the case 95% of the time. But we will be
getting a new computer lab with XP in about 4 weeks. These comptuers will
not have been in the domain previously. I want them to be added as they are
imaged and joined during the reboot. The default name should be the user
acct name and a number because I will not be using a naming file. After all
the computers are imaged, I will rename them according to their final
location.
I'll check by in after further testing. But unfortunately I do not have any
computer around that are not part of the domain to check this part of the
problem.