Table outlines the minimum and recommended hardware requirements for Windows Server R2 as provided by Microsoft:. As with any other operating system installation, you will receive improved performance if you have a faster processor and additional memory on your system.

Further, when you install Windows Server R2 on an Itanium-based computer, you must have an Intel Itanium 2 processor and additional hard disk space. Computers with more than 16 GB RAM require additional disk space for paging, hibernation, and dump files. With disk space at an all-time minimum cost, it is easy to acquire a high-capacity hard disk.

You will certainly need plenty of disk space on a server that will be a domain controller in a large domain. Microsoft recommends that you also perform the following actions before installing Windows Server R As explained in Chapter 1, Windows Server Core includes a minimal version of the server software without the GUI; you perform all configuration tasks from the command prompt.

Follow this procedure to install Windows Server Core and perform initial configuration tasks:. After a few minutes, you receive the Windows Server R2 screen shown in Figure Click Install now to begin the installation. Figure Starting the installation of Windows Server R2.

Windows copies temporary files and then displays the Get important updates for Windows Setup screen shown in Figure Figure This screen enables you to select either the complete installation of Windows Server R2 or the Server Core option.

You receive the options shown in Figure to upgrade or install a clean copy of Windows Server R2. Select Custom advanced to install a clean copy of Windows Server R2. The upgrade option is available only if you have started the installation from within Windows Server , Windows Server R2, or the original version of Windows Server Take a coffee break while the installation proceeds.

This takes some time particularly when installing on a virtual machine , and the computer restarts several times. As shown in Figure , Setup charts the progress of installation. Type and confirm a strong password. When informed that the password is changed, click OK. After a minute or so, the desktop appears, containing a command window but no Start screen or desktop icons see Figure This is the standard Windows Server Core interface.

All configuration, management, and troubleshooting of Windows Server Core is done from the command line. Available utilities enable you to perform almost all regular configuration tasks in this fashion.

Table describes some of the more useful available commands. Joins an Active Directory domain. You will be prompted for the username and password of a user with domain administrator privileges. Configures and manages a series of common Server Core installation properties. See Figure Figure The Sconfig.

We discuss many Server Core commands and PowerShell cmdlets in various chapters of this book and other Cert Guide books in this series. Although Microsoft markets Server Core as being the default Windows Server R2 installation, the full GUI version still represents the most easily managed version of the server. Windows displays a Welcome message and prepares your desktop.

Then the desktop with Server Manager shown in Figure appears. When you shut down a Windows Server R2 computer, it displays the Shutdown Event Tracker dialog box, which asks you for a reason for shutting down the server.

For learning purposes, it is helpful to disable this item. You can do so by typing gpedit. On the dialog box that appears, click Disabled and then click OK. You cannot upgrade a Windows Server or older computer or a computer running any client version of Windows to Windows Server R2.

This command returns the index number for the server with a GUI image. Then type the following command:. Use the following PowerShell command in place of those given in steps 2 and To install the complete desktop experience on your server including access to Windows Store apps as in Windows 8 or Windows 8.

This mode adds a link to Windows Store on the Start screen, as shown in Figure :. Installing the minimal server interface on your server requires you to remove the Start screen shell. Use the following PowerShell command and then restart your computer. You receive a command prompt window and the Server Manager console as previously shown in Figure As an organization grows, administration of servers can become become quite overwhelming to manage.

To help balance the workload and create a smooth support process, a delegation model should be implemented. Implementing a delegation model involves the following:. Preparing for a delegation model requires some planning up front. Deciding how to manage your systems administration can be a frustrating task.

The key to success is to define a model that best works for your situation, agree upon the long-term strategy, and discipline those involved to stick with the model. There are three basic strategies to select from when deciding how to manage your environment:. Containing characteristics of both decentralized and centralized models, the shared or delegated approach focuses on centralized policies and procedures governed by the enterprise admins.

This approach is hierarchical in nature in that many layers of administration can be defined. For example, the main office might contain the majority of the systems. These systems are managed by senior administrators or an enterprise admin group. Desktop engineers might be delegated administrative access to all desktops but might escalate issues to site admins or even enterprise admins if necessary. Once a delegation model has been selected, the next step is to decide how to delegate access.

Depending on the server, installed roles, and applications installed, there are different ways to delegate access. In some cases, applications or roles include an interface where elevated access is granted.

In most other situations, local built-in groups can be used to grant different access to different delegates depending on their function. For example, suppose you have delegated backup duties to a small team of junior administrators. To help streamline this in larger organizations, you might consider additional layers of group nesting along with group policy to push down the elevated access to a group of servers.

This method provides a more scalable solution as expanding delegate access is as simple as adding more junior admin accounts to a domain group. The domain group is then automatically added to the backup operators local group on the servers. Active Directory will be discussed in more detail later. Refer to Table for a listing of built-in local groups and their functions.

Grants full access and control to the computer. Allows members to change and manage permissions and access to the computer. Ability to back up and restore files regardless of the permissions assigned to the folder or files. These users are unable to modify and manage permissions. Users are granted virtually no access to the system other than to use the Internet and basic applications. They are granted temporary profiles upon logon. Limited access to log on to the computer.

Allows users to run applications, use local devices and peripherals but not make administrative changes. When delegating administrative tasks, it is a good practice to create separate delegate accounts for users.

The idea is to operate on the principle of least privilege, meaning for normal operations you would use a standard user account with enough access to perform your job. When elevated privileges are required, invoke the run as function or log in with your delegate account. This reduces the risk of unintentional changes that could make for an unpleasant day for the admin.

You can assign different sets of administrative responsibility to different users, and these can include segments of the directory structure such as OUs or sites. The following are several benefits of delegating administrative control:. When designing your AD DS forest structure, you should keep in mind the administrative requirements of each domain.

Each domain has the capability to contain a different OU hierarchy. The forest administrators, who are members of the Enterprise Admins group, are automatically granted the ability to create an OU hierarchy in any domain within the entire forest. Domain administrators, who are members of the Domain Admins group in each separate domain, by default are granted the right to create an OU hierarchy within their own domain.

When you initially create your OU design, you should do so to enable administration. After that, you should create any additional OUs required for the application of Group Policy and management of computers. The final step in delegating administrative duties is identifying the toolsets available to your delegates.

Microsoft has provided us with the following tools to help with administrative tasks:. Before using administrative tools, you must first ensure that the necessary access rights have been granted and that you have addressed any prerequisites, such as.

Net Framework 4. It helps administrators cut down on repetitive tasks by defining prebuilt configurations that accompany PowerShell 4. Configuration parameters are saved in a Managed Object File MOF and can be used as a baseline for comparison or as a template for new deployments. DSC is often used in the following situations:. DSC works via two basic methods: Pull and Push. The Pull method works through the use of a Pull Server.

Using this method, you can configure a server as the Pull Server, which acts as central configuration repository storing the configuration data for computers. In large environments, nodes can be configured to pull from the server as they come online. The second method is the Push method. In smaller implementations, a central server can be configured to Push DSC configurations. As an administrator, you also have the ability to use a combination of both Pull and Push methods.

DSC works through the basis of defining configurations within scripts. Using Notepad, you can build a custom DSC configuration.

Configurations contain several components, all of which are organized within a configuration block. The keyword Configuration tells PowerShell that a specific configuration is to follow. Although no baseline specifications are offered, minimum and recommended client device specifications should be evaluated to arrive at a satisfactory underlying VM template. Overview This document provides a set minimum and recommended system requirements, both hardware and software, for multi-user sites operating the current suite of CCH Software products.

Disk space required on client devices at runtime: MB per program. Virtual Environments and Thin Client Environments Virtual Environments are supported where the virtual environment is invisible to the application layer and it is designed to deliver a simulated physical environment of equivalent functionality and performance.

Hence, the operation of the application in the virtual environment will be identical to its operation in a physical environment. Full Desktop Deployment only. See the Thin Client dedicated section for an example specification. Peer-to-Peer Peer-to-Peer P2P configurations are supported with the following conditions and warnings: Connectivity issues do not fall within our remit, either at point of installation or through ongoing use. If the server is also to be used as a client computer, then we recommend that both workloads are witnessed at peak times to ensure performance levels are known.

The deactivation of anti-virus software and firewall may be required at point of installation. We currently support up to 6 users with P2P configurations. Hardware requirements – single server installations and dedicated database servers The requirements in the following table apply to a single server with a built-in database or dedicated database servers in the environment.

If these services are hosted on dedicated Application Services then sufficient resources should be allocated to meet the expected workload. Network 1 Gbps or higher Microsoft. NET Framework 3. Software Requirements The requirements in the following section apply to the following installations: Single server with built-in database Dedicated database servers Minimum software requirements This section provides minimum software requirements for each server.

System Requirements – client devices The requirements in the following table apply to client devices in the environment. The latest generation of CPUs are recommended. The currently supported Microsoft Office versions are: Microsoft Office Microsoft Office Microsoft Office Microsoft Integration is typically implemented between the following Office applications: Word Excel Outlook Choose the appropriate edition of Office to enable the entire suite of functionality.

Same as minimum. Note : Windows Server , R2, and are only available in bit architecture. Open source render manager for visual effects and animation. Convert video files and package them for optimized delivery. App migration to the cloud for low-cost refresh cycles. Data import service for scheduling and moving data into BigQuery.

Reference templates for Deployment Manager and Terraform. Components for migrating VMs and physical servers to Compute Engine. Storage server for moving large volumes of data to Google Cloud. Data transfers from online and on-premises sources to Cloud Storage. Migrate and run your VMware workloads natively on Google Cloud. Security policies and defense against web and DDoS attacks. Content delivery network for serving web and video content. Domain name system for reliable and low-latency name lookups.

Service for distributing traffic across applications and regions. NAT service for giving private instances internet access. Connectivity options for VPN, peering, and enterprise needs. Connectivity management to help simplify and scale networks.

Network monitoring, verification, and optimization platform. Cloud network options based on performance, availability, and cost. Google Cloud audit, platform, and application logs management. Infrastructure and application health with rich metrics. Application error identification and analysis. GKE app development and troubleshooting. Tracing system collecting latency data from applications.

CPU and heap profiler for analyzing application performance. Real-time application state inspection and in-production debugging. Tools for easily optimizing performance, security, and cost. Permissions management system for Google Cloud resources.

Compliance and security controls for sensitive workloads. Manage encryption keys on Google Cloud. Encrypt data in use with Confidential VMs. Platform for defending against threats to your Google Cloud assets. Sensitive data inspection, classification, and redaction platform. Managed Service for Microsoft Active Directory. Cloud provider visibility through near real-time logs.

Two-factor authentication device for user account protection. Store API keys, passwords, certificates, and other sensitive data. Zero trust solution for secure application and resource access.

Platform for creating functions that respond to cloud events. Workflow orchestration for serverless products and API services. Cloud-based storage services for your business.

File storage that is highly scalable and secure. Block storage for virtual machine instances running on Google Cloud. Object storage for storing and serving user-generated content. Block storage that is locally attached for high-performance needs. Contact us today to get a quote.

Request a quote. Google Cloud Pricing overview. Pay only for what you use with no lock-in. Get pricing details for individual products. Related Products Google Workspace. Get started for free. Self-service Resources Get started.

Stay in the know and become an Innovator. Prepare and register for certifications. Expert help and training Consulting. Partner with our experts on cloud projects. Enroll in on-demand or classroom training.

Partners and third-party tools Google Cloud partners. Explore benefits of working with a partner. Join the Partner Advantage program. Deploy ready-to-go solutions in a few clicks. Machine type families. Regions and zones. Get started. Plan and prepare.

Work with regions and zones. Images and operating systems. OS images. Premium operating systems. Access control. Create VMs. Create a VM. Create Spot VMs. Spot VMs. Preemptible VMs. Create custom images.

Create and manage instance templates. Create multiple VMs. Create a managed instance group MIG. Bulk creation of VMs. Create sole-tenant VMs. Use nested virtualization. Manage VM boot disks. Migrate VMs. Import disks and images. Automatic import. Manual import. Move a VM within Google Cloud. Connect to VMs. Connection methods.

Access management. IAM-based access control. SSH key management. Best practices. Manage storage. About disks. Disk encryption and security. Persistent disks. Manage disk performance. Use regional persistent disks for high availability services. Ephemeral disks local SSD. Manage local SSD performance. Back up and restore. Back up VMs. Back up disks. Create application consistent snapshots.

Restore from a backup. Manage VMs. Basic operations and lifecycle. Stop and start VMs. View VM properties. Update VM details. Configure IP addresses. Delete VMs. Manage groups of VMs. Support a stateful workload with a MIG. Configure stateful MIGs. Group VMs together. VM host events. Manage metadata. Securing VMs. Manage operating systems. Guest environment. Manage guest operating systems. About VM Manager. Create and manage patch jobs.

Work with OS policies. Legacy beta. Manage OS images. Manage licenses. Use startup scripts. Deploy workloads. Web servers. Send email from a VM. SQL Server. Microsoft Windows. Windows Server. Load testing. Machine learning. Monitor logs. Monitor resources. Autoscale groups of VMs. Create and manage autoscalers. Reserve zonal resources. Load balancing. Build reliable and scalable applications.

Resource utilization. Use recommendations to manage resources. Manual live migration. Workload performance. Accelerated workloads with GPUs. GPUs on Compute Engine. Install drivers.

System Requirements for Windows Server Essentials | Microsoft Docs.Performing an in-place upgrade of Windows Server | Compute Engine Documentation | Google Cloud

 
› searchwindowsserver › tip › Be-aware-of-essential-. English only. 2 GB RAM. 1 CPU. 80 GB hard drive. To use the VHD distribution, you must have a computer running Windows Server R2.

– F-Secure User Guides

 
› searchwindowsserver › tip › Be-aware-of-essential-. English only. 2 GB RAM. 1 CPU. 80 GB hard drive. To use the VHD distribution, you must have a computer running Windows Server R2.