Windows 7 has a mass appeal to Windows XP users and their system administrators. While major advances were made in Windows Vista and Windows 7, you will always find people opposing change. And, boy! A lot has changed in the user interface since Windows XP!
In the past opposition has been dealt with with deception many times. The first sewing machines, for instance, were disguised as furniture, so they’d lack any resemblance with the industrial sewing machines found in factories.
In this post I’ll show you how to revert parts of the user interface in Windows 7 back to Windows XP. Using clear step-by-step procedures you’ll find how to:
- Go back to grey windows and bars
- Change back the Taskbar and re-enable the Quick Launch
Fade to grey
To lose the transparency on the taskbar and revert it back to grey, all you need to do is select the Windows Classic theme. To select it, right-click on an empty space on the desktop and select Personalize from the context menu. Under Change the visuals and sounds on your computer scroll down to Basic and High Contrast Themes (6). Select Windows Classic as your theme. Close the Personalization window.
The Windows Classic theme will also automatically change the Window borders to Windows XP-style dimensions.
The taskbar
One of the major improvements in Windows 7 is the new taskbar and the Aero capabilities, Flip 3D, Aero Shake, Aero Snap and Aero Peek, coming with it. The taskbar even got a new name: “The Superbar”. It, of course, is the first giveaway to Windows XP users, something has changed.
Correct the buttons and the height
To correct the lay-out of the taskbar itself, you need to edit its properties. Right-click on an empty space on the taskbar and select Properties from the context menu. Perform the following actions:
- Under Taskbar appearance select Use small icons
- Under Taskbar appearance select Combine when taskbar is full as value for Taskbar buttons.
- Click OK.
Now all you need to do is unpin the programs, currently available on the taskbar.
Re-enable the Quick Launch icons
With the standard Windows 7 buttons gone, you can start re-enabling the Quick Launch icons Windows XP users love. For this you need to add the Quick Launch Toolbar to the taskbar. Your first step is to right-click on an empty space on the taskbar, expand Toolbars and click on New toolbar…. The New Toolbar – Choose a folder window appears. Type the following location in the Folder: field:
%appdata%\Microsoft\Internet Explorer\Quick Launch
Click Select folder to add the Quick Launch folder to your taskbar. It should appear on the right side of your taskbar. Of course this is not the place where you’d want the Quick Launch bar or how you want it to look, so let’s change that.
First off, right-click on the Quick Launch label and deselect both Show Text and Show title. Now right-click on en empty space on the taskbar and deselect Lock the taskbar. Drag the Quick Launch bar next to the Start Button, where Windows XP lovers would expect it to be. If necessary swap dragging the Quick Launch with the other taskbar areas.
Fix Windows Live Messenger
One of the annoyances in Windows 7 is the way Windows Live Messenger interacts with its taskbar buttons. With the Windows XP settings you’ll find starting Windows Live Messenger results in two taskbar buttons. To fix this you’ll need to run Windows Live Messenger in Windows Vista compatibility mode.
In the Start Menu Search field type msnmsgr.exe. Right-click the search result and select Properties from the context menu. Open the Compatibility tab. Under Compatibility Mode select Windows Vista for the Run this program in compatibility mode for: field. Click OK.
Concluding
It’s not hard to revert parts of the user interface in Windows 7 back to Windows XP and fool users at first glance. This might just be what you need to convince your users their new desktops are up to spec.
Further reading
Get Windows 7 Taskbar On Windows XP
Windows 7 Superbar for XP: ViGlance
Windows 7 Tips: Round One
Tweak the Windows 7 Taskbar with Taskbar Overlord
Taskbar Overlord Tweaks the Windows 7 Taskbar
Windows 7 Taskbar: Some Beta to RC Changes
Windows 7: Superbar Overview
How to Get the Old Thin Taskbar Buttons with Text in Windows 7?
Make the Windows 7 Taskbar Work More Like Windows XP or Vista
The Windows 7 Taskbar
The New Windows Taskbar in Windows 7
Restore classical Taskbar in Windows 7
Evolution of the taskbar in Windows 7 – “Superbar”
More on the Windows 7 UI: new taskbar will be mandatory
How to Enable or Disable Quick Launch in Windows 7
Disclaimer Pre-release Software
The information on this webpage applies to software from Microsoft that was in testing phase but utilizable by experienced users by the time the webpage was written. This software has not been released for sale, distribution or usage for the general public. The information on this webpage and the software are provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
“I’ve always believed in information equality.”
While hundreds of companies charge their customers for services with knowledge and experience as unique selling points (USPs), I’ve sat on the sideline enjoying the view. I heard these companies (most of them Microsoft Partners) complaining about shifting expectations and a changing landscape. They fear becoming obsolete, because customers wise up and Microsoft (among others) supply standard tools, frameworks and even products to replace their tools, frameworks and products. Lately even with Online Services. I’ve known information is dynamic in nature. I expected nothing less in this line of business.
“It’s why I started blogging.”
I felt information can be made available freely, without repercussions. Standard practices may be shared without cost, product pitfalls may be found easily and demos can be shown indefinitely. In the end for business it’s not information that counts, but relationships and reputation. I feel a customer should connect without you, not because he knows you’re capable of doing the job, but because you’re granted the job.
“It’s why I kept blogging.”
My employer benefits from my blog. Not in a direct financial way, but in an indirect relationship-based way. Because when I speak to a client I direct them to information I’ve shared here. Because when the (potential) customer reads the information he is reminded of the ways of his current IT partner. … and not just customers. Other IT Pros started reading this blog as well… and linking back to it. As a company we could have generated more revenue on the short term (if our sales force would be up to spec) but in the long term we’re seeing increased deal sizes, etc.
“It’s way this blog had 250.000+ hits in three years.”
Today marks the third anniversary of this blog. A lot has happened in my life. I’ve become a father, an MVP, a Product Manager and even a Bachelor in ICT. I’ve continued to share my creative views on using Microsoft products and technologies (Active Directory, Hyper-V) and people obviously like them. Starting from 0 visitors per day, back in June 2006, this blog picked up to receive nearly 700 hits per day (on weekdays). The rate in which these hits increase is even more staggering: It doubles every year. The first year this blog saw 35,000 hits, the second year 70,000 and in the third year it reached its current 140,000 hit/year average.
“It’s why I’m passionate about this website.”
With my blog receiving a third the hits of the DirTeam.com / ActiveDir.org Weblogs I didn’t need to think twice when Carlos asked me to become the Chief Technology Officer (CTO) of the website, effectively making sure the website(s) on these servers continue to run smoothly.
“It’s why I love this stuff”
Being awarded a 2009 Microsoft Most Valuable Professional (MVP) award for Directory Services is simply the icing on the cake. I’m making an effort because I want to and because people ask me to. People keep telling me I’m doing a brilliant job. That’s what keeps me going. Microsoft recognizes me and values my feedback. That’s nice.
“It’s why it feels like a dream come true”
Just a simple guy, with a simple view and simple means, making an effort. Being noticed, being seen. It’s like a dream come true…
On Patch Tuesday for June 2009 (yesterday, June 9, 2009) Microsoft released security bulletin MS09-18 yesterday to address a vulnerability in Active Directory and Active Directory Application Mode (ADAM) that could allow remote code execution.
It’s should not come as a shock Microsofts Active Directory and Active Directory Application Mode (ADAM) contain insecure code, allowing for much mayhem in enterprise environments. Since MS07-039, MS08-003, MS08-35 and MS08-60 you should have experience with patching these particular Server Roles.
What I did find shocking was the way Microsoft talks about Active Directory Application Mode (ADAM), which is the old name for what most of us now call Active Directory Lightweight Directory Services (ADLDS), but when I examined the Security Bulletin I found out just why:
This vulnerability does not affect Windows Server 2008.
Again, Windows Server 2008 (and Windows Vista) are on the list with unaffected versions of Windows. Up to today only MS08-60 applies to Windows Server 2008. Recollecting: This was a moderate (not a critical) vulnerability that allows denial of service (not remote code execution).
To me, this shows the exceptional feat the Microsoft teams have accomplished in Windows Server 2008. It strengths me in my belief: Windows Server 2008 is the most secure Windows Server platform to date.
For all you Windows 2000 Server and Windows Server 2003 admins out there:
Happy patching!
(especially you, Windows 2000 Server aficionados!)
Further reading
ADAM vs ADLDS
971055 MS09-018: Vulnerabilities in Active Directory could allow remote code execution
969805 MS09-018: Description of the security update for Active Directory: June 2009
970437 MS09-018: Description of the security update for Active Directory Application Mode (ADAM): June 2009
(MS09-018) Microsoft Windows Active Directory Memory Leak Vulnerability (971055)
Microsoft released Service Pack 2 for Windows Vista and Windows Server 2008 to the Download Center and Windows Update. The Service Packs are available in five languages (English, French, German, Japanese and Spanish). Localized packages in your favorite languages (not including Medieval Swahili) are expected to arrive within two weeks. (unofficially available here)
Windows Vista Service Pack 2 and Windows Server 2008 Service Pack 2 are now available on Windows Update. It will feature on Automatic Updates from June 30th, 2009. Be sure to prepare a blocker tool within the next five weeks, if you don’t fancy it.
Windows Vista Service Pack 2
Windows Vista Service Pack 2 is the second Service Pack for Windows Vista. Windows Vista Service Pack 2 includes all hotfixes and security updates to date for Windows Vista with Service Pack 1. For a complete list take a look here.
Windows Vista Service Pack 2 is not a cumulative update. It does not contain the updates from Windows Vista Service Pack 1. Installation of Windows Vista Service Pack 2 requires Windows Vista Service Pack 1.
New functionality
Windows Vista Service Pack 2 also introduces some new functionality:
- Bluetooth 2.1
- Windows Search 4.0
- Windows Connect Now (WCN) Wi-Fi Configuration
- Improved performance for Wi-Fi connections after resuming from sleep mode
- exFAT file system now supports UTC timestamps
- Support for new form factors, such as ICCD/CCID
- Improved performance for the RSS feeds sidebar
- Ability to record data to Blu-Ray media
- Improvements in Media Center (Content protection for TV)
- Improvements in application compatibility
- Improvements in reliability
- Support for the 64-bit central processing unit (CPU) from VIA Technologies
- Removal of the 10 open outbound TCP connection limit
- Improved power management
Windows Server 2008 Service Pack 2
Windows Server 2008 Service Pack 2 is the first Service Pack for Windows Server 2008. Windows Server 2008 already included Service Pack 1 when it launched. Windows Server 2008 Service Pack 2 includes all hotfixes and security updates to date for Windows Server 2008. For a complete list take a look here.
Windows Server 2008 Service Pack 2 also introduces some new functionality:
- Hyper-V as a fully integrated feature
- More authentication options for WebDAV redirector
- Improved backwards compatibility for Terminal Server license keys
- Event logging support in Statistical Process Control (SPC)
- DNS Server now listens over ISATAP address
- Improved power management
Downloads
Windows Server 2008 Service Pack 2 and Windows Vista Service Pack 2
Five Language Standalone DVD ISO (KB948465)
Windows Server 2008 Service Pack 2 and Windows Vista Service Pack 2
Five Language Standalone for x64-based systems (KB948465)
Windows Server 2008 Service Pack 2 and Windows Vista Service Pack 2
Five Language Standalone for x86-based systems (KB948465)
Windows Server 2008 Service Pack 2
Five Language Standalone for ia64-based Systems (KB948465)
Further reading
Windows Vista and Windows Server 2008 SP2 RTW
Hotfixes and Security Updates in Windows Server 2008 SP2 and Windows Vista SP2
Windows 2008 and Windows Vista Service Pack (SP) 2 Available Now
Service Pack 2 for Vista available to download
How to obtain the latest service pack for Windows Server 2008
Microsoft releases Windows Vista SP2 and Server 2008 SP2
Microsoft releases Windows Vista SP2 and Server 2008 SP2
Windows Vista and Windows Server 2008 SP2 Released
Vista Service Pack 2 Standalone is available
SP2 for Vista, Windows Server 2008 now on Microsoft Download site
Windows Service Pack Blocker Tool Kit
Windows Vista SP2 is live, ready to download
Not everyone likes the chilly climate of the server room or the mesmerizing humming of racks, stuffed with server hardware. For these pseudo-admins, Microsoft releases remote management tools. (They work wonders for managing Server Core installations, too!)
The latest incarnation was released two weeks ago and works with Windows 7.
History of remote management tools
For Windows 2000 Server-based environments and Windows Server 2003-based environments, Microsoft enabled remote management from a workstation through the infamous adminpak.msi, which could be found in the %systemroot%\system32 folder of the server. For Windows Server 2008-based remote management tools, however, Microsoft introduced a different tool: The Remote Server Administration Tools (or RSAT for short) For a Windows Server 2008 R2-based environment Microsoft released a new version of the RSAT, designed to run on Windows 7 clients.
Hands on with the Tools
To get hands on with the Release Candidate Remote Server Administration Tools (RSAT) for Windows 7, follow the 3 steps below:
Step 1 Download the software
Below are the all-important download links for the Release Candidate Remote Server Administration Tools (RSAT) for Windows 7.
Microsoft Remote Server Administration Tools for Windows 7 Beta (x86) (35,9 MB)
Microsoft Remote Server Administration Tools for Windows 7 Beta (x64) (42,8 MB)
Step 2 Install the Tools
Installation of the Release Candidate Remote Server Administration Tools (RSAT) for Windows 7 is fairly straight forward when you’re familiar with the way Microsoft update files (*.msu files) work:
After downloading the appropriate package for your architecture (x86 or x64), simply double click the downloaded file.
Of course you would have no problem clicking the Yes button in the screen that asks whether you’d want to install the update corresponding to Knowledgebase article 958830.
The second screen confronts you with the license terms for this piece of pre-release software. Clicking I Accept would start the actual installation process.
When installation is done, you’d click the Close button.
Step 3 Configure the tools
Now that you’ve installed the update package you can enable the remote tools of your choice. Click Start, click Control Panel, and then click Programs. In the Programs and Features area, click Turn Windows features on or off.
When you expand Remote Server Administration Tools you’ll find the tools of your choice:
- Feature Administration Tools:
- BitLocker Password Recovery Viewer
- Failover Clustering Tools
- Group Policy Management Tools
- Network Load Balancing Tools
- SMTP Server Tools
- Storage Explorer Tools
- Storage Manager for SANs Tools
- Windows System Resource Manager Tools
- Role Administration Tools:
- Active Directory Certificate Services (AD CS) Tools
- Active Directory Domain Services (AD DS) Tools
- Active Directory Lightweight Directory Services (AD LDS) Tools
- DHCP Server Tools
- DNS Server Tools
- File Services Tools
- Hyper-V Tools
- Terminal Services Tools
- Server Manager
You can indicvidually select the tools you need. Clicking OK installs them to the Administrative Tools folder.
Step 4 Making the tools visible in the Start Menu
Just like in Windows Vista, the Administrative Tools folder is not by default visible in the Start Menu in Windows 7. To make it visible right click the Windows orb and select Properties from the context menu. On the Start Menu tab, click Customize… in the top right corner.
Scroll all the way to the bottom of the list until you reach the System administrative tools section. Select either the Display on the All Programs menu option or the Display on the All Programs menu and the Start menu option. Click OK twice to confirm your choice.
Step 5 Enjoy!
You’re now ready to manage your Windows Server 2008 R2 boxes!
Concluding
The Release Candidate Remote Server Administration Tools (RSAT) for Windows 7 allow you to remotely manage your Windows Server 2008 R2 boxes.
In this release of the Remote Server Administration Tools (RSAT) the Hyper-V Manager is included, but unfortunately there is no method to manage WINS. It feels like Microsoft has completely forgotten about their initial name resolution protocol…
Related Posts
Remotely managing your Server Core using RSAT
Remote Server Administration Tools (RSAT) – “Adminpak” for Windows Vista SP1
Further reading
Windows 7 RC RSAT Tools Released
Group Policy Infrastructure in Windows: Today and Tomorrow
Remote Server Administration Tools (RSAT) for Windows 7 RC released to the web!
Remote Server Admin Tools (RSAT) for Windows 7 RC – now available
Active Directory Powershell: Installation using RSAT on Windows 7
Remote Server Administration Tools (RSAT) for Windows 7 RC released to the web!
Windows 7 RC Remote Server Tools Available
Microsoft releases update to RSAT tools for Windows 7
Hyper-V RC Release Download Links
RSAT for Windows 7 Release Candidate
RSAT for Windows 7 x86 or x64
Windows 7 RC – RSAT Tools released
Microsoft release RSAT for Windows 7
Admin Pack for Windows 7 RC
Windows 7 Remote Server Admin Tools Available
Remote Server Admin Tools (RSAT) Windows 7
Disclaimer Pre-release Software
The information on this webpage applies to software from Microsoft that was in testing phase but utilizable by experienced users by the time the webpage was written. This software has not been released for sale, distribution or usage for the general public. The information on this webpage and the software are provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
One of the new and interesting features in the Windows 7 Release Candidate (RC), mentioned a few days ago, is the ability to utilize a virtual Windows XP with Service Pack 3 environment for application compatibility.
This feature is called Windows 7 XP Mode and builds on Windows Virtual PC 7. The new Virtual PC now offers features like clipboard sharing, printer sharing, USB support and application publishing.
About Application Compatibility
While most applications, developed for Windows XP will normally run on Windows Vista and Windows 7, a couple of applications will not. A common tactic to approach these applications is to use Compatibility Mode, but for some applications Compatibility Mode doesn’t offer a solution, because, for instance, these applications:
- Use specific (deprecated) Windows features
mIRC is such an application, which will error on exit, because it wants to utilize the Windows Agent, which is no longer present.
- Install specific drivers
Daemon Tools is a classic example of this kind of applications
- Use dongles
Previous versions of AutoCAD, for instance required these to start up the program
For most of these applications Windows XP Mode offers a solution, but still a few exceptions exist:
- Applications that require DirectX
Since Windows XP Mode utilizes a virtual Windows XP installations and Windows Virtual PC doesn’t offer DirectX (yet), you can’t, for instance, play games in Windows XP Mode.
- 64bit applications
Since Windows Virtual PC doesn’t offer 64bit guest support, you can’t use Virtual XP Mode to solve compatibility issues with 64bit applications, you’d typically install on a Windows XP x64 installation.
Install Windows XP Mode
To use Windows XP Mode in the Windows 7 Release Candidate (RC) follow the following steps:
Meet the requirements
Make sure your computer meets the requirements for Windows 7 and Virtual PC 7.
Your computer should be equipped with the minimum system requirements to run Windows 7 (at least a 1 GHz processor and 1 GB RAM) and should have Data Execution Prevention (DEP) and Hardware-assisted Virtualization turned on in the BIOS.
While 1GB of RAM is recommended for 32bit systems and 2GB of RAM is recommended for 64bit systems, one should know that running a Virtual Windows XP installation allocates RAM. By default Windows XP Mode allocates 256MB of RAM.
Several tools exist to check whether Data Execution Prevention (DEP) and Hardware-assisted Virtualization are turned on in the BIOS. A common tool is SecurAble. Microsoft offers a special webpage where people can check their hardware. There, links to the more accurate tools can be found for Intel processor-based systems and AMD processor-based systems:
Get the Windows 7 Release Candidate
Windows Virtual PC 7 and Windows XP Mode can only be installed in a supported manner on the Release Candidate of Windows 7. Download and install Windows 7 Release Candidate, build 7100.
It really doesn’t matter whether you install the 32bit (x86) or 64bit (x64) version of the Windows 7 Release Candidate. Both will do, as long as you meet the requirements above.
Get Windows Virtual PC 7 Beta
Download and install the Windows Virtual PC 7 Beta package corresponding with your Windows 7 Release Candidate installation (32bit or 64bit).
Once you’ve downloaded either Windows6.1-KB958559-x86.msu, (for x86 installations of Windows 7) or Windows6.1-KB958559-x64.msu (for x64 installations of Windows 7), double-click it. Review the end-user license agreement and accept it to install the update.
Once the installation is done, restart the computer.
In contrast to other Windows update packages (*.msu files), Windows Virtual PC will be installed and ready for use. Two shortcuts should be present in the Start Menu:
- Virtual Machines
- Virtual Windows XP
The first shortcut is the Virtual Machines folder in the profile of the logged on account. This folder acts as the new Virtual PC console. Experienced Virtual PC users will find most of the features from previous versions in the streamlined user interface of this folder, although after initial installation the folder is empty.
Get Virtual Windows XP
The easiest way to get your hands on the virtual Windows XP with Service Pack 3 installation is to follow the Virtual Windows XP shortcut in the Start Menu. This shortcut will redirect you to the Windows XP Mode Beta download location. Download the Windows XP Mode package, corresponding with your Windows 7 installation (32bit or 64bit)
Virtual Windows XP is a pretty hefty download, but the 445MB contains everything you typically find in a Windows XP with ServicePack 3 installation: It is a compressed and sysprepped installation.
Note:
Although a 64bit download of Windows XP Mode Beta is available,
Windows XP Mode offers a 32bit Windows XP installation only.
After downloading double-click VirtualWindowsXPMode.msi
Follow the on screen instructions to install, configure and automatically run your virtual Windows XP installation:
- Agree to the Virtual Windows XP License Agreement
- Specify a password for Virtual Windows XP
- Specify Automatic Update Settings
- Start Virtual Windows XP
Install & publish an application
Your own applications
Install the application, that needs Windows XP compatibility, inside your virtual Windows XP installation, like you would with every other application on every other Windows XP installation. After installation, open the application once. When your done close the Virtual Windows XP screen.
A shortcut to the application will become available in the Start Menu of your Windows 7 installation, appended by ' (Virtual Windows XP)'.
Built-in Windows applications
Since the Windows XP with Service Pack 3 installation Microsoft ships for XP Mode contains all the games, it’s easy for users to use these games when the games in Windows 7 are disabled by an administrator. Most built-in Windows applications have been excluded from publishing, however.
You can easily get shortcuts for these applications to appear in your Windows 7 Start Menu by editing the registry in the Virtual Windows XP installation and deleting the key corresponding to the application in:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtual Machine\VPCVAppExcludeList
Also, if a shortcut is not already present for your application in the Programs folder of the All Users Start Menu you need to manually create one.
Concluding
Windows XP Mode offers Windows XP compatibility for 32bit applications, that don’t require DirectX. It is easy and fast to set up when you meet the requirements. If you require additional features in the enterprise though (like central management and deployment), Med-V is for your weapon of choice.
Further reading
Easy Way to Determine If CPU Supports Windows 7 Virtual PC (XP ...
Hyper-V: Will My Computer Run Hyper-V? Detecting Intel VT and AMD-V
Virtual XP Mode and Windows 7
Windows XP Mode and Windows Virtual PC Available on TechNet
How to confirm your PC can run Windows XP Mode
Coming Soon: Windows XP Mode and Windows Virtual PC
Secret No More: Revealing Windows XP Mode for Windows 7
More on Windows 7's 'XP Mode'
How to Set Up and Use XP Mode in Windows 7
Windows 7 RC Available, Includes “XP Mode”
Windows XP Mode Internals - Part 1 (Overview)
Windows 7's XP Mode to Require 2GB of RAM, True Processor Virtualization
Windows XP Mode for Windows 7 Screens
Microsoft to provide 'XP Mode' with Windows 7
Windows XP Mode coming to Windows 7, could be a game-changer
Windows 7 reveals XP mode AKA the IT guy’s wet dream
XP Mode confuses and amuses Windows 7 reviewers
Windows 7 XP Mode Explained- It’s Beta Software
Since parenthood takes up a lot of time (heating bottles, changing diapers/nappies, getting lost in those beautiful baby-eyes, walking around with her in your arms and all that jazz) I guess some of you expect to see a little less technical content on this blog.
I agree, but you certainly won’t find less attempts to be witty. As proof I created a little game. It’s Microsoft orientated (of course!), has to do with our baby girl and just cracks me up every time. (must be my weird sense of humor)
Below are two pictures. One of the pictures shows our girl. The other picture shows Microsoft CEO Steve Ballmer. Spot the difference! *
* Or just be amazed by the amounts of similarity between the two expressions…
Sophie Berkouwer
May 2nd, 2009 | 14:30 | 4000 gr | 49 cm
We are thrilled with the birth of our first daughter, Sophie.
She was born on May 2nd in the Vlietland Hospital in Schiedam, the Netherlands.
It was a beautiful day to be born!
Tip!
Be sure to check out the gallery with pictures !
The Release Candidates (RCs) for Microsofts upcoming Windows Client Operating System, Windows 7, and Microsofts upcoming Server Operating System, Windows Server 2008 R2, are now available for public download.
While these Release Candidates were already available for download to TechNet and MSDN subscribers from April 30th, now everyone can legally (and safely) download the bits belonging to the Release Candidates for both the 32-bit (x86) and 64-bit (x86-64, or x64 for short) version of Windows 7 and the 64-bit versions (x64 and ia64) of Windows Server 2008 R2.
Version information
The technical identification string for the Windows 7 and Windows Server 2008 R2 Release Candidates is 6.1.7100.0.winmain_win7rc.090421-1700. This string contains the following information:
- These Release Candidates are still identified as NT version 6.1. Windows Vista and Windows Server 2008 showed NT version 6.0. A common misconception is Windows Server 2008 R2 and Windows 7 are also Windows NT version 7.
- These Release Candidates were compiled on April 21st, 2009. Compiling succeeded the first time and finished around 17:00.
- The Build number is 7100. Builds with a number between 7000 and 7100 are members of the Release Candidate (RC) branch. Numbers above 7105 are members of Branch pushing towards RTM. More information here.
Changes from Beta
Microsoft communicated the following changes in functionality between the Beta versions of Windows 7 and Windows Server 2008 R2 (Build 7000) and the Release Candidate versions of Windows 7 and Windows Server 2008 R2 (Build 7100):
Windows 7
- Internet Explorer 8 (RTM)
- Remote Media Streaming
- Windows XP Mode & Windows Virtual PC 7 Beta
- Several enhancements to the Windows Taskbar, JumpLists and Search
- Several enhancements to Windows Touch
- Several enhancements to Windows Media Player
- Tweaks in User Account Control (UAC)
- System partition reduction (from 200MB to 100MB)
- Several Direct Access improvements
More information on the changes between Windows 7 Beta and Windows 7 RC is available on the E7 blog here and here.
Windows Server 2008 R2
- Internet Explorer 8 (RTM)
- Several DirectAccess improvements
- New PowerShell cmdlets
- Applocker User Interface
- Tweaks in User Account Control (UAC)
- Print Administrator delegation
- Several changes to Remote Desktop Services (RDS)
- 64 Logical Processor support in Hyper-V (up from 32)
- Hyper-V Processor Compatibility Settings
More information is available in the What’s Changed in This Release Candidate of Windows Server 2008 R2 section on TechNet.
Downloads
Windows 7
To get your hands on the bits and product key, related to the Release Candidate (RC) for Windows 7 you can use the menu provided here. ISO downloads are available in both 32-bit (x86) and 64-bit (x64) versions in English, German, Japanese, Spanish and French. Sizes for the ISO downloads range from 2,413MB (x86) to 3,119MB (x64)
Additional Language Packs can be found on Microsofts Connect Website. Windows7Center.com has the skinny on the Language packs, including the Connect Invitation ID to get started and a lengthy tutorial on changes the screen language.
The Windows 7 Upgrade Advisor beta can be found here. This tool can be used to scan a PC to see if it's ready for Windows 7, and reports any known compatibility issues.
Windows Server 2008 R2
To obtain bits and a product key for the Release Candidate for Windows Server 2008 R2 take a look here. Both ISO downloads as VHD downloads are available.
ISO downloads are available in 64-bit editions (x64 and ia64) in English, German, Japanese, Spanish and French. Sizes for the ISO downloads range from 2,371MB to 2,930MB.
The downloadable VHDs are available in English only and contain a fully functional evaluation copy of Windows Server 2008 R2 x64 Enterprise Edition (RC) supplied as both a Full installation and Server Core installation.
Note:
The downloadable VHD for Windows Server 2008 R2 RC requires Hyper-V.
Additionally the Release Candidate for the Windows 7 RC Automated Installation Kit (AIK) is also available. This Kit allows you to customize and deploy the Windows 7 and Windows Server 2008 R2 Operating Systems in large environments. The Windows AIK download weighs 1,435MB.
Concluding
Welcome to the Windows 7 Release Candidate!
Further reading
Microsoft PressPass: Windows 7 Release Candidate Is Available From Microsoft
Leaked Windows 7 RC Build 7100 May Contain A Trojan
RTM Builds – Clearing the Confusion
Windows 7 Ultimate test version available to public today
Windows 7 RC Download now up for non-subscribers
Windows 7 RC Now Available to Public
Windows 7 Release Candidate Available for Public May 5th!
Windows 7 and Windows Server 2008 R2 Release Candidates are now available on MSDN
Windows 7 Release Candidate Is Available From Microsoft
Windows 7 Release Candidate Is Available From Microsoft
Windows Server 2008 R2 Release Candidate and WAIK – now available
Announcing Windows Server 2008 R2 Release Candidate (RC)
Windows 7 Release Candidate is now available!
RC for Windows Server 2008 R2 and Windows 7 released
Download Windows 7 Beta Display Language Interface Packs (LIP and MUI)
Windows® Automated Installation Kit (AIK) for Windows® 7 RC
Yesterday I needed to install a box with Microsoft Windows 2000 Server for some educational purposes.
While installing this Operating System, which is nearly ten years old and nearly out of support, I noticed some differences, compared to installing Windows Server 2008. These changed made me feel a bit nostalgic, but I’m glad installing has been made SO much simpler in the last years.
Experiences
- Setup disks
The CD I’m using is Windows 2000 Server without any Service Packs. None, what so ever. This version of the Windows 2000 Server CD is not bootable. The BOOTDISK subfolder contains four *.img files that need to be written to floppies. Both a 16-bit tool (makeboot.exe) and a 32-bit tools (makebt32.exe) are available to do so.
Afterwards it’s time to boot from floppy 1, change floppies 2 through 4 and after 10 minutes finally doing some real installing. Don’t forget to take floppy four out of the machine too: your box won’t but until you do…
- Text-based setup
Windows 2000 Server uses a text-based setup to go through the first few steps to install your server. WordPerfect under water screen galore! One of the screens, by the way, is the End User License Agreement (EULA). F8 is used to agree with it, which is a nice touch, but got canned somewhere along the way.
- FAT can be used for formatting
While useful for dual boot scenarios with FAT-based Windows NT installations, nowadays you don’t need to choose to format your system partition with FAT or NTFS. Where are my fast format options, anyway? This is taking up way more time than usual. Windows Server 2008 would’ve been installed by now.
- Files being copied
Oh well… at least I’m not staring at blue Microsoft progress bars… these are yellow. Oh wait… copying files?! Wait, that’s right. Up until Windows Vista, Windows was copied to disk file by file, making installation last for an hour.
- Graphics-based setup
When you get through the text-based piece of the setup you’re in round 2. The 256color-rich graphical user interface for installing Windows 2000 Server. At least the window can be dragged around, while waiting for progress, creating an excellent diversion.
- Product Keys
You can’t install Windows 2000 Server without a Product Key. Furthermore, you need to have a Product Key, corresponding with the media type. When installing Windows 2000 Server (or Windows 2000 Professional or even Windows XP Professional for that matter) using a Select CD, you need to have a Select Product Key. When using a trial CD, you need a trial Product Key. The same goes for Retail media: Only a Retail Product Key is accepted…
Again, this was fixed with Windows Vista. One media for all purposes. Don’t have a
Product Key at hand when installing? Don’t worry! You can install it without entering a Product Key and simply enter it later. Or not at all and enjoy Windows for 30 days.
- Information gathering
During installation Windows 2000 Server Setup asks a lot of questions. About the time and date, about the administrator password, about the registered owner, about the licensing mode, about networking settings and about its hostname. Not too bad in its own, but every time Setup needs information, installation stops until you’ve answered the question.
Windows Server 2008 Setup is much less hassle: Input some information at the start, walk away, return 20 minutes later, change the administrator password and input remaining information.
- Configure your Server wizard
While it was a good idea at the time Windows 2000 Server launched, the post-logon wizard comes to maturity in more recent versions of Windows Server. Windows Server 2008 R2 even goes beyond current local wizardry and allows to run the Server Manager remotely.
Trends
Windows 2000 Server brought a lot of new stuff. Active Directory was one of them.
When looking at Windows 2000 Server and its successors a couple of trends emerge:
- Installation is getting simpler.
Bootable CDs/DVDs replaced the bootable floppies of Windows NT and Windows 2000 Server. The choice not to cut up Windows Server 2008 to CDs was a good one in this perspective.
- Installation is getting faster.
Image-based setups, combined with information gathering at the beginning and after installation is done, speeds up installing Windows Server.
- Installation is getting easier.
A Product Key isn’t always available, so why ask for it explicitly during setup? I feel it’s a good thing the media / product key lock-in has been removed. It makes installing Windows so much easier.
- Installation is getting more secure.
The out of the box experience has improved dramatically in the last Windows versions. Since the programs, launched at startup, provide an overview of what the server is doing, it’s easier for novice administrators to find their way and manage the system more proactively.
- Formats wither fast
Ten years ago FAT and FAT32 were king. Today you have to try hard to install Windows on a FAT32 partition…
Concluding
Despite the better installation experience, I’m left with one question:
Can we have F8 back to agree with the End User License Agreement?
For old times sake ;-)
Want to hear first hand what Windows Server 2008 R2 brings to Active Directory? Want to be able to ask questions to a couple of highly knowledgeable Directory Services MVPs?
Look no further! Just tune in!
Laura Hunter and Brian Desmond will be doing a webcast discussing and demoing the new Active Directory features in Windows Server 2008 R2 tomorrow as well as answering Active Directory questions. The 90 minute time slot is expected to be filled with 45 to 60 minutes on the new features in Windows Server 2008 R2 and the remainder taking questions on the presentation and Active Directory in general.
Laura and Brian love to see you there!
Registration Link
https://oreillymedia.webex.com/oreillymedia/onstage/g.php?d=662451195&t=a
Date
Friday, April 24, 2009
Time
10am PT, San Francisco | 6pm - London | 1pm - New York | Sat, Apr 25th at 3am - Sydney | Sat, Apr 25th at 2am - Tokyo | Sat, Apr 25th at 1am - Beijing | 10:30pm - Mumbai
Duration
Approximately 90 minutes.
Cost
Free
More information
WS2008 R2 Active Directory Webcast - Tomorrow, Friday 4/24
What's New in Windows Server 2008 R2 Active Directory
O’Reilly Webcast: What’s New in Windows Server 2008 R2 Active Directory - Friday, April 24 O’Reilly Webcast: What’s New in Windows Server 2008 R2 Active Directory - Friday, April 24
Free WS2008 R2 Active Directory Webcast
Designing and implementing a virtual environment on top of Hyper-V can be challenging. In the first four parts of this series I looked at the design choices and management actions regarding Active Directory in Hyper-V environments. Jorge made some interesting points as well, but one Active Directory best practice still remains to be tackled:
Physically secure all domain controllers in a locked room.
In this part I’ll look into the possible ways of securing virtual Domain Controllers running on top of Hyper-V, besides the apparent open doors written by John Gilham:
- Using NTFS rights and auditing on the virtual host
- Using Encryption File System (EFS) on the virtual host
- Using BitLocker Drive Encryption
- Using syskey.exe
NTFS rights
To secure files on a server one would normally look at NTFS rights. For Hyper-V security the same approach is valid, but one should know which accounts to give access to what data.
Let’s first look at the data. Two pieces of information define virtual machines on a Hyper-V virtual host:
- Configuration Information
This information contains the rights management within the Hyper-V Manager and contains information on each virtual machine. The files in this location are small. The configuration files are typically stored in:
C:\Program Files\Microsoft\Windows\Hyper-V
- VM configuration and hard disks
Virtual hard disks contain the information stored on the hard disks within the virtual machine. Snapshots are virtual hard disks that are used as differencing disks when you use the snapshot functionality in Hyper-V. Virtual hard disks and snapshots are stored in the same folder. These are big files. This folder is typically located at:
C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks
As a security measure you should move the default location where the above information is stored to another location. This can be done in the Hyper-V Management Microsoft Management Console (MMC).
In a Hyper-V environment the following accounts should be given access to the above locations:
| Location | Account | NTFS Rights |
Configuration
location | Administrators
SYSTEM | Full Control
(This folder, subfolders, and files)
Full Control
(This folder, subfolders, and files) |
VM Hard disks
location | Administrators
SYSTEM
CREATOR OWNER
| Full Control
(This folder, subfolders, and files)
Full Control
(This folder, subfolders, and files)
Full Control
(Subfolders and files only) |
All other accounts should be given as limited NTFS rights as possible.
The above NTFS rights of course need to be audited. For this use the following high level steps:
- Log in as an administrator on the hyper-V virtual host.
- Right click on the location where either the Hyper-V configuration information or the VM hard disks are stored and right-click the folder. Select Properties.
- Click the Security tab, and then click the Advanced button.
- Click the Auditing tab.
- Click the Add button to make the Select User, Computer, or Group dialog box display. Add the administrators group and SYSTEM account.
- The Auditing Entry dialog box displays. Specify the type of access you want to audit using this dialog box. Next to the access right, select Failed, and then click OK.
- Click OK to close the Properties dialog box
Also, be sure to check your auditing settings afterwards…
Encryption File System (EFS)
Back in the Virtual Server 2005 days Microsoft advised to use the Encryption File System (EFS) to secure virtual hard disks on the disk of the virtual host. While this meant the performance of the virtual machine would diminish with roughly 5%, it was a good security measure. This practice was dropped by Microsoft for Hyper-V, quoting Mert Biyiklis blog:
Microsoft specifically advices not to use Encryption File System (EFS) with Hyper-V.
Hyper-V does not support the use of storage media if EFS has been used to encrypt virtual hard disks. More information can be found here.
BitLocker Drive Encryption
BitLocker Drive Encryption can be used to encrypt the contents of the entire hard disk of a Windows installation, except certain boot files, stored on a dedicated boot partition. This feature is currently available in some versions of Windows Vista and Windows 7 and of course in Windows Server 2008 and Windows Server 2008 R2.
BitLocker is an excellent method to encrypt virtual machines, but only from the virtual host itself. Quoting the Hyper-V security guide:
Use BitLocker Drive Encryption in the Hyper-V management operating system only. Do not run BitLocker Drive Encryption within a virtual machine. BitLocker Drive Encryption is not supported within virtual machines.
To enable BitLocker Drive Encryption on a virtual host, make sure to read the post by Jesper Johansson on enabling BitLocker on an existing computer. It involves creating a separate primary partition, making it bootable, booting from it and then turning encryption on. Once you’ve succesfully encrypted your system drive, you can encrypt any other partitions or volumes on which you’ve stored your configuration information and/or virtual hard disk files.
A further note should also be picked up from Microsoft Knowledgebase article 947302 regarding using BitLocker Drive Encryption in Failover Clustering scenarios:
Volumes that are encrypted by BitLocker are not supported in a clustered environment in Windows Server 2008.
This means you can’t encrypt volumes, containing highly available virtual hard disks in a Hyper-V Failover clustered environment…
Syskey.exe
The System Key Utility (syskey.exe) is used in old skool (non-virtualized) situations to secure account data on disk. On non-Domain Controllers the passwords in the Security Account Management (SAM) database are further encrypted. On Domain Controllers the passwords in Active Directory data are further encrypted, using stronger encryption algorithms beyond the default algorithms.
Syskey uses an encryption key. This key can either:
- be stored on disk (server generated, default)
- be a system boot password (configured by the administrator)
- be stored on a floppy and needed at boot time (server generated)
Inside the Virtual Domain Controller
Using one of the first two options inside your virtual Domain Controllers results in a situation that isn’t really useable from a security point of view. Remote Server Management and automated Patch Management will need extra procedures, where an admin on a remote location might need to have the password or floppy to reboot the machine when needed.
Syskey on disk
When using the System Key Utility (syskey.exe) with a server generated password on a virtualized Domain Controller disk it becomes harder to retrieve passwords from the Active Directory, when it’s turned off. However, the virtual disk can be taken from a virtual host and brought online on any other Hyper-V environment. One of the most commonly used attack vectors can’t be stopped using this System Key Utility scenario.
Syskey floppy
Hyper-V can’t work with hardware floppies, so the floppy needs to be virtualized and optionally inserted. A virtual floppy can be used, but needs to be stored on the virtual host and needs to be inserted using the Hyper-V Manager. Both require an administrative role being given to someone you might not want to give it to. Storing it besides the virtual hard disk then again is simply security by obscurity.
Syskey password
A boot password is a good security measure, when implemented correctly. Since a virtual Domain Controller can present its password screen at boot time, only procedures needs to be in order to facilitate remote server management and patch management.
The challenge using the System Key Utility (syskey.exe) inside your virtual Domain Controller is now evident. When used properly it can add an additional layer of security. If used improperly it results in hassle and weaknesses.
On the virtual host
Using the System Key Utility (syskey.exe) inside your virtual host doesn’t offer the multitude of options.
Syskey floppy
The floppy drive option requires an administrator at a remote location to have the floppy or leaving the floppy in the virtual host itself.
Syskey password
The boot password requires an administrator at a remote location to know the boot password. Unless you’re using advanced remoting hardware and software like iLO, DRAC, etc you won’t be able to remotely access the boot screen. Adding another person to your inner circle of trust most often results in scenarios you’d want to avoid with these kinds of persons.
Syskey on disk
The server generated password on disk is something you could implement, though. The scenario doesn’t require local access to the virtual host(s), while adding at least a layer of defense against network attacks.
Concluding
It should be imperative you should not let unauthorized, incapable and unknown persons anywhere near your domain controllers. Implementing this best practice in a Hyper-V environment though isn’t as easy as it seems.
To secure Active Directory Domain Controllers in a Hyper-V environment, use the following techniques:
| Security Measure | Virtual Host | Virtual Guest
(Domain Controller) |
| NTFS rights and auditing | Yes | Built-in* |
| Encryption File System (EFS) | No | No |
| BitLocker Drive Encryption | Yes
(Unless clustered) | No |
| System Key Utility (syskey.exe) | Yes
(Disk based) | Yes
(Disk, password based) |
* A default installation of Active Directory on a Windows Server further restricts user rights
on the file system and the registry, compared to a default Windows Server installation.
Related Posts
Virtualizing Domain Controllers
Active Directory in Hyper-V environments, Part 1
Active Directory in Hyper-V environments, Part 2
Active Directory in Hyper-V environments, Part 3
Active Directory in Hyper-V environments, Part 4
Further reading
Active Directory Best practices
VDI Security - Using Encryption to Protect Virtual Machine Resources
Download details: Hyper-V Security Guide
Hyper-V Step-by-Step Guide: Hyper-V and Failover Clustering
Virtual PC Guy's WebLog : Whitepaper: Hyper-V and BitLocker
[DOC] Windows Server 2008 Hyper-V and BitLocker Drive Encryption
Windows BitLocker Drive Encryption Step-by-Step Guide
Hyper-V Security Best Practice: Use BitLocker
BitLocker and Hyper-v
Volumes that are encrypted by BitLocker are not supported in a clustered environment
Q. Does Hyper-V support Windows BitLocker Drive Encryption running … - Windows IT Pro
Planning for Hyper-V Security
How to use the SysKey utility to secure the Windows Security Accounts Manager database
Windows NT System Key Permits Strong Encryption of the SAM
SYSKEY
Cracking Syskey and the SAM on Windows XP, 2000 and NT 4 using Open Source Tools What happens when syskey is installed, and how to get rid of it
Protecting the SAM with Syskey
Looking for a complete resource on remotely managing your Server Core box? Look no further! I've done research on the topic the last year and have come up with the following remote management methods:
Remotely managing your Server Core using Compmgmt.msc
Remotely managing your Server Core using RSAT
Remotely managing your Server Core using RDP
Remotely managing your Server Core using WinRM and WinRS
Remotely managing your Server Core using SSH
The remaining question is which method to use in which situation:
Is your environment a mixed environment?
When your environment contains Windows XP and Windows Server 2003 hosts, you can't use many features in the Computer Management MMC (compmgmt.msc) Snap-ins or the Event Viewer from these hosts. The Remote Server Administration Tools (RSAT) cannot be used as well and the Windows Server 2003 Adminpak doesn't offer management of all Server Core features.
Use RDP or SSH from Windows XP and Windows Server 2003.
From Windows Vista SP1 and Windows Server 2008 you can use any method.
Does your environment consist of different routed subnets?
When your Server Core installation of Windows Server 2008 and your Windows Vista box are on different subnets you can't use many of the Computer Management MMC (compmgmt.msc) Snap-ins.
Use RDP or SSH in routed environments.
Does your environment consist of different domains or workgroups?
Many tools reuse your credentials to authenticate with the Server Core installation. cmdkey.exe provides a way to use alternative credentials, but these won't always work well with certain MMC Snap-ins.
Use WinRM / WinRS, RDP or SSH in multi-domain and workgroup environments.
Microsoft has released Windows Internet Explorer 8.0 to the web last Thursday. Besides improved reliability, security, performance and a handful of new features, Internet Explorer 8 introduces a new rendering engine, which is enabled by default. This new engine might break your mission-critical web based applications.
To provide IT Professionals, like you and me, with information to cope with these new situations, Microsoft has issued a load of documents, guidance and other downloads to assist them in deploying, managing and blocking Internet Explorer 8.0. Other IT Professionals have also written about Internet Explorer 8.0.
Below is a combined list of Internet Explorer 8.0 resources:
Blocking
Download links
Compatibility
Deployment & Management
Feature overviews
Comparisons
Security
Support
Fun stuff
One of the most exciting new features in Windows Server 2008 R2 is the ability to live migrate virtual machines between nodes of a Failover Cluster. In contrast to Windows Server 2008’s Hyper-V this enables admins to failover virtual machines without noticeable downtime.
SCVMM 2008
Admins can use the built-in Cluster Admin (GUI) tools to failover virtual machines at any time. Virtual Machine Manager (VMM), a member of Microsoft’s System Center family, allows for more pro-active deployments and management, beyond the built-in tools.
System Center Virtual Machine Manager (SCVMM) offers:
- A web interface to manage virtual machines, that enables admins to start and stop virtual machines. (Power) Users can also use this functionality, transforming the web interface into a self-service portal.
- PowerShell cmdlets to manage virtual machines from the command line and scripts.
- A library in which you can store virtual machine templates, virtual machine disks and (PowerShell) scripts to easily and fast produce new virtual machines.
- Performance & Resource Optimization (PRO) tips, to integrate with System Center Operations Manager (SCOM) 2007. These tips provide the ability to pro-actively perform actions / run scripts, kicked off by events detected by System Center Operations Manager (SCOM) 2007.
- Intelligent placement and consolidation candidate functionality to make more informed decisions where to place new virtual machines and/or migrate virtual machines to.
- Management of VMWare ESXi and ESX hosts the Microsoft way.
A server license for System Center Virtual Machine Manager (SCVMM) can be purchased as any other Microsoft product, but System Center Virtual Machine Manager (SCVMM) doesn’t require Client Access Licenses (CALs), or Management Licenses (MLs) as they are called in the System Center universe. Virtual Machine Manager (SCVMM) can also be purchased as part of the Systems Management Suite Enterprise (SMSE).
SCVMM 2008 R2
The R2 version of System Center Virtual Machine Manager (SCVMM) 2008 goes beyond System Center Virtual Machine Manager (SCVMM) 2008 and adds support for Hyper-V R2, the version of Hyper-V that ships with Windows Server 2008 R2 (currently in beta). It also adds support for the following Hyper-V R2 features:
System Center Virtual Machine Manager (SCVMM) 2008 R2 is currently in public beta. You can join the Beta program here. (Live ID required) This will enable you to download and use Beta 1 of System Center Virtual Machine Manager (SCVMM) 2008 R2 as either an installation package or a preconfigured virtual machine (*.vhd file).
If you need assistance with the beta please participate in the public forums for System Center Virtual Machine Manager.
Related posts
An early look at new Hyper-V features
Further reading
Microsoft System Center Virtual Machine Manager 2008
System Center Virtual Machine Manager 2008 R2 beta available
What is VMM 2008 R2 Beta and what are its new capabilities?
SCVMM 2008 R2 Beta started
SCVMM 2008 R2 Beta – now available for download
System Center Virtual Machine Manager R2
Windows Server 2008 R2 Hyper-V Live Migration Demo
Managing VI3 with SCVMM considered harmful
Disclaimer Beta Software
The information on this webpage applies to software from Microsoft that was in testing phase but utilizable by experienced users by the time the webpage was written. This software has not been released for sale, distribution or usage for the general public. The information on this webpage and the beta software are provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.