Renaming anything in a Microsoft’s environment is a risky business. Whether you are thinking about renaming a Domain Controller, an Active Directory domain (you better get your resume updated first), Exchange Server 2007 (ouch!), or a Microsoft Office SharePoint Server (MOSS) 2007, you know it could potentially turn into a nightmare. Of course, a lot depends on your environment and the size and complexity of your network.<\/p>\n
I haven’t had the pleasure to actually rename a MOSS 2007 server in a production environment, but I ran into this blog by Mirjam van Olst. She explains the step-by-step procedure, in case you ever have a need to rename a MOSS server, so I thought I’ll share this with you.<\/p>\n
Renaming a MOSS server is meticulous job. If anything goes wrong along the way chances are that you need to reconfigure your whole MOSS environment.<\/em><\/p>\n Here are the steps to take, and the order in which to take them if you want to rename a server that has MOSS already installed and configured on it:<\/em><\/p>\n *** NOTE: Use only letters, digits and minus for the machine name (so no underscores), max 15 characters.<\/em><\/p>\n * Change each alternate access mapping for your MOSS\/WSS deployment in Central Administration: Your server is now renamed. Renaming anything in a Microsoft’s environment is a risky business. Whether you are thinking about renaming a Domain Controller, an Active Directory domain (you better get your resume updated first), Exchange Server 2007 (ouch!), or a Microsoft Office SharePoint Server (MOSS) 2007, you know it could potentially turn into a nightmare. Of course, a lot […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[54,11,38],"tags":[],"class_list":["post-796","post","type-post","status-publish","format-standard","hentry","category-sharepoint","category-tips-tricks","category-windows-2003"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
\n– Open Central Administration, “Operations” Tab, “Alternate access mappings” link
\n– Modify each mapping item to reflect your newly chosen server name<\/em><\/p>\n
\n* Use stsadm.exe to invoke the “renameserver” command option:
\n– Open a command prompt window
\n– cd “C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\12\\BIN”
\n– stsadm -o renameserver -newservername <newname> -oldservername <oldname><\/em><\/p>\n
\n* Rename your Server via Change Name Operation in Windows Server 2003:
\n– Start Menu | Control Panel | System, “Computer Name” tab, “Change” button.
\n– Input your new server name<\/em><\/p>\n
\n* Reboot the server NOW.<\/em><\/p>\n
\n* After reboot, open command prompt
\n– cd C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\12\\BIN
\n– stsadm -o updatefarmcredentials -userlogin <domainuser> -password <password>
\n– iisreset \/noforce<\/em><\/p>\n
\n* Check all application pool identities in IIS, update where the old machine name is still there.<\/em><\/p>\n
\n* If you already have a search index drop this, and rebuild it<\/em><\/p>\n
\n<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"