1 / 23

WCL306: 64-bit Windows 7 - Is Now the Time to Deploy?

WCL306: 64-bit Windows 7 - Is Now the Time to Deploy? . Michael Niehaus Senior Software Development Engineer Microsoft Corporation. Why? Reasons for moving to Windows 7 x64. Using the latest hardware capabilities Accessing up to 192GB of memory Support for UEFI

adele
Download Presentation

WCL306: 64-bit Windows 7 - Is Now the Time to Deploy?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WCL306: 64-bit Windows 7 - Is Now the Time to Deploy? Michael Niehaus Senior Software Development Engineer Microsoft Corporation

  2. Why?Reasons for moving to Windows 7 x64 • Using the latest hardware capabilities • Accessing up to 192GB of memory • Support for UEFI • Support for the latest software capabilities • Applications that can leverage larger amounts of memory • Windows OS integrity features • Windows features that leverage hardware capabilities • Let’s explore the details…

  3. Why?More about memory • Typical configurations are growing • 4GB (and higher) systems are very common today in enterprises • Due to architectural limitations, not all of the memory will be accessible to x86 OSes • Often only 3.2GB to 3.5GB is usable • http://blogs.technet.com/b/markrussinovich/archive/2008/07/21/3092070.aspx • See for yourself with MSINFO32 • If buying machines with more than 3GB RAM, you want Windows 7 x64

  4. Why?More about OS integrity features • Kernel Patch Protection – “PatchGuard” • Protects the integrity of the OS kernel by preventing third parties from “patching” the core kernel functionality • Used to deter rootkits and other malicious code • Hardware Data Execution Prevention (DEP) • Memory not marked “executable” will not be executed • With 64-bit Windows, this is enforced at the hardware layer; 32-bit Windows uses a software implementation • Signed Drivers • All kernel-mode drivers must be signed to run on Windows x64 – unsigned drivers cannot be installed or loaded

  5. Why?More about UEFI • Today’s BIOS has been around for a long time • 16-bit code, 1MB address space limitation, slow option ROM initialization • The new “Unified Extensible Firmware Interface” specification replaces the existing BIOS with a brand new scheme • 32-bit and 64-bit support, CPU independence, full memory access, modular • Many systems ship today with support for UEFI • HP laptops; Dell servers and laptops; IBM servers; etc. • See http://www.uefi.org/news/uefi_industry/UEFIEvaluationPlatforms_2010.pdf for a list • “Legacy” fallback support

  6. Why?More about UEFI • Disk size will soon be an issue with a legacy BIOS • Master boot record (MBR) maximum bootable disk size is 2.2TB • Drives are shipping today that are bigger than that • Seagate: “Industry is not ready for 3TB drives”http://www.tomshardware.com/news/HDD-LBA-GUID-3TB-UEFI,10436.html • UEFI eliminates disk size issues • GUID Partition Table (GPT) allows for a maximum size of about 16.8 million TB

  7. Why?UEFI and Windows • Microsoft only supports UEFI with 64-bit Windows • No support for x86 OSes (requires “legacy” BIOS fallback mode) • There are UEFI-specific Windows features: • Faster initial booting • No need to use Int13 BIOS calls • Faster resume from hibernate • No need to use Int13 BIOS calls • Multicast PXE boot • http://www.microsoft.com/whdc/system/platform/firmware/UEFI_Windows.mspx

  8. Why?Retail decision-making process • With retail OEMs, the decision is simple: • More than 3GB RAM? You must use Windows 7 x64 • Otherwise, we might let you choose – OEMs would prefer to only support x64 (easy if customers don’t request it) • 75% of PCs sold through retail use Windows 7 x64 • Once larger internal drives are common, there likely will no longer be a choice • Windows 7 x64 + UEFI + GPT

  9. Why Not?Typical concerns about Windows 7 x64 • Hardware compatibility • Software compatibility • Drivers • Inertia • Let’s explore the details…

  10. Concerns:Hardware compatibility • Processors must support x64 • Supported with most desktop and laptop processors released since 2006 • Intel Core 2, Intel i3/i5/i7, Pentium 4 (some models) • AMD Athlon 64, Operon, Turion, Phenom, Sempron (most models) • Supported with the latest Atom processors • “Pineview” • Supported with most ULV processors • Don’t buy machines without x64 support

  11. Concerns:Software compatibility • No support for 16-bit applications • Use Remote Desktop Services, Windows Virtual PC • The Application Compatibility Toolkit can identify application architecture (16-bit, 32-bit, 64-bit) • Applications with low-level OS interfaces need x64 versions • Antivirus, firewall, and VPN software • Anything else that installs a driver (e.g. Sentinel dongle) • Applications could have issues specific to Windows 7 x64 • While most 32-bit applications work fine, testing and remediation steps are necessary • The Windows 7 Compatibility Center now has 64-bit compatibility data

  12. Concerns:Office compatibility • With Office 2010, there is now a 64-bit version • Supports Excel spreadsheets larger than 2GB • Supports bigger, more complex Project files • There are compatibility concerns: • Most available add-ins are presently 32-bit only • VBA compatibility issues when calling Windows APIs • Consider moving to Office 2010 x64 once all of your needed add-ins are available as 64-bit versions • The solution is simple: • Stick to the 32-bit version of Office 2010

  13. Concerns:Internet Explorer compatibility • There are limitations with the 64-bit Internet Explorer: • Can’t load any 32-bit ActiveX controls • Requires 64-bit add-ins (e.g. Java) • Some common ones (e.g. Flash) aren’t available for 64-bit IE • The solution is simple: • Use the 32-bit version of IE on 64-bit OSes • This is the default – you need to go out of your way to run 64-bit IE

  14. Concerns:Administration • Scripts and batch files need to be aware of differences • Location of files • C:\Program Files vs C:\Program Files (x86) • C:\Windows\System32 vs. C:\Windows\SYSWOW64 vs. C:\Windows\SysNative • 64-bit or 32-bit only tools, ActiveX controls, PowerShell snap-ins, etc. • ConfigMgr complications • Inventory of 32-bit vs. 64-bit, e.g. Add/Remove Programs • Task sequences always run 32-bit, may not find 64-bit programs, and need to use 32-bit ActiveX control for accessing environment

  15. Why Not?Availability of Drivers • Recent hardware has drivers • Windows Logo Program requires 64-bit drivers • Vendors must submit 64-bit drivers with 32-bit drivers in order to be certified for Windows 7 • Vendors can submit 64-bit drivers without submitting 32-bit drivers • Older hardware (e.g. printers) may not have drivers • Most of the time these aren’t supported on Windows 7 x86 either • Time to replace

  16. When?Important considerations as you plan your Windows 7 deployment • Gartner, Inc., “Plan to Implement Some 64-Bit Versions of Windows 7,” Stephen Kleynhans, October 6, 2009 • So it is only a matter of time… By 2014 75% of all business PCs will be running a 64-bit edition of Windows Corporate buyers need to establish a position on moving to 64-bit as part of their Windows 7 planning

  17. When?Important considerations as you plan your Windows 7 deployment • Should you support both Windows 7 x86 and x64? • Maybe, but it will require additional work • Multiple images, driver sets • Additional application testing • Target exceptions • 90/10 is better than 50/50 • Can you be “pure”? • Certainly, but that’s easiest as part of the hardware refresh cycle

  18. How?Tools from Microsoft capable of deploying Windows 7 x64 • Which deployment tools support Windows 7 x64? • All of them! • Windows Deployment Services • Microsoft Deployment Toolkit 2010 • System Center Configuration Manager 2007 • Which tools support UEFI? • Windows Deployment Services

  19. Useful links • Windows 7 Compatibility Center • http://www.microsoft.com/windows/compatibility/windows-7/en-us/default.aspx • Pushing the Limits of Windows: Physical Memory • http://blogs.technet.com/b/markrussinovich/archive/2008/07/21/3092070.aspx • 64-Bit Momentum Surges with Windows 7 • http://windowsteamblog.com/windows/b/bloggingwindows/archive/2010/07/08/64-bit-momentum-surges-with-windows-7.aspx • 2.2TB Drive Partition Limits • http://www.uefi.org/learning_center/UEFI_MBR_Limits_v2.pdf • UEFI and Windows • http://www.microsoft.com/whdc/system/platform/firmware/UEFI_Windows.mspx • Why UEFI • http://community.edc.intel.com/t5/New-to-Intel-Architecture-Blog/Ask-a-BIOS-Guy-quot-Why-UEFI-quot/ba-p/2781

  20. Q&A

  21. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

  22. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related