• Microsoft introduces new search experience – www.bing.com

    bingLogo_lg

    Microsoft Corp. today unveiled Bing, a new Decision Engine and consumer brand, providing customers with a first step in moving beyond search to help make faster, more informed decisions. Bing is specifically designed to build on the benefits of today’s search engines but begins to move beyond this experience with a new approach to user experience and intuitive tools to help customers make better decisions, focusing initially on four key vertical areas: making a purchase decision, planning a trip, researching a health condition or finding a local business.

    The result of this new approach is an important beginning for a new and more powerful kind of search service, which Microsoft is calling a Decision Engine, designed to empower people to gain insight and knowledge from the Web, moving more quickly to important decisions. The new service, located at http://www.Bing.com, will begin to roll out over the coming days and will be fully deployed worldwide on Wednesday, June 3.


    The new service, located at http://www.Bing.com, will roll out over the coming days and will be deployed worldwide on Wed., June 3, 2009.

    For more information visit the following links

    http://www.microsoft.com/presspass/presskits/bing/default.mspx

    http://www.microsoft.com/presspass/press/2009/may09/05-28NewSearchPR.mspx

    Bing Reviewer’s Guide

    Discover Bing- Interactive Product Guide

     

    My Bing Screen

    aviraj bing

    Happy Binging

  • Hyper-V: Step-by-Step Guide to Using Live Migration in Windows Server 2008 R2

    This guide details the steps required to perform a live migration of Hyper-V™ virtual machines from one node in a Windows Server® 2008 R2 failover cluster to another node.windows-server-2008-r2-logo

    Live migration overview

    Live migration is a new Hyper-V feature in Windows Server 2008 R2, which requires the failover clustering role to be added and configured on the servers running Hyper-V. Live migration allows you to transparently move running virtual machines from one node of the failover cluster to another node in the same cluster without a dropped network connection or perceived downtime. In addition, failover clustering requires shared storage for the cluster nodes. This can include an iSCSI or Fiber-Channel Storage Area Network (SAN). All virtual machines are stored in the shared storage area, and the running virtual machine state is managed by one of the nodes. For a detailed overview of live migration and the benefits of using it, see Windows Server 2008 R2 Hyper-V Live Migration.

    Considerations before using live migration

    This guide assumes you are familiar with the requirements for using Hyper-V and failover clustering, which are covered in Hyper-V Step-by-Step Guide: Hyper-V and Failover Clustering.

    Specific recommendations to consider before using live migration are listed below:

    • For each node of the failover cluster: use more than one network adapter; configure at least one network adapter for the private virtual network. We recommend that you configure a dedicated private network with Gigabit speed for live migration traffic. This network should be separate from the network for managing the failover cluster, from the network for the virtual machine, and from the network for storage.
    • We recommend that you make the hardware and system settings of the nodes in the failover cluster as similar as possible to minimize potential problems.
    • If possible, do not apply IPSec policies on a private network for live migration because this can significantly impact the performance of live migration.
    • Ensure that the source and destination nodes (for the live migration) in the failover cluster are connected through the same IP subnet. This is so the virtual machine can retain the same IP address after live migration.
    • Before reverting a clustered virtual machine back to a snapshot, you should first shut down the virtual machine from Failover Cluster Manager, take a snapshot of the virtual machine, and restart the virtual machine.
    • When creating the virtual machine, we recommend that you configure the storage location under SystemRoot/ClusterStorage in the Cluster Shared Volumes.

    Processor compatibility

    Hyper-V provides processor compatibility settings to make it easier to perform a live migration of a virtual machine to another physical computer with a different processor version. The Migrate to a physical computer with a different processor version setting in Hyper-V Manager allows you to move a running virtual machine to a physical computer with different processor features without restarting the virtual machine. It is recommended that you enable this setting to ensure that the virtual machine uses only the features of the processor that are available on all versions of a virtualization-capable processor by the same processor manufacturer. It does not provide compatibility between different processor manufacturers. When this setting is not used, Hyper-V provides the virtual machine with all the virtualization features offered by the physical processor. The setting is also useful for high availability and backup and recovery scenarios because it makes it easier to move a highly available virtual machine to another node in a cluster or restore the virtual machine to different hardware.

    More to read…CLICK HERE TO DOWNLOAD

  • DOWNLOAD: Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1: RC (ISO)

    The Windows SDK for Windows 7 and .NET Framework 3.5 SP1: RC provides documentation, samples, header files, libraries, and tools designed to help you develop Windows applications using both native (Win32®) and managed (.NET Framework) technologies.

    The Windows SDK for Windows 7 and .NET Framework 3.5 SP1: RC provides the documentation, samples, header files, libraries, and tools (including C++ compilers) that you need to develop applications to run on Windows 7 RC and the .NET Framework 3.5 SP1. To build and run .NET Framework applications, you must have the corresponding version of the .NET Framework installed. This SDK is compatible with Visual Studio® 2008, including Visual Studio Express Editions, which are available free of charge.
    Please see the Release Notes for the full list of supported platforms, compilers, and Visual Studio versions and any late breaking issues. For detailed information about the content in this SDK, including a description of new content, please see the Getting Started section in the documentation.

    System Requirements
    • Supported Operating Systems: Windows 7

    Windows 7 RC; Windows Server 2003; Windows Server 2008; Windows Vista; Windows XP Hard disk space - choose a disk drive with a minimum of 2.5 GB of free space. We highly recommend that you have your machine fully patched through Microsoft Update before beginning setup. The .NET Framework 3.5 SP1 tools and samples contained in this SDK require installation of the .NET Framework 3.5 SP1 which is available with Visual Studio 2008 or a standalone install of the .NET Framework 3.5 SP1.

    Instructions

    For this release, the Windows SDK is available thru a DVD ISO image file so that you can burn your own DVD or web setup. Due to the large size of the ISO file, we highly recommend that you use a download manager tool to manage the ISO download. To verify that your download of the ISO file for the Windows SDK is correct, check that the CRC and file size match the following:
    ================================================
    File Name: GRC1SDK_EN_DVD.iso
    Chip: X86
    CRC#: 0xBF75EF1B
    SHA1: 0xE2567CBF7DF45D69A52869A915CF9EE093B80CAA
    ================================================
    File Name: GRC1SDKX_EN_DVD.iso
    Chip: AMD64
    CRC#: 0x0241F71B
    SHA1: 0x63A39CBE6976F3053F8DA3E8DBCAA79CFB2AE596
    ================================================
    File Name: GRC1SDKIAI_EN_DVD.iso
    Chip: IA64
    CRC#: 0x5FB4007D
    SHA1: 0x908CC7305189BD54A885291778C4D0A934AAE8FA
    ================================================
    Please note if you are running a 64-bit version of Windows and Visual Studio 2008, please upgrade to Visual Studio 2008 SP1 before installing the Windows 7 SDK. This prevents an issue where some platform configuration choices are unavailable in Visual Studio’s New Project Platform and New Solution Platform dialogs.

  • Windows 7 RC General Availability

    DOWNLOAD WINDOWS 7 Release Candidate

    http://www.microsoft.com/windows/windows-7/download.aspx

    windows-7-logo

  • Frequently Asked Questions: Virtual Hard Disks in Windows 7

    Some of the brief content…windows-7-logo

    This article provides answers to common questions about Virtual Hard Disks in Windows 7.

    Questions related to VHD file types

    Questions related to native VHD boot

    Questions related to backup support for volumes in attached VHDs

    Questions related to VHD file types

    What are the different VHD file types?

    There are three types of VHD files. You can create these files using the Hyper-V Manager or (in Windows 7) using the Windows disk-management tools:

    1. Fixed VHD. A fixed VHD is a file with an allocated size that does not change. For example, if you create a VHD that is 2 gigabytes (GB), the system will create a file that is approximately 2 GB (with some space used for internal VHD structure) and the file will be 2 GB regardless of the data written to it.
    2. Dynamic or expandable VHD. A dynamic or expandable VHD is a file that is as large as the data written to it at any given time. As more data is written, the file dynamically increases in size. For example, the size of a file for a 2 GB dynamic VHD is initially around 2 megabytes (MB) on the host file system. As data is written to the VHD, the file grows with a maximum size of 2 GB.
    3. Differencing VHD. A differencing VHD is similar to a dynamic VHD, but contains only the modified disk blocks of an associated parent VHD. A differencing VHD is linked to a parent VHD and is sometimes referred to as a “child” VHD. The parent VHD file is read-only and therefore you must modify the differencing disk. The file type of the parent VHD can be any of the three VHD types, including another differencing VHD. Multiple child VHD files create a differencing chain.

    CLICKE HERE TO READ COMPLETE FAQ