When I try to join Win 7 to domain with 'System properties, Computer name', I get an error message:-" The operation was not succesfull, This could be because an existing computer account having name 'brandy' was previously createdusing a different set of credentials. Use a different computer name, or contact your administrator to remove any stale conflicting account. The error was: Access is denied."Thats nice.- I am the administrator.- My PC is registered to the domain with name 'brandy'- There is no other 'brandy' in the network- There is no information (or link) in the error message, how to set or remove the existing credentialsPlease give me a hint, what to do.-------------------------------------It would be much better, if all the network configuration parameters were collected in just one file, where they could be edited with Notepad or Excel and copied to be sent via email.I repeat this:It would be much better, if all the network configuration parameters were collected in just one file, where they could be edited with Notepad or Excel and copied to be sent via email.Having about one hundred dull and stupid windowses for network configuration makes it feel that I'd better wait for the next version of Windows. Maybe the programmers have by then learned how to build an OS. Now it feels as they have just collected pieces from here and there, thrown them together and painted multicolour cream over that all.Please take a step backwards. We have learned how to handle the network in WinXP. Now in Win7 everything has been changed and we have to spend time to find everything again.The change has not given us but troubles.We just jumped over WinV to minimise the price of the change. It is extremely expensive to teach our workers to handle the new system. I might be even less expensive to move to Linux than to a new version of Windows.Making things in fancy coloured windowses doesn't make things better. It makesthings just different.I have joined hundreds of Windows PCs to domain since Win311 (and used and built more OSs than you have even heard).

Option 1: Go to the domain controller and reset the computer object named brandy. Option 2: Rename your computer.

DarienHawk67 said: Option 1: Go to the domain controller and reset the computer object named brandy. Option 2: Rename your computer. Please could you tell me what has happened.I am not the domain controller administrator and in the future it will be waluable to know, what has happened. I don't find I have done anything exeptional. I have just followed the guidelines we have learned with WinXP.If the problem really lies in the AD system or the domain administrator has done something he might be interested.

It sounds like the computer was previously joined to the domain when you were running a different OS. If you install a new OS the computer is a different computer for all intents and purposes. Even re-installing the same OS will cause this problem. If you are no longer usingthe previously installed OSyou would have to delete that computer name from Active Directory before it can be re-used. If you are dual booting and want to join the domain in each OS you will have to have different computer names in each OS.Kerry Brown MS-MVP - Windows Desktop Experience

Okay, now we are percolating coffee. When you installed Windows 7, did you replace another machine that was named brandy? If that is the case, then Kerry Brown has your answer. Regardless of the computer name, each computer installation is represented by a unique SID. Even if you took one computer with the name brandy and reloadedit inthe same exact manner with the same name, the computer will have a different SID; therefore, it will have a different identity. When that happens, a domain admin needs to reset the computer object in AD so that it can rejoin the domain. Being you are not a domain admin without full domain rights, that explains your issue. You must coordinate with him or her joining a computer. What you can do is see if he or she will delegate privileges to a certain OU so that you can add, remove, and rename accounts and objects only in that particular OU. The problem does not lie with Windows 7, the AD system, or with the domain admin; the problem stems from uncoordinated actionslack of communication. Have them reset the brandy computer object.