Configuring OS language settings. Server system configuration
Views: 123361
0
Configuring a DNS server to point to itself
One of the first tasks that should be performed immediately after installing a DNS server is to configure its TCP/IP settings so that it points to itself when DNS name resolution occurs, unless there is a special reason that it didn't do this.
3. In the window Network connections click right click mouse on the Connect by icon local network and choose in context menu Properties item.
4. Double click on the element Internet Protocol(TCP/IP) (Internet Protocol (TCP/IP)).
5. In the section of the window that is associated with the DNS server, make sure that the Use the following DNS server address radio button is selected, and enter the IP address of your DNS server in the “Preferred DNS server” field.
6. If there is another DNS server, specify its IP address in the Alternate DNS server field.
7. Click OK twice to changes made came into force.
Setting up a DNS server
1. Open the Server Manager console.
2. Expand the Roles, DNS Server and DNS nodes in sequence, then click on the DNS server name.
3. From the Action menu, select Configure DNS Server.
4. On the Welcome page of the DNS Server Configuration Wizard, click Next.
5. Select the Create forward and reverse lookup zones radio button (recommended for large networks) and click the Next button.
6. Select the option Yes, create a zone live view now (recommended) and click Next.
7. Specify what type of zone you want to create, in in this case selecting the Main Zone option and clicking the Next button. If the server is a domain controller with write access, the Save zone in check box will also be available for selection. Active Directory.
8. If you save the zone in Active Directory, select the replication scope and click the Next button.
9. Enter fully qualified Domain name zone (FQDN) in the Zone Name field and click Next.
10. At this stage, if you create a zone that is not integrated with AD, you can either create a new text file for a zone, or import an existing one. In this case, select the Create option new file with this name and leave the default settings, then click on the Next button to continue.
11. On the next page you will be asked to allow or block the DNS server from receiving dynamic updates. In this example, we will prohibit the DNS server from accepting dynamic updates by selecting the Prohibit dynamic updates radio button and clicking the Next button.
12. The next page asks you to create a reverse lookup zone. In this case, select the Yes, create reverse lookup zone now radio button and click Next.
13. Specify that the reverse lookup zone should be the main zone by selecting the Main zone radio button and click the Next button.
14. If you save this zone in Active Directory, select the replication scope and click Next.
15. Leave the default IPv4 Reverse Lookup Zone option selected and click Next.
16. Enter the network ID for the reverse lookup zone and click Next. (Typically, the Network Identifier is the first set of octets from the zone's IP address. For example, if the network uses the Class C IP address range 192.168.0.0/24, then the Network Identifier can be entered as 192.168.0.
17. If you create a zone that is not AD-integrated, you will again be prompted to either create a new file for the zone or import an existing one. In the example under consideration, select the Create a new file with the same name radio button and click the Next button.
18. You will then be prompted to indicate whether dynamic updates should be allowed. For the purposes of this example, select the Prohibit dynamic updates radio button and click Next.
19. On the next page you will be asked to configure the repeater settings. In this example, select the No, you should not forward requests radio button and click Next.
20. The final screen will provide a summary of those selected for inclusion and addition to the database DNS changes and zones. Click the Finish button to make all these changes and create the desired zones.
Open the Server Manager console. Expand sequentially the nodes Roles, DNS server, DNS, server name, forward lookup zones and select the zone we created.
All efforts of Microsoft developers and marketers are devoted to rehabilitation
trademark after the virtual failure of the Vista venture. The media only talks
about Windows 7, but about the preparation of a new release of the server version of Win2k8, which received
Few people know only a modest addition to the name R2. Meanwhile, the tandem of these
two operating systems can make working on the network more secure, productive and
comfortable.
Initially for Win2k8R2 a louder name was envisaged -
Windows Server 7, but at the PDC 2008 conference it was announced that the new product will be
be called precisely, and it should not be considered
as a main release, but as an intermediate release. This created confusion and a lot of questions,
because at first everyone was convinced for a long time that everything would be exactly the opposite.
The guys from Microsoft clarified the situation, indicating that the corporation plans to release
new versions of server OS according to the scheme 2 years (update) and 4 years (new release),
that is, R2 is precisely an update after Win2k8. They probably did this
so as not to “shade” the output of the seven. On the other hand, the release of Win2k8 was welcome
accepted by specialists, and changing the name could scare off those who are now
wants to buy this OS. Otherwise, most will postpone the transition and wait
Win7Server, roughly the same as the situation today with Vista and Win7.
A beta version of the system became available for download in mid-January 2008.
On August 14th the company, which at the end of July this year was released in RTM status
along with Windows 7. Microsoft Download subscribers can now download the system
Network (MSDN) or TechNet services, the rest of the new server OS will be
available from October 22nd.
The list of major new products announced in R2 is placed on one page,
but this is exactly the case when quantity turns into quality. "Small" ones
There are quite a lot of improvements. But first things first.
Windows Server 2008 R2: what's new?
Among the main innovations is an updated virtualization system
2.0,
supporting Live Migration technology, which allows you to migrate on the fly
virtual machines between physical servers. Dynamic storage
virtual machines Provides hot-plugging and hot-plugging capabilities
storages. Physical and virtual systems can be easily deployed using VHD
(Virtual Hard Disk
) files. And, unlike previous version OS, Hyper-V
is an integral part of the system, that is, there is no separation into regular versions
and "with Hyper-V".
The topic of virtualization in R2 is not exhausted with the Hyper-V update. Term
"virtualization" now covers three technologies: Server Virtualization, Client
Virtualization and Presentation Virtualization. It is noted that R2 is
a full-fledged VDI solution (Virtual Desktop Infrastructure, infrastructure for
virtualization of client workstations), providing centralized
managing everyone virtual systems and simple provision of computers.
How it works? A Hyper-V-enabled server runs many
virtual machines with client OS from WinXP to Win7. User
(implying that he is sitting at a low-power computer or thin client under
running Windows Fundamentals or Linux) to get to your desktop,
connects remotely to a separate one (VDI completely isolates virtual environments
users) virtual machine. The VM can either be hardwired to
him, or any of the available ones - it depends on the type of infrastructure used
VDI - static or dynamic. In short, VDI is
a unique combination of RDP connections and virtualization.
Terminal Services has been renamed to Remote Desktop Services (RDS),
which more reflects its purpose - work in the VDI structure. But VDI is not
the only innovation in RDS. Multi-monitor configurations are supported,
video and audio are very High Quality. Win7 users can easily get
Access to remote application or desktop using the new applet
RemoteApp & Desktop Connection without feeling the difference between local and
terminal applications.
The standard delivery includes the updated PowerShell 2.0, quantity
The changes in which, compared to 1.0, are quite large:
- Improved API;
- GUI for creating and debugging scripts;
- PowerShell in Remote Desktop Services;
- Executing commands on a remote machine using WinRM 2.0;
- Background execution of tasks (PSJob);
- Running a process on one or more machines and working with WPF (Windows
Presentation Foundation) - a new subsystem in the composition. NET Framework 3.0,
allowing you to create beautiful graphical interfaces.
Some old cmdlets have been improved, and about 240 new ones have appeared.
The updated IIS (version 7.5) integrates FTP (with new settings files,
based on .NET XML), WebDav, URLScan 3.x (limiting types of http requests),
Administration Pack (SQL database management, configurator, reports, filtering
requests). Previously, all this was implemented as a separate extension, but now
just one click of the mouse is enough. Improved PHP support for FastCGI implementation.
Back in IIS 7.0, it was possible to create applications in an isolated pool, which
contributed to increasing the level of reliability and safety. In IIS 7.5 each pool
applications run at a unique, less privileged level
authenticity. By the way, the fact that the new IIS is completely trusted is evidenced by
the fact that Microsoft moved its website to version 7.5 in February.
We will also add the ability to publish with one click in Visual Studio 10, new
performance counters and management tool Web Deployment Tool (MS
Deploy), allowing Web server administrators to easily deploy,
synchronize and migrate sites, including configuration, content and
SSL certificates.
Server Core can now also install .NET, including ASP.NET and
PowerShell. Install 2.0 and 3.0 .NET Framework using a new utility DISM
(Deployment Image Servicing and Management), which is included in the standard
delivery of the system and the WAIK kit (the /Online key allows you to manage settings
working system):
>
> dism /Online /Enable-Feature /FeatureName:NetFx3-ServerCore
An interesting innovation is the opportunity additional installation attributes and
properties on files in File Server Resource Manager. This actually combines NTFS with
SharePoint libraries and provides almost limitless possibilities for
processing files according to various characteristics.
From now on only 64
It was previously reported that Win2k8 will be the last 32-bit version of the server OS.
And so it happened - R2 will be released only for x64/ia64 architectures. AMD Companies
and Intel no longer produce 32-bit processors for servers based on the architecture
x86, therefore leaving the 32-bit market and shifting emphasis towards 64-bit OS and
applications looks quite logical. Although support for 32-bit applications in R2
remained and was implemented using the WOW64 (Windows on Windows64) emulation layer. By
default in Server Core version and Hyper-V support WOW64 is disabled. To
enable support for 32-bit applications; the administrator just needs to run
one command:
> dism /Online /Enable-Feature /FeatureName:ServerCore-WOW64
And – to support 32-bit .NET applications:
> dism /Online /Enable-Feature /FeatureName:NetFx2-ServerCore
> dism /Online /Enable-Feature /FeatureName:NetFx2-ServerCore-WOW64
> start /w ocsetup ServerCore-WOW64
> start /w ocsetup NetFx2-ServerCore-WOW64
The current version of Win2k8 supports up to 64 logical processors. In R2 they
the number was increased to 256. Considering that in Lately number of cores per
one physical processor is constantly increasing, such a reserve is definitely not superfluous
will. Moreover, if the cores are not used, they can be turned off, thereby
saving a lot of electricity. Virtual machine running under new
Hyper-V supports up to 32 logical CPUs (in the previous version there were only
4). By the way, by logical processor in Windows we mean not only the number
cores, but also the simultaneous number of processed threads. In messages
it slipped out that Win2k8R2 can work with 32 4-core processors, each
the core of which simultaneously processes 2 data streams (32 CPU x 4 cores x 2
data stream = 256).
Minimums named system requirements: 1.4 GHz 64bit CPU, 512 MB RAM, HDD
10 GB. The recommended ones, as you understand, are significantly higher. When planning
server configuration should also take into account that the Standard version supports
maximum 32 GB RAM, and Enterprise and Datacenter up to 2 TB RAM.
There are many other new features available in R2; some of them were found in
seven. So, in Windows Firewall There may be several active profiles (Private,
Public or Domain), which does not cause problems when connecting to multiple networks;
added support for http links in QoS, implemented VPN Reconnect and DHCP
Failover. QoS service allows you to prioritize traffic when accessing
certain resources. Previously in the "Application Name" tab in "Policy-Based QoS"
there were only two points with which you could set either everything or
certain applications. Now the tab is called "Application Name or URL"
and here you can specify the name/template of the http resource whose traffic will be assigned
increased priority. New feature VPN Reconnect, which is part of RRAS
(“Routing and Remote Access Service”), allows the VPN client to
automatically restore the VPN connection in a situation where communication with
The VPN server was temporarily interrupted (previously this had to be done manually or
wait a fairly long timeout). To enable VPN Reconnect,
should choose VPN type IKEv2 (Internet Key Exchange, described in RFC 4306).
Windows Server 2008 R2 Management Tools
Installation new system, which was simplified in Win2k8 to
sequential pressing of the "Next" key, in R2 practically did not change
(by the way, on beta, when installing, looms at the bottom of the screen Windows inscription 7). All
installation can be done in literally 6 mouse clicks - after several
reboots and entering the administrator password we get ready-made system. In the window
registration, you can create a floppy disk to reset the password (namely a floppy disk, not
CD/DVD, so you will need a floppy drive). While creating hard sections disk
The wizard by default creates two partitions (boot and system) so that there is no
problems activating BitLocker.
Subjectively, the updated OS works faster than the previous one, this is especially good
visible under virtual machines. After loading you will be greeted by a stylized desktop
under Win7. To change the screen resolution, you do not need to open the Appearance panel.
Instead, the Screen Resolution item is located in the context menu. Other
changes are made through the "Control Panel". In general, regarding perestroika
There are quite a few changes to the interface, but I think you are interested in completely different ones
tools.
Before we had time to get used to all the innovations of Win2k8, we got a number more in R2
improvements. The "Initial Configuration Task" launched immediately, when
whose help are carried out initial settings, did not change. But in Server
Manager now has an opportunity that was clearly missing before - remote
connection to another server. Now just go to Action – Connect to
Another Computer and enter the data of another system running R2.
And most importantly: supported remote control not only the systems in full
installation, but also in Server Core. That is, many administrators will not have the agony of choice:
use safe and fast, but inconvenient/unusual to manage Core
or install complete system. It should also be noted that Server Manager
is part of Remote Server Administration Tools for Win7 (using RSAT
can control Win2k3 and Win2k8). In a domain environment, if there are appropriate
You're right, there won't be any connection problems. And in a peer-to-peer network, a computer with
which is produced remote connection, must be added to "trusted
hosts" (for details on WinRM, see the article "", published in
).
> winrm set winrm/config/client @ (TrustedHosts="system, system2")
When performing administrative tasks, UAC can interfere and block
work. To avoid this, you should select the section
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system,
where to create a LocalAccountTokenFilterPolicy parameter of type DWORD with a value of 1.
By the way, if from under the usual account run commands in the console,
require admin rights, you may receive the message "Elevated permissions are
required then run..." The solution is simple: select the cmd.exe shortcut in the Start menu and
"Run as administrator" item in the context menu.
The list of roles and components has changed, now their number is 17 and 40 (in
Win2k8 - 16 and 35), some roles received a different name. For example, to replace
Terminal Services technology has come new - Remote Desktop Services,
Accordingly, the name changed. WSUS is now part of R2. And he's not
You need to download it from the Internet and install it yourself, keeping track of the dependencies. IN
components we find BranchCache (local caching of data received from
central server), Direct Access management console (makes it easier to connect
users to corporate network), WinRM IIS Extension (the component is intended
to manage the server using the WS-Management protocol), and
Windows Server Migration Tools (allow you to transfer some
roles and settings from Win2k3-Win2k8 servers in R2).
For individual roles (Web-server IIS, AD Domain Services, AD Certificate
Services, DNS, RDS) the Best Practices Analyzer (BPA) tool is available. He
will help configure the role in accordance with Microsoft recommendations, and in case
problems arise - to understand what actually happened, and, if necessary,
return the system to its initial state.
Three new cmdlets for PowerShell - Add-WindowsFeature, Get-WindowsFeature
and Remove-WindowsFeature allow you to add, remove and view information about
selected role. Yes, so that they are available, do not forget at the beginning of the work
load the Servermanager module. For example:
PS C:\> Import-Module servermanager
PS C:\>Get-WindowsFeature
And put the one you need by selecting its name from the list:
PS C:\> Add-WindowsFeature -Name "File-Services" –IncludeAllSubFeature
What's New in Active Directory
Service AD DS (Active Directory Domain Services) received in R2
several new and very interesting features. For example, the Active basket appeared
Directory Recycle Bin resembling Windows Recycle Bin. Now accidentally deleted
the object can be quickly restored. Considering that the previous operation
required account resuscitation great effort, such a possibility may
welcome. The object restored from AD RB receives all its
attributes. By default, the lifetime of a deleted object in AD RB is 180
days, after which it goes into the "Recycle Bin Lifetime" state, loses
attributes and after some time is completely deleted. Change this value
possible by setting the msDS-deletedObjectLifetime parameter. If the domain is on
Win2k8R2 level, the AD recycle bin is activated automatically.
New PowerShell cmdlets make server administration easier with
command line. Converting a domain to R2 mode is very simple:
PS C:\> Set-ADForestMode –Identity domain.ru -ForestMode
Windows2008R2Forest
Now enable AD RB:
PS C:\> Enable-ADOptionalFeature –Identity ‘CN=Recycle Bin
Feature,CN=Optional Features,CN=Directory Service,CN=Windows
NT,CN=Services,CN=Configuration,DC=domain,DC=ru’ –Scope Forest –Target
'domain.ru'
You can view the list of deleted objects using the ldp.exe utility or
using the Get-ADObject and Restore-ADObject cmdlets.
The R2 package included new utility djoin.exe, which has several purposes
unusual - connecting to a domain that is currently unavailable. Such a necessity
may be needed when deploying virtual machines and when ordering
pre-configured equipment to the supplier, so as not to disclose credentials. Principle
quite simple: first, on a system connected to the domain using djoin.exe,
An XML file is created, which is then imported on the connecting system.
In addition, the Active Directory Administration Center has been updated,
which integrated all AD management tasks and replaced ADUC (Active
Directory Users and Computers console).
Conclusion
There are quite a lot of innovations in Win2k8R2, and they really simplify many things.
aspects of Windows network administration. Of course, for the final release something
may still change or be added. Therefore, what will the final look like?
version Win2k8R2, time will tell. In the meantime, download and test!
WWW
Resources for:
- information for IT professionals on Microsoft TechNet -
http://go.microsoft.com/fwlink/?LinkID=66006 - information for developers on Microsoft MSDN -
go.microsoft.com/fwlink/?LinkId=67404 - Articles in the Support Knowledge Base (KB) -
go.microsoft.com/fwlink/?LinkID=55142 - Microsoft Connect newsgroups -
Today I will talk about how to raise a terminal server to Windows based Server 2008 R2. Overall it's quite simple, but there are a few subtle points, so:
1. What you will need
A powerful computer (server) with Windows Server 2008 R2 installed on it. (I wrote about how to install this axis here)A valid terminal server client license purchased through one of the existing programs licensing. (In this article I will use the agreement number found on the Internet for the Enterprise Agriment program. At the time of writing, the working numbers were: 6565792, 5296992, 3325596, 4965437, 4526017.)
2. Install Remote Desktop Services
Launch the server manager (“Start” - “Administration” - “Server Manager”). Expand the “Roles” tab and click “Add roles”.
The “Add Roles Wizard” will launch. Click “Next”, then select the “Remote Desktop Services” role from the list and click “Next” 2 times again.
We will see the window for selecting role services. In it, select “Remote Desktop Session Host” and “Remote Desktop Licensing” and again “Next” 2 times.
Select the authentication method “Do not require network-level authentication” so that you can connect from old clients. Then click “Next”.
In the next step, you need to select a licensing mode: “Per device” or “Per user”. To understand how these modes differ, consider a simple example. Let's assume you have 5 licenses. With the “Per Device” mode, you can create an unlimited number of users on the server who will be able to connect via remote desktop from only 5 computers on which these licenses are installed. If you select the “Per User” mode, then only 5 selected users will be able to access the server, regardless of what device they are connecting from. Choose the mode that suits you best and click “Next”.
At this point, you need to add users or a group of users who will have access to the Terminal Service. To do this, click “Add”, “Advanced”, in the “Search” window that opens, select the user and click “OK”. In order for all users, without exception, to be able to connect to our terminal server, we add the “Everyone” group. Then click “OK” and “Next”.
If you want to be able to listen to audio data and watch video via a remote desktop, then check the appropriate box. Same with sound recording and Windows Aero. Having selected the necessary parameters, click “Next”.
Now you need to configure the discovery scope for remote desktop licensing. If you have Active Directory installed, then select “This domain” or “Forest”, depending on the structure of the domain. Otherwise, select “This working group" and click "Next".
We check all the settings and click “Install”.
After installation, a reboot will be required.
3. Installing a Remote Desktop Licensing Server
If everything is done correctly, then after the reboot we will see a window with a message that the installation was successful, but with a warning that we need to configure the licensing settings on the Remote Desktop Session Host server.
Let's specify the licensing server manually. To do this, launch the “Remote Desktop Session Host Configuration” snap-in (“Start” - “Administrative Tools” - “Remote Desktop Services”). There we see that the remote desktop licensing server is not specified.
Double-click on this line, in the “Properties” window that opens, select the “Licensing” tab and click the “Add” button.
We select servers from known licensing servers. In our case, the licensing server is located on the same computer as the terminal server. Add it and click "OK".
Now, if we go to the “Licensing Diagnostics” tab, we will see that the licensing server is selected, but not enabled.
To start and activate the Remote Desktop Licensing Server, launch the “Remote Desktop Licensing Manager” (“Start” - “Administration” - “Remote Desktop Services”). In the manager we see our server and the status “Not activated”. Right-click on it and select “Activate Server”.
The “Server Activation Wizard” will launch. Click "Next". In the next window, select the connection method “Auto (recomm.)” and click “Next” again. Fill in information about the organization. Then, filling out additional information(optional) and clicking “Next”, we will see a message about successful server activation.
Now you need to install licenses. If this is not done, the licensing server will issue temporary licenses valid for 120 days. To install licenses, click “Next”, leaving the “Run the license installation wizard” checked. Or you can run this wizard from the “Remote Desktop Licensing Manager” by right-clicking on the server and selecting “Install licenses”. There we can check that the server is activated.
When the “License Installation Wizard” starts, click “Next” and we are taken to the window for selecting a licensing program. The following actions depend on the method of purchasing licenses. In my example this is "Enterprise Agreement". By selecting desired type licensing, click “Next”.
Enter the agreement number and click “Next”. In the next window, select the product version: “Windows Server 2008 or Windows Server 2008 R2”, select the same license type that we selected when adding roles (“per user” or “per device”) and enter the number of required licenses.
Click “Next” and wait for the message about the successful installation of the license. (I would like to note that for reasons unknown to me, this procedure doesn't always end positively. If the wizard reported that the license installation failed, try repeating the procedure some time later. Sooner or later the license will be installed. Checked more than once.) If everything went well in the server manager we should see the parameters of our license.
And let’s make sure that there are no problems by going to the “Licensing Diagnostics” tab in the Server Manager.
That's it, the installation of the terminal server is complete. You can connect to the server using the built-in Windows client"Remote Desktop Connection"
This guide is intended for those who want to install Windows Server 2008 R2 themselves.
I strongly recommend never using any third party Windows builds. Use only original installation images. This will help you avoid many problems and get maximum performance and stability.
I recommend always using English editions of Windows Server. As practice shows, the original (English) versions of Windows work more stable, and it will also be easier for you to communicate in the same language with professionals in case of problems or if you want to exchange experiences.
To begin installing Windows Server 2008 R2, you need to boot from the installation DVD Windows disk Server 2008 R2. To do this, you need to select the CD/DVD drive first in the boot list in your server’s BIOS or use the options Boot Menu. On each server, the BIOS and Boot Menu buttons are different, but usually when the server boots, it is written on the screen which keys need to be pressed in order to get into the BIOS or Boot Menu.
BIOS appearance on different servers may differ, but the ideology remains the same.
You need to go to the “Boot” tab and select “Boot Device Priority”.
To do this, go to the “Exit” tab and select “Save Changes and Exit”.
Click “OK”.
Now, the next time you restart your computer, you will be able to boot from the installation DVD disc Windows Server 2008 R2. To do this, you will need to press any key on the keyboard when the message “Press any key to boot from CD or DVD” appears.
After successfully booting from the Windows Server 2008 R2 installation DVD, the first step is to select your regional settings. In our example, we use the English language Windows version Server 2008 R2, so it would be best to use the default settings.
Click on the “Next” button.
Click on the “Install now” button.
Please note that if you need to install Windows Server 2008 R2 in Server Core mode, then you need to select “Windows Server 2008 R2 Standard (Server Core Installation)”.
IN in this example is being considered Windows installation Server 2008 R2 Standard (Full Installation).
Select “Windows Server 2008 R2 Standard (Full Installation)” and click “Next”.
Now you need to accept the license terms.
This step offers two installation options:
- "Upgrade". This is not the best option. As practice shows, numerous programs may not be compatible with the new operating system, and after updating you will not be able to work with them, in addition, there is a possibility of dragging problems from the old operating system to the new one, thus losing all stability.
"Custom". This is the best option for installing any version of the operating system Windows systems. It allows you to start working with the system “with clean slate”, so after installation you will get maximum performance and stability. All that remains is to install the drivers and the software you are used to working with.
Now you need to choose which disk the new one will be installed on. operating system and allocate space for installation.
If you have more than one disk installed or there are already several partitions on the disk, all this will be displayed on at this stage. You need to be careful and understand in advance which partition you want to install the operating system on.
In this example, one 60Gb disk is installed. In order to create a partition on the disk, you must select “Drive options”.
Then select “New”.
In this case, everything will be allocated for the system free place on disk, so we leave the default value in the “Size” section. Click on the “Apply” button.
The operating system notifies you that it may need to create additional sections on a disk for storing system files.
Click on the “OK” button.
Thus, all free disk space was allocated for the operating system, but at the same time the system reserved a small partition for itself.
Now you need to select the partition on which you intend to install the operating system and click on the “Next” button.
The operating system installation process has begun.
The computer will automatically restart several times.
After installation is complete, the operating system will begin to prepare the server for operation.
Now you need to specify strong password for the “Administrator” account.
Specify a strong password and press “Enter”.
The password for the “Administrator” account has been successfully set.
Click on the “OK” button.
The installation of Windows Server 2008 R2 is complete.
Now you need to install the drivers. They can always be downloaded from the device manufacturer’s website, in the technical support section. On the manufacturer's website, you need to find exactly your server, and also indicate that you need drivers for Windows Server 2008 R2. Without the appropriate drivers, your server will not function correctly.
Here are some links to the technical support section of popular manufacturers.