The following error occurred attempting to rename the computer. the account already exists.

Hi Folks,

Error:
 The following error occurred attempting to rename the computer. the account already exists.

Solution work for me.

1. Checked host name has removed from AD.
2. Checked DNS entry has removed.
3. Dis-join domain.
4. Change host-name whatever do  you want.
5. restart server.

It's work for me....


Comments

Post a Comment

Popular posts from this blog

Server Error - 404 file or directory not found

Image
Hi folks, After installation of Enterprise CA, I got an error "erver Error - 404 file or directory not found" while browsing certsrv web portal ( https://hostnameofCA/certsrv ).   Also check Inetpub directory is any virtual directory is in place. There was no virtual directory found.  Server OS : windows server 2008 Finally I found my mistake. While installation of Enterprise CA I didn't select   Web enrollment sub option. Then I add "Web enrollment"   role service from server manager and it's work.  
Read more

Active Directory operation failed on "domain.local". You cannot retry this operation: "Insufficient access rights to perform the operation

Image
Hi Folks, Error:- Active Directory operation failed on "ORLDC01.DRMAIN.local". You cannot retry this operation: "Insufficient access rights to perform the operation 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 ".You do not have the appropriate permissions to perform this operation in Active Directory. One possible cause is that the Lync Server Control Panel and Remote Windows PowerShell cannot modify users who belong to protected security groups (for example, the Domain Admins group). To manage users in the Domain Admins group, use the Lync Server Management Shell and log on using a Domain Admins account. There are other possible causes. For details, see Lync Server 2010 Help. ** When user account belongs to the administrator group or domain admin group so you cannot modify the properties in special modifying external access policy getting above error. In this case, you can perform changes from the active directory as w...
Read more

Error code 8004E00F - COM+ was unable to access the Microsoft Distributed Transaction Coordinator

You can get this when opening Admin tools, Component services., Console root, Component Services, My Computer, COM+ Applications. This is caused by MSDTC (Distributed transaction coordinator) Service being set to run under the local system account. Or the service is not running. Often this service is disabled on Exchange servers. Check to see if the service is running…. Start services (services.msc) locate “Distributed Transaction Coordinator” and check the “Log On tab”. Change the Log on account to NT Authority\NetworkService Just type NT Authority\NetworkService the Password is left blank. If you have done the above and your still getting Error code 8004E00F when you try to view Component services, you need to do this…. Run regedt32 and locate HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC. Check to see if the DWORD value “TurnOffRpcSecurity” exists. If yes, change the data value to “1”. If the key does not exist, add a DWORD value TurnOffRpcSecurity with a value data of 1. Stop service...
Read more