Archive

Archive for March, 2009

Installing Windows 2008 R2 with Hyper-v in Core version

March 10, 2009 Leave a comment

Steps that you need to use to install and configure the Hyper-V on a Windows 2008 Core

Note the following:

  • There is no way to upgrade from a previous version of the Windows Server operating system to a Server Core installation. Only a clean installation is supported.
  • There is no way to upgrade from a full installation of Windows Server 2008 to a Server Core installation. Only a clean installation is supported.
  • There is no way to upgrade from a Server Core installation to a full installation of Windows Server 2008. If you need the Windows® user interface or a server role that is not supported in a Server Core installation, you will need to install a full installation of Windows Server 2008.

Compare Server Core Installation Options

Server Role

Enterprise

Datacenter

Standard

Web

Itanium

Active Directory Domain Services

Available
Available
Available
Not Available
Not Available

Active Directory Lightweight Directory Services

Available
Available
Available
Not Available
Not Available

DHCP Server

Available
Available
Available
Not Available
Not Available

DNS Server

Available
Available
Available
Not Available
Not Available

File Services

Available
Available
Limited
Not Available
*Not Available

Hyper-V

Available
Available
Available
Not Available
Not Available

Print Services

Available
Available
Available
Not Available
Not Available

Web Services (IIS)*

Partial/Limited
Partial/Limited
Partial/Limited
Partial/Limited
Not Available

 

 

 

·         Enable CPU virtualisation assistance and DEP in the BIOS.

·         Install Windows Server 2008 Enterprise x64 (Core Installation).

·         Determine the NIC ID: netsh interface ipv4 show interfaces.

·         Set the IP address for NIC, let say for NIC #2:
netsh interface ipv4 set address name=”2″ source=static address=192.168.1.20 mask=255.255.255.0 gateway=192.168.1.1

·         Set the DNS: netsh interface ipv4 add dnsserver name=”2″ address=192.168.1.2 index=1.

·         Rename server: netdom renamecomputer %computername% /NewName:HyperSvr1.

·         Reboot for that to take effect: shutdown /r /t 0.

·         Join it to domain: netdom join %computername% /domain:CONTOSO /userd:administrator /passwordd:*.

·         Reboot for that to take effect: shutdown /r /t 0.

        ·         Install the Hyper-V update: wusa.exe Windows6.0-KB950050-x64.msu.

·         Reboot.

 

·         Install the Hyper-V role: start /w ocsetup.exe Microsoft-Hyper-V.

·         Reboot.

·         Disable the firewall netsh firewall set opmode mode=disable

 

 

To manage a server running a Server Core installation by using a terminal server client:

1. On the server running a Server Core installation, type the following command at a command prompt:

      cscript C:WindowsSystem32Scregedit.wsf /ar 0

This enables the Remote Desktop for Administration mode to accept connections.

BTW, in order to view your current settings you can type:

      cscript C:WindowsSystem32Scregedit.wsf /ar /v

If you see "1" in the script output, that means that RDP connections are denied. If you see a "0", they will be allowed.

Note: If you are running the Terminal Services client on a previous version of Windows, you must turn off the higher security level that is set by default in Windows Server 2008. To do this, type the following command at the command prompt:

      cscript C:WindowsSystem32Scregedit.wsf /cs 0

To enable remote management from an RDP connection through the firewall

1. To enable remote management from any MMC snap-in, type the following:

      netsh advfirewall firewall set rule group="Remote Desktop" new enable=yes (you may have already done this step)

To open an RDP session with the Server Core machine

1. On the remote management computer, click Start > Run, type mstsc, and then click OK.
      
2. In Computer, enter the name of the server running a Server Core installation, and click Connect.
      
3. Log on using an administrator account.

4. When the command prompt appears, you can manage the computer using the Windows command-line tools.

      Note that while you’re logged on to the server, the original server console session is locked out.

5. When you have finished remotely managing the computer, type logoff in the command prompt to end your Terminal Server session.

Also, from the command line of the Server Core box, type: c:windowssystem32cscript scregedit.wsf /cli   for a listing of all the command line references

Advertisement
Categories: Virtualization

Determining if your machine is ready for Windows 2008 R2 and/or Hyper-V

March 10, 2009 Leave a comment
Windows 2008 R2 will be released only on 64bits. How could you determine if your machine is ready to install Hyper-V?
There is a software that’s check if the processor is 64 bits and if it support’s Virtualization
SecurAble probes the system’s processor to determine the presence, absence and operational status of three modern processor features:
 
  • 64-bit instruction extensions,
  • Hardware support for detecting and preventing the execution of code in program data areas, … and
  • Hardware support for system resource “virtualization.”

Download

 

Categories: Virtualization

Windows 7 Virtual Roundtable Q&A: Part One

March 10, 2009 Leave a comment
 
 Here is the first set of questions and answers that address Windows 7, along with the destinations to find more detail:

Q:  When will the Automated Installation Kit (AIK) fully support Windows 7?

Q:  Will any other version of Windows be able to read BitLocker To Go "with an add-on or additional software"?
  • A:  Yes, you will be able to unlock and read from BitLocker files on Windows XP and Windows Vista.
Q:  When can we expect Microsoft Deployment Toolkit (MDT) 2010 to be released, or release candidate 1 (RC1) for deploying Windows 7?
Q:  Is the kernel the same for Windows Vista Service Pack 1 (SP1) and Windows 7?
  • A:  The kernel consists of many different files; it is updated with Windows 7, but is based on the same underlying architecture.
Q:  Has ReadyBoost changed from Windows Vista?
  • A:  ReadyBoost in Windows 7 adds support for concurrently using multiple flash devices (such as USB keys, Secure Digital cards, and internal flash devices) and for caches larger than 4 GB. ReadyBoost supports exFAT, FAT32, and NTFS file systems.
Q:  In Windows 7 can you toggle or set all local policy settings individually as a preference instead of having to enforce for flexibility/versatility?
  • A:  No. Group Policy settings are independent of Group Policy Preferences. There is no 1:1 relationship between them in Windows 7.
Q:  Will the Applocker Group Policy Object (GPO) will be available on Windows Server 2008?… or is just on Windows Server 2008 R2?
  • A:  AppLocker is not dependent on a specific version of Windows Server. You can manage AppLocker from a Windows 7 client using the Group Policy Management Console (GPMC) that ships in the Remote Server Administration Tools (RSAT) for Windows 7, which is currently in Bet. You can download the beta here.
Q:  You say any app that runs on Windows Vista should run on Windows 7, does that hold true for any app that runs on Windows XP? Should it run on Windows 7 as well?
  • A:  Since Windows Vista and Windows 7 share similar design frameworks, there is a foundation for application compatibly. Since Windows XP has a different framework, the levels of application compatibility are not the same.
Q:  Will there now be a possibility to burn an .iso image file without burning software?
  • A:  Yes. Double-click an ISO, and Windows 7 opens a minimalistic dialog. Choose a burner, select whether or not to verify your burn, and burn/cancel.
Q:  Will Microsoft support the RC [of Windows 7]?
Q:  Will there be an Application Compatibility Toolkit available for Windows 7 like there was for Windows Vista? When might that be available?
  • A:  Yes. We plan on releasing an update to the Application Compatibility Toolkit (ACT) in April to support Windows 7 pre-releases. There will also be a version corresponding with Windows 7 release to manufacturing (RTM).
Q:  What kinds of improvements are being made in the area of application compatibility testing and migration?
  • A:  There will be a version of the Application Compatibility Toolkit to support Windows 7 available in the April 2009 timeframe. Additionally, the Windows system application compatibility fix (shim) database is constantly extended with each Windows release milestone.
Q:  What is the migration process to get my stuff off of a Windows 7 box before I have to flatten it to install the final version?
  • A:  For individual use, Windows Easy Transfer can be used to gather files and settings from your computer and save to an external location. For organizational use, the User State Migration Tool (part of the Windows Automated Installation Kit) can also perform in-place user profile migration using Hard-link Migration along with a clean operating system install.
Q:  Will Deployment Image and Servicing Management be supported for existing Windows Server 2008?
  • A:  Deployment Image Servicing and Management (DISM) supports Windows 7 client and Windows Server 2008 R2. DISM also leverages an included shim for Package Manager (pkgmgr.exe) to enable DISM to perform Package Manager commands against Windows Vista or Windows Server 2008 images.
Q:  Why is Windows 7 more quick to start up compared to Windows Vista?
  • A:  In working to improve performance for startup we have focused on making improvements in the following areas:
    • The efficiency of core Windows code
    • Only starting certain services when they are needed (demand-start services)
    • The way device drivers are initialized
    • Allowing multiple device drivers to start at the same time (parallelization)
    • An overall reduction in the memory and CPU required to start and run the graphics system
Q:  Windows 7 performance out of the box experience does seem much better than Windows Vista, but is there anything that addresses the overall issue of performance degradation over time that plagues devices over time without having to configure or buy and configure additional third party software?
  • A:  Microsoft has invested in PerfTrack, an automated reporting feature in Windows that tracks the performance of over 400 experiences on the PC. Windows 7 also includes troubleshooters such as IE Performance as well as a Check for Performance Issues to help users check for performance issues over time.
Q:  Where can I find detailed step-by-step process for building a Virtual Hard Disk (VHD) that can be selected as the boot disk on a Windows 7 system?
  • A:  Detailed guidance for creating Boot from VHD files is currently being created. The basic process is to create a virtual disk using diskpart.exe, attach the virtual disk using diskpart.exe, use ImageX to apply a System-Prepared Generalized Windows Imaging (WIM) file to the attached virtual disk, then detach the virtual disk using diskpart.exe. After the VHD file is created, add an entry into the boot loader using bcdedit.exe to point to the file location of the VHD file. This only works with Windows 7 Enterprise and Ultimate editions and Windows Server 2008 R2 VHD files.
Q:  Will deployment of Windows 7 use the same tools as Windows Vista (WIM files, ImageX, etc…)?
  • A:  Most tools are retained from Windows Vista. Deployment Image Servicing and Management consolidates functions of IntlConfig, PEImg and PkgMgr in the Windows AIK for Windows 7. DISM supports PkgMgr functions against Windows Vista and Windows Server 2008 images. Integrated tools like the Microsoft Deployment Toolkit and System Center Configuration Manager 2007 will also support Windows 7 and Windows Server 2008 R2 deployment.
Q:  Are there any improvements in the Windows 7 imaging technology such as WAIK, SIM, MDT, ImageX compared with Windows Vista?
Q:  How can you deploy BitLocker with a custom image?
  • A:  There are two common approaches. You can pre-partition the drive for BitLocker, install the operating system, and enable BitLocker via deployment task sequence. Or, you can run the BitLocker Drive Preparation tool post-install and enable BitLocker via deployment task sequence. The default installation of Windows 7 will automatically create the BitLocker partition at install time.

Published 09 March 09 08:49 AM | Celine Allee
http://blogs.technet.com/springboard/archive/2009/03/09/windows-7-virtual-roundtable-q-a-part-one.aspx

Categories: Windows 7