Saturday 10 January 2015

How to clone a WFE/ Application server in SharePoint Farm using SYSPREP?


There could be different ways to add a new server in existing environment. Many organization can find cloning is simplest way to replicate all customization in new server. Remember, cloning SharePoint Farm server is not supported by Microsoft.
But you can go by this strategy to save some time you can clone existing WFE by following below steps:
     1.    Put it offline to not interfere with current Farm
     2.    Remove all Application Pools and Sites in IIS
     3.    Remove SharePoint Logs
     4.    Do SYSPREP and then connect it to Farm with different name.

This tool SYSPREP stands for System Preparation tool (more info here: http://technet.microsoft.com/en-us/library/cc721940(v=ws.10).aspx ). When launched it does few actions that will prepare the server for duplication like:
  •  Removes system-specific data from Windows like the server name, the network settings (IP and MAC addresses)
  •  Rearming the license and activation data
  •  Remove the SID and domain related data

For SharePoint 2010 & 2013 there are components that will endure a “SYSPREP” than others:
·   SharePoint components that will endure a SYSPREP are:
  • Server Roles configure during pre-requisite
  • SharePoint binaries
  • Language Packs
  • Service Packs
  • Cumulative Updates
  • Hotfixes


·   The SharePoint components that won’t endure a SYSPREP and give an unsupported server are:
  • Every tasks related to the configuration wizard, Central Administration and farm settings
  • SharePoint server member of a SharePoint farm cannot be used to create a clone or template


While using cloning do not take clone of a standalone server.
I recommend you do fresh install (OS, SP, language packs, Updates), but do not connect to Farm, then do SysPrep and save this image for future use (clonnable).

No comments:

Post a Comment