MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.
This article explains about designing a disaster recovery plan for Roaming Profiles.
Have you ever wondered creating a disaster recovery plan for Roaming profiles without clustering. This is really interesting when someone wants to switch over Roaming profile in a network where one of Domain Controller is failing and other Domain Controllers are alive to serve the client requests.
Let's say you have two 100 client computers in your network and two domain controllers named: DC1 and DC2. All users have been configured with roaming profiles setup on DC1 and DC2. These users frequently log on to DC1 and switch over to DC2 in case of failure.
For some reasons, you want to create a disaster recovery plan for Roaming users - you want these users to switch over to DC2 and retrieve their roaming profile from DC2 in case of DC1 failure. Setup seems not so easy! but this is how you do it actually:
You need a startup script and deploy this script using Group Policy throughout the network.
This disaster recovery plan for roaming profiles can be designed by creating a Windows startup script. LOGONSERVER environment variable is common between these two DCs. You just need to set this in your script so that when script starts it should read the authentication server name and set in user's property using LDIFDE tool.
You can see LOGONSERVER by typing SET command at command prompt. This tells by which DC this client was authenticated.
In the above scenario clients roaming profile are located at DC1.
Netlogon finds a suitable domain controller for the client.
Sets the Environment variable: LOGONSERVER to the DC is about to authenticate client.
Startup script runs.
This script checks the path of Roaming profiles from the user's property using LDIFDE tool.
Script pings the domain controller (let's say client is configured to use romaing profiles on DC1 and DC2 is supposed to authenticate client in this regard.)
Script gets a "Request Timed Out" message from DC1.
Script assumes that this domain controller is not available on the network.
Then it takes the DC name from the LOGONSERVER environment variable and sets this LOGONSERVER in user's property and in registry as well : .
Netlogon passes control to Winlogon service.
Winlogon finally allows client to log on to computer.
Client logs on to computer. His profile path is checked and roaming profile is loaded from DC2 directly.
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition