Home

 

 

Events  |  News  |  Press  |  Support  |  Training  |  Promos  |  Locations  |  Careers  |  About Us User Groups

  >   Shortcuts

 

Table of Contents

 

News Bulletin - AEC Edition

News Bulletin - MCAD Edition

New Bulletin - Archives

Customer Profiles

Industry News & Comment

Product Reviews

Cadtales

CRM News

Data Management & Consulting

Technical Perspective

Tips & Tricks

News & Events

Promotions
 

  Archives:
 

Technical Perspective Archives

 

   
 


 
 

 Technology Bulletin

Windows Server 2008:
New Release Candidate Shows Promise.
 

It seems that the folks at Microsoft are working overtime to get back on track with their operating system releases. The latest in the current line of new entries is the release candidate for Windows Server 2008. It has some features that are really quite desirable and includes Hyper-V. Why should you care? Well, hopefully you can find the answers in this article. Read on!

 

Looking to Windows Server 2008 RC
Known during the development process as Longhorn, Windows Server 2008 Release Candidate 1 with Hyper-V Beta is now available for evaluation. So what the heck is Hyper-V? Formerly code named Viridian, Hyper-V is a virtualization environment integrated with Windows Server 2008 RC 1. Microsoft Windows Server 2008 will be the most advanced Windows Server operating system yet. Its design will allow programmers to power and deliver the next generation of networks, applications, and Web services in a secure network infrastructure without minimizing the experience for the end user. The new web tools coupled with virtualizations, security enhancements, and management utilities promise again to save time, money and provide a secure, solid foundation for your IT needs.

How about some details?
The release candidate of Windows Server 2008 brings to the forefront the technology that people are looking for today; the kind that aids productivity and saves money. How does an operating system save money? Total Cost of Ownership (TCO). Windows Server 2008 RC1 allows businesses to invest in high powered servers that are configured through virtualization to perform the functions of multiple servers. This makes the product attractive because it can actually lower hardware requirements but also by reducing power and cooling costs and management costs while optimizing the infrastructure. By enabling business continuity through the ability to minimize both scheduled and unscheduled downtime and the use of clustering to reduce downtime, this product carries the promise of making your business more productive.

What are the hardware requirements?
As with any product, there are the requirements (usually the bare minimums) and then the real requirements. Keep in mind that the information presented here is based on a release candidate and the actual requirements are subject to change right up until the final release of the product. Also note that the actual requirements will be higher depending on the applications and features you deploy.

  • Processor: 2GHz or faster

  • RAM: 4 GB+

  • Disk Space: 40 GB Min

  • DVD-ROM

  • SVGA or above graphics

  • Keyboard

  • Mouse

Note:
The use of Itanium Processor based machines have even higher system requirements. These systems require additional planning. Information can be viewed here along with other very helpful information (http://www.microsoft.com/learning/windowsserver2008/default.mspx).

 

Before you start.
OK, so you intend to evaluate Windows Server 2008 in a non-production environment. Well, before you install Windows Server 2008, Microsoft has a great checklist for you to follow and I am including it below:

  • Check for application compatibility. To help with this, you can use the Microsoft Application Compatibility Toolkit. Although it is primarily used to provide compatibility information about network applications, you can also use it to prepare for Windows Server 2008. For more details, see the Windows application compatibility information (http://go.microsoft.com/fwlink/?LinkID=29880).

  • Disconnect UPS devices. If you have an uninterruptible power supply (UPS) connected to your destination computer, disconnect the serial cable before running Setup. Setup automatically attempts to detect devices that are connected to serial ports, and UPS equipment can cause issues with the detection process.

  • Back up your servers. Your backup should include all data and configuration information that is necessary for the computer to function. It is important to perform a backup of configuration information for servers, especially those that provide network infrastructure, such as Dynamic Host Configuration Protocol (DHCP) servers. When you perform the backup, be sure to include the boot and system partitions and the system state data. Another way to back up configuration information is to create a backup set for Automated System Recovery.

  • Disable your virus protection software. Virus protection software can interfere with installation. For example, it can make installation much slower by scanning every file that is copied locally to your computer.

  • Run the Windows Memory Diagnostic tool. You should run this tool to test the random access memory (RAM) on your computer. To use the Windows Memory Diagnostic tool, follow the instructions in the Windows Memory Diagnostic Users Guide (http://go.microsoft.com/fwlink/?LinkID=50362).

  • Provide mass storage drivers. If your manufacturer has supplied a separate driver file, save the file to a floppy disk, CD, DVD, or universal serial bus (USB) flash drive in either the root directory of the media or in one of the following folders: amd64 for x64-based computers, i386 for 32-bit computers, or ia64 for Itanium-based computers. To provide the driver during Setup, on the disk selection page, click Load Driver (or press F6). You can browse to locate the driver or have Setup search the media.

  • Be aware that Windows Firewall is on by default. Server applications that must receive unsolicited inbound connections will fail until you create inbound firewall rules to allow them. Check with your application vendor to determine which ports and protocols are necessary for the application to run correctly.  For more information about Windows Firewall see (http://go.microsoft.com/fwlink/?LinkID=84639).

  • Prepare your Active Directory environment with Windows Server 2008 updates. Before you can add a domain controller that is running Windows Server 2008 to an Active Directory environment that is running Windows 2000 or Windows Server 2003 operating systems, you will need to update the environment.

Note: Even if you have followed these steps previously, you must repeat these procedures prior to installing this release candidate.


To do this, you need to update the Active Directory environment by using the following procedure. If you are performing an unattended installation, perform this step before you install the operating system. Otherwise, you will need to do this after you run Setup and before you install Active Directory Domain Services.

What should you do now?
For now, you can download a trial version of the software. The best way to make sure your evaluation is successful is to read, plan, review and then install, unless you want to be on the bleeding edge of technology and live by the seat of your pants! Just remember, this software is a release candidate as of this writing and the features and requirements are still subject to change. Also remember, install this as a test, not in a production environment!

All product names / logos, company names / logos are copyrights of their respective holders. John Boline is an MCSE, CNE, USE and a member of the Network Professional Association. The content herein is often based on late-breaking events. Much of the material is based on information from sources that are believed to be reliable. Hagerman & Company, Inc. disclaims all warranties as to the ultimate accuracy or completeness of the information. Hagerman & Company, Inc. and its employees shall have no liability for errors, omissions or inadequacies in the information contained within this article or for any interpretations thereof. The recommendations, positions and best practice policies outlined herein represent Hagerman & Company, Inc. initial analysis and therefore are subject to change as further information which may have bearing on these positions is made available. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice. Entire contents 2007 Hagerman & Company, Inc. All rights reserved. Reproduction of this publication in any form without prior written permission is forbidden.

top

 

 

This page last edited on Tuesday, March 09, 2010


e-vol. 64, February 2008

by John Boline
Service Manager,
MCSE, CNE, USE


 


print version

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Anaheim, CA  |  Chicago, IL  Cincinnati, OH  Evansville, IN  Glendale, CA  |  Indianapolis, IN  |  Knoxville, TN  |  Louisville, KY |  Memphis, TN  |  Mishawaka, IN  |   Mt. Zion, IL   Nashville, TN  |  Overland Park, KS  |  Sacramento, CA  |  San Diego, CA  |  San Jose, CA  |  San Ramon, CA |  Schaumburg, IL  St. Louis, MO   

Copyright 2009 Hagerman & Company, Inc.