Ghost Solution Suite

Why is it that when I use the Console to create a configuration task to rename a PC, it leaves the old name out in Active Directory? I'm almost positive that I did this in the past and it just overwrote the old name.

That's strange I don't think that happens for us... leaving an old AD computer account shouldn't happen since it's supposed to keep the same SID, right?

Maybe the domain acct you are having DS use doesn't have the correct AD permissions to rejoin computers to the domain?

Btw, this is for Symantec Ghost Solution Suite and not DS.

Thanks for the tip George, I check our Ghost account and it didn't have enought rights so we added it to the Domain Admin group but it's still leaving the old PC name.

Oh sorry about the DS assumption. :)

Hmm, if it's a domain admin and still doing it then I'm stumped. :(

Yup me too, but thanks for the suggestions.

 Hi Zick,

Ghost does not remove the old account, but client is removed from that account. In case if you use an existing name, it will re-create the account. In case if it does not have rights to delete and re-create the account it will fail. This happens some times when the machine account is owned by Administrator of the domain.

Krish

Hi Krish,
Thanks for responding althought it was not the answer I hoped to hear. That's too bad it does not remove the old names as now that makes more work for me to go back and delete all the old names off Active Directory.

Yes that's a frustrating design... lame.

Zick, I guess you could script the removal of the computer account from AD. I have a Deployment Solution job that does this using dsquery and dsrm.

all in one line:
dsquery computer domainroot -name "%NAME%" -u adminacct -p password | dsrm -noprompt -u adminacct -p password -q

So, the DSQUERY returns the FQDN of the computer account and pipes the result to the DSRM to delete the account. You just need to make sure the DSQUERY and DSRM exe files which are part of the Windows Admin Toolkit are present.