Hardware requirements for windows 2008 r2

It is also important to be aware of the upgrade options available with each edition. With this objective in mind, this chapter will focus on providing an overview of both the different Windows Server R2 editions and the recommended hardware requirements. The first item of note for users familiar with the first version of Windows Server is that the R2 edition is only available for bit systems. Whilst some editions of the original Windows Server operating system were available in bit versions, this is now no longer the case for the R2 version.

The Foundation edition of Windows Server R2 is the new entry level edition and is designed specifically with the small business in mind. It is the least expensive of the various editions and lacks some of the more advanced functionality typically found in the higher end editions such as full Active Directory support and Hyper-V virtualization capabilities.

Making sure if you have the right specs is a must. To run server R2, your hardware must meet certain requirements to run it. It requires a bit processor unless you're running on Itanium based systems.

Your processor must run on at least a 1. It's recommended your processor is 2. The least amount of available disk space you need to run it is 10 GB. For best performance, we suggest you've 40 GB or more of disk space available for the system to run better. The display requirement for this operating system is at least a Super VGA by monitor or one with better resolution.

To run the system you'll need the basics. The keyboard and mouse are essential to run this operating system. If you're running the server on an Itanium-based system, you'll need to meet certain hardware requirements. Your system must have an Intel Itanium 2 processor and more disk space available. With the Server Core installation option, the traditional Windows interface is not installed, so you must configure the server from the command prompt.

Note that if you use a Server Core installation, you cannot install some modules that rely on the. NET Framework or managed code. For more information, see Using Server Core. After the Windows Server or Windows Server R2 setup is finished, log on to the server for the first time, and the Initial Configuration Tasks window automatically opens.

You can now configure the new server by using commands in the Initial Configuration Tasks window. Skip to main content. This browser is no longer supported. On the Configure page at the end of the installation wizard, the context is switched to the service account that you created.

The machine. If the proxy configuration is being done in an existing setup, the Microsoft Azure AD Sync service needs to be restarted once for the Azure AD Connect to read the proxy configuration and update the behavior. It's common for proxy servers to have connection idle timeout configuration. Ensure the configuration is set to at least 6 minutes or more. For more information, see MSDN about the default proxy element. For more information when you have problems with connectivity, see Troubleshoot connectivity problems.

NET Framework 4. You need this version or a later version installed on your server. You can configure. For more information about TLS 1. Make sure you have the. NET 4.