70-410Training Guide Installing and Configuring Windows Server 2012 R2 - Windows server 2012 r2 standard configuration guide free
Looking for:
Windows server 2012 r2 standard configuration guide free |
Windows Server 2012 - Installation - Windows server 2012 r2 standard configuration guide free
Using PowerShell, an administrator can perform a series of commands. Some common commands are outlined in Table Windows services have been around for some time. If you recall, a service is an application that runs in the background without a traditional user interface or requiring user interaction to complete its core function.
Services and their configurations are stored in a database known as the Service Control Database. Information is also stored under subkeys located in the Registry. Many services are installed and configured by default when the operating system or additional roles are installed.
Depending on the scenario, some services require additional configuration and management. As with all administrative operations, managing services also requires the proper permissions.
Members of the local administrators group, account operators, domain admins, or higher all have the ability to manage services by default. Microsoft has provided two methods for managing services, the services. An administrator will use these methods to perform the following:. To manage services via a GUI, use the Services. The services snap-in, as shown in Figure , can be launched by searching for services. In the instances where services need to be managed remotely from a central console, you can add the Services snap-in to a custom Microsoft Management Console.
To do this, launch the MMC application from the Search charm, add the Services snap-in to the console, and specify the name of another computer or browse to it using the Browse button as shown in Figure Figure Remote Services Management.
Regardless of local or remote, a handful of items are configurable from the Services snap-in. Each service listed has a series of configurable properties. As you can see, several configurable items are grouped into different tabs as outlined in Table Used to configure the account used to start the service upon boot up.
In most cases, this is defaulted to the Local Service or System built in accounts. If a specific account has been delegated the ability to run the service, this tab provides the ability to supply the authoritative credentials. Commonly used SC commands are listed in Table Queries a server for Service Status. Creates a new service in the Service Control Managers database. The startup type, location to the binary path, display name, and so on are among the configuration options for this command.
These are only a few of the options available for the SC command. Multiple network interface cards are joined together and operate as a single entity. Previously, NIC Teaming was left for the manufacturers to provide a tool.
From the NIC Teaming interface, highlight the available adapters to be added to the team as shown in Figure Confirm that all appropriate adapters are checked. Figure New Team Dialog Box. Expand the Additional Properties drop-down and choose the appropriate Teaming mode. The following modes can be selected:. This is the most common teaming method as it supports just about any Ethernet switch.
The passive links stand by and take over during a failover event resulting from the active link failing.
The use of enterprise classed managed switches is required. After you have successfully configured a NIC Team, a new logical adapter will be available for management under the Network and Sharing Center. From here, you can manage adapter settings much like you have done previously with a traditional adapter. There are many scenarios and configurations for NIC Teaming. To create a new NIC Team, execute the following command:. To remove the NIC Team, execute the command:.
I would like to receive exclusive offers and hear about products from Pearson IT Certification and its family of brands. I can unsubscribe at any time. Pearson Education, Inc. This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.
To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:. For inquiries and questions, we collect the inquiry or question, together with name, contact details email address, phone number and mailing address and any other additional information voluntarily submitted to us through a Contact Us form or an email.
We use this information to address the inquiry and respond to the question. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.
Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites.
Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey. Occasionally, we may sponsor a contest or drawing.
Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law. If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information informit.
On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature. We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.
You are only charged for the resources consumed during the upgrade, including:. Use the pricing calculator to generate a cost estimate based on your projected usage. Performing an in-place upgrade of a virtual machine VM instance that is running an earlier version of Windows Server can be a pragmatic way to modernize your infrastructure and to mitigate the risks of approaching the end of the support lifecycle of Windows Server versions. Before you decide to use an in-place upgrade to migrate to a newer version of Windows Server, be aware of the following limitations:.
Downtime: Depending on the configuration and software installed, the upgrade might take an hour or longer. During the upgrade, access to the VM instance is limited because:. Risk: Depending on the configurations of your existing instances and the installed software:.
Depending on the workload running on your Windows Server instance, you can reduce downtime and risk by pursuing different approaches. A Windows Server product key is valid for only a specific version; when you perform an upgrade to a later version of Windows Server, you must supply a new product key.
There are two primary scenarios:. You are upgrading a VM instance that is based on a public operating system image provided by Google: In this scenario, you must use the predefined KMS client setup keys for the version of Windows Server that you are upgrading to.
The upgrade does not incur additional charges. You are upgrading a VM instance for which you brought an existing license: In BYOL , you need to acquire a product key from your license vendor to perform the upgrade. Check the Microsoft documentation to determine which edition you can upgrade to and whether you are eligible for license conversion. You are upgrading a VM instance that is based on a public operating system image provided by Google: In this scenario, you can use the volume license installation media provided by Google.
The steps to access this installation media are provided below. You are upgrading a VM instance that is based on an imported disk or image: In this scenario, you cannot use the installation media provided by Google. Instead, you have to use an installation media that matches the type of media that you used to install Windows Server on the imported disk or image.
Before you begin your upgrade, review the Microsoft documentation about prerequisites and potential limitations for the version of Windows Server you are planning to upgrade to:. Verify that your VM instance meets the system requirements for Windows Server and has sufficient free disk space.
Review recommendations for upgrading server roles , known issues , and the upgrade process for Windows Server R2. Review the recommendations for planning an in-place upgrade. Verify that you aren't affected by features removed or deprecated in Windows Server R2. Verify that any of your custom or third-party software is compatible with Windows Server R2.
Review the server role upgrade and migration matrix for Windows Server and application compatibility table. Verify that you aren't affected by features removed or planned for replacement in Windows Server Review the Windows Server and Microsoft Server application compatibility list. Before you start the upgrade, we recommend that you create a snapshot of your VM instance , so that you can revert to a safe state in case anything goes wrong:.
Create a regular snapshot for the boot disk of your VM instance. Verify that Windows Server is up to date by using Windows Update. Disable or uninstall antivirus, antispyware, and other agents that can interfere with the upgrade or are incompatible with the Windows Server version that you're upgrading to.
Before you can perform the upgrade, attach the necessary installation media to the VM instance. The right media to use depends on your scenario:. You are upgrading a VM instance that is based on an imported disk or image: In this scenario, you also need to attach the volume license installation media provided by Google so that you can access the necessary scripts. Additionally, you have to attach a custom installation media that matches the type of media that you used to install Windows Server on the imported disk or image.
Go to the Google Cloud console. Set the default project ID. Create a disk based on the installation media. This command adds a disk named win-installers to your project. This disk is not attached to any VM instance.
Attach the disk to your VM instance by using read-only ro mode, so that you can attach the disk to multiple VM instances if necessary:. If you are upgrading a VM instance that is based on an imported disk or image, attach the custom installation media as an additional disk:.
Follow the steps in Creating an image from an ISO file to create a disk from the ISO image that you want to use as custom installation media. Attach the disk to your VM instance, by using read-only ro mode so that you can attach the disk to multiple VM instances if necessary:. By default, Windows Setup prompts you for input at various points during an upgrade.
Because you can't connect to the VM instance by using RDP during the upgrade and therefore can't provide any input, run the upgrade in unattended mode. For more information, see Connecting to instances. Change the working directory to the installation media.
The correct working directory depends on the Windows Server version that you are upgrading to:. Start the Windows upgrade. The required steps to start the upgrade depend on the Windows Server version that you are upgrading to and whether your VM instance is based on a public operating system image or on an imported disk or image:.
Run upgrade. The script completes the following steps:. In some cases, Windows Setup might show a Select Image screen. If you see this screen, select the configuration that matches your current configuration:. If you currently use Windows Server with full desktop experience, select Datacenter Desktop Experience. Depending on the machine type of your VM instance and your Windows Server configuration, the upgrade might take between 10 and 60 minutes to complete.
During that time, you can observe the status through the serial port output :. Wait until the machine has rebooted four times. Depending on the configuration of your VM instance, it might take 30 minutes or more for these reboots to occur.
You can recognize a reboot by output that looks similar to this:. After the fourth reboot, wait until the output GCEMetadataScripts: Finished running startup scripts or No startup scripts to run appears.
You can now connect to the VM instance to verify that the upgrade has been successfully completed. Restart the VM instance to ensure all changes take effect.
It might take 1 to 2 minutes for the reboot to complete before you can connect to the VM instance again. Connect to the machine by using an RDP client. Use Windows Update to install the latest Windows updates. You might have to restart the VM instance multiple times during this process. If you suspect that the upgrade failed or is not progressing, use the following approaches, in order, to diagnose the situation:.
To check the progress of the upgrade process, view the serial port output of the VM instance:. During the upgrade, you should observe four reboots. If you don't observe any progress for more than 30 minutes after the first reboot, it is likely that the upgrade failed. Go to VM instances. Using the EMS console, check the Windows Setup log files and the event log for indications that the upgrade is still progressing or for information about any errors that might have occurred.
When prompted for credentials, enter the username and password of an administrative user account. Use the remote PowerShell session to check the Windows Setup log files and the event log. If you can't connect to the instance by using Windows Remote Management WinRM , you can cancel the upgrade and analyze the log files from a different VM instance. To do this, follow these steps:.
Stop the VM instance. Detach the boot disk from the instance. Create a new, temporary Windows Server instance, and attach the boot disk of the original instance as an additional disk. Use the temporary Windows Server instance to analyze the setup log and event log files of the instance that you were trying to upgrade. After you have completed the analysis, detach the disk from the temporary instance and reattach it as a boot disk to the original VM instance. For information about troubleshooting your Windows Server instances, see Tips and troubleshooting for Windows instances.
To avoid incurring further costs after you have completed this process, delete the installation disk. You can create an installation disk based on the Google-provided image at any time. If you don't plan to upgrade more VM instances in the same zone, delete the installation disk:. In Cloud Shell, delete the win-installers disk that you created earlier:.
Learn how to bring existing licenses to Compute Engine. Learn how to connect to Windows instances. Learn about sole-tenant nodes on Compute Engine. Work through more Windows tutorials. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.
For details, see the Google Developers Site Policies. For example, it can make installation much slower by scanning every file that is copied locally to your computer. Provide mass storage drivers. If your manufacturer has supplied a separate driver file, save the file to a floppy disk, CD, DVD, or Universal Serial Bus USB flash drive in either the root directory of the media or the amd64 folder.
To provide the driver during Setup, on the disk selection page, click Load Driver or press F6. You can browse to locate the driver or have Setup search the media. Be aware that Windows Firewall is on by default. Server applications that must receive unsolicited inbound connections will fail until you create inbound firewall rules to allow them. Check with your application vendor to determine which ports and protocols are necessary for the application to run correctly.
The table below briefly summarizes supported upgrade paths to Windows Server If you do not see your current version in the left column, upgrading to this release of Windows Server is not supported. If you see more than one edition in the right column, upgrade to either edition from the same starting version is supported.
The course labs consist of configuring three virtual machines to join a Windows Server R2 network, creating Windows Server R2 domain environment and installing and configuring different server roles. Obtaining the Microsoft Server Certification Exam can help you to enhance your career opportunities and also helps to boost your income. Microsoft Server Certification is a highly-sought certification.
Many positions either prefer or require Microsoft Server Certification. You can also see now a day many companies are asking for Microsoft Server Certification in their Job descriptions. An investment in your career is an investment in yourself.
There is no time like the present to take charge of your career. Take your career to the next level by studying for and passing the Microsoft Windows Server Certification exam! Direct Download. The system partition will need extra space for any of the following circumstances: If you install the system over a network. Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.
Ensure that you have updated and digitally signed kernel-mode drivers for Windows Server If you install a Plug and Play device, you may receive a warning if the driver is not digitally signed. If you install an application that contains a driver that is not digitally signed, you will not receive an error during Setup. In both cases, Windows Server will not load the unsigned driver. If you are not sure whether the driver is digitally signed, or if you are unable to boot into your computer after the installation, use the following procedure to disable the driver signature requirement.
This procedure enables your computer to start correctly, and the unsigned driver will load successfully. Before you install Windows Server , follow the steps in this section to prepare for the installation. Disconnect UPS devices.
❿Microsoft Server 2012 R2 – Hands-on Training Part I - Windows server 2012 r2 standard configuration guide free
Он заставил Джаббу вмонтировать в «ТРАНСТЕКСТ» переключатель системы «Сквозь строй», и та отворилась, она его уже достала. Автобус номер 27 следует к хорошо известной конечной остановке. Да взять хотя бы его электронное имя. Они болтали, но немало и плохого.
❿
Comments
Post a Comment