Wednesday, February 29, 2012

INSTALLING A VIRTUAL OPERATING SYSTEM(HYPER-V) IN WINDOWS 2008

Open Server Manager and then navigate through the console tree to Roles -> Hyper-V -> Microsoft Hyper-V Server. If this is the first time that you have used Hyper-V, then you will be prompted to accept Hyper-V License Agreement. Once you accept the license agreement, the various Hyper-V options will be made available to you.
The first thing that you must do is to click on the Connect to Server link, located in the Actions pane. When you do, you will be prompted to select the computer that you want to connect to. Choose the Local Computer option, and click OK. You will now see the screen in
Figure A.
Figure A
This is the main screen that you will use for managing virtual machines.

Creating a New Virtual Server
To create a new virtual server, click the New -> Virtual Machine options found in the Actions pane. When you do, Windows will launch the New Virtual Machine Wizard. The wizard’s initial screen explains that you can click Next to begin customizing a virtual machine, but that you also have the option of clicking Finish right now to create a virtual machine that uses the default values. For the purposes of this article, we will create a custom virtual machine so that you can see the options that are available to you.

With that said, click Next and you will be prompted to enter a name and a location for the virtual machine that you are creating. I recommend using a descriptive name. The location is up to you, but if your server contains a striped RAID array, then that is a good location to choose for performance reasons

Click Next and you will be prompted to enter the amount of memory that is to be assigned to the new virtual machine. By default, new virtual machines are assigned 512 MB of RAM, but that isn’t really enough if you plan on running Windows Vista or Windows Server 2008. I would recommend 1 GB for Vista and 2 GB for Windows Server 2008 installations.

Click Next, and the wizard will prompt you to choose which network adapter you want to use for the machine’s virtual network connection. As you may recall, when you installed Hyper-V, you were given the opportunity to select one or more network adapters to be used by virtual machines. This option allows you to pick from the network adapters that you previously selected. The idea is that you can use a different network adapter on each virtual machine if you want, so that no single network adapter becomes over burdened.

When you have made your selection, click Next, and you will be prompted to choose the virtual hard drive that you want the machine to use, as shown in Figure B. As you can see in the figure, you can either create a new virtual hard drive, or you can use an existing one. Since there aren’t any existing virtual hard drives right now, we will have to create a new one. Windows defaults to creating a virtual hard drive that’s 127 MB in size, but you can create a drive of up to 2 TB if you want
Figure B

Click next, and you will be prompted to install an operating system on the new virtual machine. You have the option of installing an operating system later on, but you can also choose to install from a CD (or an .ISO file), a boot floppy, or from an installation server, as shown in Figure C
Figure C
You can choose to install an operating system now.

When you’ve made your choice, click Next. You will now see a summary of the options that you have created. If you have chosen to go ahead and install an operating system, then insert the operating system media, select the option to start the virtual machine, and click Finish. Windows will now launch the virtual machine and begin installing the operating system, as shown in Figure D
Figure D 
Windows will launch the new virtual machine and begin installing the guest operating system. And with that, we are done!

Tuesday, February 28, 2012

Desktop Virtualization

Many IT organizations now-a-days are looking at desktop virtualization to upgrade their entire approach to desktop management. Today, individual desktops are hard-coded combinations of OS, apps and user settings, and managed one-by-one on an ongoing basis. Desktop virtualization is a solution where one moving part doesn’t have to disrupt any of the other moving parts in order to make a change. It is the concept of separating a personal computer desktop environment from the physical machine through a client-server computing model.

One of the most significant benefits of desktop virtualization is that it gives IT administrators an easy and centralized way to manage employees' computers. Instead of each computer being separate, administrators create just a handful of VMs or VM templates for different roles within a company. For instance, a company may create one VM for each worker in a research and another for each sales representative. These VMs would include not just the operating system, but also any applications and drivers the employee would need. Such deployments work best where many employees need essentially the same functionality

Vendors providing support for desktop virtualization There are large numbers of vendors providing deskop virtualization solutions. Below mentioned are the top among the lot
Microsoft – Microsoft Virtual PC, Remote desktop services, etc.
Citrix -        Citrix XenDesktop
VMware -   VMware View, VMware v Sphere, etc.
Symantec -  Endpoint Visualization

Diagrammatic representation of desktop virtualization
Advantages
1.Simpler provisioning of new desktops.
2.Reduced downtime in the event of server or client hardware failures.
3.Desktop image management capabilities.
4.Secure remote access to the enterprise desktop environment.
5.Desktop Virtualization offers major savings on expending on physical computer systems by easily installing and configuring VMs on a single computer system

Limitations
1.Compatibility – Not all applications can be virtualized easily.
2.Potential security risks if the network is not properly managed.
3.Some loss of user autonomy and privacy.
4.Challenges in setting up and maintaining drivers for printers and other peripherals.
5.Difficulty in running certain complex applications such as multimedia.
6.Increased downtime in the event of network failures.
7.Complexity and high costs of VDI deployment and management

Thursday, February 9, 2012

Add the Command Prompt to the Windows Explorer Right-Click Menu

A hidden functionality in Windows allows you to right click on a directory, and select “Command Prompt Here” from the menu.
Here’s the registry hack to get this working. Make sure you back up your registry just in case. it’ll show you the step-by-step method, but you can skip down to the bottom for the alternate reg file.

Step-By-Step Method:
Type regedit.exe into the Start\Run dialog, and then navigate to the following registry key:

 HKEY_CLASSES_ROOT\Directory\shell Once you are at that key, right click and choose the New Key option:
Name the key “CommandPrompt” without the quotes and then double-click on the default value. Change the text to “Command Prompt Here” as seen here:
Right click on the new Command key and select New key, as you did before. Name the new key Command as well, and then double-click the default value of that key. Set the text of that key to this: cmd.exe /k cd %1 You can see what it should look like here:
Now when you right click on the folder, you should see this dialog:
That will open up a prompt like this:
Alternate method: You can create a text file named anything.reg, and insert this text into it:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\shell\CommandPrompt]
@=”Command Prompt:”
[HKEY_CLASSES_ROOT\Directory\shell\CommandPrompt\Command]
@=”cmd.exe /k cd %1
Double click on that file, and the text will be entered into the registry, and you’ll have the same right click command prompt.

Monday, January 30, 2012

How to Enlarge Data Partitions without losing data after Raid expansion in Linux


Scenario : Customer needs to expand Data volume after expanding array size in Linux.
Possibilities : only Last Partitions can be expanded through Resize2fs
Recommendation : Please ask customer to take backup of File systems/system.

Step to be followed: 

Suppose you have a Partition called c0d0p7 in last cylinder and mounted as a ext3.
#df -h
Filesystem                  Size   Used     Avail   Use%       Mounted on 

/dev/cciss/c0d0p2       15G       4.5G     9.3G    33%        /
/dev/cciss/c0d0p1       99M      12M     83M     12%       /boot
None                          4.0G      0          4.0G     0%        /dev/shm
/dev/cciss/c0d0p6       46G      85M     44G      1%        /name1
/dev/cciss/c0d0p7       46G      103M   44G      1%        /name2

1) Un mount  that file system/Mount point
2) Now you have to remove Journal feature ( if it is ext3 file system) from the file system
# tune2fs -O ^has_journal /dev/cciss/c0d0p7 # tune2fs 1.35 (Date)
Now you have to run e2fsck command to check file systems.
3) root@ff13manish /]# e2fsck -f -y /dev/cciss/c0d0p7 
e2fsck 1.35 (Date) Pass
Pass 1: Checking inodes, blocks, and sizes Pass
Pass 2: Checking directory structure Pass
Pass 3: Checking directory connectivity Pass
Pass 4: Checking reference counts Pass
Pass 5: Checking group summary information
/Name2: 16/6111232 files (6.3% non-contiguous), 209772/12209392 blocks
4) Execute the fdisk -l command 
Disk /dev/cciss/c0d0: 220.1 GB, 220122071040 bytes
255 heads, 63 sectors/track, 26761 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Devic Boot                         Start       End              Blocks           Id        System
System /dev/cciss/c0d0p1      1            13              104391            83       linux
/dev/cciss/c0d0p2                14           1925           15358140        83       linux
Linux /dev/cciss/c0d0p3       1926       3455           12289725        82      linux swap
/dev/cciss/c0d0p4               3456         26761       187205445      5         Extended
/dev/cciss/c0d0p5               3456         9535         48837568+      83       Linux
/dev/cciss/c0d0p6              9536          15615       48837568+       83      Linux
/dev/cciss/c0d0p7             15616        21695         48837568+       83    Linux Original Cylinder size with 46GB

Command (m for help): quit 

“Delete the Last partition and create it again”.

5) [root@ff13manish /]# fdisk /dev/cciss/c0d0

The number of cylinders for this disk is set to 26761. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with:

a.Software that runs at boot time (e.g., old versions of LILO)
b.Booting and partitioning software from other OS’s (e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): d
Partition number (1-7): 7

“Don’t Quit here  with save option , you have to continue without coming out from fdisk Menu”
Command (m for help): n
First cylinder (15616-26761, default 15616)
Using default value 15616
Last cylinder or +size or +sizeM or +sizeK (15616-26761, default 26761)

Using default value 26761
Command (m for help): p 
Disk /dev/cciss/c0d0: 220.1 GB, 220122071040 bytes
255 heads, 63 sectors/track, 26761 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot                   Start        End        Blocks            Id     System
/dev/cciss/c0d0p1 *           1             13        104391             83     linux
/dev/cciss/c0d0p2             14           1925     15358140         83     Linux
/dev/cciss/c0d0p3             1926       3455     12289725         82     Linux swap
/dev/cciss/c0d0p4             3456       26761   187205445       5      Extended
/dev/cciss/c0d0p5             3456       9535     48837568+      83     Linux
/dev/cciss/c0d0p6             9536      15615    48837568+      83     Linux
/dev/cciss/c0d0p7             15616    26761    89530213+      83     Linux (Now Size moves to 89 GB)


Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at the next reboot. Syncing disks.
6) Execute Partprobe command 
# partprobe
7) Execute Reszie2fs command
[root@ff13manish /]# resize2fs /dev/cciss/c0d0p7
resize2fs 1.35 (Date)
Resizing the filesystem on /dev/cciss/c0d0p7 to 22382553 (4k) blocks
The filesystem on /dev/cciss/c0d0p7 is now 22382553 blocks long.

8) Now enable ext3 feature in filesystems
tune2fs -j /dev/cciss/c0d0p7
tune2fs 1.35 (Date)
Creating  journal inode: done
This filesystem will be automatically checked every 22 mounts or 180 days, whichever comes first.
Use tune2fs -c or -i to override.
Now check by mounting the filesystems
[root@ff13manish /]# mount  -t ext3 /dev/cciss/c0d0p7  /Name2
[root@ff13manish /]# df -h
Filesystem               Size         Used     Avail     Use%     Mounted on 

/dev/cciss/c0d0p2        15G      4.5G    9.3G        33%          /
/dev/cciss/c0d0p1        99M      12M     83M      12%         /boot
None                             4.0G     0       4.0G        0%          /dev/shm
/dev/cciss/c0d0p6        46G      85M     44G       1%          /Name1
/dev/cciss/c0d0p7        85G      107M    83G      1%         /Name2

Check your data :
[root@ff13vel /]# cd /name2
[root@ff13vel name2]# ls
lost+found  report-4b79378d-0000265d-00000003.zip  RHEL 4 AS UTILITY FOR LINUX
[root@ff13vel name2]# ls -al            
total 104
drwxr-xr-x   4 root root  4096 Feb 17 11:27 .
drwxr-xr-x  29 root root  4096 Feb 17 10:08 ..
drwx------2 root root 16384 Feb 16 17:01 lost+found
-rw-r--r--1 root root 67517 Feb 15 18:27 report-4b79378d-0000265d-00000003.zip
drwxr-xr-x   2 root root  4096 Feb 15 16:57 RHEL 4 AS UTILITY FOR LIN

Sunday, January 29, 2012

Procedure to remove Khatra.exe virus manually

1. Go to task manager and select regsvr.exe(if found), gHost.exe , khatra.exe , Xplorer.exe rt click and select end process tree. press WIN+r or start>RUN

2.type cmd and hit enter
3.GO to the the drive where your OS is installed
4.In the command prompt make sure you get the command line as c:\ or d:\ (this can be achieved by the command "cd .." without quotes)
5.Type attrib -s -h -r khatra.exe Repeat the same process for the location c:\windows\system32
6.type del khatra.exe
7.Follow the same process for gHost.exe & Xplorer.exe as they are also part of the virus. To make sure that the virus is out of you pc ,
check your registry
1.win+R type regedit
2.ctrl+F type in search one by 1 the names of the
3.processes i.e khatra,gHost,Xplorer
4.search the entire registry n go-on deleting the values you find.

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More