How to Quickly Create a Virtual Machine on Microsoft Azure ?

Hi

 today we will create a virtual machine on Microsoft Azure through Quick Way

You use the Quick Create method to quickly create a virtual machine in the Management Portal. When you create this machine, you use one dialog box to provide the configuration details.

Note: This article creates a virtual machine that is not connected to a virtual network. If you want your virtual machine to use a virtual network, use the From Gallery method instead and specify the virtual network when you create the virtual machine. For more information about virtual networks, 

1. Sign in to the Azure Management Portal.
2. On the command bar, click New.
   
3. Click Virtual Machines, and then click Quick Create.
   
   The Create a New Virtual Machine dialog box appears.
4. Type the following information for the new virtual machine:
   • DNS Name - the name that is used for both the virtual machine that is created and the cloud service that contains the virtual machine.
   • Image - the platform image that is used to create the virtual machine.
   • User Name - the name of the account that you want to use to manage the virtual machine.
   • Account Password - type and confirm a strong password for the account.
   • Location - the region that contains the virtual machine.
5. Click the check mark to create the virtual machine.
   Note: A storage account is automatically created to contain this virtual machine.
   You will see the new virtual machine listed in on the Virtual Machines page.

and to connect to your Machine 

Highlight on the Machine then click on Connect to download the RDP Connection File 
which will use to connect Remote desktop to the Virtual Machine 

       

Double click on the RDP File 

                         

Then click on " Connect "

                                       

Then type your password here and click " ok " to connect  

Convert VMware VMs to Hyper-V VMs Free " 5nine "

How to Convert VMware VMs to Hyper-V VMs Free With 

    Free 5nine V2V Easy Converter performs fast and non-intrusive host to host conversion and fixup of selected VMware Virtual Machines to Microsoft Hyper-V VMs with the highest conversion success ratio.

5nine V2V Easy Converter can be used as a standalone tool on different versions of Windows Server, including Microsoft Hyper-V Server 2012 R2/2012/2008 R2 (SP1), Windows Server 2012 R2/2012/2008 R2 (SP1) GUI and Core installations.

Current version of 5nine V2V Converter supports conversion of Windows Server 2012 R2/2012/2008, Windows 8.x/7, Windows Server 2003 (x86 and x64), and most of Windows 2000 Advanced Server, Ubuntu and CentOS configurations. It also supports conversion to Gen1 and Gen2 Hyper-V Virtual Machines.

5nine V2V EasyConverter may be considered as a complimentary tool to MVMC too

Supported Operating Systems

• Windows Server
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012 R2 Core
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 Core
  • Microsoft Windows Server 2008 R2 SP1
  • Microsoft Windows Server 2008 R2 SP1 Core
• Microsoft Hyper-V Server
  • Microsoft Hyper-V Server 2012 R2
  • Microsoft Hyper-V Server 2012
  • Microsoft Hyper-V Server 2008 R2 SP1
• Windows 8.x
• Windows 7 x64

VMware ESXi version

• VMware ESXi 4.x or higher

Download 

Watch the Movie 

Thanks @5Nine_Software

Kaspersky Mail Checker Error

The add-in “kaspersky mail checker” (c:\program files\kaspersky lab\kaspersky anti-virus 6.0 for windows workstations mp4\mcou.dll) cannot be loaded and has been disabled by outlook.

Log into an account with administrator rights, make sure Outlook is closed and run these two commands individually:

if you want to use the below commands with new Versions you have to change the below commands depending on the ver number and the folder path

regsvr32 -u "C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4\mcou.dll

 Then

regsvr32 "C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4\mcou.dll

that's it :)

VMware vSphere Mobile

VMware vSphere Mobile Watchlist allows you to monitor the virtual machines you care about in your vSphere infrastructure remotely on your phone. Discover diagnostic information about any alerts on your VMs using VMware Knowledge Base Articles and the web. Remediate problems from your phone by using power operations or delegate the problem to someone on your team back at the datacenter.
IMPORTANT NOTE: A VMware vSphere installation (5.0 and above) is required to use VMware vSphere Mobile Watchlist. Access to your vSphere infrastructure may need a secure access method like VPN. Contact your IT department for further assistance.

   

FEATURES:

• EASILY CREATE VM WATCHLISTS
  Select a subset of VMs from your VMware vSphere VM inventory to tell the app what VMs to track. Use multiple lists to organize these important VMs.
• VMS AT A GLANCE
  Review the status of these VMs from your device including: their state, health, console and related objects.
• SUGGESTED KB ARTICLES
  Got an alert on your VM? Let VMware vSphere Mobile Watchlist suggest what KB Articles might help you or search the web to gather more information.
• REMEDIATE REMOTELY
  Use power operations to remediate many situations remotely from your device.
• DELEGATE TO YOUR TEAM
  For those situations where you are not able to fix an issue from the device, VMware vSphere Mobile Watchlist will enable you to share the VM and alert information along with any suggested KB articles and other web pages relevant to the current problem. Your colleagues back in the datacenter can use this context to resolve the issue.

Download Now

iTunes App Store:  https://itunes.apple.com/us/app/vmware-vsphere-mobile-watchlist/id792869677?ls=1&mt=8

Google Play:  https://play.google.com/store/apps/details?id=com.vmware.beacon&hl=en

VMW Community:  https://communities.vmware.com/community/vmtn/vsphere/vsphere-mobile

Blog

Download All Videos and Slides from TechEd 2014 Europe

                      

Microsoft is publishing the sessions from Microsoft TechEd Europe 2014 (October 2014) The sessions will be available on Channel9, after the conference.This is an update of my previous download script for TechEd North America. 

Reference link

Download Script  

How To Boot From VHD ?

How To Boot From VHD  ?

                  if you have already Windows Operating System VHD , you can boot from the VHD file
                  just follow the bellow Steps

          1- Sysprep the existing virtual disk you need to boot from
          2- Attach new VHD using Computer Management | Disk Management | Attach VHD

Browse for the path

Now the VHD attached successfully on Drive later G

open the CMD as Administrator

Then Type “bcdboot G:\Windows” 

then after that just restart your PC you will see the boot menu

 

Removing Boot to VHD

Removing Boot to VHD is super simple.

1) If you are in your Boot to VHD operating system, restart your PC and select a different OS.

2) Open MSCONFIG, select the Boot Tab, highlight the Boot to VHD OS you wish to remove, click delete

               

This will remove the entry from the Operating System selection screen at bootup.

3) Navigate to where you stored the .VHD file used for Boot to VHD

Copy or move the file if you wish to save it
Delete the file to recover hard drive space

              

Free E-book - Manage your Hyper-v over Powershell

Free E-book - Manage your Hyper-v over Powershell 

           Tech your self how to Manage your VM over Powershell
           From the below Download link free Ebook , you will find alot of commands and scripts

Thanks @AltaroHyperV

Enjoy :)


Download

Online Re-sizing Of Hyper-V Virtual Disks in Windows 2012 R2

Hello

    As we Talked before,  about the advantages of  Microsoft Windows 2012 R2
    so now you can Re-sizing the volume of your VM online :)

 


Remember :  VM volume has to be VHDX otherwise you will not use it

• and it support Generation 1 & 2
• VHDX can't be shared 
• you can Extend and Shrink the virtual disk 
• VM should be  attached to a vSCSI controller
• This feature can leverage ODX for speed when available

If there is no UN-allocated disk space the option to shrink the VHDX won’t even show

which is mean you’ll first need to shrink the volume inside the virtual machine if all disk space has already been allocated

Free - Prepare for your VCAP and VCP exams With Veeam

@veeam

Veeam Has released 2 study Guide prepared by VMware certified professionals Jason Langer and Josh Coen.
for

VCP5-DCV & VCAP5-DCA 

hurry up 

http://go.veeam.com/vcp-vcap-study-guide-sponsorship.html

The Advantages of Hyper-v Generation 2

Hi

 Let's talk about the New Generation 2 of  Hyper-v  Windows 2012

• Generation 2 virtual machines use UEFI firmware instead of the BIOS.

• Generation 2 virtual machines use software-based devices for video. They support the same video modes as generation 1 virtual machines.

• Generation 2 virtual machines can use software-based Fibre Channel and network adapters.

• Generation 2 virtual machines have faster boot times.

• Generation 2 virtual machines support the VHDX file format and support large boot volumes up to 64 TB. You can also use online resizing to expand or shrink your virtual hard disk files (VHDX). This includes the operating system (boot drive) and data volumes. Online resizing is only available for SCSI-attached VHDX files.

• Generation 2 virtual machines support 64-bit versions of Windows 8 or Windows Server 2012 and Windows Server 2012 R2.

• CD/DVD devices can be hot-added and hot-removed from a generation 2 virtual machine. No CD/DVD devices are present by default.

• Generation 2 virtual machines support ISO format images.

• Generation 2 virtual machines are available for integration services setup.

• You can manage generation 2 virtual machine boot order using Windows PowerShell, Hyper-V Manager, or Windows Management Interface (WMI).

• Secure Boot is not available in generation 1 virtual machines Generation 1 virtual machines use the BIOS and emulated IDE before software-based devices can be utilized 

What is Windows Server ODX?

POSTED ON SEPTEMBER 22, 2014 BY AIDAN FINN IN WINDOWS SERVER 2012 WITH 0 COMMENTS

Offloaded Data Transfer (ODX) is a feature that was added to Windows Server 2012 and later versions to enhance the performance of compatible storage area networks (SANs). Similar to vStorage APIs for Array Integration (VAAI) in VMware, ODX speeds up the movement and creation of blocks and files, which makes it a great feature to have in a virtualized environment. In this article, I will explain ODX, the system requirements, and an unfortunate issue that many SAN customers have experienced.

What is Offloaded Data Transfer (ODX)?

Imagine you have two servers that are connected to the same SAN, where both servers are using it for file storage. You want to move or copy a file from Server1 to Server2. At a high level, this is what happens:

1. Server1 reads the file from the SAN a bit at a time
2. Server1 sends the file, a bit at a time, to Server2 over the LAN
3. Server2 sends the bits of the file back to the SAN to be stored

It seems like a waste to send a file over the relatively latent LAN to transfer it from one LUN to another LUN on the same SAN. What if we could cut out the middleman? That’s what ODX does!

Server1 coordinates with the SAN and Server2 via a token handover. The SAN takes up the load and performs a file copy without sending the file over the LAN. This greatly speeds up data movement between servers on the same SAN.

How ODX enhances data transfer in a SAN (Source: Microsoft)

There are other scenarios where ODX offloads data transfer from Windows to the SAN. What if a server needs to copy a file? That file copy is offloaded to the SAN. What if a Hyper-V host needs to create or extend a newly fixed virtual hard disk? That can take quite some time, but not if ODX offloads the zeroing out process. And what if you want to convert VMware virtual machines into Hyper-V virtual machines? ODX will help, even more so if you happen to use NetApp MAT to do the work.

System Requirements

The first and most important component is the SAN. You must have a SAN that is certified for Windows Offloaded Data Transfer and is connected to your servers using one of the following:

• iSCSI
• Fibre Channel
• Fibre Channel over Ethernet
• Serial Attached SCSI (SAS)

You can copy between different arrays if the copy manager for the storage arrays supports cross-storage array ODX. In addition, the storage arrays must be from the same vendor.

Your physical machines that are performing the copy must be running Windows Server 2012 R2, Windows Server 2012, Windows 8.1, or Windows 8.

Any file system filter drivers must opt-in to ODX or doesn’t prevent ODX. Non-supporting filters include Windows Server data deduplication and BitLocker. Pay attention to data replication and anti-malware products. The volumes must be unencrypted and Storage Spaces is not supported. The volume must be NTFS, and ReFS is not supported.

Note that you can build a Scale-Out File Server (SOFS) using a SAN that offers ODX. The SOFS nodes are connected to the SAN using legacy data protocols, and application servers connect to the SOFS using SMB 3.0. Data movement to the SAN can be optimized using ODX by the SAN.

Regarding the files — they must be 256 KB or larger to be eligible for optimization. Highly-fragmented files will naturally hurt performance.

Enabling and Disabling ODX

ODX is enabled by default and will be used by Windows Server, including Hyper-V, when compatible storage and eligible operations are discovered. This, unfortunately, has led to issues with allegedly compatible SANs, such as HP’s 3Par that could cause VHD/X data corruption, where this issue should be resolved with up-to-date installations.

You can disable ODX with a registry edit with the following PowerShell cmdlet (note that a value of 1 disables ODX):

1	Set-ItemProperty HKLM:SYSTEMCurrentControlSetControlFileSystem -Name “FilterSupportedFeaturesMode” -Value 1

A reboot is required after setting this value.

Unfortunately, being on the Windows Server HCL doesn’t guarantee anything with hardware enhancements, such as ODX and VMQ. I would recommend testing your storage system with and without ODX enabled.

Reference  : Petri  

How To Migrate From VMware to Microsoft Hyper-V Server 2012

How To Migrate  From VMware to Microsoft Hyper-V Server 2012

          Microsoft Hyper-V Server 2012 is now a true contender in the virtualization space as it brings a great number of new features missed in the previous offering of Hyper-V.  While an in-place upgrade option is unavailable due to architectural changes involved in implementing Hyper-V Server 2012, the in network migration process detailed in this "Step-By-Step" post works well and simplifies the process.  Those who currently utilize System Center Virtual Machine Manager are aware that System Center provides this functionality and is great for large scale migrations

For those without System Center Virtual Machine Manager, or those wishing to migrate only a few VMs, Microsoft offers a free stand-alone tool to enable the migration of virtual machines from VMware to Hyper-V

Preparation of the target Hyper-V Server 2012

1. Download and Install Hyper-V Server 2012
    
2. Set up the same Virtual Networks as the source host in Hyper-V Manager using the "Virtual Switch Manager" host action.
3. Download the FREE Microsoft Virtual Machine Converter (MVMC) solution accelerator tool
   
   The MVMC tool converts VMware virtual machines created with:
• vCenter Server 5.0
• vCenter Server 4.1
• ESXi Server 5.0
• ESXi/ESX Server 4.1
4. Run the MSI
5. Enter a location where you want to install MVMC or use the default location and continue with the installation on the local machine
   
    .

Converting Virtual Machines Using the MVMC GUI

1. Open MVMC, open the Source page, and then enter the details to connect to a VMware vCenter Server, ESX server, or ESXi server
   
   
2. In the Address box, type the server IP address or the name of the VMware source server
3. In the User name box, type the user name
4. In the Password box, type the password and click Next
5. On the Virtual Machines page, select a virtual machine on the source VMware server to convert
   
   
   
   
6. Click Next
7. On the Virtual Machine Connection page, enter the credentials of an administrative account that can connect to the virtual machine. The connection is required for uninstalling VMware tools on the source virtual machine. The virtual machine must be joined to an Active Directory domain.
   
   
8. In the Virtual machine box, type the name of the virtual machine
9. In the User name box, type the domain and user name
10. In the Password box, type the password
11. In the Final state of source virtual machine option, select whether the source virtual machine should be turnedOn or Off when the restoration is complete
12. In the Final state of target virtual machine option, select whether the target virtual machine should be turnedOn or Off when the conversion is complete
    
    
    
    
13. Click Next
14. On the Workspace page, click Browse to select a workspace folder path from where the UI can be run. Be sure to select a location that has enough disk space for the converted VHD files
    
    
15. Click Next
16. On the Hyper-V Host page, enter the details to connect to the destination Hyper-V server where the virtual machine will be created following conversion and specify the UNC path for placement of the VHD files
    
    
17. In the Address box, type the server IP address or the name of the Hyper-V source server
18. In the User name box, type the domain and user name
19. In the Password box, type the password
20. In the Path box, click Browse to select the UNC path to where the VHD file will be copied on the destination Hyper-V server
21. Select whether the VHD file should be Fixed size or Dynamically expanding
    
     
22. Click Next
23. On the Summary page, review the details and click Finish to complete the conversion. If warnings are displayed, review them before proceeding with the conversion
    
    
24. On the Completion page, seen when the virtual machine conversion has completed successfully, click Close

Note : 

• MVMC expands the dynamic VHD file to its full size. To reduce a VHD file by removing blank space on the disk, see Edit Virtual Hard Disk Wizard at http://technet.microsoft.com/en-us/library/cc755149.aspx
• Once the conversion has completed successfully, MVMC starts the virtual machine and leaves it as it is. If you do not want the virtual machine to be started, go to the Hyper-V manager in the destination server and shut down the virtual machine
• The account executing the setup must be the local administrator on the machine
• For best performance, it is recommended that the conversion is run on the destination host (this means that MVMC is installed and run from the Hyper-V hypervisor).
• MVMC always takes a snapshot of the original source virtual machine before the tools are uninstalled and will restore the virtual machine to its original state once the disks attached to the virtual machine are successfully copied to the machine where the conversion takes place
• Remote access through Windows Management Instrumentation (WMI) must be enabled on the source virtual machine
• MVMC assumes that the virtual machine is in a running state. Virtual machines that are not running (offline virtual machines) cannot be converted by MVMC
  
• The virtual machine must have VMware tools installed and be connected to an Active Directory domain
  
• The boot disk attached to the source virtual machine will be converted to an IDE-based VHD and all data disks attached to the source virtual machine will be converted to SCSI VHDs
  
• MVMC will create another instance of the virtual machine on Hyper-V based on the source virtual machine configuration. The source virtual machine will remain intact but will be shut down during the conversion process

Feature Comparison

Processor and Memory Support

Network

Storage

Manageability

Microsoft Virtual Machine Converter 3.0

Microsoft Virtual Machine Converter 3.0

Microsoft® Virtual Machine Converter (MVMC) is a Microsoft-supported, stand-alone solution for the information technology (IT) pro or solution provider who wants to convert virtual machines and disks from VMware hosts to Hyper-V® hosts and Microsoft Azure

New Features in MVMC 3.0
The 3.0 release of MVMC adds the ability to convert a physical computer running Windows Server 2008 or above server operating systems or Windows Vista or above client operating systems to a virtual machine running on Hyper-V host.

Standard Features

• Converts virtual disks that are attached to a VMware virtual machine to virtual hard disks (VHDs) that can be uploaded to Microsoft Azure.
• Provides native Windows PowerShell capability that enables scripting and integration into IT automation workflows.
  Note The command-line interface (CLI) in MVMC 1.0 has been replaced by Windows PowerShell in MVMC 2.0.
• Supports conversion and provisioning of Linux-based guest operating systems from VMware hosts to Hyper-V hosts.
• Supports conversion of offline virtual machines.
• Supports the new virtual hard disk format (VHDX) when converting and provisioning in Hyper-V in Windows Server® 2012 R2 and Windows Server 2012.
• Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.1, and VMware vSphere 4.1 hosts Hyper-V virtual machines.
• Supports Windows Server® 2012 R2, Windows Server® 2012, and Windows® 8 as guest operating systems that you can select for conversion.
• Converts and deploys virtual machines from VMware hosts to Hyper-V hosts on any of the following operating systems:
• Windows Server® 2012 R2
• Windows Server® 2012
• Windows Server 2008 R2 SP1
• Converts VMware virtual machines, virtual disks, and configurations for memory, virtual processor, and other virtual computing resources from the source to Hyper-V.
• Adds virtual network interface cards (NICs) to the converted virtual machine on Hyper-V.
• Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.0, and VMware vSphere 4.1 hosts to Hyper-V.
• Has a wizard-driven GUI, which simplifies performing virtual machine conversions.
• Uninstalls VMware Tools before online conversion (online only) to provide a clean way to migrate VMware-based virtual machines to Hyper-V.
  Important MVMC takes a snapshot of the virtual machine that you are converting before you uninstall VMware Tools, and then shuts down the source machine to preserve state during conversion. The virtual machine is restored to its previous state after the source disks that are attached to the virtual machine are successfully copied to the machine where the conversion process is run. At that point, the source machine in VMware can be turned on, if required.
  Important MVMC does not uninstall VMware Tools in an offline conversion. Instead, it disables VMware services, drivers, and programs only for Windows Server guest operating systems. For file conversions with Linux guest operating systems, VMware Tools are not disabled or uninstalled. We highly recommend that you manually uninstall VMware Tools when you convert an offline virtual machine.
• Supports Windows Server and Linux guest operating system conversion. For more details, see the section “Supported Configurations for Virtual Machine Conversion” in this guide.
• Includes Windows PowerShell capability for offline conversions of VMware-based virtual hard disks (VMDK) to a Hyper-V–based virtual hard disk file format (.vhd file).
  Note The offline disk conversion does not include driver fixes.

System Requirements

Supported Operating System

Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2

Before you install Microsoft Virtual Machine Converter (MVMC), you must install the following software on the computer on which you want to run MVMC:
• Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 SP1 operating systems
• Microsoft .NET Framework 3.5 and .NET Framework 4 if you install MVMC on Windows Server 2008 R2 SP1
• Microsoft .NET Framework 4.5 if you install MVMC on Windows Server 2012 [A1] or Windows 8.
  Note Although MVMC installs on all of these versions, using the Windows PowerShell cmdlets that are released as part of MVMC requires Windows PowerShell Runtime 3.0, as the cmdlets function only on Windows Server 2012 [A2] and above or Windows 8.
• Install Feature Bits Compact server
• Visual C++® Redistributable for Visual Studio® 2012 Update 1

----------------------------------------------------------------------------------

Quick Summary:-

Convert virtual machine and disk from Vmware Host to Hyper-V
Convert virtual machine and disk from Vmware Host to Microsoft Azure
Perform P2V – Physical to Virtual Machine Conversion

The supported guest operating system are:-

Windows Server 2008 R2 SP1
Windows Server 2012
Windows Server 2012 R2

Linux based guest operating system
Supported Vmware version:-

VMware vSphere 5.5,
VMware vSphere 5.1, and
VMware vSphere 4.1

For Download