vBulletin statistics
november 2007 - Posts - Windows Server blog by Kurt Roggen [BE]

november 2007 - Posts

At IT Forum in Barcelona, Microsoft publicly announced the upcoming release of Remote Server Administration Tools (RSAT). I already talked about RSAT a while ago in a previous post.

Microsoft Remote Server Administration Tools enables IT administrators to remotely manage roles and features in Windows Server 2008 from a computer running Windows Vista with Service Pack 1. It includes support for remote management of machines running a Server Core or Full Server installation of Windows Server 2008. This feature has been requested by customers as a replacement for the Windows Server 2003 Administration Tools Pack (adminpak.msi). Remote management of machines running Windows Server 2003 (R2) is also included. 
All tools within RSAT will support the management of Windows Server 2008 servers; some of these tools (included in the adminpak.msi) will also support Windows Server 2003 servers.

Remote Server Administration Tools is compatible with 32-bit and 64-bit versions of the December 2007 release candidate of Windows Vista with SP1.
Remote Server Administration Tools can be used to manage 32-bit and 64-bit versions of the December 2007 release candidate of Windows Server 2008.
Remote Server Administration Tools will be available as a Microsoft Update package.  Update packages have an .msu file extension and are associated with the Windows Update Stand-alone Installer (wusa.exe).

RSAT Questions & Answers 

Q.   Is RSAT the next version/generation of ADMINPAK.MSI?
A.   Yes.  As ADMINPAK.MSI provides IT Professionals the ability to remotely manage their Windows Server 2003 servers, RSAT provides updated functionality for Windows Server management from PCs running Windows Vista with Service Pack 1.

Q.   Will RSAT run on the gold (RTM) version of Windows Vista?
A.   No.  RSAT will require Windows Vista with Service Pack 1.

Q.   How can my customer obtain the beta of RSAT?
A.    The RSAT beta will be an open, public beta.  Customers wishing to test RSAT will be able to register at http://connect.microsoft.com once the beta announcement is made.

Q.     When will RSAT be available?
A.     RSAT will enter public beta in November, 2007.  Target Release to Web (RTW) is in the Windows Server 2008 timeframe.

Technorati Tags: , ,

Last year, Microsoft acquired DesktopStandard and obtained GPOVault and most of the PolicyMaker family.  GPOVault has been updated and released as Advanced Group Policy Management (AGPM), part of the Microsoft Desktop Optimization Pack for Software Assurance (MDOP).  For more information about AGPM see my previous postPolicyMaker Standard Edition and PolicyMaker Share Manager will be available to Microsoft customers in two ways as "Group Policy Preferences" and will be integrated into the Group Policy Management Console (GPMC) in:

  • Windows Server 2008 (starting with November CTP)
  • Remote Server Administration Tools (RSAT) for Windows Vista SP1

So, Windows Server 2008 includes the new Group Policy Preferences built-in to the Group Policy Management Console (GPMC). Additionally, administrators can configure preferences by installing the Remote Server Administration Tools (RSAT) on a computer running Windows Vista Service Pack 1 (SP1).
But what is actually the difference between "Group Policy (settings)" and "Group Policy Preferences"??

The key difference between "Group Policy Preferences" and "Group Policies (settings)" is enforcement.  "Group Policies" enforce policy settings and prevent users from changing them.  Group Policy Preferences does not (necessarily) enforce settings to machines/users, but merely applies the settings as preferences.
image

clip_image001"Group Policy Preferences" extend more than 20 Group Policy categories within a Group Policy Object (GPO) and enable IT professionals to configure, deploy, and manage operating system and application settings including mapped drives, scheduled tasks, power options, files and/or folders, printers, folder options and Start menu settings for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP systems.
The white paper below describes some of these new features and describes how you can use Group Policy Preferences to better deploy and manage computer and user preferences.

"Group Policy Preferences" do not require you to install any services or components onto your servers.  Windows Server 2008 includes Group Policy Preferences by default as part of the Group Policy Management Console (GPMC).  Administrators will also be able to configure and deploy Group Policy preferences in a Windows Server 2003 environment by installing the Remote Server Administration Tools (RSAT) on a computer running Windows Vista with SP1.  Both RSAT and Windows Vista SP1 will be available in the first quarter of 2008.

Although you don’t have to install any services to create GPOs (Group Policy Objects) that contain Group Policy Preferences, you must deploy the Group Policy Preferences client-side extension (CSE) to any client computer to which you want to deploy these preferences.  The CSE will be available as a separate download from Microsoft and will support the following Windows versions:

  • Windows XP with SP2
  • Windows Vista
  • Windows Server 2003 with SP1
  • Windows Server 2008 already includes the CSE.
For more information: "Group Policy Preferences white paper".

Related Reading:

As I've mentioned already in a previous post, there is no more BDD SA (Business Desktop Deployment Solution Accelerator).  It has been renamed to "Microsoft Deployment" (tools).  Microsoft Deployment is the next version of Business Desktop Deployment (BDD) 2007.

The current generation of automated deployment tools from Microsoft is increasingly unified; the same tools, utilities and products in many cases offer support and functionality for desktop and server deployment tasks.

Microsoft Deployment unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance.  Microsoft Deployment adds integration with recently released Microsoft deployment technologies to create a single path for image creation and deployment, including:

  • System Center Configuration Manager 2007 Operating System Deployment (OSD)
  • Windows Automated Installation Kit (WAIK)
  • Windows Deployment Services with new multicast technology (WDS in Windows Server 2008)
  • Application Compatibility Toolkit 5.0 (ACT)
  • User State Migration Tool 3.0.1 (USMT)
  • Office system 2007
  • Windows Server 2008 Server Manager for automated server role definition

Lite Touch Installation (LTI) now supports Windows Server 2008 deployments:

  • Support for deploying Windows Server 2008 Beta 3 and RC0, including support for Server Core installation options. 
  • Automated server role definition using Server Manager

Let's have look at deploying a typical Branch Office Server which holding its typical roles:

  1. (Read-Only) Domain Controller
  2. DNS Server
  3. DHCP Server
  4. WINS Server (optional)
  5. Windows Deployment Server (for local deployment of your clients and possibly servers)

Throughout the Task Sequencer, you now have the option to "Install Roles and Features" and furthermore configure some of those Server Roles once they are installed. For your information, it also support the Server Role for "Windows Server Virtualization".


Task Sequencer now supports Server Manager operations to "Install Roles and Features".


Automated server role definition using Server Manager, where ServerManagerCmd.exe does the actual work. 

1. Read Only Domain Controller

Configuration of the Active Directory Domain Services role, which drives dcpromo.exe.

2. DNS Server


As part of the Active Directory Installation process, DNS will be installed.
You can configure separate zones via the "Configure DNS" task, which drives the DNScmd.exe.


3. DHCP Server


Configuration of DHCP Scope(s) will be driven by netsh.exe in the background.


4. WINS Server


Configuration of WINS will be driven by netsh.exe in the background.


5. Windows Deployment Server

Initial installation parameters are required for a Server Role installation (using ServerManagerCmd.exe) and also drive WDSutil.exe.
However, further configuration (adding boot images, installation images, etc...) should be done through the WDSutil.exe CLI (via a custom created Task).

For more information, have a look at a previous post on Windows Deployment Services in Windows Server 2008.

 

Related postings: MS Deployment Tools (Codename Deployment 4), Windows Server 2008 Deployment Solution Accelerator (WSD SA)

Related blogs: Microsoft Deployment Team blog

Tags:

Over 5,000 attendees in Barcelona for five days of in-depth technical training, offering hundreds of learning opportunities – evaluate the latest products in the labs, meet face-to-face with the experts and network with your EMEA peers.

I will be doing my talk about Windows Server 2008 Server Manager on Wednesday... I'll make sure that later on a screencast on Server Manager appears on my blog site.  Barcelona... here we come (again)!!

 

Server Manager is a new feature in Windows Server 2008 that guides administrators through the process of installing, configuring, and managing Windows Server 2008 roles and features. For more information about Server Manager, see the Windows Server 2008 Server Manager site.

In addition to roles and features that are included with Windows Server 2008 by default, Server Manager enables integration of additional roles and features that are available on the Microsoft Download Center and Windows Update Web sites as optional updates to Windows Server 2008.

One role that will be available as an update is Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1).
This update to Server Manager enables full integration of WSUS 3.0 SP1 into Server Manager, allowing installation, configuration, and management of WSUS 3.0 SP1 using the Server Manager console and wizards.

To detect updates for Server Manager for new roles in Windows Server 2008, click Check for New Roles on the Server Manager home page in the Server Manager console. If a new role is available, you are redirected to Windows Update to download and install the update for Server Manager.

You can also participate in the Beta program and have the opportunity to try the new WSUS 3.0 SP1 role with full Server Manager integration, and provide feedback directly to the Server Manager teams. If you are interested in participating, the download is available at http://connect.microsoft.com/windows/Downloads/DownloadDetails.aspx?DownloadID=9315.
For more information or questions, please contact smcpe@microsoft.com.

Tags:

Windows Search is an indexing desktop search platform released by Microsoft for the Windows operating system. It is available as part of Windows Vista and Windows Server 2008 operating system, where it is known by the name of Windows Search (also referred to as Instant Search).

For Windows XP and Windows Server 2003, the indexed search technologies are available as Windows Desktop Search (or WDS). While older versions of WDS were available for Windows 2000 as well, the latest release (version 3) is available only for Windows XP and Windows Server 2003. 

Windows Search is the indexed search platform that debuted with Windows Vista and offers a superset of the features provided by WDS.  However, both Windows Search and WDS share a common architecture and indexing technology, and also are API-compatible with one another.  All Ifilters and protocol handlers that work with WDS 3.x will also work with Windows Vista and Windows Server 2008 because of this shared indexing engine.

Ifilters and protocol handlers are what the indexing engine uses to index files and other data stores like e-mail, etc. Windows ships with a number of default IFilters and protocol handlers and supports indexing for over 200 common file types out of the box. To support thumbnails and full previews in the Explorer, a developer would want to write both a thumbnail extractor and a preview handler.  To support metadata write-back to a file format on Windows Vista, a developer would want to use a property handler.  Going with a simple IFilter is the easiest path, but these other technologies ultimately offer a better user experience.

Windows Search supports word-wheeling as well as Advanced Query Syntax.  However, unlike WDS, Windows Search can seamlessly mix indexed and non-indexed files. If the location being searched is indexed, the search is performed against the index.  If it is not indexed, the files are processed on-the-fly with the same IFilters and Property-handlers as they would be if they were indexed. This allows for more consistent results, though, at the cost of searching speed.
In indexed locations, both filenames and contents are being searched.  However, in non-indexed locations, only filenames are searched for.

Enterprises will be pleased that Windows Vista has the ability to index files that are taken “offline” or cached locally, but there's more to come with Windows Server 2008...  Windows Search in Windows Server 2008 also includes a feature known as Federated Search.  Using this, if the file server - on which a network file share is hosted - is running either Windows Vista or Windows Server 2008, any searches against the share will be federated (read: delegated) to the server.  The server will perform the search against its local index and present the results to the client system, filtering out the files the user does not have access to.  This procedure is totally transparent to the user.

Natural language search is also supported and so the user can search for things like "photo taken last week" or "email sent from Dave".  However, this is disabled by default.  Natural language search uses expressions in the queries in Natural Query Syntax (NQS), which is the natural language equivalent of AQS.

While Windows 2000 and Windows Server 2003 included the Indexing Service, WDS and Windows Search use a different architecture and a new indexing engine.  Windows Search replaces the Indexing Service in Windows Vista and Windows Server 2008 and is available in the Windows Server 2008 "File Server" server role services.

Windows Search Service is a new indexing solution that is included in Windows Server 2008 as a role service in the File Services role.  It creates an index of the most common file and non-file data types on your server - such as e-mail, contacts, calendar appointments, documents, photos, multimedia, and other formats extended by non-Microsoft files. Indexing files and data types enables you to perform fast file searches on your server from computers running Windows Vista, or from computers running Windows XP or Windows Server 2003 with Windows Desktop Search installed.
Indexing Service is an indexing solution that is included with Windows Server 2008 and was part of previous releases of Windows.

When you install Windows Search Service using the "Add Roles Wizard" or the "Add Role Services Wizard" in Server Manager, you are given the option to select the volumes that you want to index. We recommend that you select a volume that is used exclusively for hosting shared folders. Indexing files and data types in folders that are not shared on your network will not benefit client computers connecting to your server and will consume system resources.

If you want to index individual shared folders, you can add them later to the list of indexing locations by using Indexing Options in Control Panel.

The Windows Search engine also integrates with Group Policy and allows centralized configuration of the indexer.

The Windows Search indexer runs as a service, known as Windows Search, and performs the I/O operations with low priority.  As a result, whenever other processes require the I/O bandwidth or processor time, it is able to pre-empt the indexer, thereby significantly reducing the performance hit associated with the indexer running in the background.

Windows Search technologies share a common architecture and seamless integration with a growing range of Microsoft enterprise search products including Microsoft Office 2007, Microsoft Office SharePoint Server 2007 and Windows Server 2008.   

Additional reading:

Server Message Block (SMB), also known as CIFS (Common Internet File System) is the file sharing protocol used by default on Windows based computers.  Windows includes an SMB client component (Client for Microsoft Windows) and an SMB server component (File and Printer Sharing for Microsoft Windows).

SMB in Windows Server 2008 and Windows Vista support the new SMB version 2.0 that has been redesigned for today's networking environments (wireless, possible high loss, timeouts, high latency, ...) and for the needs of the next generation of file servers (EFS over the wire, Offline Files and Folders enhancements, ...).

Machines running Windows Server 2008 and Windows Vista support both SMB v1.0 and SMB v2.0.  However SMB 2.0 can only be used if both client and server support it!!  So, the SMB protocol revision to be used for file operations is decided during the negotiation phase

A Vista client advertises to the server that it can understand the new SMB 2.0 protocol.  If the server (Windows Server 2008 or otherwise) understands SMB 2.0, then SMB 2.0 is chosen for subsequent communication, otherwise they fall back to SMB 1.0. 

This preserves "downwards" compatibility so that deploying Vista clients or Windows Server 2008 servers should be simple and straightforward.   The following list below describes what protocol will be used when communicating between different types of client and servers.

  • Vista client <> Vista client or Windows Server 2008 – SMB 2.0
  • Non-Vista client <> Vista client or Windows Server 2008 – SMB 1.0
  • Vista client <> Non-Vista client or Non-Windows Server 2008 – SMB 1.0
  • Non-Vista client <> Non-Vista client or Non-Windows Server 2008 – SMB 1.0

For an overview of the impact on network throughput, have to look at the white paper of a third-party benchmark study done by The Tolly Group which compares network throughput and time-to-completion of several tasks when using Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2008 .