MicrosoftCategory Archives

Deploying DaRT to the PC (Adding DaRT to the Boot Menu)

Deploying the DaRT image in a recovery partition to each PC means you always have the right DaRT image when you need it for each PC. That means if you have Windows 7 x64 you need DaRT image created only for Windows 7 x64. DaRT can be placed in its own partition or over the top of the WinRE recovery partition for F8.

In this post I would like to describe how to manually deploy DaRT image to the Boot Menu on your PC’s or laptops. As always I will describe entire procedure through lots of pictures.
This is a very simple procedure, and I hope it will help someone.

First of all create your DaRT ISO image with the desired settings and files.

Create a partition on the target PC equal to or greater than the size of your DaRT ISO. The size of the DaRT ISO has approximately 210 MB for Windows 7.
In my scenario, I created \F: partition with 1GB size.

Extract the files from the DaRT ISO and copy them to your target partition, also on the target partition create folder named Windows\System32 and from C:\Windows\System32 copy winlogon.exe to that folder. Just like on the pictures below.

OK, now follows the most important part!
Create script with relevant command line. In my scenario follow the script described below.

bcdedit /create {ramdiskoptions} /d “IT Pro UG DaRT Demo”
bcdedit /set {ramdiskoptions} ramdisksdidevice partition=F:
bcdedit /set {ramdiskoptions} ramdisksdipath \boot\boot.sdi
bcdedit /create /d “IT Pro UG DaRT Demo” /application OSLOADER –>Record the GUID returned from this command
bcdedit /set {GUID} device ramdisk=[F:]\sources\boot.wim,{ramdiskoptions}
bcdedit /set {GUID} path \windows\system32\winload.exe
bcdedit /set {GUID} osdevice ramdisk=[F:]\sources\boot.wim,{ramdiskoptions}
bcdedit /set {GUID} systemroot \windows
bcdedit /set {GUID} winpe yes
bcdedit /set {GUID} detecthal yes
bcdedit /displayorder {GUID} /addlast
bcdedit /timeout 20

Type the script in notepad and save it as “DaRT.bat”. This is an automated script.

If you want to run script manually open command prompt and type command lines described below.

bcdedit /copy {current} /d “IT Pro UG Dart Demo”
bcdedit /set {GUID} device vhd=[G:]\sources\boot.wim
bcdedit /set {GUID} osdevice vhd=[G:]\sources\boot.wim
bcdedit /set {GUID} detecthal on
bcdedit /timeout 20

If you want to know more about how to configure Boot Configuration Data follow this link.

At the end you have new boot entry on your PC or laptop.

If you need repair your or users PC’s or laptops, restart the machine end boot from your newly created recovery partition.

In rare support scenarios where the hard drive is severely damaged (eg. MBR failure), booting from the hard drive image of DaRT is not an option and a CD/DVD or USB will need to be used.

In one of the following posts I will describe how to use a Remote Connection with the DaRT7 and which all features we have for that scenario.

That’s it for today!

Romeo Mlinar

February 1, 2012

Administration, DaRT, Microsoft, Recovery, Windows 7, Windows Server

5 comments

Adding Hyper-V host to VMM 2012 RC that is in Perimeter network (DMZ)

In this post I would like to describe how to add Hyper-V host to Virtual Machine Manager 2012 RC when host isn’t in a trusted domain. In this scenario I ‘ll add Hyper-V host which is in Perimeter network.

To do that you must meet all requirements.

Step 1.

First you need to install VMM Local Agent on Hyper-V host just like in the picture below.

Step 2.

Go to your VMM 2012 RC Server, open Console –> VMs and Services –> right click on selected container –> Add Hyper-V Hosts and Clusters and follow procedure.

Because your Hyper-V host is in the Perimeter network you need to mark that option.

Fill in all fields. Pay attention to Security file path.

We are done with the wizard.

Our Hyper-V host with guests appeared in the VMM Console.

Step 3.

The most important thing if you want to connect via Console or via RDP to VM’s through VMM Console is to export Hyper-V server certificate and import to VMM server. How to do that? Follow instructions below.

On Hyper-V server open MMC and Add/Remove Snap-in, add Certificates –> Service Account –> Local Computer. Expand WinRM\Trusted Root Certification Authorities –> Certificates. Export certificate and import to your VMM server.

After you import certificate on VMM server you will be able to connect via Console or via RDP.

Done!

Romeo Mlinar

January 27, 2012

Hyper-V, Microsoft, SCVMM, Virtualization

15 comments

Transferring FSMO roles (How to Transfer FSMO Roles?)

Today I had to transfer FSMO roles from one domain controller to another. In this post I want to explain how to do. First of all I want to explain what is FSMO (Flexible Single Master Operation).

We have a five FSMO roles;

1. Schema – Forest-wide and one per forest.
2. Domain Naming – Forest-wide and one per forest.
3. RID – Domain-specific and one for each domain.
4. PDC Emulator – Domain-specific and one for each domain.
5. Infrastructure – Domain-specific and one for each domain.

If you want to transfer the FSMO role must be a member of the following group:

In most cases we keep the FSMO role holders in the same DC (domain controller) as has been configured by Active Directory installation process.
The transfer of an FSMO role is the suggested form of moving a FSMO role between DCs and can be initiated by the administrator for some reason or by demoting DC. The transfer process is not initiated automatically by the operating system.
FSMO role transfer initiated by the administrator is very simple, but when you have demoted DC then you have a problem.
The process of moving the FSMO role from non-operational role holder to a different DC is called Seizing, and is described in the Seize FSMO roles to a domain controller article.

You can transfer FSMO roles via ntdsutil.exe command-line or by using the GUI. If you prefer the GUI, you can use the following three MMC snap-in tools:
– Active Directory Schema snap-in (Schema master)
– Active Directory Domains and Trusts snap-in (Domain Naming)
– Active Directory Users and Computers snap-in (RID, PDC, Infrastructure)

NOTE: You must be logged on the target domain controller. If you are NOT logged onto the target domain controller, in the snap-in, right-click the icon next to Active Directory Schema, Active Directory Domains and Trusts and Active Directory Users and Computers and press Connect to Domain Controller. Select the domain controller that will be the new role holder and press OK.

Transferring the Schema Master via GUI.

1. Register the schmmgmt.dll library by pressing Start>Run and typing; regsvr32 schmmgmt.dll and Enter.

2. From the Run command open an MMC Console by typing MMC.
3. On the console menu, press Add/Remove snap-in and select Active Directory Schema.
4. Right-click the Active Directory Schema and press Operations Master.
5. Press the Change button and then press OK.

Transferring the Domain Naming master via GUI.

1. Open the Active Directory Domains and Trusts snap-in from the Administrative Tools folder.
2. Right-click the Active Directory Domains and Trust icon and press Operations Master, press the Change button.
3. Press OK all the way out.

Transferring the RID Master, PDC Emulator and Infrastructure Master via GUI.

1. Open the Active Directory Users and Computers snap-in from the Administrative Tools folder.
2. Right-click the Active Directory Users and Computers icon and press Operations Master.
3. Select the appropriate tab for the role you wish to transfer, one by one (RID, PDC, Infrastructure), and press the Change button.
4. Press OK all the way out.