How to use Rescue Mode on Windows Cloud?

 

Today most of the businesses are using the Windows cloud server for their website and the reason behind it is that they can easily manage and handle their website. And today if you are using Windows cloud server for your website and now if you are looking for information how to use Rescue Mode on Windows Cloud Servers then here is the complete information on it. Rescue mode is an upkeep express that can permit you access to an inert/ unresponsive server. You can use this to fix the configuration problems or to copy your data and files and move those to another server.

 

You will get a temporary password once after the rescue images has completed. And you need to copy that password if you wish to enter into your server in rescue mode through an SSH client. So once after entering the rescue mode, you will have 24 hours to fix your case before it automatically reverts back to the previous instance.

 

>>> Windows 2008 SP2 rescue type

 

First, you need to enter into your computer management, then you need to right click on disk 1 and select on-line. So this will automatically assign the volume a drive letter, usually D:. So today if you are using Windows 2008 SP2 then the BCD store will stay on the System Bar. And when fixing up the bootloader you need to point to the BCD store. The bar setting will be the drive where the location of the System Distribution. Along with that you also need to run bcdedit and point it to your original drive’s store:



For Windows 2008 SP2, the BCD store will stay on the System Bar. When fixing up the bootloader, you’ll need to point to the BCD Store. The partition setting will be the drive where the location of the System Partition (where \Windows is located). The idea is we need to put the correct disk signature into the BCD store, so that Windows can boot properly. You’ll need to first run bcdedit and point it to your original drive’s store:

 

Microsoft Windows [Version 6.0.6002]

Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

 

C:\Users\Administrator>bcdedit /store d:\boot\bcd

 

Windows Boot Manager

--------------------

identifier              {bootmgr}

device                  partition=C:

description             Windows Boot Manager

locale                  en-US

inherit                 {globalsettings}

default                 {ntldr}

displayorder            {1d25cc4a-fc03-11de-b973-d1d82d39e489}

toolsdisplayorder       {memdiag}

timeout                 30

resume                  No

 

Windows Boot Loader

-------------------

identifier              {1d25cc4a-fc03-11de-b973-d1d82d39e489}

device                  partition=C:

path                    \Windows\system32\winload.exe

description             Microsoft Windows Server 2008

locale                  en-US

inherit                 {bootloadersettings}

osdevice                partition=C:

systemroot              \Windows

resumeobject            {1d25cc4b-fc03-11de-b973-d1d82d39e489}

nx                      OptOut

 

Now in that, you need to take the unique identifier under the Windows Boot Loader section. So once after identifying you need to use the appropriate one.  And the default path for the BCD store is \boot\bcd so if the drive you are working with is D:, then the full path is D:\boot\bcd. Use the below command

 

bcdedit /store <full path to BCD store> /set <Windows Boot Loader Unique Indentifier> osdevice partition=<drive letter where original \Windows folder resides>

bcdedit /store <full path to BCD store> /set <Windows Boot Loader Unique Indentifier> device partition=<drive letter where original \Windows folder resides>

bcdedit /store <full path to BCD store> /set {bootmgr} device partition=<drive letter where original \Windows folder resides>

bcdedit /store <full path to BCD store> /set {memdiag} device partition=<drive letter where original \Windows folder resides>

bcdedit /store <full path to BCD store> /set {ntldr} device partition=<drive letter where original \Windows folder resides>

 

Below is the sample output from the BCD command:

 

C:\Users\Administrator>bcdedit /store d:\boot\bcd /set {1d25cc4a-fc03-11de-b973-d1d82d39e489} osdevice partition=d:

The operation completed successfully.

 

C:\Users\Administrator>bcdedit /store d:\boot\bcd /set {1d25cc4a-fc03-11de-b973-d1d82d39e489} device partition=d:

The operation completed successfully.

 

C:\Users\Administrator>bcdedit /store d:\boot\bcd /set {bootmgr} device partition=d:

The operation completed successfully.

 

C:\Users\Administrator>bcdedit /store d:\boot\bcd /set {memdiag} device partition=d:

The operation completed successfully.

 

C:\Users\Administrator>bcdedit /store d:\boot\bcd /set {ntldr} device partition=d:

The operation completed successfully.

 

>>> Windows 2003 rescue type

 

In here you need to enter to your computer management.  And in there you need to right click on Disk 1 and need to select on-line. Now it will on-line the disk and it will set the System Reserved Partition to D: and your original storage volume to E:. But occasionally it will flip the drive order  so the System Reserved Partition is E: and the original storage volume is D:.

 

And in Windows 2008 R2, the BCD store will reside on the Boot Partition which is 100MB in size. So when fixing up the bootloader, you’ll need to point to the BCD Store. The partition setting will be the drive where the location of the System Partition (where \Windows is located). You’ll need to first run bcdedit and point it to your original drive’s store:

 

Microsoft Windows [Version 6.1.7600]

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

 

C:\Users\Administrator>bcdedit /store e:\boot\bcd

 

Windows Boot Manager

--------------------

identifier              {bootmgr}

device                  partition=E:

description             Windows Boot Manager

locale                  en-US

inherit                 {globalsettings}

default                 {ntldr}

resumeobject            {ca73fe20-fc0c-11de-8f38-8e2c5384be89}

displayorder            {ca73fe21-fc0c-11de-8f38-8e2c5384be89}

toolsdisplayorder       {memdiag}

timeout                 30

 

Windows Boot Loader

-------------------

identifier              {ca73fe21-fc0c-11de-8f38-8e2c5384be89}

device                  partition=C:

path                    \Windows\system32\winload.exe

description             Windows Server 2008 R2

locale                  en-US

inherit                 {bootloadersettings}

recoverysequence        {ca73fe24-fc0c-11de-8f38-8e2c5384be89}

recoveryenabled         Yes

osdevice                partition=C:

systemroot              Windows

resumeobject            {ca73fe20-fc0c-11de-8f38-8e2c5384be89}

nx                      OptOut

 

Next, you need to take the unique identifier under the Windows Boot Loader section. And use the below BCD command

 

bcdedit /store <full path to BCD store> /set <Windows Boot Loader Unique Indentifier> osdevice partition=<drive letter where original \Windows folder resides>

bcdedit /store <full path to BCD store> /set <Windows Boot Loader Unique Indentifier> osdevice partition=<drive letter where original \Windows folder resides>

bcdedit /store <full path to BCD store> /set {bootmgr} device partition=<drive letter where original \Windows folder resides>

bcdedit /store <full path to BCD store> /set {memdiag} device partition=<drive letter where original \Windows folder resides>

 

Following is sample output from the BCD command:

 

C:\Users\Administrator>bcdedit /store e:\boot\bcd /set {ca73fe21-fc0c-11de-8f38-8e2c5384be89} osdevice partition=e:

The operation completed successfully.

 

C:\Users\Administrator>bcdedit /store e:\boot\bcd /set {ca73fe21-fc0c-11de-8f38-8e2c5384be89} device partition=e:

The operation completed successfully.

 

C:\Users\Administrator>bcdedit /store e:\boot\bcd /set {bootmgr} device partition=e:

The operation completed successfully.

 

C:\Users\Administrator>bcdedit /store e:\boot\bcd /set {memdiag} device partition=e:

The operation completed successfully.

 

>>> Windows 2003 rescue behavior

 

So now you will be in rescue mode, so you'll need to go to disk management and assign the secondary disk a drive letter in order to manipulate the original volume. Once everything is done exit from rescue mode and your cloud server will reboot normally.