Browsing Posts published in January, 2010

Share This :)

Windows Vista and Windows 7 comes with telnet disabled. This is not required by the average user and so is probably a safety precaution.

Here You will learn How to Enable it

  • Open Control Panel from the Start Menu
  • Switch to classic view from the top left of the control panel (if you are not already)
  • Then click Programs and Features, here you should see a list of all the software that is installed on your system. Now on the top left (in the same position where you clicked Classic View) you should see an option ‘Turn Windows features on or off’, click it.
  • You will see a dialog like this after a bit of waiting.
  • Now scroll down until you find an option saying ‘Telnet Client’, and then wait a while until the following dialog to disappear.
  • And when it says several minutes, it really means several minutes. Now open cmd and type in telnet, and you will have your telnet client up and running.

  • Share This :)

    Q: What is new in the Windows Server 2008 R2 Hyper-V RC build compared to the R2 Beta?
    A: The Windows Server 2008 R2 Hyper-V Release Candidate build includes the following improved and new functionality over beta.
    • Support for up to 64 Logical Processors –increasing the logical processors support from 24 to 64 enables customers to achieve higher consolidation ratios and more scalable virtualization scenarios on Windows Server than ever before.
    • Processor Compatibility Mode for live migration– allows live migration across different CPU versions within the same processor family, (e.g.”Intel Core 2-to-Intel Pentium 4” or “AMD Opteron-to-AMD Athlon”) enabling migration across a broader range of Hyper-V host hardware.
    • VM Chimney (TCP Offload) and VMQ support are disabled by default

    The following are new Windows Server 2008 R2 Hyper-V features that were also in the R2 beta.
    • Live Migration
    • Jumbo Frame Support
    • Hot Add/Remove of storage (VHDs and Pass Through Disks)
    • Second Level Address Translation (SLAT) processor support for both Intel (EPT) and AMD (RVI)
    • Core Parking
    • Improved network performance via support for TCP Chimney and VMQ (specific hardware NICs required)
    • Improved VHD performance for dynamic and difference disks
    Q: When will the Windows Server 2008 R2 Hyper-V RC build be released?
    A: Windows Server 2008 R2 Hyper-V RC is currently available from www.microsoft.com/hyper-v.
    Windows Server 2008 R2 Hyper-V RC Production Support
    Q: Are production deployments of Windows Server 2008 R2 Hyper-V RC supported?
    A: Windows Server 2008 R2 Hyper-V is still in the pre-release phase and production deployments are not recommended / supported.
    Windows Server 2008 R2 Hyper-V Questions
    Q: What does WS08 R2 Hyper-V contain?
    A: With WS08 R2 Hyper-V, customers will get a compelling solution for core virtualization scenarios – Production server consolidation, dynamic datacenter, test & development and business continuity. With the initial version of Hyper-V, we have seen massive customer interest and adoption for Hyper-V with over 300K downloads of the RTM and the latest IDC report showing that Microsoft has 23% market share in virtualization. Windows Server 2008 R2 provides customers better flexibility with features like live migration and cluster shared volumes for storage flexibility; greater scalability with support for up to 64 logical processors and improved performance with support for enhanced networking support (TCP offload support for virtual machines) and support for hardware page tables.
    Q: What’s new in R2?
    A: The major technology investment areas for WS08R2 are Virtualization, Web, and Management these along with several features that improve Scalability & Reliability and deliver a strong value proposition along with WIN7 Clients. These features include:
    • Live Migration – Allows customers to move virtual machines from one host to another in seconds with no loss of performance. This facilitates hardware maintenance and upgrades, manual failover, and the consolidation of workloads on fewer servers. Automation in the datacenter also helps trim IT spending on labor and maintenance.
    • DirectAccess– Allows remote workers to securely connect to their work environment as if they were on the corporate network and it also lets IT administrators manage those PCs as if they were on premise, without the use of a VPN. Resulting in greater flexibility for remote workers and reduced office costs.
    • Branch Cache – Customers can greatly reduce Wide Area Network (WAN) bandwidth consumption between the datacenter and branch offices. The result is a significant reduction in networking costs because most organizations pay for bandwidth by the byte.

    Q: What is the number of logical processors that will be supported by Hyper-V in Windows Server 2008 R2?
    A: Hyper-V in Windows Server 2008 R2 will support up to 64 logical processors in the physical machine.
    Q: Why is there a difference between the number of logical processors supported in Windows Server 2008 R2 and the number of logical processors supported by Hyper-V?
    A: The Windows Server OS is designed to run on the widest range of HW from single processor servers to the largest scale-up servers. Hyper-V is designed for the most common hardware configurations that customers will deploy for virtualization. The vast majority of servers that will be deployed for virtualization will be 2 and 4 socket servers. Hyper-V will support up to 64 logical processors in Windows Server 2008 R2 and we will continue to work with our partners to provide solutions to help customers take advantage of future hardware innovations to meet their current and future business needs.

    Q: When will Microsoft Windows Server 2008 R2 Hyper-V RTM?
    A: Server 2008 R2 will RTM in the second half of 2009.
    Q: How many guest OSes can I run?
    A: The actual number of guest OSes will depend on the physical hardware and the characteristics of the different virtualized workloads. Windows Server 2008 R2 Hyper-V will support upto 64 logical processors and 1 TB of memory for the host system. We will announce the maximum number of guest instances than can run on Microsoft Windows Server 2008 R2 Hyper-V closer to RTM. Additionally, each guest OS must have a valid license.
    Clustering and Live Migration
    Q: Up to how many nodes on a cluster does Live Migration support?
    A: Live Migration is supported on up to 16 node failover clusters.
    Q: What is the maximum number of supported VMs per node?
    A: For production deployment, up to 32 VMs per node for server workloads and up to 64 VMs per node for VDI workloads are supported. Customers must plan for adequate capacity when a failover occurs and VMs from the failed host are brought online on different nodes of the cluster.
    Q: Will Live Migration work on with a cluster of mixed AMD and Intel host nodes?
    A: For Live Migration or Quick Migration to work, all cluster nodes must have processors from the same processor vendor, for example Intel or AMD.
    Q: Assuming host nodes have a virtualization capable processor from the same manufacturer, can I migrate a VM from a host using an older processor to a host with a newer processor?
    A: It is highly recommended to use identical processors on all nodes of a cluster using Quick or Live Migration.
    A new functionality introduced in RC is the “Processor Compatibility Mode” option. This functionality can be enabled for VMs to allow both Live Migration and Quick Migration from newer to older processors from the same manufacturer.
    The setting is under VM settings > Processor > “Migrate to a physical computer with a different processor version”.
    You can live migrate or quick migrate a running VM from an older processor to new processor and back without the “Processor Compatibility Mode” option as long as the VM is running all the time.
    Q: Are there any new tools included with Windows Server R2 Server Core to help manage the Hyper-V?
    A: A new server configuration script is available in the Windows Server 2008 R2 Hyper-V RC. Type sconfig at the command line to start the server configuration utility.

    Supported Guests
    Q: What operating systems are supported as guests on Windows Server 2008 R2 Hyper-V RC?
    A: The following operating systems are supported as guests with integration services with Windows Server 2008 R2 Hyper-V RC:
    • Windows Server 2000 Server and Advanced Server with SP4 (uniprocessor)
    • Windows XP SP3 32 bit (uniprocessor)
    • Windows Vista SP1 32 & 64 bit (uniprocessor)
    • Windows 7 client 32 & 64 bit (uniprocessor)
    • Windows 7 client 32 & 64 bit (multiprocessor, two virtual processors)
    • Windows Server 2003 SP2 32 & 64 bit (uniprocessor)
    • Windows Server 2003 SP2 32 & 64 bit (multiprocessor, two virtual processors)
    • Windows Server 2003 R2 SP2 32 & 64 bit (uniprocessor)
    • Windows Server 2003 R2 SP2 32 & 64 bit (multiprocessor, two virtual processors)
    • Windows Server 2008 32 & 64 bit (uniprocessor)
    • Windows Server 2008 32 & 64 bit (multiprocessor, four virtual processors)
    • Windows Server 2008 R2 32 & 64 bit (uniprocessor)
    • Windows Server 2008 R2 32 & 64 bit (multiprocessor, four virtual processors)
    • SUSE Linux Enterprise Server 10 (x86/x64) (uniprocessor, no integration components)
    Q: What Linux guests are supported in Windows Server 2008 R2 Hyper-V RC?
    A: Windows Server 2008 R2 Hyper-V is still in the pre-release phase and production deployments are not recommended / supported. Single processor VMs of SUSE Linux Enterprise Server 10 without integration components are currently the only recommended Linux distribution during RC.
    Hyper-V Upgrade Guidance
    Windows Server 2008 Hyper-V ? Windows Server 2008 R2 Hyper-V (RC)
    Q: Can I upgrade my existing Windows Server 2008 Hyper-V host to Windows Server 2008 R2 Hyper-V RC?
    A: Yes. Upgrade of Hyper-V installations from WS2008 Hyper-V to WS2008 R2 Hyper-V RC is supported. You can perform an in-place upgrade of your machine from Windows Server 2008 to Windows Server 2008 R2 and still have the Hyper-V role enabled on the system.
    Q: I have a number of virtual machines that I created using Windows Server 2008 Hyper-V. Can I move these virtual machines to Windows Server 2008 R2 Hyper-V RC?
    A: The following methods of moving a VM from WS2008 Hyper-V to WS2008 R2 Hyper-V RC will be supported:
    1. In-place upgrade of the host from WS2008 Hyper-V to WS2008 R2 Hyper-V RC.
    2. Exporting a VM from a machine running WS2008 Hyper-V and importing to a machine running WS2008 R2 Hyper-V RC.
    3. Backing up a VM from WS2008 Hyper-V and restoring it on WS2008 R2 Hyper-V RC
    At the end of each operation above, the VM configurations that were created in WS2008 Hyper-V will still be registered in WS2008 R2 Hyper-V RC.
    Although all guest synthetic devices with continue to function with the older drivers on RC, updating the guest integration services to the latest R2 version is highly recommended to access the optimal performance of the R2 drivers and integration services of RC.
    Windows Server 2008 R2 Hyper-V (Beta) ? Windows Server 2008 R2 Hyper-V (RC)
    Q: Will I be able to upgrade my Windows Server 2008 R2 Hyper-V (Beta) host to the R2 RC?
    A: Yes. Upgrade of installations from Windows Server 2008 R2 Hyper-V Beta to Windows Server 2008 R2 Hyper-V RC is supported. You can perform an in-place upgrade of your machine from Windows Server 2008 R2 Hyper-V Beta to Windows Server 2008 R2 Hyper-V RC and still have all the virtual machines available.
    Q: Will I be able to reuse my virtual machines that were created with the R2 beta release with Windows Server 2008 R2 Hyper-V RC?
    A: The following methods of moving a VM from R2 Beta to R2 RC will be supported:
    1. In-place upgrade of the host from Windows Server 2008 R2 Hyper-V Beta to Windows Server 2008 R2 Hyper-V RC.
    2. Exporting a VM from a machine running HVS2008 R2 Beta and importing to a machine running Windows Server 2008 R2 Hyper-V RC.
    3. Backing up a VM from Windows Server 2008 R2 Hyper-V Beta and restoring it on Windows Server 2008 R2 Hyper-V RC
    Save states and snapshots will upgrade normally with beta to RC upgrades.
    Although all guest synthetic devices with continue to function with the beta drivers on RC, updating the guest integration services to the latest R2 version is highly recommended to access the optimal performance of the R2 drivers and integration services for RC.
    Future release upgrade path: Windows Server 2008 R2 Hyper-V (RC) ? Windows Server 2008 R2 Hyper-V (RTM)
    Q: Will I be able to do an in-place upgrade of my Windows Server 2008 R2 Hyper-V RC host to the RTM release of R2?
    A: Upgrade of Hyper-V installations from RC versions to RTM of R2 will be supported. You can perform an upgrade of Windows Server 2008 R2 Hyper-V from RC to RTM.
    Q: Will I be able to reuse my virtual machines that were created with the R2 RC release with Windows Server 2008 R2 Hyper-V RTM?
    A: Yes. VM’s that were running with the RC version of Windows Server 2008 R2 Hyper-V will automatically be upgraded to run on RTM version. Note this upgrade will not update the integration services inside the virtual machine. Users will need to install the latest integration services for optimal stability and performance.
    Networking Guidance

    Q: What are the VMQ and TCP Chimney offload features?
    A: Windows Server 2008 R2 is being delivered with new optional optimizations to enhance the networking performance of virtual machines. The networking optimization features are Chimney for Virtual Machines (VM-Chimney) and Virtual Machine Queues (VMQ). Depending on the NICs available to you and the traffic types you encounter, one or both of these technologies may produce substantial improvements in your networking performance, either through greater bandwidth utilization or, in slower NICs, lower CPU utilization to process the same load.
    Both VM-Chimney and VMQ require hardware support. These features are only available when using specific hardware NICs (please refer to the section below for supported NICs).

    NICs:
    For Windows Server 2008 R2 RC,
    • VM-Chimney capable drivers are available on the RC media for the following NICs:
    o Broadcom Net-Xtreme II 1 Gb/s NICs (Models 5706, 5708, and 5709)
    o Broadcom 10Gb/s NICs (Models 57710, 57711)

    • VMQ capable drivers are available on the RC media:
    o Intel Kawela (E1Q) 1 Gb/s NICs (also known as Pro/1000 ET NICs)
    o Intel Oplin NICs (IXE) 10Gb/s NICs (also known as 82598)
    To determine which NIC(s) your system has, go to the Windows Device Manager and expand the Network Adapters entry. If one of the above mentioned Network Adapters is listed, then your host should be capable of using the associated networking optimization feature.
    Drivers for additional NICs that support these features are expected to be available in the RTM timeframe. Some vendors may produce VMQ-capable or Chimney-capable drivers for their NICs and release them through other channels such as their own support web sites.
    Feature interactions:
    • A connection will not be offloaded if it is part of an IPSec rule.
    • Connections may not be available if the Windows Firewall or any other filter driver that requires packet inspection for that particular connection.
    • Currently available NIC teaming drivers do not support the use of either of these features.
    • There are known issues with the in-box 10Gb/s Broadcom NICs with Chimney turned on.
    • VMQ and Chimney may be independently available on separate NICs in the same host machine.
    • If both Chimney and VMQ are available on the same NIC at the same time, Windows Server 2008 R2 will use VMQ (for Windows Server 2008 R2 RC there are no NICs we are aware of that support both).

    System Center Virtual Machine Manager (SCVMM) Support
    Q: Can I manage Windows Server 2008 R2 Hyper-V hosts with SCVMM?
    A: The SCVMM 2008 R2 release will enable management of Windows Server 2008 R2 Hyper-V hosts from SCVMM. A beta version of SCVMM 2008 R2 is currently available for customers from www.microsoft.com/scvmm.
    Q: Can I manage Windows Server 2008 R2 Hyper-V RC hosts with SCVMM R2 Beta?
    A: No, The current beta of System Center Virtual Machine Manager 2008 R2 will not support managing Windows Server 2008 R2 Hyper-V RC. The RC for SCVMM 2008 R2 will be available by June 2009. A beta version of SCVMM 2008 R2 is currently available for customers from www.microsoft.com/scvmm.

    Source: http://www.microsoft.com/windowsserver2008/en/us/white-papers.aspx

    Share This :)
    Windows Server 2008

    Windows Server 2008

    Q: What is Windows Server 2008 R2?
    A: Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new innovations to enable customers to quickly save money and be more efficient today and more effective tomorrow. New virtualization capabilities including Live Migration, Web resources, management enhancements, and exciting Windows 7 integration help customers increase the reliability, flexibility and efficiency of their server infrastructures.

    Q. What editions/versions does Windows Server 2008 R2 come in?
    A. Windows Server 2008 R2 will be released with six editions which include:
    Windows Server 2008® R2 Foundation is an entry-level cost-effective technology foundation for your business designed for small business owners and IT Generalists supporting small businesses. Foundation is an inexpensive, easy-to-deploy, proven and reliable technology that provides organizations with the foundation to run the most prevalent business applications as well as share information and resources.
    Windows Server® 2008 R2 Standard is an advanced server platform that provides more cost-effective and reliable support for business workloads. It offers innovative features for virtualization, power savings, and manageability and helps make it easier for mobile workers to access company resources.
    Windows Server® 2008 R2 Enterprise is an advanced server platform that provides more cost-effective and reliable support for mission-critical workloads. It offers innovative features for virtualization, power savings, and manageability and helps make it easier for mobile workers to access company resources.
    Windows Server® 2008 R2 Datacenter is an advanced server platform that provides more cost-effective and reliable support for mission-critical workloads. It offers innovative features for virtualization, power savings, and manageability and helps make it easier for mobile workers to access company resources.
    Windows ® Web Server 2008 R2 is a powerful Web application and services platform. Featuring Internet Information Services (IIS) 7.5 and designed exclusively as an Internet-facing server, it offers improved administration and diagnostic tools to help reduce infrastructure costs when used with a variety of popular development platforms. With included Web Server and DNS Server roles, as well as improved reliability and scalability, this platform allows you to manage the most demanding environments — from a dedicated Web server to an entire Web server farm.

    Windows Server® 2008 R2 for Itanium-Based Systems delivers an enterprise-class platform for deploying business-critical applications. Scale database, line-of-business, and custom applications to meet growing business needs. Help improve availability with failover clustering and dynamic hardware partitioning capabilities*. Virtualize deployments with rights to run an unlimited number of virtual instances of Windows Server**. Windows Server 2008 R2 for Itanium-Based Systems helps provide the foundation for a highly dynamic IT infrastructure. *Requires supporting server hardware.** Requires a third-party virtualization technology. Hyper-VTM is not available for Itanium-based systems.

    Q. When will Windows Server 2008 R2 be available for purchase?
    A. Windows 7 will be generally available on October 22nd, with Windows Server 2008 R2 available on or before that date. However, existing Volume Licensing customers will be able to download Windows 7 and Windows Server 2008 R2 in the second half of August. More information on licensing, pricing and availability can be found here.

    Q. Why should I upgrade to Windows Server 2008 R2 from previous versions of Windows Server?
    A. We are always focused on driving forward with our business and the development of new versions. We are working to ensure our customers and partners have the guidance they need to deploy the new server software. We encourage customers to invest in Windows Server 2008 to provide a better migration path to WS08 R2.

    For more information about Windows Server 2008 R2 and the value it brings to customers, please visit http://www.microsoft.com/windowsserver2008/en/us/R2.aspx

    Q. What’s new in Windows Server 2008 R2?
    A. Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new innovations to enable customers to quickly save money and be more efficient today and more effective tomorrow. New virtualization tools, Web resources, management enhancements, and exciting Windows 7 integration help customers increase the reliability, flexibility and efficiency of their server infrastructures. These features include:
    • Live Migration – enables customers to move virtual machines from one host to another with no perceivable downtime. Live migration facilitates hardware maintenance and upgrades, manual failover, and the consolidation of workloads on fewer servers. With this level of automation in the datacenter, IT costs related to labor, power, cooling and maintenance can be decrease.
    • Hyper-V support for up to 64 logical processors –increasing the logical processor support from the original 16 to 64 enables customers to achieve higher consolidation ratios with new multi-core hardware and more scalable virtualization scenarios than before.
    • Hyper-V processor compatibility mode for Live Migration– allows Live Migration across different CPU versions within the same processor family, (e.g.”Intel Core 2-to-Intel Pentium 4” or “AMD Opteron-to-AMD Athlon”) enabling migration across a broader range of server host hardware.
    • DirectAccess– allows remote workers to securely and seamlessly remotely connect to their work environment as if they were on the corporate network and lets IT administrators continually manage those PCs, without the use of a VPN, resulting in greater flexibility for remote workers and reduced administration costs.
    • BranchCache™ – customers can reduce Wide Area Network (WAN) bandwidth consumption between the datacenter and branch offices by keeping a branch copy of frequently used data. The result is a significant reduction in networking costs because most organizations pay for such bandwidth by the byte.
    • Remote Desktop Services: enables customer to deploy a unified infrastructure for all their centralized desktop deployments, whether based on user session or on VDI architecture.
    • File Classification Infrastructure (FCI) – provides customers with a built-in solution for file classification and management, helping to save them time and money. Administrators can automatically classify files based on content and location, generate reports and schedule file management tasks to manage data, helping mitigate risk to their business. FCI also enables ISV partners to build on top of it.
    • Improved power management – empowers customers to save right out of the box. New processor power management and default settings, reduced storage power consumption and enhanced budgeting and metering capabilities help save power and money. Recent tests found that Windows Server 2008 R2 improved power efficiency by up to 18 percent over Windows Server 2003.
    • Windows PowerShell 2.0- helps enterprises optimize resources and trim costs with powerful scripting capabilities which can help automate server deployment and configuration, simplifying management. 2.0 offers significant enhancements from the previous version with the inclusion of more than 240 pre-built “cmdlets” as well as a new graphical user interface (GUI) that adds professional-level development features for writing scripts.
    • IIS 7.5 – Full support for .NET on Server Core, as well as updated PHP support, new management tools and bundled extensions.

    Q: Will Windows Server 2008 R2 only be available in 64-bit?
    A: Yes. 64-bit processors have become the industry standard for systems ranging from the most scalable servers to desktop PCs. This shift has driven server standards forward, so the 64-bit processor is our focus.

    Q: Do I have to upgrade to 64-bit CPU hardware to run Windows Server 2008 R2?
    A: Yes.

    Q: Can I run 32-bit applications on Windows Server 2008 R2?
    A: Yes. Like Windows Server 2003 and Windows Server 2008, Windows Server 2008 R2 will provide for 32-bit applications with Windows on Windows 64, or WOW64. Both 32-bit and 64-bit applications can run natively on x64 processors, with Windows Server managing the transitions – resulting in excellent performance for both. The end result is a platform that utilizes the existing wealth of 32-bit applications while also providing a smooth migration path to 64-bit computing.

    Q: What will my upgrade experience be like moving from Windows Server 2008 to Windows Server 2008 R2?
    A: The Microsoft Deployment Toolkit 2008 is the recommended process and toolset to automate desktop and server deployment. Microsoft Deployment Toolkit 2008 provides detailed guidance and job aids for every organizational role involved with large-scale deployment projects.

    Q: What tools can customers use to determine if their applications or ISV applications will run on the new platform?
    A: We have free testing tools and guides available at www.microsoft.com/windowsserver/appcompat to help IT professionals, corporate developers and ISVs test their applications on Windows Server 2008 R2. The “Windows 7 and Windows Server 2008 R2 Application Cookbook” outline the changes between the operating system versions and the Software Compatibility Toolkit has highly automated test tools that run 25 test cases for compatibility. Users will be able to determine if the application is compatible and potential issues.

    Q. Does Windows Server 2008 R2 offer virtualization?
    A. Yes. Hyper-V has become an integral part of the Windows Server platform in the Windows Server 2008 R2 release. To learn about the exciting new features available with Hyper-V, please visit http://www.microsoft.com/windowsserver2008/en/us/R2-virtualization.aspx

    Q. What management improvements does Windows Server 2008 R2 provide?
    A. Streamlined management is a key focus of Windows Server 2008 R2. Several management consoles have been updated with new tools and wizards, and many have been rebuilt to run on top of the newly updated PowerShell, including the new Active Directory Administration Center. For its part, PowerShell has been updated with rover 240 new cmdlets and the ability to administer servers remotely.

    Q. What changes have there been in Windows Server 2008 Terminal Services?
    A. With the Windows Server 2008 R2 release, Terminal Services has become Remote Desktop Services (RDS). In conjunction with the Virtual Desktop Infrastructure (VDI), RDS offers new virtual application and desktop resources. Administrators can now roll out such resources to users more easily and dynamically; additionally, protocol improvements provide users with upgraded graphics, multimedia and network performance improvements and tight integration with Windows 7.

    Q. How does Windows Server 2008 R2 support my Web applications?
    A. Windows Server 2008 R2 builds on Windows Server 2008’s IIS 7.0 platform with the new IIS 7.5. The new web server continues its strong presence as a Web application server, now adding updated administration capabilities, enhanced support for PowerShell as well as support for PHP and ASP.NET on IIS servers running on Server Core. You can learn more by visiting the Web and Application Platform page.

    Q. How does Windows Server 2008 R2 work with Windows 7?
    A. Windows Server 2008 R2 and Windows 7 were developed in conjunction for an optimized “Better Together” experience. While Windows Server 2008 R2 can work with any Windows desktop operating system, working with Windows 7 provides numerous new and enhanced features and business benefits, including optimized mobile computing with DirectAccess, improved remote computing with BranchCache, and powerful new access to virtual resources that act identically to local resources via Remote Desktop Services. You can learn more on the Windows Server 2008 R2 and Windows 7—Better Together page.

    Q. What applications work with Windows Server 2008 R2?
    A. For a full run-down on Windows Server 2008 R2 application compatibility, links to the Windows Server Catalog and IT Pro testing tools, please visit the Application Compatibility for IT Professionals and Developers resource page.

    Q. Are there tools available to assess my infrastructure readiness for Windows Server 2008 R2?
    A. Yes, the Microsoft Assessment and Planning (MAP) Toolkit will assess readiness for migration to Windows Server 2008 R2.

    Source: http://www.microsoft.com/windowsserver2008/en/us/white-papers.aspx

    Share This :)

    The certification on Windows Server 2008 system will use a new generation of certification system—MCTS and MCITP system.
    It is known that the most concern of the candidates is how to upgrade MCSE 2000/2003 or MCSA 2000/2003 to credentials on Windows Server 2008 System. Here, to the best of my ability, I will give an enough detailed introduction.
     First of all,you could not be upgraded directly to the new certification system, if you just have MCSE 2000 or MCSA 2000.However, you can do, only if you have credentials on Windows Server 2003.And if you have MCSE (MCSA) certifications on Security or MCSE (MCSA) on Exchange, you must know that there aren’t both of the certifications on security and Exchange in the new certification system any more, which are covered in the new subjects.
    Besides, there will be separate MCTS or MCITP on ISA or Exchange Server.
    If you want to upgrade your MCSA on Windows Server 2003 to Windows Server 2008, you can choose the following paths. Certification roadmap
    1. To get MCTS: Windows Server 2008 Active Directory and MCTS: Windows Server 2008 Network Infrastructure, you are required to pass 70-648.
    That is to say:
    MCSA 2003 +70-648 = MCTS: Windows Server 2008 Active Directory, Configuring
                                                 + MCTS: Windows Server 2008 Network Infrastructure, Configuring
                                                 = 70-640 +70- 642
    2. To get MCTS: Windows Server 2008 Active Directory, Configuring? MCTS: Windows Server 2008 Network Infrastructure and MCTS: Windows Server 2008 Applications Platform, Configuring, you are required to pass 70-649.
    In other words:
    MCSE +70-649 = MCTS: Windows Server 2008 Active Directory, Configuring
                          + MCTS: Windows Server 2008 Network Infrastructure, Configuring 
                         + MCTS: Windows Server 2008  Applications Platform, Configuring
                           = 70-640 +70- 642 +70-643
    Notice: All of those upgrade exams could not upgrade you directly to MCITP.
    So, if you have MCSA/MCSE 2003, you are required to pass the corresponding Pro exams to get MCITP.
    1.If you want to get MCITP: server Administrator, you are required to pass both of 70-648 and 70-646.That is to say:
    MCSA 2003 +70- 648 + 70-646 = MCITP: Server Administrator.
    2.If you want to be upgraded to MCITP: Enterprise Administrator, you are required to pass four exams: 70-648, 70-643, 70-620 or 70-624 or 70-680, 70-647.
    In other words:
    MCSA 2003+ 648 + 643 + 620(or 624 or 70-680) + 647 = MCITP: Enterprise Administrator.
    3.If you want to upgrade MCSE 2003 to MCITP Server Administrator, you are required to pass 70-649 and 70-646.
    That is to say:
    MCSE 2003+ 70- 649+70-646 = MCITP: Server Administrator.
    4.If you want to be upgraded to MCITP: Enterprise Administrator, you are required to pass three exams:70-649, 70-620 or 70-624 or 70-680, 70-647.
    In other words:
    MCSE 2003+70-649 +70-620(or 624 or 70-680) + 647 = MCITP: Enterprise Administrator.
    My advice: if you are prepared for MCSE, and want to be upgraded to Credentials on Windows Server 2008, you’d better pass 70-620 instead of the popular exam 70-270 as MCSE exam on client operating systems client operating systems
    Besides, I think it is necessary to know about Microsoft’s new certification on Windows Server 2008 system.
    MCTSFocused on configuring and troubleshooting key technologies
    MCITPFocused on advanced infrastructure design
    MCTS credentials on Windows Server 2008 will involve the following aspects:
    1 Active Directory Domain Services AD
    2 Identity and Access Management
    3Internet Services
    4 Terminal Services
    5 Networking Infrastructure
    As was mentioned above, MCTS credentials on Windows Server 2008 systems have three exams, which aim to measure the skills on AD ,SASystem Architectureapplication.
    MCITP credentials on Windows Server 2008 will involve the aspects below:
    1. Infrastructure Operations
    2. Active Directory Design and Planning AD

    Original Post By: http://www.microsoftkit.com

    Share This :)
    Table Of Contents
    1. Introduction
    2. An Overview of the OSI Model
    3. Layer 1 – The Physical Layer
    4. Layer 2 – The Data Link Layer
    5. Layer 3 – The Network Layer
    6. Layer 4 – The Transport Layer
    7. Layer 5 – The Session Layer
    8. Layer 6 – The Presentation Layer
    9. Layer 7 – The Application Layer
    10. Layers 8, 9, and 10
    11. TCP/IP Model Overview
    12. Equipment at the Layers




    Introduction


    The Open Systems Interconnection (OSI) model is a reference tool for understanding data communications between any two networked systems. It divides the communications processes into seven layers. Each layer both performs specific functions to support the layers above it and offers services to the layers below it. The
    three lowest layers focus on passing traffic through the network to an end system. The top four layers come into play in the end system to complete the process.
    This white paper will provide you with an understanding of each of the seven layers, including their functions and their relationships to each other. This will provide you with an overview of the network process, which can then act as a framework for understanding the details of computer networking. Since the discussion of networking often includes talk of extra layers, this paper will address these unofficial layers as well. Finally, this paper will draw comparisons between the theoretical OSI model and the functional TCP/IP model. Although TCP/IP has been used for network communications before the adoption of the OSI model, it supports the same functions and features in a differently layered arrangement.


    An Overview of the OSI Model



    A networking model offers a generic means to separate computer networking functions into multiple layers.Each of these layers relies on the layers below it to provide supporting capabilities and performs support to the layers above it. Such a model of layered functionality is also called a protocol stack or protocol suite.

    Protocols, or rules, can do their work in either hardware or software or, as with most protocol stacks, in a combination of the two. The nature of these stacks is that the lower layers do their work in hardware or firmware (software that runs on specific hardware chips) while the higher layers work in software.

    The Open System Interconnection model is a seven-layer structure that specifies the requirements for communications between two computers. The ISO (International Organization for Standardization) standard 7498-1 defined this model. This model allows all network elements to operate together, no matter who created the
    protocols and what computer vendor supports them.

    The main benefits of the OSI model include the following:

    • Helps users understand the big picture of networking
    • Helps users understand how hardware and software elements function together
    • Makes troubleshooting easier by separating networks into manageable pieces
    • Defines terms that networking professionals can use to compare basic functional relationships on different networks
    • Helps users understand new technologies as they are developed
    • Aids in interpreting vendor explanations of product functionality


    Layer 1 – The Physical Layer


    The physical layer of the OSI model defines connector and interface specifications, as well as the medium (cable) requirements. Electrical, mechanical, functional, and procedural specifications are provided for sending a bit stream on a computer network.

    Components of the physical layer include:

    • Cabling system components
    • Adapters that connect media to physical interfaces
    • Connector design and pin assignments
    • Hub, repeater, and patch panel specifications
    • Wireless system components
    • Parallel SCSI (Small Computer System Interface)
    • Network Interface Card (NIC)

    In a LAN environment, Category 5e UTP (Unshielded Twisted Pair) cable is generally used for the physical layer for individual device connections. Fiber optic cabling is often used for the physical layer in a vertical or riser backbone link. The IEEE, EIA/TIA, ANSI, and other similar standards bodies developed standards for this layer.


    Note: The Physical Layer of the OSI model is only part of a LAN (Local Area Network).

    Layer 2 – The Data Link Layer

    Layer 2 of the OSI model provides the following functions:

  • Allows a device to access the network to send and receive messages
  • Offers a physical address so a device’s data can be sent on the network
  • Works with a device’s networking software when sending and receiving messages
  • Provides error-detection capability
  • Common networking components that function at layer 2 include:

  • Network interface cards
  • Ethernet and Token Ring switches
  • Bridges
  • NICs have a layer 2 or MAC address. A switch uses this address to filter and forward traffic, helping relieve congestion and collisions on a network segment.

    Bridges and switches function in a similar fashion; however, bridging is normally a software program on a CPU, while switches use Application-Specific Integrated Circuits (ASICs) to perform the task in dedicated hardware, which is much faster.


    Layer 3 – The Network Layer

    Network Layer

    Layer 3, the network layer of the OSI model, provides an end-to-end logical addressing system so that a packet
    of data can be routed across several layer 2 networks (Ethernet, Token Ring, Frame Relay, etc.). Note that network
    layer addresses can also be referred to as logical addresses.

    Initially, software manufacturers, such as Novell, developed proprietary layer 3 addressing. However, the networking industry has evolved to the point that it requires a common layer 3 addressing system. The Internet Protocol (IP) addresses make networks easier to both set up and connect with one another. The Internet uses IP addressing to provide connectivity to millions of networks around the world.

    To make it easier to manage the network and control the flow of packets, many organizations separate their network layer addressing into smaller parts known as subnets. Routers use the network or subnet portion of the IP addressing to route traffic between different networks. Each router must be configured specifically for
    the networks or subnets that will be connected to its interfaces.

    Routers communicate with one another using routing protocols, such as Routing Information Protocol (RIP) and Open version of Shortest Path First (OSPF), to learn of other networks that are present and to calculate the best way to reach each network based on a variety of criteria (such as the path with the fewest routers). Routers and other networked systems make these routing decisions at the network layer.

    When passing packets between different networks, it may become necessary to adjust their outbound size to one that is compatible with the layer 2 protocol that is being used. The network layer accomplishes this via a process known as fragmentation. A router?s network layer is usually responsible for doing the fragmentation.
    All reassembly of fragmented packets happens at the network layer of the final destination system.

    Two of the additional functions of the network layer are diagnostics and the reporting of logical variations in normal network operation. While the network layer diagnostics may be initiated by any networked system, the
    system discovering the variation reports it to the original sender of the packet that is found to be outside normal network operation.

    The variation reporting exception is content validation calculations. If the calculation done by the receiving system does not match the value sent by the originating system, the receiver discards the related packet with no report to the sender. Retransmission is left to a higher layer?s protocol. Some basic security functionality can also be set up by filtering traffic using layer 3 addressing on routers or other similar devices.


    Layer 4 – The Transport Layer



    Layer 4, the transport layer of the OSI model, offers end-to-end communication between end devices through a network. Depending on the application, the transport layer either offers reliable, connection-oriented or connectionless, best-effort communications.

    Some of the functions offered by the transport layer include:

    • Application identification
    • Client-side entity identification
    • Confirmation that the entire message arrived intact
    • Segmentation of data for network transport
    • Control of data flow to prevent memory overruns
    • Establishment and maintenance of both ends of virtual circuits
    • Transmission-error detection
    • Realignment of segmented data in the correct order on the receiving side
    • Multiplexing or sharing of multiple sessions over a single physical link

    The most common transport layer protocols are the connection-oriented TCP Transmission Control Protocol (TCP) and the connectionless UDP User Datagram Protocol (UDP).


    Layer 5 – The Session Layer



    Layer 5, the session layer, provides various services, including tracking the number of bytes that each end of the session has acknowledged receiving from the other end of the session. This session layer allows applications functioning on devices to establish, manage, and terminate a dialog through a network.

    Session layer functionality includes:

    • Virtual connection between application entities
    • Synchronization of data flow
    • Creation of dialog units
    • Connection parameter negotiations
    • Partitioning of services into functional groups
    • Acknowledgments of data received during a session
    • Retransmission of data if it is not received by a device


    Layer 6 – The Presentation Layer



    Layer 6, the presentation layer, is responsible for how an application formats the data to be sent out onto the network. The presentation layer basically allows an application to read (or understand) the message.

    Examples of presentation layer functionality include:

    • Encryption and decryption of a message for security
    • Compression and expansion of a message so that it travels efficiently
    • Graphics formatting
    • Content translation
    • System-specific translation


    Layer 7 – The Application Layer



    Layer 7, the application layer, provides an interface for the end user operating a device connected to a network. This layer is what the user sees, in terms of loading an application (such as Web browser or e-mail); that is, this application layer is the data the user views while using these applications.

    Examples of application layer functionality include:

    • Support for file transfers
    • Ability to print on a network
    • Electronic mail
    • Electronic messaging
    • Browsing the World Wide Web


    Layers 8, 9, and 10


    Whether a designed to be a humorous extension or a secret technician code, layers 8, 9, and 10 are not officially part of the OSI model. They refer to the non-technical aspects of computer networking that often interfere with the smooth design and operation of the network.

    Layer 8 is usually considered the office politics layer. In most organizations, there is at least one group who is favored, at least temporarily, by management and receives special treatment. When it comes to networking, this may mean that this group always has the latest and/or fastest equipment and highest speed network
    links.

    Layer 9 is generally referred to as the blinders layer. This layer applies to organizational managers who have already decided, usually with little or no current information, to dictate a previously successful network plan.

    They may say things such as:

    • “It worked in my last company, so we will use it here.”
    • “Everybody says this is the right solution.”
    • “I read in an airline magazine that this was the best way to do it so that is what we will do.”

    What these managers seem to forget is that they are paying a highly qualified staff to provide them with useful information. These managers bypass planning in order to make a quick decision.

    Layer 10, the user layer, is in every organization. But users are much more than a layer. While they are one of the reasons the network exists, users can also be a big part of the need for troubleshooting. This is especially true when the users have computers at home and have decided to help the network administrator or
    manager by making changes to the network without consulting the network staff. Equally challenging is the user who didnt do anything when the network segment in his/her immediate vicinity suddenly stopped working. In these cases, the layer 10 identification coincides with layer 10 troubles (and the ID10T label
    some technicians have used).


    TCP/IP Model Overview



    The OSI model describes computer networking in seven layers. While there have been implementations of networking protocol that use those seven layers, most networks today use TCP/IP. But, networking professionals continue to describe networking functions in relation to the OSI layer that performs those tasks.

    The TCP/IP model uses four layers to perform the functions of the seven-layer OSI model.

    The network access layer is functionally equal to a combination of OSI physical and data link layers (1 and 2). The Internet layer performs the same functions as the OSI network layer (3).

    Things get a bit more complicated at the host-to-host layer of the TCP/IP model. If the host-to-host protocol is TCP, the matching functionality is found in the OSI transport and session layers (4 and 5). Using UDP equates to the functions of only the transport layer of the OSI model.

    The TCP/IP process layer, when used with TCP, provides the functions of the OSI models presentation and application layers (6 and 7). When the TCP/IP transport layer protocol is UDP, the process layers functions are equivalent to OSI session, presentation, and application layers (5, 6, and 7).


    Equipment at the Layers



    Some of the layers use equipment to support the identified functions. Hub related activity is “Layer One”.
    The naming of some devices designates the functional layer such as “Layer Two Switch” or “Layer Three Switch”.
    Router functions focus on “Layer Three”. User workstations and servers are often identified with “Layer Seven”.