My IT Blog

“Each IDE controller can have two devices. You can not boot from a SCSI controller. This means an IDE disk will be required. The boot disk will be IDE controller 0 Device 0. If you want a CDROM it will consume an IDE device slot.” Source:   MSDN Blog The hypervisor that runs the virtual BIOS does not support booting from a SCSI controller, today, but it does support the following boot devices: CD IDE Legacy Network Adapter Floppy The root reason is SCSI in a synthetic device and there is no VMBUS until after boot. One might think that this shouldn’t be a problem, after all, the virtual machines can still boot from regular IDE-based virtual disks. So where’s the catch? The main problem is related to the fact that in Virtual Server, virtual SCSI controllers have major performance benefits over virtual IDE controllers. In Virtual Server, it is recommended to attach the Virtual Disks to one or more SCSI controllers to improve disk input/output (I/O) performance. IDE is limited to

 Active Directory enables single sign on to access resources on the network such as desktops, shared files, printers etc. Active Directory provides advanced security for the entire network and network resources.  Active Directory is more scalable and flexible for administration. Functional levels help the coexistence of Active Directory versions such as, Windows NT, Windows 2000 Server, Windows Server 2003 and Windows Server 2008. The functional level of a domain or forest controls which advanced features are available in the domain or forest. Although lowest functional levels help to coexist with legacy Active Directory, it will disable some of the new features of Active Directory. But if you are setting up a new Active Directory environment with latest version of Windows Server and AD, you can set to the highest functional level, thus all the new AD functionality will be enabled. Windows Server 2003 Domain Functional Levels: Windows 2000 mixed (Default), Windows 2000 native, Wind

ESXi 5.0 To avoid the rather complex set of instructions that you needed to follow in 4.1, VMware introduced new  detach  and  unmount operations to the vSphere UI & the CLI. As per  KB 2004605 , to avoid an APD condition in 5.0, all you need to do now is to  detach  the device from the ESX. This will automatically unmount the VMFS volume first. If there are objects still using the datastore, you will be informed. You no longer have to mess about creating and deleting rules in the PSA to do this safely. The steps now are: Unregister all objects from the datastore including VMs and Templates Ensure that no 3rd party tools are accessing the datastore Ensure that no vSphere features, such as Storage I/O Control or Storage DRS, are using the device Detach the device from the ESX host; this will also initiate an unmount operation Physically unpresent the LUN from the ESX host using the appropriate array tools Rescan the SAN

# setterm -powersave off -blank 0 Useful on the console of virtual hosts in vmware or virtualbox, for example.

What is an Inventory? An Inventory is the process of mounting media in the drive and reading the media label, which is then displayed in the  Devices  view. If this is the first time that Backup Exec ™ has encountered this media, the media label is also added to the  Media  view. Note : Each time new tape is introduced in the tape drive or robotic library, it must be inventoried so that the Backup Exec database gets updated with the new tape Information. To Inventory a Tape/Robotic Library: 1. Insert the tape 2. Click the  Devices  tab 3. Select the correct tape drive/robotic library slot 4. Right-click on the tape drive/robotic library slot and select  Inventory  (Figure 1) Figure 1 The inventory will complete and should display the correct tape name. What is a Catalog? When cataloging a tape, Backup Exec reads the header information from the tape and stores it in a file on the hard drive. The information contained in the catalog includes, but is not limited

Instead of configuring a virtual machine as a DHCP server, you can use the virtual DHCP server for your virtual network. To configure the virtual DHCP server: 1. Open the  Virtual Server Administration Website . 2. Under  Virtual Networks , select Configure  and then click the virtual network. 3. In  Virtual Network Properties , click  DHCP server . 4. Check the  Enabled  checkbox, then configure the necessary DHCP server options. 5. Click OK.

When the Remote Desktop Client is exited by pressing the ‘X’ on the control panel the remote session continues to run on the server even though no client is connected. Next time the user connects the desktop session will appear exactly as it was left before. To end the session select Start in the remote desktop session, click on the right arrow button in the bottom right hand corner of the menu and select Log Off. This will close down the remote desktop session and close the remote desktop client.

I always wonder how many throughput does a Virtual Machine consume when running in Hyper-V Host. Not always we dedicate a NIC for a Virtual Machine. For better consolidation, we always share several Virtual machine within a 1 Gbps NIC. Let say, you have 4 Virtual Machines running and share on 1 Gbps NIC. Will each Virtual Machine consume and limited to 250 Mbps? Well not really. Some VM will consume more throughput than 250 Mbps and will eventually impact the performance for the rest of the VM. This is what i found out when testing Hyper-V Vnext which seem like solving this case. On Virtual Network, you can configure to set minimum and maximum throughput per Mbps on each virtual machine. Great right…I’m excited to wait this feature available on next release of Hyper-V.