How to rename a Windows Server 2008 Domain Controller
At my company we develop on virtual machines, the problem is that we create a new VM for every client. Since there is a lot, we have a base VM setup up with Windows Server 2008 R2, and SQL Server 2008 R2. This is a master VM and gets copied to create a client VM every time. The problem with this is that it is also setup as a local domain controller. Renaming a DC is a risky business, but I found a great post on how to use tools provided by Microsoft to rename a server that is a DC, and this is a pretty simple three step operation:
There is only one requirement, the user running these commands must be a domain admin. So open a Command Prompt window, and type the following commands:
NOTE: for this I am going to use the following details:
- Current name: jnbapp.dev.local
- New name: devapp.dev.local
- Domain: dev (dev.local)
- netdom computername jnbapp.dev.local /add: devapp.dev.local
- netdom computername jnbapp.dev.local /makeprimary: devapp.dev.local
- You must now restart the machine, you can’t skip this step !!
- Once restarted: netdom devapp.dev.local /remove:jnbapp.dev.local
netdom is tool that you can use to do many operations, but here we are telling it that we want to modify the “computername” settings.
Once you have done those 4 simple steps, your DC is now renamed.
Disclaimer:
Please read the disclaimer if you plan on using anything from this article.
Help Test Net Framework 4 Beta 2 with Windows Update
I follow Scott Hanselman’s blog and he is a Microsoft fundi, he works for them and he posts regularly about the goings on at Microsoft. One of his posts recently caught my eye and I was glad to see it.
The .Net framework team are allowing people to test the latest Beta release of the .Net 4 client profile via the windows update. The update will be a recommended update when it is officially released about 6-8 weeks after the release of .Net Framework 4.
Below is comparison of the 4 client profile and 3 client profile.
| .NET Framework 3.5 SP1 Client Profile | .NET Framework 4 Client Profile |
| Web Install | Local Package & Web Install |
| Only Windows XP SP2 or SP3 and x86 architecture. | All platforms and CPU architectures supported by the full .NET Framework 4 Beta 2 except IA64. |
| Separate from the framework. | Part of the full .NET Framework. The .NET Framework is made up of the Client Profile and Extended components that exist separately in Add or Remove Programs. |
| Windows Update will upgrade it to the full .NET Framework. |
Independent component.
|
if you want to test the Beta, then here is how you go about it:
if you have no dot net 4 bits on your machine, Just make a text file with some meaningful name and make sure the file extension is .reg, and put the following text in it:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4B2WU]"OptIn"=dword:00000001
then save and close it, and double click on the file and it will insert the registry key and you will be able to install the client profile from windows update.
You can do it from an administrator command prompt if you want:
reg.exe add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4B2WU" /v OptIn /t REG_DWORD /d 1 /f
I have heard that if you have any .net 4 components installed already, that the client profile will not install.
When they release the client profile it will install over the beta install and will upgrade it.
If you experience any problems, just remember it can be uninstalled, but do report any issues you have at The .Net Framework 4 Setup & deployment support forum.
about me
I am a C#, Silverlight, K2 workflow and Sharepoint Consultant, living and working in Johannesburg, South Africa. I have a passion for teaching people anything I can in order to spread the knowledge and skills I have. You can follow me on twitter at @MrThirsty.