Windows 2008 r2 desktop deployment

A first step would be to evaluate using MD, since:. Assuming that WDS is appropriate for your needs, the general approach to manage a deployment project includes:. This section of the Hosting Guidance provides details for each of these project phases.

Notice that they are consistent with those found within the MD documentation. Windows Deployment Services assists with the rapid adoption and deployment of Microsoft Windows operating systems.

Use it to set up new computers through a network-based installation without having to be physically present at each computer and without having to install directly from CD or DVD media. The components of Windows Deployment Services are organized into the following three categories:. The largest area of savings is on a server at idle load, thanks mainly to improvements in driver tuning and power management in hardware that can be used by the OS.

However, even after loads begin to creep up, clever OS management features can maintain a significant reduction in power consumption. This is made possible through a rewritten processor power-management engine and enhancements to storage power management, among other features. Core parking is another interesting feature that intelligently detects loads on a system and prioritizes and optimizes the distribution of that processing workload among all of the cores available to the operating system.

For instance, on single quad-core processor, core parking will enable modest workloads to be carried out only on one core and allow the remaining three cores to remain in a power-saving inactive state.

When workloads become heavy enough to require the use of other cores, the OS "lights up" the other cores as necessary to handle the duties, and then returns them to the inactive state -- creating, in other words, a "bursting" of processor capacity.

The ability to detect power use and act on that is something new to Windows, and Windows Server R2 adds power consumption and budgeting information reporting features. Unlike some of the other out-of-the-box features, reporting and budgeting require the server hardware to play along.

Whatever power plan is created can be administered remotely, and whatever existing power-management settings you may have in R1 also can be administered remotely. Along with this comes the power budgeting feature, useful in certain scenarios where you want to cap the amount of power used by systems.

Windows can intelligently control the power use of every device on supported systems, down to the device level in some cases, and establish a "governor" on power use that can be very useful in power-limited situations. This lets employees and contractors work in a consistent, managed environment from any location without a major investment in client hardware and the management difficulties usually associated with a remote scenario.

An important new feature of RDS is the new connection broker, which takes service requests from clients both on- and off-premises and connects them with virtual or real desktops, applications and anything in between. The broker supports virtual desktops that maintain their state on a per-user basis or that destroy themselves after each session.

This is great for contractors, overseas employees and temporary workers who only need access to resources while engaged in their work. With RemoteApp, Web Access and RD Gateway services, the connection broker allows seamless access to both hosted desktops and applications. If you are considering application and session virtualization, this is worth a look; in the past, such capabilities required using a third-party solution like Citrix with Windows Server.

There are also enhancements to the RDP experience, like multiple monitor support, enhanced audio support, Windows Media redirection, Windows Aero Glass support -- as in Windows 7 -- and enhanced bitmap acceleration. Share this page with your network. Copy Text. Unpublish revision. Options Republish immediately.

Submit Cancel. This is a permanent link to this article. Step 6. Step 8. A dialog box will appear. Step 9. You should see the IP address you just added in the list. Step Repeat Steps 7 to 9 for each additional IP address or IP address range you wish to add to the server. You will want to add whitelist all IPs that you regularly connect to the server from.