I recently needed to rename a Hyper-V server (which is essentially a server core install of Windows Server 2008 R2). It took so doing, but I found the command.
Netdom renamecomputer oldname /newname:newname /userd:someuser /passwordd:*
Replace the computer names with valid ones and a domain admin user, and the command will prompt for your password. That’s it, reboot and you’re set!
I’ve been beating my head against the wall for a week on trying to forcibly remove a corrupted Exchange 2007 install on one of my servers. The AD Configuration tree became corrupted and a restore did not fix it, so I rebuilt a new server and migrated the mailboxes there. Problem solved! Except, now how do I remove the old server…when I try to uninstall, I get warned that Public Folder database still has replicas. Well, the only way to get rid of that is to replicate them to another server, but that’s not possible with this crippled server.
Solution? Delete the database from the configuration partition of Active Directory manually. To do so, you need to launch an ADSI edit session in the MMC and add the ADSI snap-in. This requires the Server 2003 Resource Kit Tools or the Remote Server Admin features for AD in Server 2008 and Server 2008 R2. I usually go to a domain controller to do this, as it has the ADSI plugin already installed.
Once connected, expand the tree to your server in question. You’ll find the storage group with your public folder store listed:
There, you will find the store in the right-hand pane:
All set! I successfully uninstalled Exchange 2007 from this server as soon as that was done. Since it contained no vaild public folders, I didn’t care if any data was lost. But be careful, it will ruin your public folder stores if you have not successfully and verifiably replicated the public folders to your new server.