Showing posts with label Virtualized XP. Show all posts
Showing posts with label Virtualized XP. Show all posts

Saturday, 9 July 2011

Windows XP Professional Service Pack 3 – Fresh Install Has How Many Updates?

We are setting up a couple of retail Windows XP Professional SP3 VMs. Once the base OS install was complete and the Hyper-V Integration Services were installed we allowed XP to cache updates.

The first round of updates state 100 available:

image

We allowed all updates but four:

image

Included in that first round was IE8:

image

We removed the Download and Install Updates check mark to just install IE8 since we are looking for the next round’s true update requirement.

Round 2 wanted two of the four dropped updates:

image

From there we received notification for one:

image

We then went to Microsoft’s Update site and updated to Microsoft Update.

Once we went through the Genuine Advantage Tool install we were able to choose from the remaining updates:

image

We had thought that we were done updating after the above Microsoft Update process but Windows Automatic Update chose to toss more our way after that.

Start to finish the update process for the freshly installed Windows XP Professional SP3 took a little over an hour and a half.

Note that the XP Pro base image used to install the OS was a trial version so the OS image was quite dated.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Tuesday, 27 October 2009

Windows 7 XP Mode – Those VHDs Are Portable!

We just rebuilt a client’s Lenovo T500 that we had installed Windows 7 RTM and XP Mode RC onto.

Besides the need to start fresh with an RTM version of XP Mode, our client also had us install a 160GB Intel second generation Solid-State Drive.

So, we decided to start with a fresh install of the Windows 7 Enterprise x64 OS and XP Mode.

The main thing to keep in mind when it comes to working with RTM versions of XP Mode and users changing out their hardware is the ability to take that XP Mode VM with them to the new system.

Another reason to keep this in mind is that the previous drive in this case was encrypted with BitLocker. We may have been able to gain access to it if we had a similar T500 series around the shop and the original BitLocker backup key . . . maybe.

Thus, a new consideration when it comes to migrating a user’s profile to a new workstation (workstation setup checklist post) is to get those VHDs.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Wednesday, 12 August 2009

Toshiba Tecra S10 – Virtualization Is Disabled By Default in BIOS

We just received a new Toshiba Tecra S10 laptop that does not even have a product page on Toshiba’s site yet.

The unit is a new model Tecra S10 with a Core 2 Duo T9600 2.8GHz CPU and 4GB of RAM. The principle reason for sourcing this model is the high resolution 1680x1050 LCD along with the extra processing power presented by the Intel C2D T9600.

We will be installing Windows 7 Ultimate x64 on this laptop as we require XP Pro Mode. Toshiba seems to be a bit behind Acer on the architecture front as the Windows Vista on it is x86 (32bit). Acer has started factory shipping all of their laptops with Windows Vista x64 versions which means 64bit Acer drivers are available for their products.

The lack of 64bit drivers for the Tecra may present a bit of a problem with Windows 7 x64. If it does, we will back off and install the x86 version of Windows 7 Ultimate x86.

Since we require XP Pro Mode, we need to verify if the BIOS on this laptop has the Intel VT enabled. The chipset is Centrino 2 vPro (previous blog post on Windows 7 XP Pro Mode and hardware requirements).

To get into the Tecra’s BIOS, we need to do the following:

  • Press and hold the ESC key then power up the laptop.
  • Press the F1 key when requested to do so.

Once into the BIOS, sure enough the Intel VT setting was Disabled. We also took note that the Trusted Execution Technology was also Disabled. Since both are required, we enabled them.

One other note of interest, both the TPM and Intel’s AMT (vPro) management were disabled in the BIOS out of the box. The TPM is required for BitLocker and BitLocker To Go. Intel’s AMT is required for remote out-of-band management of the laptop. Both will be enabled as well.

Now we’re off to set up a USB flash drive to install Windows 7 (TechNet Magazine article) with.

We use the OCZ ATV Turbo flash drive for all bootable and high data volume usage because time is money and they are soak the USB bus fast!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Tuesday, 4 August 2009

XP Pro Mode – Hardware Virtualization is Required

The Intel ProcessorFinder site is the place to go when looking up the features that a particular CPU supports.

Each CPU series shares a common feature set with some exceptions where there may be a couple of versions at the low end of the model set that have features "disabled" to augment the value at the high end.

Intel did this with the 5200 series Xeons as well as others, and still does it with the Core 2 Quad series with the amount of L2 cache being 50% smaller on the "value" versions of the CPU line. Most of the CPU lines have subtle feature differences between the entry and top end products.

Virtualization (Intel calls it VT) is a base feature. The desktop Media G series boards support VT (C2D, C2Q), while the Executive Q series (vPro) supports higher end VT-d and VT-Appliance settings for more advanced virtualization scenarios such as embedded VMs or the XP Pro Mode in Win7.

The base G series with VT enabled will also do XP Pro Mode since the hardware virtualization has been embedded in Virtual PC 2007 which is what XP Pro Mode is based on.

In the end, we always try to make sure we have the right product for the job.

Laptops have been very iffy when it comes to BIOS enabled hardware features implemented.

To get hardware virtualization on laptops, the laptop needs to have at least the Centrino Pro series chipset in our experience.

Information on the Centrino Pro chipset:

If XP Pro Mode is required by a client, we need to be particularly aware of the hardware setup Windows 7 will be running on as XP Pro Mode does require hardware level virtualization to be enabled in the system’s BIOS.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Friday, 1 May 2009

Windows 7 XP Pro Mode – Requires a Physical Box with AMD-V or Intel VT Turned On

When it comes to running the new XP Pro Mode on Windows 7, the host OS must be on physical hardware that has hardware virtualization enabled in the system’s BIOS.

Hyper-V, VMWare, Virtual PC, and other virtualization products running Windows 7 in a VM will not allow for us to test the new XP Pro Mode in Windows 7.

image

The download on Connect shows that with the:

NOTE: Windows Virtual PC requires processor (sic) capable of hardware virtualization, with AMD-V™ or Intel® VT turned on in the BIOS.

The link in the screenshot is the actual link in the above quote but it is not live yet.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Tuesday, 28 April 2009

Windows 7 – XP Pro Mode is Virtualized XP Professional

Damir Bersinic and John Bristowe were presenting to our Edmonton Microsoft User Group this evening on Windows 7 and Windows Server 2008 R2.

A new feature that can be installed with Windows 7 Professional or Ultimate is XP Pro Mode. These OSs will be licensed for 1 instance. For those who have Windows Vista Software Assurance tied into the Microsoft Desktop Optimization Pack, the number of XP Pro Mode instances that can be run on a workstation covered by MDOP is 4!

Essentially, it is a VHD of Windows XP Professional that resides on the user’s system. Whenever there is a need for an application such as Internet Explorer 6 or a legacy application that will not run on a 64bit operating system or Windows 7 in general, they can be installed into the Windows XP Professional VM.

For the user, all they need to know is how to go to the XP Mode folder (exact name not known yet) under All Programs and click on that application’s icon.

They will be presented with the application’s “window” which will in fact be a TSApps session into the Windows XP Professional VM. Sound familiar to our Mac users? ;)

The solution utilizes a number of different virtualization and application delivery technologies to make sure the user can do their job without thinking about how things are working underneath it all!

The VM is somewhat manageable just as a Virtual PC 2007 VM would be. It can be connected to the local network via bridge, the Windows 7 workstation can provide NAT services for the VM so that it can access the Internet, or it can run without any network connectivity at all.

When bridged into the domain, and subsequently joined to the domain, the XP Pro VM will require the same considerations as any physical or Hyper-V based virtual machine running the OS would:

  • Patch management.
  • AntiVirus and Malware protection.
  • Group Policy structures for the VM and others like it.

Now, the above assumes a small network where there will be no centralized management of the XP Pro Mode VMs.

For larger organizations, the XP Pro Mode VMs are a part of Microsoft’s new virtualization product called Microsoft MED-V. The VMs can be managed down to almost the minutest detail.

We can see a use for Windows 7 XP Pro Mode for some of our clients that have Line of Business Applications that will not cooperate with Windows Vista or now Windows 7.

The catch is though, having these VMs on the client systems introduces another level of complexity, disaster recovery elements, and management needs.

Apparently the Release Candidate getting released for us on TechNet this Thursday and to the general public in the first week of May will have the ability to enable XP Pro Mode.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Wednesday, 15 April 2009

ShadowProtect Image Recovery into a Hyper-V VM

We need to get to images restored into VMs running on Hyper-V for the test Swing Migration we are doing for the messed up “Professional” SBS in this post.

The deeper we are digging into this the more and more it may be a good idea to start fresh and work the client workstations from there.

But, we have committed to the business owners to run through the Swing test anyway, so we are well into it now.

The existing SBS was imaged using ShadowProtect and has been restored to one of our lab servers using the Hardware Independent Restore feature. We cleaned up the IBM XServe hardware pieces in the Device Manager and made sure that the lab server hardware drivers were installed and stable.

We are running a portion of the Swing virtually with the NewSBS ending up on the same lab server we have the restored SBS on now which is a Swing Off and Swing On again.

On this particular SBS network there is a Terminal Server. So, we took an image of it as well as one critical workstation. We are restoring both images to VMs running on Hyper-V Server 2008 (yes, we got it up and running though with no add-in RAID controller).

When we went to boot from the ShadowProtect I.T. Edition ISO in the VM, the WinRE would choke on the networking portion of the ShadowProtect startup routine. We ended up needing to uninstall the standard Hyper-V NIC and use a Legacy NIC to get things rolling. We were using the Windows Vista WinRE version too.

We placed the two ShadowProtect images on a network share to run the restore process in the Hyper-V based VMs using drive mapping feature in the ShadowProtect recovery environment.

When it comes to restoring an encrypted ShadowProtect image that is password protected using AES 128bit security, CPU crunching capabilities and GHz speed sure make a huge difference on the restore times.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Saturday, 20 December 2008

Hyper-V on Server Core Rehash - Scratch to Production and Hardware Considerations

Server Core + Hyper-V after the fact: Build it and they will come! :)

Blog posts:

When working with the Server Core installation on a domain, it is a good idea to add the principle domain user to the local domain admins group. But only that user.

For other users that will manage only certain VMs on the Hyper-V box, there is AzMan. This is just a teaser since the Tech Days presentation went through AzMan and Hyper-V rather quickly, we will need more time to delve into the methodology. Anyone already familiar please feel free to drop some hints/suggestions/tidbits into the comments! ;)

Once the above steps have been completed, Hyper-V Manager on Vista SP1 or in Server 2008 (either Hyper-V Role enabled or management tool) will be able to connect.

Make sure to enable the remote advanced firewall management on the Server Core box for all profiles! If all else fails, at least we can still work the firewall rules via a GUI.

When it comes to the Hyper-V on Server Core hardware, make sure the box has at least 2 network cards! One NIC needs to be tied to the internal domain/workgroup and needs to be dedicated to management use only.

The second NIC, or any additional ones, will be for the Hyper-V virtual switch. Once the second NIC is bound via the Virtual Network Manager in Hyper-V, it is okay to disable the NIC in the Device Manager of the Hyper-V Server Core box. The Hyper-V Switch will continue to function since it is riding directly on the NIC hardware.

Also, when it comes to the hardware configuration and the number of cores enabled for a VM, there may not be a logical progression for core assignment. Here is an example (CPU focus only):

  • Hardware has a pair of E5440 Xeons (8 Cores).
    • 1 Virtual CPU: Vista VM
    • 1 Virtual CPU: Vista VM
    • 1 Virtual CPU: XP Pro VM
    • 1 Virtual CPU: XP Pro VM
    • 2 Virtual CPUs: Server 2008 VM + SQL 2008 Standard
    • 2 Virtual CPUs: Server 2008 VM + Exchange 2007 Standard

The logical thought progression would be to settle each VM on a core for the singles and a pair of cores for the VMs that have two virtual CPUs. Eight virtual CPUs demanded by the VMs with 8 cores available. But, that is not how the actual CPU tasks are served up across the cores. The above example may run just fine for a small shop with relatively low CPU to VM usage. But, as the VMs demand more processor horsepower, the more difficult it becomes to divvy up a pair of cores for the VMs with 2 virtual CPUs.

Now, take the above configuration and tweak it a bit:

  • Hardware has a pair of E5440 Xeons (8 Cores).
    • 2 Virtual CPUs: Vista VM
    • 2 Virtual CPUs: Vista VM
    • 4 Virtual CPUs: Server 2008 VM + SQL 2008 Standard
    • 4 Virtual CPUs: Server 2008 VM + Exchange 2007 Standard

We dropped the XP Pro single CPU VMs by moving them to another Hyper-V box because we knew the load on this particular Hyper-V box was going to jump.

Now, the question is, will increasing the number of virtual CPUs actually improve VM performance?

What we actually end up with is a competition for CPU cycles between the low virtual CPU count Vista VMs that are easier to assign CPU cycles to and the high virtual CPU count Server 2008 VMs. As demand increases VM performance would actually decrease due to the need to juggle virtual CPU demands across the 8 Xeon cores.

We could throw the most expensive pair of Xeon X5492 Quad Cores that we have bumped up to 3.9GHz into the Hyper-V box running the second set of VMs and still we would not see top performance out of them due to the virtual CPU count in the VMs.

Ultimately, the point is that increasing the VM virtual CPU count does not necessarily mean that the VM's performance will increase.

Some of the Tech Days virtualization sessions discussed the above hardware considerations. We tied them into our own virtualization experiences.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Thursday, 28 August 2008

SBS 2008 - Some test lab considerations

One of the major questions we need to ask ourselves when we are going to test a new server OS or workstation OS product is: how?

Some criteria to consider in that how:
  • Internet connection.
    • Static IP with URL A for DNS, MX for mail, SSL.
    • dDNS setup.
    • No Internet connection at all.
  • SBS 2003/8 specific: Remote Web Workplace functionality.
  • Server or workstation hardware
  • Virtualized OSs.
  • Terminal Services
  • Group Policy settings from OU structure right through to the minutest GPO and its settings.
  • Workstations.
    • Hardware or Virtualized.
    • XP Pro and/or Vista Business/Ultimate
  • Microsoft Office version
  • Line of Business Applications
The above list is by no means complete. But, it does give us food for thought.

For us, the imperative when looking to test a beta product, SBS 2008 for example, is to make sure that we have a setup that is close to what a real production environment would be like.

This imperative becomes all the more important as we began to realize just how much SBS 2008 has changed over SBS 2003. We absolutely needed an Internet connection with at least a dDNS setup or, in our case, a dedicated static IP with the proper DNS settings in place.

As an example, we wanted to run through setting up SSL with a third party certificate for Remote Web Workplace because the new Getting Started Tasks contained a wizard just for that purpose. With that cert in place, the next step was figuring out how to make ISA 2004/6 work with the SBS 2008 RWW setup and so on.

When it comes to our client specific setups, we create a lab environment that mirrors their production environment. It is then critical for us to provide the necessary infrastructure to facilitate the mirror. To some extent, virtualization can help a lot here, but not completely.

In the case of SBS 2008, as mentioned in previous posts, we have a couple of lab setups in the shop. The critical one for us right now is the Springer Spaniels SBS 2008 setup that is a part of the book that I am co-authoring with Harry Brelsford.

It is the Springers' lab setup that needs to be stable and properly configured as our other lab setup is the one we like to blow up by doing silly things like enabling the Intel ProSet NIC Teaming settings and then running the wizards ... can you say reinstall anyone? ;)

This is an overview of the Springers' lab:
  • Intel X3070 Xeon Dual Core CPU on an Intel S3000AHLX server board, 8GB Kingston ECC Intel approved RAM, Intel SRCSASRB RAID controller in RAID 0+1 with 4x 320GB Seagate ES series hard drives for a total of 640GB of storage.
  • SBS 2008 RC1 is installed and in the process of being configured.
  • 4x workstations configured as follows:
    • Intel Core 2 Quad Q6600, Intel DQ965GF or Intel DQ35JO motherboard , 6-8GB Kingston RAM, 2x 320GB Seagate ES or AS series hard drive in RAID 1 via on board RAID controller all tucked into an Antec Minute 300 or 350 for space saving.
    • Windows Vista Ultimate x64.
  • Workstation VM setup:
    • Station 1: 4x Windows XP Pro VMs using our TechNet Plus for licensing (lab).
    • Station 2: 4x Windows XP Pro VMs using our TechNet Plus for licensing (lab).
    • Station 3: 2x Windows XP Pro, 2x Windows Vista Ultimate VMs using TechNet Plus (lab).
    • Station 4: Server 2003 R2 Std for ISA (TechNet in lieu of Open Lic.), Server 2008 Std x64 (SBS 08 RC1 Premium).
  • Network Setup:
    • Internet static IP bound to our own ISA 2004 (on SBS R2 Premium) with DNS A, MX, SPF records in place for springersltd.com.
    • The Springers' SBS 2008 box sits behind a D-Link DI-604 consumer router with a publishing rule on our ISA 2004 to allow it out only.
      • D-Link internal Springers' IP range: 192.168.99.0/24
      • D-Link WAN port IP: 192.168.125.210 (reservation on our internal SBS DHCP setup)
    • Our ISA 2004 has the Springers' SSL certificate bound a publishing rule set to allow HTTPS and SharePoint 987 to forward to the D-Link's internal IP. The D-Link forwards those to the Springers' SBS 2008 box.
    • Our ISA 2004 also has VPN and SMTP for the springersltd.com forwarded to the D-Link then on to the Springers' SBS 2008 box.

We have limited the number of virtual workstations to 4 per physical workstation as we plan on stress testing the setup by having a number of people logging in at the same time as the Springers' users. They will do things like run Outlook to create and send e-mail, Word documentation, SharePoint, and the like.

Yes, the workstation grade hardware hosting the VMs will not necessarily provide the "real world" experience like having those desktops on a Hyper-V enabled server with a high performance RAID array setup and a couple of cores assigned to each would provide, however, it will give us some indications as to how the Xeon 3070 will hold up under 10 users with a number of the server services in use simultaneously.

Note that the D-Link is a temporary measure until we reach the stage where we are installing the Windows Server 2008 x64 Standard server that is a part of the SBS 2008 Premium setup. When we have reached that stage, then, we will look at setting up ISA on Windows Server 2003 R2 Standard either as a VM, or if we have a spare box kicking around, a dedicated hardware solution.

There is a significant cost in time and equipment in the lab setups we have. It only makes sense that if we want to provide the best possible product knowledge to facilitate our ability to provide our clients with the best solutions for their needs, then we need to invest time and money.

This is critical: The closer and closer we get to the Cloud and its opportunities and pitfalls, the more our knowledge and experience will be the key to us and our I.T. company moving forward successfully.

Take careful note: The "we" and "our" in the above sentence means every single employee and contractor that works with us under this umbrella we call MPECS Inc. It also means our clients and their feedback, the vendor contacts we work with, our peers in the local I.T. industry, and you our blog readers that provide excellent feedback for us to build on.

Ultimately, it will be our teamwork that carries us through this transition period.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Friday, 2 May 2008

Hyper-V on Server Core - Some initial observations and hardware planning

We have had a chance to have some production Windows XP and Vista virtual machines running in Hyper-V on Server Core Standard for a few days now.

We decided to copy over our production VMs to Hyper-V, because that was the only way we were going to get any real experience with the product.

All in all, the experience has been positive.

Some of the high points:
  • VM performance is faster than Virtual Server 2005 R2 SP1 on W2K3 R2 Standard SP2.
    • Single core to single core on an identically equipped 1U Intel Xeon 3000 Series.
    • From VM boot times, to program start up, to running some pretty intense reports in QuickBooks, things move a lot quicker.
  • Adding a second core to the Hyper-V based VM increases performance significantly.
  • Server Core's overhead is a paltry 256MB of RAM, in this case leaving 7.75GB to the VMs.
  • Server Core's hard drive footprint is relatively small, and can be made smaller by removing not needed packages (Server Core blog how-to).
One of the first things we needed to do to get Hyper-V to work with the newer Intel S3000AH series NIC setup in our 1U was to download the Hyper-V RC0 and install it.

We downloaded the MSU file to a company folder share the Server Core system was connected to, copied it over to a local folder on the Server Core machine, then ran the update from the command line from that folder by typing it's full name and hitting Enter.

The RC0 install routine fired up with no issues, rebooted the machine, then ran some more install routines on login.

We needed to have Windows Vista SP1 on the workstation we were going to install the Hyper-V management console (x64 Console, x86 Console) on.

We have run into a few Hyper-V hiccups and a strange VM performance issue:
  • Our Windows Vista SP1 VM that came from a Virtual Server 2005 R2 SP1 with Virtual Machine additions removed would not setup on Hyper-V at all.
    • This is a known limitation at this point
  • Our Hyper-V based server must have read/write permissions given to shared folder where any ISOs reside
    • Access to the ISOs on our Windows based storage server works fine
    • Access to ISOs on an Intel SS4000E in either Local Authentication or Active Directory Authentication Mode will not work.
  • The XP VMs go into some sort of near death pause for anywhere from 15-30 seconds periodically and somewhat randomly.
What we are also finding out with the current setup is that the performance bottleneck has moved from the Windows OS to the storage subsystem. We have discovered that we need a really good hardware accelerated RAID controller to reduce or eliminate that bottleneck.

All in all, as Hyper-V goes through its final development phase into RTM, things can only get better.

Working with both Server Core and Hyper-V has been a really good experience so far. A neat part of the whole endeavour is discovering all of the quick and simple ways one can manage the server from the command line. And subsequently, manage the Full Server 2008 Install in the same manner.

Next up ... PowerShell! ;)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Tuesday, 29 April 2008

Hyper-V - Migrating VS 2K5 R2 SP1 XP VMs to Hyper-V

There is a little bit of a process to get that XP Pro VM from Virtual Server 2005 R2 SP1 onto Hyper-V and get the Hyper-V Integration Services installed.
  1. Install Windows XP Service Pack 3 (Reboot required).
  2. Uninstall VS 2K5 R2 SP1 VM Additions.

  3. Reboot.
  4. Install Hyper-V Integration Services.
    1. Cancel the New Hardware Found dialogues.
    2. Update the HAL.

    3. Reboot.
    4. Installation of Integration Services runs as soon as the user logs on.
    5. Cancel any New Hardware Found dialogues as they will hang up the post reboot install.
    6. One final reboot.
When working with the VMs via the Hyper-V management console, one needs to CTRL+ALT+End to send the CTRL+ALT+DLTE key stroke pattern.

There are a few others, but once the Integration Services are installed and configured, things go pretty smooth.

So far, with just a single core assigned to each VM running on the 1U Xeon X3230 based server we are noticing a pretty good performance increase. The OS is Server 2008 x64 Standard Core with Hyper-V RC0 installed and configured.

The out of the box Hyper-V would not work with the Intel NICs in this particular box. We needed to update right away.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Monday, 28 April 2008

Windows XP SP3 RTM bits available on TechNet

The bits for Windows XP Service Pack 3 Release to Market are available to TechNet Plus subscribers now.

Windows XP Service Pack 3 (x86) ISOs

The download is only available via the Top Downloads section of the site.

Windows XP Service Pack 3 is a requirement for anyone planning on running an XP VM on Windows Server 2008 Hyper-V.

Time to get your bits, read the release notes (RC Version), and start testing!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Saturday, 18 August 2007

Virtual Server - VM Memory & CPU requirements

We have been working with Virtual Server 2005 R2 SP 1 for our virtualization needs.

The two key physical limitations to the number of virtual machines, in our experience, are the amount of memory installed and the speed and number of cores on the CPUs.

Windows Server 2003 Standard R2 x64 serves most of our virtualization needs. With the /PAE switch in boot.ini, we get to address as much RAM as we need.

For Intel based uniprocessor servers we are limited to 8 GB of RAM. For dual processor servers we are limited to 32 GB of RAM.

We tend to configure one (1) virtual machine for each core on a processor. For a Quad Core uniprocessor server we would run a maximum of 4 virtual machines. For a V8 server, dual Quad Core CPUs, we would run a maximum of 8 virtual machines.

This setup is, of course, based on the limitations of VS 2K5 of one core to one virtual machine.

VMWare Server would give us the option of dual SMP - two cores - for a virtual machine if the situation warranted. We would reduce the number of VMs running on the host OS accordingly.

A good portion of our client based virtualization needs are for remote desktop serving. The ability to run virtual XP Pro or Vista Business desktops provides flexibility for Group Policy based desktop security, user and application limitations via Group Policy, Line of Business apps that may not be able to be installed on a Terminal Server, Remote Web Workplace access via "Connect to my computer at work", and more.

An XP Pro VM can run quite comfortably on 512 MB of RAM while on a dual 3.06 GHz Intel Xeon based server. Virtualization is one place where Hyper-Threading actually works.

Windows Vista Business will require a minimum of 1 GB of RAM when running virtually. Anything less than that and Vista takes a pretty heavy performance hit.

We tend to set at least 2 GB of RAM to a virtualized SBS installation. That is the minimum we would install on a physical SBS installation, so we stick with it for VMs.

Windows Server 2003 Standard R2 serving DNS to the Internet can run on 256 MB of RAM. Install Exchange and the memory requirements jump up to at least 1 GB with 2 GB being better. ISA virtualized will run okay on 512 MB but better on 1 GB.

A rule of thumb is to leave a minimum of 384 MB of RAM for the host OS. Make sure that only the host OS basics are installed. For Windows Server 2003 Standard R2, remove or disable all nonessential services to lean out the OS.

So far, virtualization has done great things for our clients and for us. It can greatly reduce the costs of running a few extra dedicated remote desktops when all of the client's staff is laptop based. It can provide a single box solution for a number of light duty server roles that are easy to backup and restore as needed and in short order.

For those of us in IT, it eliminates the hardware/$$$ limitation on our testing labs. One V8 server will serve most small shop's server/client VM environmental needs. No more need to have four, five, or more boxes with a KVM or two just for those lab situations where we need to test whether our client boxes will blow up with the next run of updates and patches!

It also gives us a tremendous time saver: Undo Disks! With undo disks enabled, if that run of patches or updates does blow up the virtualized client SBS or other server box, we can undo the patches by discarding the changes and then start again. Hopefully we will be able to figure out which patch is causing the problems with what installed component and go from there.

All in all, virtualization can provide an excellent way for us to create some pretty neat solutions for our clients with a very attractive price point.

This is needed to enable Windows Server 2003 Standard R2 x64 to access installed RAM above 4 GB: Microsoft KB 283037: Large memory support is available in Windows Server 2003 and in Windows 2000

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Wednesday, 18 April 2007

Virtual Server - VSS Service and Virtual Machine Memory Usage

We utilize Microsoft Virtual Server 2005 R2 on a number of different hardware platforms running a number of different operating systems.

One of the curious things that I have noticed is with regards to memory management by the VSS service.

The following is a screen shot of the server's Task Manager Process Tab:


The VSS service is using about 12 MB of physical memory.

The configuration of this particular machine is as follows:
  • Intel SR2300 2U
  • Two Intel Xeon 2.8 GHz CPUs
  • 6 GB ECC PC2700 RAM
  • Dual Seagate 76 GB SCA2 SCSI SW RAID 1
  • Windows Server 2003 Enterprise with PAE switch
We have loaded up two XP Pro SP2 and two Vista Business virtual machines with both having an allotted 1 GB of system memory.

The above Task Manager shot was taken while all four virtual machines were running. There is no evidence from the service memory usage that they are running.

However, on the Performance Tab, we see the following:


The server has a total of 4.21 GB of RAM allotted to running processes.

So, somewhere in there, the VSS has grabbed the necessary physical RAM and made sure that the respective machines are getting what they need.

To date, other than one glitch with one of the Virtual Vista machines blue screening on a boot up, we have had trouble free performance.

The primary purpose for this platform is to test virtualizing the desktop OS environment to provide our clients with a solid alternative to Terminal Services.

The Microsoft Virtual Server 2005 R2 site.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

Monday, 19 March 2007

Need to familiarize yourself with SBS? Try This --->

Do you have a spare machine around with enough memory and processor speed to install a base OS and Virtual Server on top? If you do, the following assumes a little bit of experience with Virtual Server 2K5 R2 as that is what we run our virtual environments on.

You could run your SBS install stages; install some XP desktops, Vista desktops, and another server or servers if you like within the virtual environment.

You could run the entire project virtually, start to finish, without impacting your production environment. If need be, all operating systems can be Eval versions so as to not impact licensing issues.

Running things virtually requires nothing special in the way of hardware or software.

To get to RWW on the virtual SBS domain via your internal network do the following:

Virtual SBS: Create an internal network accessible only by the workstations and SBS NIC 1. Add a second NIC to the virtual SBS box that is attached to the machine's physical NIC so it can pull an IP from your internal DHCP server.

On your internal DHCP server, create a reservation for the MAC address of the virtual SBS NIC 2.

On your internal DNS server, add an (A) record to the IP address reserved for the virtual SBS server above: virtualsbs.mydomain.local (your domain setup) = IP 192.168.xxx.xxx (your IP subnet)

Run the SBS setup on your virtual server, complete stage 1, post stage 1 install and configure the base installation as you normally would and then continue on with stage 2 for the complete SBS install.

Internet Wizard URL: same as your internal DNS (A) record: virtualsbs.mydomain.local

You will be able to send e-mail from the virtual domain, only SMTP e-mail coming in will not happen if you already have an SBS server, or Exchange server on your internal network. POP3 Connector solution could be implemented here if you want full e-mail functionality on the virtual domain. RWW will be accessible via your Web browser internally: http://virtualsbs.mydomain.local/remote.

Install the workstation OSs. This can be done at the same time as the SBS stage 2 install.

Once you have the SBS install, Premium Tech (if needed), and the ToDo list finished, you can go ahead and create some virtual users and computers and then run through the Add Computer wizard for the XP and/or Vista workstations. This gives you the opportunity to install the SBS/Vista RipCurl! ;)

The above will give you a complete install, start to finish. Mess up? No worries, start again. You will be able to run Eval versions for about 6 months give or take from the install date. This is more than enough time to play with the virtual SBS environment to get comfortable with the look and feel of installing SBS.

You can get SBS 2K3 Premium SP1 Eval on eBay without a problem, and SBS 2K3 Premium R2 Eval by purchasing the R2 Eval pack which is little more than shipping and handling from Microsoft. XP Pro can be had via eBay, as can Office, and others. Vista trial can be had via any Vista RTM media obtained via TechNet, MSDN, or a DVD that came with a system.

This setup also gives you the opportunity to explore Group Policy settings without creating havoc on a production SBS environment. Create and destroy OU's and policies. Learn how to get very granular with the application of your policy settings. No risk of GP tattoos on your virtual desktops ... you can pause the virtual desktops to be hit with the GP before hand and copy the VHD. Save it for later when you want to reverse things. The same is true for the virtual SBS VHD.

Need to figure out how to install software to certain machines via GP? Then this is the place to do it! Office 2003, 2007, Windows Defender for XP, and more can be distributed via GP (Eval and OLP versions for Office).

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists