READ Free Dumps For Microsoft- 70-410
| Question ID 8951 | Your network contains an Active Directory domain named contoso.com. The domain contains three servers named Server1, Server2, and Server3.
You create a server group named ServerGroup1.
You discover the error message shown in the following exhibit. (Click the Exhibit button.) You need to ensure that Server2 can be managed remotely by using Server Manager.
What should you do? Exhibit:
|
| Option A | On DC1, run the Enable-PSSessionConfiguration cmdlet.
|
| Option B | On Server2, run the Add-Computer cmdlet.
|
| Option C | On Server2 modify the membership of the Remote Management Users group.
|
| Option D | From Active Directory Users and Computers, add a computer account named Server2, and then restart Server2.
|
| Correct Answer | C |
Explanation This is a security issue. To be able to access Server2 remotely through Server Manager the user need to be a member of the Remote Management Users group. Note: * Name: BUILTIN\Remote Management Users Description: A Builtin Local group. Members of this group can access WMI resources over management protocols (such as WS-Management via the Windows Remote Management service). This applies only to WMI namespaces that grant access to the user. * Enable-ServerManagerStandardUserRemoting Provides one or more standard, non-Administrator users access to event, service, performance counter, and role and feature inventory data for a server that you are managing by using Server Manager. Syntax: Parameter Set: Default Enable-ServerManagerStandardUserRemoting [-User]
[-Force] [-Confirm] [-WhatIf] [ ] Detailed Description Provides one or more standard, non-Administrator users access to event, service, performance counter, and role and feature inventory data for a server that you are managing, either locally or remotely, by using Server Manager. The cmdlet must be run locally on the server that you are managing by using Server Manager. The cmdlet works by performing the following actions: Adds access rights for specified standard users to the root\cimv2 namespace on the local server (for access to role and feature inventory information). Adds specified standard users to required user groups (Remote Management Users, Event Log Readers, and Performance Log Readers) that allow remote access to event and performance counter logs on the managed server. Changes access rights in the Service Control Manager to allow specified standard users remote access to the status of services on the managed server. Incorrect: Not A: the Enable-PSSessionConfiguration.This is an advanced cmdlet that is designed to be used by system administrators to manage customized session configurations for their users. Reference: Enable-ServerManagerStandardUserRemoting
| Question ID 8952 | You have a server named Server1 that runs Windows Server 2012 R2.
You try to install the Microsoft .NET Framework 3.5 Features feature on Server1, but the installation fails repeatedly. You need to ensure that the feature can be installed on Server1.
What should you do?
|
| Option A | Install Windows Identity Foundation (WIF) 3.5.
|
| Option B | Install the Web Server (IIS) server role.
|
| Option C | Connect Server1 to the Internet.
|
| Option D | Run the Add-AppxProvisionedPackage cmdlet.
|
| Correct Answer | C |
Explanation Explanation/Reference: The files needed are no longer available on the local Hard drive. We need to connect the server to the Internet. Important to note that when starting with Windows Server 2012 R2 and Windows 8, the feature files for .NET Framework 3.5 (which includes .NET Framework 2.0 and .NET Framework 3.0) are not available on the local computer by default. The files have been removed. Files for features that have been removed in a Features on Demand configuration, along with feature files for .NET Framework 3.5, are available through Windows Update. By default, if feature files are not available on the destination server that is running Windows Server 2012 R2 Preview or Windows Server 2012 R2, the installation process searches for the missing files by connecting to Windows Update. You can override the default behavior by configuring a Group Policy setting or specifying an alternate source path during installation, whether you are installing by using the Add Roles and Features Wizard GUI or a command line.