How do I install or remove Windows on Windows 64 (WoW64) on my Windows Server 2008 R2 server core installation?

The WoW64 component is named ServerCore-WOW64. To install it, use the standard ocsetup method: Start /w ocsetup ServerCore-WOW64

To uninstall, use Start /w ocsetup ServerCore-WOW64 /uninstall

Note that this installs/removes the core WoW64 environment, and you need to reboot after changing this. There are also additional WoW64 packages for the various Windows Server 2008 R2 roles to enable 32-bit application support in those roles: Failover Clustering—FailoverCluster-Core-WOW64 PowerShell—MicrosoftWindowsPowerShell-WOW64 .NET 2—NetFx2-ServerCore-WOW64 .NET 3—NetFx3-ServerCore-WOW64 Printing—Printing-ServerCore-Role-WOW64 Server Core IME—ServerCore-EA-IME-WOW64 SUA—SUACore-WOW64

Before installing these components, you must first install the native 64-bit role/feature that this augments with 32-bit compatibility. For example, before installing NetFX3-ServerCore-WOW64, you need to have installed NetFX3-ServerCore.

You won't be told by an application install or application execution that you are missing WoW64 if you need it. Instead, you'll see more generic errors such as "Error 1719: The Windows Installer Service could not be accessed" during a 32-bit application installation, or "The system cannot execute the specified program" id you're trying to run a 32-bit program. Related Reading: Q. Is Windows Server 2008 R2 built on Server 2008's kernel in the same way that Windows Server 2003 R2 was built on Server 2003's kernel?

From: WindowsITpro

Microsoft will support server virtualization for Office Communications Server 2007 R2

Microsoft Wednesday announced that it will support server virtualization for Office Communications Server 2007 R2, its first statement on what portions of its real-time platform will run in a virtual environment.

In a post on Microsoft's Office Communications Server (OCS) blog, Jerome Berniere, senior program manager in the Office Communications group, said the company would support both "fully distributed virtualized topology across several hypervisors and for a single server virtualized topology."

The topologies are supported on Windows Server 2008 Hyper-V and any Server Virtualization Validation Program (SVVP) certified partner solution.

The virtualization will support presence, group chat and instant messaging. The IM support includes remote access, federation and connection to public IM.

The company made the announcement in conjunction with its annual TechEd conference going on this week.

Berniere also said a number of server services would be supported, including: front-end, back-end SQL Server 2008 64-bit; group chat channel; group chat compliance; archiving; monitoring (CDR only); and edge access.

Microsoft said the virtual machines must be running on Windows Server 2008 64 bits. Berniere wrote on the blog, "archiving server and monitoring server can be connected to a virtualized enterprise pool, but they must run on a physical server."

Source: itworld

Functions of IT Support Services

Its responsibility of IT support companies to keep all data safe while maintaining network server security, server upgrades and migrations, email management services and disaster recovery solutions. Such server support technicians help you to run your business smoothly. Therefore, there is high need to have a contract with an IT support service company as well as recommended.

Role of IT Support Services

It is the responsibility of the IT support services provider to ensure the effortless running of all computer systems and entire network.

· Install and configure operating systems as per the agreed standards.
· Give assistance in maintenance and compilation of all significant software and hardware.
· In server failure condition, IT support services provides the facility for disaster recovery solutions for your data as well as server upgrade and if needed migrate to other improved systems.
· Provide secure backup services with complete email management, even remotely.
· Provide repair services and troubleshooting for small and large businesses and always help you get access to the newest technology.
· Find solutions to all those problems that can hinder the smooth working of an organization or business.
· Provide proactive network installation for your network support requirements and a complete range of support packages and systems.
· Most IT support firms offer phone and online support and no need to wait for an engineer to come out to your office.
· Network support services include data security that helps you to detect promptly any computer virus and hacker threats.
· Ensure that all the software and the help desk systems are being kept up-to-date.

How to Install Read-Only Domain Controller on Windows Server 2008

Installing a Read-Only Domain Controller (RODC) isn’t much different than installing a regular domain controller.

However, there is one important factor to keep in mind. A RODC can only be installed into an existing Active Directory Domain with at least one full (non-read-only) Windows 2008 Server Domain Controller.

The reason is that the RODC is a new feature to Windows 2008 and it needs at least one DC to understand what it is doing in order to function properly.

Once the decision has been made to install a RODC the next decision is whether to install on a full-install or core-install of Windows 2008 Server.

The RODC is primarily aimed at providing additional security on an Active Directory Database for a server that is not physically secured. Installing a RODC on a Core Install of Windows 2008 provides no additional physical security.

Installing RODC on a Core Server Install

There is only one way to install RODC role on a Core Server installation. The dcpromo.exe command runs on the GUI-less version of Windows Server 2008.

Using an answer file for the command makes the process much easier than trying to get all the switches just right in the command line.

Although there are many settings available depending upon your particular infrastructure, just basic information is required to complete the command:

• an account with permissions to do what you are trying to do
• the name of the Site
• the database and log paths
• and whether or not to install DNS.

Many people will put a “yes” for RebootOnCompletion. If you are doing an actual unattended promotion then that would make sense.

Regular Installation

On a full install of Windows Servers 2008, there is of course a GUI tool to help with the process. The Active Directory Domain Services Installation Wizard handles the installation of RODC.

Type “dcpromo” at a command prompt to start the wizard. The first screen will ask you whether you want to use an existing forest, or create a new domain in a new forest. Since you must join an existing domain with a RODC, the choice is obvious.

Next you’ll be asked for a username and password. The account must be a member of Domain Admins in order to create a Read-Only Domain Controller.

Next, you’ll choose the site you wish to join.

So far, this is all the same as a regular Domain Controller install. Under “Additional Options” is where you actually choose to make this a Read-Only Domain Controller installation.

Using an answer file for the command makes the process much easier than trying to get all the switches just right in the command line.

Installing the Read-Only Domain Controller on Windows Server 2008 - 1

Although there are many settings available depending upon your particular infrastructure, just basic information is required to complete the command:

* an account with permissions to do what you are trying to do
* the name of the Site
* the database and log paths
* and whether or not to install DNS.

Installing the Read-Only Domain Controller on Windows Server 2008 - 2

Many people will put a “yes” for RebootOnCompletion. If you are doing an actual unattended promotion then that would make sense.

If you are sitting at the console, I prefer to manually reboot the server so that I can take as much time as I want to study what is on the screen if there is an issue.

Next, choose the paths for installing the components, or just click Next to use the defaults. Once the confirmation screen appears, you are all set.

Source: http://windowsserver.trainsignal.com/server-2008-install-rodc-read-only-domain-controlle

How To Disable The Shutdown Event Tracker On Microsoft Windows Server

Microsoft Windows has a feature which enables the operating system to record information about why the machine is going to be shut down or in the event of an unexpected shut down; why it was shut down.

This functionality is called the Shutdown Event Tracker. The feature is turned off by default in Windows XP Home & Professional and most other desktop versions of the operating system. In the case of Windows Server 2003 and other versions in the server family it is enabled by default.

Follow these steps:

1. Go to Start > Run and type gpedit.msc and press ok

2. Open the Computer Configuration > Administrative Templates > System Folder

3. Double click the Display Shutdown Event Tracker setting in the right hand pane.

4. Select the Disable option on the pop up window and press ok

When you attempt to Reset or Shut Down the computer next time the Shut Down Event Tracker option will no longer be displayed and you will be free to perform the operation without its annoyance. To turn it back on - repeat the above but select enabled.

Source: Ezine

How to Change Display Data Prioritization in Windows Server 2008?

Display Data Prioritization in Windows Server 2008 Terminal Services allows for automatic control over the virtual channel traffic that is passed between the client (RDP 6.0) and the server. This enables better performance and user experience because display, keyboard typing, and mouse movement data is given a higher priority over other virtual channel traffic, such as printing, clipboard operations or file transfers. This prioritization is designed to ensure that your screen performance (user experience) is not affected by bandwidth intensive actions, such as large print jobs.

In Windows Server 2008 Terminal Services, the default bandwidth ratio is 70:30. This means that display and input data will be allocated 70% of the bandwidth and all other traffic, such as print jobs , clipboard or file transfers will be allocated 30% of the bandwidth.

Changing the Display Data Prioritization

Warning! This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.

Display Data Prioritization can be changed by making changes to the Registry of the server.

1. Click Start, and then click Run.
2. In the Open box, type Regedit, and then click OK.
3. In the left pane, locate and then click the following registry key:

HKEY_LOCAL_MACHINE'SYSTEM'CurrentControlSet'Services'TermDD

The parameters you might want to change are:

* FlowControlDisable - If display data prioritization is disabled, all requests are handled on a first-in-first-out basis. The default value is 0. You can disable display data prioritization by setting the value to 1.
* FlowControlDisplayBandwidth - Controls the relative bandwidth priority for display (and input data). The default value is 70 and the maximum value allowed is 255.
* FlowControlChannelBandwidth - Controls the relative bandwidth priority for other virtual channels (such as clipboard, file transfers, or print jobs). The default value is 30 and the maximum value allowed is 255.
* FlowControlChargePostCompression - Determines if flow control will calculate the bandwidth allocation based on pre-compression or post-compression bytes. The default value is 0, which means that the calculation will be made on pre-compression bytes.

The bandwidth ratio for display data prioritization is based on the values of FlowControlDisplayBandwidth and FlowControlChannelBandwidth compared to each other. For example, if FlowControlDisplayBandwidth is set to 200 and FlowControlChannelBandwidth is set to 50, the ratio is 200:50.

Source: http://www.petri.co.il/

How to Manage server-side e-mail signatures with Policy Patrol 5?

The e-mail signature in Microsoft Exchange is difficult to manage. Users often make their own signatures, which may be in violation of company policy. This can include everything from improper use of logos, title misrepresentation, and even incorrect data. One way to manage this process is to put in server-side rules. Red Earth Software’s Policy Patrol 5 is one of the tools available for managing server-side e-mail signatures in Microsoft Exchange environments.

We’ve all seen e-mails that come from an organization where all the signatures look the same? That is a nice branding in my opinion. Among its other features, Policy Patrol has a rather advanced signature builder. It can drop in images, custom Active Directory fields, different behavior for new messages vs. replies, company logos, disclaimer text, and time-sensitive messages.



Pricing

Policy Patrol, as well as other tools in this space, are generally priced by user count and then increase with the price per user decreasing as tiers are crossed. List price for Policy Patrol 5 for 1,000 mailboxes and one year of maintenance is $1,004, which is barely more than $1 per mailbox per year. This is a good value for the functionality provided.

Source: blogs.techrepublic.com.com/datacenter/?p=766