Showing posts with label Windows 8. Show all posts
Showing posts with label Windows 8. Show all posts

Thursday, December 11, 2014

Extending VHD / VHDX Volume

I have prepared the VHDX (or VHD in some cases) and it’s SYSPREP.  Now my C Drive is only 60GB but I would like to extend the hard disk to 100GB, to enable for me to install other applications on the C Drive.

I’m going to share how I do it.

My VHD is in the external drive (USB connected Hard Drive). 

Location E:\VHD\Demo

The VHD File is WIN81-ENT-x64-SYSPREP1.vhdx

image

I mount the drive to check on the space

image

As you can see it’s about 60GB. I’ll unmount and show the steps using DISKPART command

The command as follow :

  • Open Command Prompt with Administrator rights
  • Key in DISKPART
  • Next key in Select the Disk of where your VHD is located. For me is located at E Drive.  Therefore I key in as select vdisk file=”E:\VHD\Demo\WIN81-Ent-x64-SYSPREP.vhdx” 
  • Next to expand the TOTAL size of the VHD. I key in as expand vdisk maximum=100000
  • Next key in attach vdisk
  • Then key in list disk to view. If it’s not online then key on ONLINE DISK. It should be online automatically.

image

  • Next key in list volume
  • As you can see the volume shows as still 60GB
  • I key in as select volume 6
  • Key in extend
  • Key in list volume to see the new size

image

  • Opening up the attach disk, now it’s close to 100GB

image

Now I’m done, I would like to detach the VHD

Back to the DISKPART command prompt

  • Key in detach vdisk
  • Key in exit to quit diskpart from command prompt

image

In summary, I’ve keyed in as follow :

  • DISKPART
  • select vdisk file=”E:\VHD\Demo\WIN81-Ent-x64-SYSPREP.vhdx 
  • expand vdisk maximum=100000
  • attach vdisk
  • list disk
  • list volume
  • select volume 6
  • extend
  • list volume 
  • detach vdisk
  • exit 

Command in diskpart is in GREEN, you change those values in PINK 

Hopefully the steps are helpful.

keywords : diskpart, extend vhdx, extend vhd, expand volume size

Wednesday, February 19, 2014

Performance Monitor–Create Data Collector Set Greyed Out

Recently I tried to create a New Collector Set for the Performance Monitor for one of the customer’s request.  When I launched the Performance Monitor, click to create a new Data Collector Set and found it was greyed out.

image

After some troubleshooting, it seems that a service related to it was disabled.

image

All was done is click on the Properties of the Task Scheduler and select as Automatic Start Up.   You can click on the start to get the Task Scheduler instead of rebooting for this round.  Next time the server reboots, it will auto-start the services cause you have made the changes.

Once that’s done, go back to the Performance Monitor and create the new Data Collector Set, the Next button is no more grey out.

Hope this helps Smile.

keywords : Performance monitor, next button grey out greyed out, task scheduler, cannot create data collecter set

Wednesday, February 5, 2014

Logman Error : The System cannot find the path specified

 

As I was trying to create a Log using the LOGMAN command I hit the issue

image

It states as “The system cannot find the path specified

After some findings, the issue was the Task Scheduler was not started.  Therefore I went into the Services and enable and start the Task Scheduler.

image

Once Task Scheduler is started, I executed the command with no issue.

image

Hope this helps you.  Thanks to TechNet Social.

keywords : Logman, perfmon, system cannot find path specified, diagnostic tool.

Wednesday, November 20, 2013

Remove Hidden Devices (does not display devices that are not connected)

I was having issues of booting up the VM.  It was corrupted of the XML for the VM.  So I re-created a new VM but attach back the Hard Disk from the old VM.

I boot up the new VM, then I was configuring back the IP address and suddenly it doesn’t allow me to input the IP address cause it indicated that it has been used.  I went into the Device Manager and see no items, even though I select “show hidden devices

The steps are the following that I do :

  • Open Command Prompt (run as administrator)
  • type devmgr_show_nonpresent_devices=1 then hit [Enter]
  • type start devmgmt.msc then hit [Enter]
  • Then click Show hidden devices in the View Menu
  • Remove the unnecessary devices (e.g. the Microsoft Hyper-V Network Adapter)

image

  • Then return to your NIC to input the IP address. 
  • It works for me !!

Thank you and hope this helps.

keywords : Device Manager does not display devices that are not connected to the Windows XP or Windows 2003 -based computer, Device Manager displays only non-Plug and Play devices, drivers, and printers when you click Show hidden devices on the Viewmenu. Devices that you install that are not connected to the computer (such as a Universal Serial Bus [USB] device or "ghosted" devices) are not displayed in Device Manager, even when you click Show hidden devices.

Thursday, July 4, 2013

How To Convert Physical to VHD

If you do not have the Virtual Machine Manager (VMM) to help you to convert the Physical Machine Hard Disk, then you can use another tool from the SYSINTERNALS .

To download this tool from the Microsoft Technet click Disk2vhd v1.63

Hope this helps as it has helped me.

keynote : Disk to vhd, physical to virtual, microsoft sysinternal, disk2vhd, VMM,

Thursday, March 14, 2013

How to Connect a Drive Recognize in Remote Desktop Session (MSTSC)

Over here I have a situation, I can access to the remote session (Terminal Services) to a server, but I can’t access it physically.  I need to copy some of the files into the server for certain application update.  I can’t use the \\servername\<drive> either from my station to copy from my drive to the server. 

Here’s the solution that I would like to share.

  • Run the Remote Desktop Session (or type ‘mstsc’ from RUN box)
  • Don’t connect it yet.
  • Click on the “Local Resources” tab

image

  • In the Local devices and resources click More

image

  • Select the drive that you want to attach, then click OK.

image

  • Key in the computer name and username.
  • Click “Connect”.
  • Then you can see the extra drive in the remote server.

Hope this guide helps you.

keywords : remote access, mstsc, attach external drive to remote access, attach external drive to be recognize by terminal services or remote access. USB drive recognize by remote access.

     

Tuesday, March 12, 2013

Installing .NET 3.5 Offline or Manually

 

Part of the DPM 2012 requirement is install the .NET 3.5.  Somehow in this project, there was no internet connection for it.  So I’m going to share with you the steps :

  1. Insert your Windows 2012 Installation Disk into your DVD Drive.
  2. Now run Command Prompt as Administrator. (Hint: Start > Type cmd > Now right click on Command Prompt and hit on Run as Administrator from the bottom)
  3. Now key in following command or copy and paste it in the command prompt window.
  4. Now .Net Framework will be installed within few minutes.

 

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:z:\sources\sxs


Note : z is the drive letter of DVD drive. Change it with your DVD drive letter. 

keynote : .NET 3.5 .Net DPM 2012 requirement, how to install .net 3.5 manually install .NET offline

Monday, November 26, 2012

Activating Windows 8 or Server 2012 License Key

The steps shown here is that in an environment that has no domain and/or no KMS server running. Activating the Windows 8 and Server 2012 License is different from it’s predecessors.  This needs to be done from the command prompt. To activate it, there must be a connection out to the internet.

Using the command prompt (“Run as Administrator”) key in as below follow by the license key.

C:\> slmgr.vbs /ipk <product key from MSDN (MAK)>

* Note : insert your license key in the PINK colour space then hit ENTER.

The above command will install the product key. Then next to key in the following command to activate

C:\> slmgr.vbs /ato

To check if it’s activated key in as below :

C:\> slmgr.vbs /dlv

Hope the above helps.  Thank you.

keynote : Windows 8 activation, Windows 2012 activation, key activation, license activation, license key activation.

Tuesday, June 19, 2012

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

 Windows8-11

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

Windows8-2

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

Windows8-3

Step 1.5 Create the VHD with Dynamic Expansion with 60GB

Windows8-4

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.

Windows8-8

Step 1.8  End result should be like below :

Windows8-12

 

 

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]

Windows8-17

Step 2.4 Execute the command as below :


Set-ExecutionPolicy Unrestricted
 

 

Windows8-19

 

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

image

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

Windows8-26

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

Windows8-27

 

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

Windows8-30

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

Monday, April 16, 2012

Presenting iSCSI (in a VM) to Windows Server 8 (Physical Host)

I’m going to share with you today on how I present iSCSI LUN (running as a VM Server 2008 R2) to a physical Host that is running Windows Server 8 (Running Hyper-V).  This Windows Server 8 is also running as Hyper-V role and hosting the VM that earlier I mentioned running

In summary is as below :

image

image

Host : From Windows 8 Server  (Part 1)

Hyper-v-1

  • Create a folder and label it as VHDs

Hyper-v-3

  • Launch the Hyper-V.
  • Maneuver to the SC-Fileserver-iSCSI settings
  • Click on the SCSI Controller and add Hard Drive.

Hyper-v-5

  • Click New.

Hyper-v-6

  • Click Next >

image

  • Select VHDX and click Next

 

Hyper-v-8

  • Click Next >

Hyper-v-10

  • After creating the file, it should end with vhdx extension.  The location of the folder is the same as created in Windows Explorer.

 

Hyper-v-11

  • Put in the size of the virtual hard disk and click Next.

Hyper-v-12

  • Review and click Finish.

Hyper-v-13

  • Click apply and then OK.

Hyper-v-15

  • In the Windows Server 8, launch the iSCSI Initiator.

image

  • If the iSCSI server is not running, click Yes to start it.

Hyper-v-17

  • Key in the IP address of the iSCSI IP address of the server.  In my case is 10.52.52.16.
  • Click Quick Connect.

Hyper-v-18

  • Click Done.
  • Now we switch on to the server that is the iSCSI target.

 

iSCSI Target : SC-FILESERVER-iSCSI (Part 2)

 

SC-Fileserver-2

  • Launch the Server Manager in the SC-FILESERVER-ISCSI
  • Then scroll down to the Disk Managert
  • Initialize the disk (that was just presented)

SC-Fileserver-1

  • Launch the Microsoft iSCSI Software Target.

SC-Fileserver-3

  • Right-Click New Simple Volume and then quick format it.
  • Once it’s done click Finish.

SC-Fileserver-10

  • Launch the iSCSI Target in the VM
  • Scroll to the iSCSI Targets.
  • Right-click on the right panel and then select Create iSCSI Target.

SC-Fileserver-12

  • Key in a meaningful name and click Next.

SC-Fileserver-13

  • Click Browse.

SC-Fileserver-14

  • The step performed earlier, from the host has triggered an entry into the iSCSI initiators listing
  • Select it (in  my case is C02), then click OK.

SC-Fileserver-15

  • Click Next then click Finish.

SC-Fileserver-17

  • Click on Devices on the left panel
  • Then Right-Click on the right panel and select Create Virtual Disk.

SC-Fileserver-18 SC-Fileserver-19

  • Click Next.
  • Then click Browse.

SC-Fileserver-21

  • Key in the File with .vhd extension

 

image

  • Key in the Size of the VHD and then click Next.
  • Then click until Finish.

SC-Fileserver-31

  • In the iSCSI Target, select Devices
  • Select the Disk that was just recently presented, right-click and Assign/Remote Target.

 

SC-Fileserver-32     SC-Fileserver-33

  • Click Add
  • Select the Target that was created.
  • In my example is Hyper-V-DPM.  After selecting click OK.
  • Now it’s back to the Host (physical).

 

Windows Server 8 Host Server (Part 3).

Hyper-v-21

  • In the iSCSI inititor, click on Refresh.

Hyper-v-22

  • Then click Connect.

Hyper-v-24

  • Click OK.

image

  • Now it’s ready for DPM usage.

image

  • Now the storage is ready for Hyper-V Host to use.  In my case, this LUN has been dedicated for DPM only.

Hope the above helps you for your testing or Lab environment.

      note : Hyper-V Windows 8 DPM storage, DPM 2012 storage provision from internal iSCSI or storage.