Booting up from VHD–Windows 2012 RC

As of today’s technology using Microsoft Windows 7 (Professional, Business or Ultimate), you can have wonders booting up from VHD (which means a single file) without meddling with your current working Operating Windows 7 System.

As of today I have here is a Windows Server 2008 R2 SP1 as the Operating System.   I’m going to share with you how I did it, to have the Windows Server 2012 RC boot up as VHD.

I referred to a couple of blogs and one of the blogs that I find it wonderful and informative is from Raymond Chow.

Here are the download list that needs to be downloaded before installation :

Windows 2012 RC	http://technet.microsoft.com/en-US/evalcenter/hh670538.aspx?ocid&wt.mc_id=TEC_108_1_33
Ultra ISO (if you don’t have utility to read ISO, then only you download and install)	http://www.ezbsystems.com/ultraiso/
Install – WindowsImage Powershell Script	http://archive.msdn.microsoft.com/InstallWindowsImage/Release/ProjectReleases.aspx?ReleaseId=2662

If you downloaded the ISO format, then it gives you the flexibility to prepare how much of Hard Disk space you would like to allocate for your Windows Server 2012 RC.  Of course there’s some preparation needs to be done before the VHD is build. 

However, if you decide to download the VHD ready format, then needs to jump to third part of this blog.

Part 1 – Preparation of Directory for PowerShell Script and VHD

Part 2 – Preparation of the ISO and getting VHD ready

Part 3 – Attaching the Windows Server 2012 VHD

 

Part 1 – Preparation of Directory for PowerShell Script and VHD

Step 1.1 Create a Directory to put in the PowerShell Script and also where your VHD (for the Windows Server 2012 RC) will reside in my example is D:\Windows8\VHD

Step 1.2 Using the Ultra ISO, abstract the install.wim to the D:\WINDOWS8\VHD directory

 1

 Step 1.3 Copy the Install-WindowsImage PowerShell script  into the same directory.  The end result is :

Step 1.4 From the Server Manager, expand to the Disk Management, create the VHD.

Step 1.5 Create the VHD with Dynamic Expansion with 60GB

Step 1.6 Initialize the Disk, then have it as a New Simple Volume.

Step 1.7 Next I assign it a drive letter. In my case I assign it as “W” drive.

Step 1.8  End result should be like below :

 

 

Part 2 – Preparation of ISO and Getting Windows Install into VHD

Next is we would like to have fresh Installation of the Windows 2012 RC into the VHD assign.

Step 2.1 Launch the Command Prompt and Run as Administrator

Step 2.2 Change the directory to where the location of the VHD and script is located.  E.g. D:\Windows8\VHD.

Step 2.3 Type powershell and then hit [Enter]

Step 2.4 Execute the command as below :

Set-ExecutionPolicy Unrestricted

 

 

Step 2.5 Take note of the Index of the various versions that is available.

Step 2.6 In my scenario, I’ve choosen the Windows Server 2012 RC Datacenter (Server with a GUI), therefore the Index is 4.  The command for the PowerShell would be :

.\Install-WindowsImage.ps1 –WIM D:\Windows\VHD\install.wim –Apply –Index 4 –Destination W:

Only those that is in pink in colour are the ones that is needed to change accordingly.  In my case, the WIM is in D:\Windows\VHD directory. Then next is Index 4, cause I chose for Datacenter with GUI and the Drive letter that is assigned for this VHD is W.

Step 2.7 The result should be

Step 2.8 Open up the Windows Explorer, should be able to see the following in W Drive.  It should be populated.

 

Part 3 – Attaching the VHD

Step 3.1 Exit from the PowerShell

Step 3.2 Key in the command below to add into your boot menu when starting up.  Change would be in the pink colour depending on where you install.  In my example my Windows 2012 RC is installed into the W Drive.

bcdboot w:\windows

Step 3.3 To view the entry, key in as the following

bcdedit /v

The result should be

Step 3.4 Dismount the drive that was use for the Windows Server 2012 RC installation (in my case is W Drive), then reboot the computer. 

Step 3.5 When computer is boot up, you’ll be presented with the Windows Server 2012 RC as a selection.

Happy trying and hope the steps is detail enough for you to begin to explore the Windows Server 2012 RC as VHD boot.  If there’s any errors please post it in this blog …. and if it’s successful ….. do post it too <grin>.

keywords : Windows Server 2012, Windows 8 Beta, Boot from VHD, Virtual Hard Disk boot, Windows Server 2012 RC

DPM–Deploying DPM Agent to Untrusted or Workgroup Computers

In today’s session I would like to share how you can deploy a DPM agent to a computer that is not part of your domain. 

Computer Name : SC-UNTRUST

DPM Server Name : SC-DPM2010.systemcenter.com

Firstly switch to the computer that is not part of your domain.  Then map to the DPM server using Net Use command.

Next open up the Explorer and browse to the directory of the of the mapping.

Double click on the DPMRA.msi to begin the installation.

Once it’s done, it will displayed as below. Press Enter to close the window.

Open up the command prompt in Administrator mode.  Change the directory to where the DPM agent is installed e.g.

C:\Program Files\Microsoft Data Protection Manager\DPM\bin

Then execute the command to have the computer to have the computer to pre-attach to the designated DPM server with the command :

SetDpmServer.exe –dpmservername SC-DPM2010 –isnondomainserver –username UNTRUST1

The changes will only be in pink colour according to your environment.  As shown above the SC-DPM2010 is where this untrusted computer will be attach to for the DPM backup.  As for the UNTRUST1 is a unique username.  It must be a unique username for each of the untrusted computer that will be supported by the DPM server.  You can use the unique username ONCE in the DPM server.

Once the command is executed, key in the password.  This password is needed when you attach the untrusted server in the DPM.

The end result will be as follow.

Now switch to the DPM server.  Launch the console to begin the installation of the DPM agent.

Select the Computer in a workgroup or untrusted domain and click Next.

Key in the Computer name, the unique username and the password (the same unique username and password that was created in untrusted computer earlier).  Click the Add button, then click Next.

In the Summary screen, click Attach.

Once it’s completed, click Close.

Lastly, remember to check the Password never expires in the local users in both the untrusted computer and also the DPM server.

Thank you and hope this guide is useful.

keywords : Untrusted computer in DPM,  DPM supporting untrusted computer or workgroup, workgroup computer in DPM, DPM 2007, DPM 2010, DPM 2012.

DPM–Data Protection Manager Client (client recovery issue)

After deploying the DPM agent into a Windows 7 Client and patch with the latest QFE, now it’s possible for the end-users to recover their files or folders on their own.  This is one of the great features.

After doing the synchronization and recovery point, I hit the error.  Below is the message when I click on the Recovery tab in the Data Protection Manager Client in the Windows 7.

Resolution :

First of all I browse to the registry using REGEDIT in the client (which mine is the Windows 7 PC that has joined to the domain). 

The path is as follow

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\ClientProtection

Next I create a Key.  The Key should be Multi-String Value

The Key Name should be ClientOwners

Once created, then insert the ClientOwners value in the format as below.

Once it’s done, click OK then reboot the PC.

Once the PC is rebooted, launch the Data Protection Manager Client in that particular PC. Click on the Summary tab and click Sync Now.

Once that is completed, then switch to the DPM server and then initiate a recovery point.

And when it’s completed in the DPM server, switch to the PC back.  Bring the Data Protection Manager Client, click on the Recovery tab.

In the Search for Recovery Point, click the search (just like a magnifying glass)

And now you can access the recovery from the DPM server to recover what was backup by the DPM for the client.

Thank you and hope this helps. 

Source from KB2465832

keywords : DPM found no recovery points which you are authorized to restore on the specified DPM server.  You can restore only those recovery points which you were an administrator at the time the backup was taken.  To restore other recovery points, contact your DPM administrator, or attempt to restore from another DPM. DPM 2010, DPM 2007, DPM 2012, client backup, DPM client, DPM workstation backup.

DPM–Creating DPM Protection group for Protecting Hyper-V Host Server 2008 R2 (Error ID : 31313)

 

Scenario : Installed DPM 2010 on a Hyper-V 2008 Server R2 SP1. 

The server name of this Hyper-V is B34.systemcenter.com

However when trying to create a protection group to protect the Hyper-V VM, it gives the error message (ID : 31313).  The server is already patched with the KB975354 as required by the error message.  Very weird !!  First time happening to me.

So after looking around found something that just works.

I launch the Microsoft SQL Server Management Studio (select the DPMDB database) and then key in the following in the New Query

use dpmdb Update tbl_am_installedagent Set ServerAttributes = 31 Where deleted = 0 and serverid in (select Serverid from tbl_am_server where serverName = 'b34.systemcenter.com')

Just replace the server name in the pink in colour with the correct server name (FQDN).  Execute it

The output as below :

After that I was able to create the protection group to Protect the VMs.  As I mentioned, it’s weird, very weird.  It doesn’t happen to my previous installations before.

Thank you and hope this helps you as it helps me.

Reading resource from here.

Key words : error ID 31313, KB975354 installed, Protecting Hyper-V with DPM 2010

DPM–Cannot Deploy DPM Agent to Server under same domain

There’s some weird cases going on in one of my deployments.  The server is joined to the same domain as the DPM server, however when wanted to deploy the DPM agent, the assign protected server refused to accept it.

The protected server is a HP Server.

Therefore, did a test in the lab, there was no issue.  However in the production site, there was issue.

The following was carried out :

• Uninstall the HP Server Tools and Management.
• Deploy the DPM agent through the trusted way.
• Install the HP Server Tools and Management

After the steps was carried out, then it works like a charm.  Hope this sharing benefits you.  Thank you.

keywords : DPM 2010, DPM 2012, Cannot backup domain.  Cannot deploy agent as trusted even though is in same domain as DPM server.

DPM–Critical Alert–SQL Log Backup job has detected a discontinuity in the SQL log chain for database

 

Today I’ve a scenario to share with you folks about the SQL Database backup (using DPM 2010 to backup).

The alert that I receive is as follow through the email :

After some investigation, found out that there’s a SQL Native Backup that is scheduled by the application team.  The DPM also uses the SQL backup engine before it’s data is transferred to the DPM.

It’s like 2 people trying to do the same job.  Coming to the extent, it might crash the database if not handled properly in long run.

Resolution :

Since the Application has a Native SQL backup scheduled to a folder e.g. F:\DB_Backup, then the protection group to protect this server was amended according to as below :

Removed the SQL Backup in DPM to protect the NOSTROLAB\QTNostro in the Protection Group Add in backup to protect the database backup folder i.e. F:\DB_Backup in the Protection Group

The above resolve the issue once and for all.

Hope the above helps you to resolve the issue of backing up the database with DPM.

keywords :  DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for database since the last backup. All incremental backup jobs will fail until an express full backup runs. DPM 2010, DPM 2012, DPM 2007,  Critical Alert

DPM–DPM to DPM Replication with DPM 2010 / DPM 2012 through Firewall

There was a request by one of the end users that they would like to bring down the Dynamic Ports range. Currently the Microsoft default Dynamic Ports are from 1024-65535.

Therefore the following are requested to be lock down.

The following steps are needed to be perform for all the DPMs and also the protected servers.

Now open up the command prompt (run as Administrator).

View through the Component Services from the Administrative Tools.

Scroll down to Windows Management and Instrumentation and then right click to view the properties :

The click on the Endpoints Properties of the TCPIP.

Should be able to see as above.

Next is to amend the Registry for the Dynamic Port range.  Execute the command with regedt32 and not regedit

Scroll down to the HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\

Create the key Internet

Then navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet to create the following

By end of the result, you should see the below.

Reboot the Protected Servers, Primary DPM & the Secondary DPM server

Configure the Firewall ports accordingly as below to allow the Primary DPM server and the Secondaray DPM server to communicate.  Also the firewall MUST allow the Secondary DPM server to communicate with the Primary Protected Servers by having the firewall ports configured too.

Thanks to the TechNet resource and also to Lai YS for his guide.

keywords : DPM to DPM replication, limit Dynamic ports, firewall configuration for DPM 2010 DPM 2007, Protected servers through firewall