ws icfg a04: alt textd2oqb2vjj999su.cloudfront.net/users/000/067/627/...the mcts certification in...

ws_icfg_a04: Alt Text

T3: iSCSI, File and Storage Services, and SMB 3.0

P154

Jacob Moran is a certified Microsoft instructor holding multiple Microsoft certifications including

MCITP in Windows Server 2008 Server Administrator/Active, Enterprise Desktop Support Technician

on Windows 7, SharePoint Server 2010, and SQL Server 2005 Database Administrator. He also holds

the MCTS certification in Windows Server 2008 Application Infrastructure/Network Infrastructure,

Microsoft SQL Server 2008 Implementation and Maintenance/Database Administrator, SQL Server

2005, SharePoint Server 2007/Windows SharePoint Services 3.0, and Windows Vista/Windows 7. In

addition, his certifications include MCSE (2003/2000/NT 4.0), MCSA (2003/2000), MCDST, MCDBA

(2000/7.0), MCT, CCNA, CCSI, and CompTIA A+/Security+/CTT+.

The course goal is to install and configure storage and printing services on Microsoft Windows Server

2012.

P45 (2-40)

Heading: iSCSI Target Server.

The Server Manager window is displayed. At the top of the window, the path Server Manager >

Dashboard is shown. Next to the path are the Manage, Tools, View, and Help menus. The remaining

part of the window is not visible as the Add Roles and Features Wizard is overlapping it.

The Add Roles and Features Wizard indicates that the destination server is EASYNOMAD. The wizard

includes seven pages – Before You Begin, Installation Type, Server Selection, Server Roles, Features,

Confirmation, and Results. In this example, in the wizard, the Server Roles page is open. The page

includes the note "Select one or more roles to install on the selected server." The note is followed by

the Roles section. The section contains many checkboxes. Each checkbox represents a role. Two

checkboxes are visible, File and Storage Services (Installed) and Hyper-V. The File and Storage

Services (Installed) checkbox is shown as selected. It includes two checkboxes, File and iSCSI Services

(Installed) and Storage Services (Installed). Both the checkboxes are shown as selected. The File and

iSCSI Services (Installed) checkbox further includes ten checkboxes – File Server (Installed),

BranchCache for Network Files, Data Deduplication (Installed), DFS Namespaces, DFS Replication,

File Server Resource Manager (Installed), File Server VSS Agent Service, iSCSI Target Server, iSCSI

Target Storage Provider (VDS and VSS), and Server for NFS. The File Server (Installed), Data

Deduplication (Installed), File Server Resource Manager (Installed), and iSCSI Target Server

checkboxes are shown as selected. Next to the Roles section, a description of the selected checkbox

is provided. Presently, the iSCSI Target Server checkbox is shown as selected and its description is as

follows – iSCSI Target Server provides services and management tools for iSCSI targets. In addition,

the wizard includes the Previous, Next, Install, and Cancel buttons.

P130 (2-41)

Heading: Install iSCSI Target Server Feature in PowerShell.

The Administrator: Windows PowerShell console window is displayed. The window includes the note

"Windows PowerShell. Copyright (C) 2012 Microsoft Corporation. All rights reserved." The note is

followed by the output of the add-windowsfeature fs-iscsitarget-server command. The output is

returned as a table of four columns – Success, Restart Needed, Exit Code, and Feature Result. The

table contains one row with the following details: True, No, Success, {iSCSI Target Server}. The

console window also shows the output of the get-windowsfeature fs-iscsitarget-server command.

The output is returned as a table of three columns – Display Name, Name, and Install State. The

table contains one row with the following details: [X] iSCSI Target Server, FS-iSCSITarget-Server,

Installed.

P46 (2-42)

Heading: Unified Remote Management of File and Storage Services.

Unified remote management of File and Storage Services provides a fully scriptable storage

management that can be managed remotely. It uses a single, WMI-based interface. It helps in

managing a large number of storage systems and virtual local storage, which is also known as

Storage Spaces. Storage Management Initiative Specification (SMI-S) allows you to use a single API to

manage different storage types. Storage infrastructure should support a valid version of SMI-S or the

Storage Management Provider interface. Unified remote management of File and Storage Services

provides a number of advantages for enterprise system administrators, and offers comprehensive

scriptable management through PowerShell cmdlets.

The visual shows a PC connected to three servers.

P47 (2-43)

Heading: Windows PowerShell cmdlets for File and Storage Services.

To see a comprehensive list of cmdlets for a specific module, use the Powershell command gcm -

module [ModuleName]. The Miscellaneous table is displayed. The table includes three columns –

Function, ModuleName, and PowerShell Command. It contains eight rows as follows:

Row 1.

Function – Create a new storage pool named "poolname" with 2 disks.

ModuleName – Storage.

PowerShell Command – $pdisks= get-physicaldisk $s=get-storagesubsystem new-storagepool -

friendlyname "poolname" -physicaldisks $pdisks[0] , $pdisks[1] -storagesubsystemfriendlyname

$s.friendlyname.

Row 2.

Function – Format drive F as NTFS with the label "data."


PowerShell Command – format-volume -driveletter f -filesystem ntfs -newfilesystemlabel "data."

Row 3.

Function – Format a ReFS volume and skip confirmation.


PowerShell Command – format-volume -driveletter f -filesystem refs -confirm:$false.

Row 4.

Function – Enable deduplication on a volume.

ModuleName – Deduplication.

PowerShell Command – enable-dedupvolume p:.

Row 5.

Function – Get the specified quota template.

ModuleName – FileServer ResourceManager.

PowerShell Command – $quotatemplate = get-fsrmquotatemplate -name "100 MB Limit."

Row 6.

Function – Start an optimization job.


PowerShell Command – start-dedupjob p: -type optimization.

Row 7.

Function – Map an iSCSI target to a VHD.

ModuleName – iSCSITarget.

PowerShell Command – add-iscsivirtualdisktargetmapping -path "virtualdiskname" -targetname

sqldisks.

Row 8.

Function – Connect to a target.

ModuleName – iSCSI.

PowerShell Command – connect-iscsitarget -nodeaddress $target. nodeaddress.

Next, the Get Display table is displayed. The table includes three columns – Function, ModuleName,

and Powershell Command. It contains twenty two rows as follows:

Row 1.

Function – List all physical disks.


PowerShell Command – get-physicaldisk.

Row 2.

Function – List all physical disks sorted from large to small.


PowerShell Command – get-physicaldisk | sort size -descending.

Row 3.

Function – List all physical disks associated with a pool.


PowerShell Command – get-storagepool -isprimordial $false| get-physicaldisk.

Row 4.

Function – List all storage pools.


PowerShell Command – get-storagepool.

Row 5.

Function – List all disks visible to Windows.


PowerShell Command – get-disk.

Row 6.

Function – Initialize a disk with a GPT partition on a new virtual disk.


Powershell Command – get-virtualdisk -friendlyname "virtualdiskname" | get-disk | initialize-disk -

partitionstyle "gpt."

Row 7.

Function – Create a 100 GB Partition on a virtual disk and assign it drive letter F.


PowerShell Command – get-virtualdisk -friendlyname "virtualdiskname" | get-disk | new-partition -

size 100gb -driveletter f.

Row 8.

Function – Get All SMB shares.

ModuleName – SMBShare.

PowerShell Command – get-smbshare.

Row 9.

Function – Get SMB server configurations.


PowerShell Command – get-smbclientconfiguration.

Row 10.

Function – Get All NFS shares.

ModuleName – NFS.

Powershell Command – get-nfsshare.

Row 11.

Function – Get NFS server configuration.

ModuleName – NFS.

PowerShell Command – get-nfsserverconfig.

Row 12.

Function – Get all Deduplicated volumes.


Powershell Command – get-dedupvolume.

Row 13.

Function – Get volume status.


Powershell Command – get-dedupstatus p:.

Row 14.

Function – Get scheduled jobs.


Powershell Command – get-dedupschedule.

Row 15.

Function – Get all running jobs.


PowerShell Command – get-dedupjob.

Row 16.

Function – Get all iSCSI virtual disks.


Powershell Command – get-iscsivirtualdisk.

Row 17.

Function – Get all iSCSI targets.


PowerShell Command – get-iscsitarget.

Row 18.

Function – Get all logical unit numbers (LUNs).


PowerShell Command – get-iscsiservertarget.

Row 19.

Function – Get the portal object.


PowerShell Command – $portal = get-iscsitargetportal.

Row 20.

Function – Get the current active sessions.


PowerShell Command – get-iscsisession | where isconnected -eq $true.

Row 21.

Function – Get server configurations.

ModuleName – DFSN.

Powershell Command – get-dfsnamespaceserverconfig -namespaceserver \\fs.

Row 22.

Function – Assign cluster disks.

ModuleName – FailoverClusters.

PowerShell Command – get-clusteravailabledisk | add-clusterdisk.

Next, the New Display table is displayed. The table includes three columns – Function, ModuleName,

and Powershell Command. It contains ten rows as follows:

Row 1.

Function – Create a 100 GB virtual disk using type mirror resiliency and thin provisioning.


PowerShell Command – new-virtualdisk -friendlyname "virtualdiskname" -storagepoolfriendlyname

"poolname" -size 100gb -resiliencysettingname "mirror" -provisioningtype thin.

Row 2.

Function – Create the largest possible virtual disk using the parity resiliency type and fixed

provisioning.


PowerShell Command – new-virtualdisk -friendlyname "virtualdiskname" -storagepoolfriendlyname

"poolname" -resiliencysettingname "parity" -usemaximumsize.

Row 3.

Function – Create an SMB share.


PowerShell Command – new-smbshare -name "smbsharename" -path "pathname."

Row 4.

Function – Create an NFS share with krb5 authentication and deny root access.

ModuleName – NFS.

PowerShell Command – new-nfsshare -name "nfssharename" -path "pathname" -authentication

krb5 -allowrootaccess $false.

Row 5.

Function – Create a client group and add member "username."

ModuleName – NFS.

PowerShell Command – new-nfsclientgroup -clientgroupname "cligrpname" -addmember

"username."

Row 6.

Function – Create a quota that applies the specified quota template.

ModuleName – FileServerResourceManager.

PowerShell Command – new-fsrmquota -path "pathname" -template $quotatemplate.name.

Row 7.

Function – Create an iSCSI 800 MB virtual disk.


PowerShell Command – new-iscsivirtualdisk -path "pathname" -size 800mb.

Row 8.

Function – Create an iSCSI target.


PowerShell Command – new-iscsiservertarget -targetname "sqldisks."

Row 9.

Function – Create a cluster.

ModuleName – FailoverClusters.

PowerShell Command – new-cluster -name "clu1" -node "n1","n2."

Row 10.

Function – Create a standalone namespace.

ModuleName – DFSN.

PowerShell Command – new-dfsnamespace -namespaceroottarget \\fsserver - type standalone -

namespaceroot \\fsserver\share1.

Next, the Remove table is displayed. The table includes three columns – Function, ModuleName, and

PowerShell Command. It contains five rows as follows:

Row 1.

Function – Remove an SMB share.


PowerShell Command – remove-smbshare -name "smbsharename."

Row 2.

Function – Remove an NFS share.

ModuleName – NFS.

PowerShell Command – remove-nfsshare -name "nfssharename" v.

Row 3.

Function – Remove an iSCSI virtual disk.


PowerShell Command – remove-iscsivirtualdisk -path "pathname."

Row 4.

Function – Remove a target.


PowerShell Command – remove-iscsiservertarget -targetname "sqldisks."

Row 5.

Function – Delete a virtual disk named "virtualdiskname."


PowerShell Command – remove-virtualdisk -friendlyname "virtualdiskname."

Next, the Set table is displayed. The table includes three columns – Function, ModuleName, and

PowerShell Command. It contains two rows as follows:

Row 1.

Function – Set deduplication volume configuration.


PowerShell Command – set-dedupvolume p: -excludefiletype "txt", "log" -minimumfileagedays 15.

Row 2.

Function – Set Optimization Schedule.


PowerShell Command – set-dedupschedule throughputoptimization-2 -type optimization -start "2:00

am" -days "friday", "saturday."

P48 (2-44)

Heading: SMB 3.0 Protocol.

The visual shows the eight components of an SMB 3 protocol – PowerShell cmdlets, SMB Direct

(SMB over RDMA), SMB Transparent Failover, SMB Multichannel, SMB Scale Out, SMB Encryption,

Performance Counters, and SMB Directory Leasing.

P49 (2-46)

Heading: Windows Offloaded Data Transfer (ODX) Overview.

ODX maximizes network storage services by letting intelligent storage arrays communicate with each

other directly. To give Hyper-V VMs access to ODX arrays, there are several possible approaches. You

can connect a host or VM to the SMB share of a computer hosted on an ODX-capable array. You can

place a VHD on an ODX-capable iSCSI LUN. You can use a VM's iSCSI initiator to manage ODX-capable

iSCSI LUNs. You can use a VM's virtual Fiber Channel adapter to manage ODX-capable Fiber Channel

LUNs. Storage arrays using ODX must meet the five hardware requirements, which are as follows.

Arrays must be certified to work with Windows Offloaded Data Transfer (ODX). When ODX is used

between arrays, the arrays must be from the same hardware vendor. When ODX is used between

arrays, the copy manager for the arrays must support cross-storage array ODX. Arrays must be

connected using iSCSI, Serial Attached SCSI (SAS), Fiber Channel, or Fiber Channel over Ethernet.

Array configurations must be one server with one array, one server with two arrays, two servers

with one array, or two servers with two arrays.

T5: Server Manager Remote Management P57 (2-51)

Heading: Using Server Manager to Manage Remote Servers.

By default, remote management is enabled on servers running Server 2012. Remote servers need to

be added to Server Manager's server pool. Remote servers running Windows Server 2008 and Server

2008 R2 can be managed with Windows Management Framework 3.0, .NET Framework 4.0, and

performance update KB 2682011.

The visual shows a PC, which has Win 8 Client with WRSAT installed. The PC is connected to three

remote servers.

P58 (2-52)

Heading: How to Configure Server Manager Remote Management – GUI?

The Server Manager window is displayed. At the top of the window, the path Server Manager > Local

Server is shown. Next to the path are the Manage, Tools, View, and Help menus. The main area of

the window is split into two parts. The left part includes ten nodes – Dashboard, Local Server, All

Servers, AD DS, DHCP, DNS, File and Storage Services, IIS, NAP, and Print Services. The right part

shows the page of the selected node. In this example, the Local Server node is shown as selected.

This displays its page in the right part. The page includes two sections, Properties for EASYNOMAD

and Events. The Properties for EASYNOMAD section includes a drop-down list, which is set to TASKS.

The drop-down list is followed by an area displaying the following information:

Computer name: EASYNOMAD.

Domain: easynomadtravel.com.

Windows Firewall: Domain: On.

Remote management: Disabled.

Remote Desktop: Disabled.

NIC Teaming: Disabled.

Ethernet: 192.168.2.16, IPv6 enabled.

Operating system version: Microsoft Windows Server 2012 Datacenter.

Hardware information: innotek GmbH VirtualBox.

In the information, the word "Disabled" is hyperlinked for Remote management, Remote Desktop,

and NIC Teaming. In addition to the information mentioned above, the section displays the details of

Last installed updates, Windows Update, Last checked for updates, Windows Error Reporting,

Customer Experience improvement Program, IE Enhanced Security Configuration, Time zone,

Product ID, Processors, Installed memory (RAM), and Total disk space. In this example, these details

are not visible.

The Events section indicates that there are 1261 events in total. The section includes a drop-down

list, which is set to TASKS. The drop-down list is followed by the Filter text field. Next to the text field

are two icons. Each icon includes a down-arrow indicating that it consists of more options. The

section also includes a table of six columns – Server Name, ID, Severity, Source, Log, and Date and

Time. The table contains many rows. Three of them are visible as follows:

Row 1: EASYNOMAD, 8193, Error, VSS, Application, 9/25/2012 12:43:50 PM.

Row 2: EASYNOMAD, 1014, Warning, Microsoft-Windows-DNS Client Events, System, 9/25/2012

12:41:58 PM.

Row 3: EASYNOMAD, 10020, Warning, Microsoft-Windows-DHCP-Server, System, 9/25/2012

12:41:47 PM.

It is indicated that in the Properties for EASYNOMAD section, in the information, clicking the

Disabled link for Remote management displays the Configure Remote Management dialog box.

The Configure Remote Management dialog box includes the Enable remote management of this

server from other computers checkbox. The checkbox is shown as selected. The checkbox is followed

by the note "Enable applications or commands that require Windows Management Instrumentation

(WMI) and Windows PowerShell remote access to manage this server. If you disable remote

management, applications or commands that require WMI or Windows PowerShell remote access

will fail. You might not be able to manage this computer remotely from a different local subnet

because of firewall settings. Local administrator accounts other than the built-in Administrator

account may not have rights to manage this computer remotely, even if remote management is

enabled." The note is followed by a link, which is titled as More information about remote

management, its limitations, and security risks. In addition, the dialog box includes the OK and

Cancel buttons.

P133 (2-53)

Heading: How to Configure Remote Management Using PowerShell?

The Administrator: Windows PowerShell console window is displayed. In the console window, the

Server Configuration page is displayed. The page includes fifteen options – 1) Domain/Workgroup, 2)

Computer Name, 3) Add Local Administrator, 4) Configure Remote Management, 5) Windows

Update Settings, 6) Download and Install Updates, 7) Remote Desktop, 8) Network Settings, 9) Date

and Time, 10) Help improve the product with CEIP, 11) Windows Activation, 12) Log Off User, 13)

Restart Server, 14) Shut Down Server, and 15) Exit to Command Line. It is indicated that the Domain

is easynomadtravel.com, Computer Name is EASYNOMAD_02, Remote Management is Disabled,

Windows Update Settings are Automatic, and Remote Desktop is Enabled ensuring more secure

clients, and Help for improving the product with CEIP is Not participating. The options are followed

by the note "Enter number to select an option:." It is indicated that selecting option 4 displays the

Configure Remote Management page. The page indicates that remote management is currently

disabled. It includes four options – 1) Enable Remote Management, 2) Disable Remote Management,

3) Configure Server Response to Ping, and 4) Return to main menu. The options are followed by the

note "Enter selection:." It is indicated that selecting option 1 displays the note "Enabling Remote

Management." The Configure Remote Management message box is also displayed. The message box

includes the note "Successfully enabled Remote Management." It also includes the OK button.

P59 (2-54)

Heading: WinRM.

The Administrator: Windows PowerShell console window is displayed. The console window includes

the note "Windows PowerShell. Copyright (C) 2012 Microsoft Corporation. All rights reserved." The

note is followed by the output of the winrm command. The output includes the note "Windows

Remote Management Command Line Tool. Windows Remote Management (WinRM) is the

Microsoft implementation of the WS-Management protocol which provides a secure way to

communicate with local and remote computers using web services. Usage: winrm OPERATION

RESOURCE_URI –SWITCH:VALUE [-SWITCH:VALUE] …] [@{KEY=VALUE[;KEY=VALUE]…}]." The note is

followed by two tables, For help on a specific operation and For help on related topics. The For help

on a specific operation table includes two columns. The first column includes ten commands and the

second column includes their functions. The rows are as follows:

Row 1: winrm g[et] -?, Retrieving management information.

Row 2: winrm s[et] -?, Modifying management information.

Row 3: winrm c[reate] -?, Creating new instances of management resources.

Row 4: winrm d[elete] -?, Remove an instance of a management resource.

Row 5: winrm e[numerate] -?, List all instances of a management resource.

Row 6: winrm i[nvoke] -?, Executes a method on a management resource.

Row 7: winrm id[entify] -?, Determines if a WS-Management implementation is running on the

remote machine.

Row 8: winrm quickconfig -?, Configures this machine to accept WS-Management requests from

other machines.

Row 9: winrm configSDDL -?, Modify an existing security descriptor for a URL.

Row 10: winrm helpmsg -?, Displays error message for the error code.

The For help on related topics table includes two columns. The first column includes nine commands

and the second column includes their functions. The rows are as follows:

Row 1: winrm help uris, How to construct resource URIs.

Row 2: winrm help aliases, Abbreviations for URIs.

Row 3: winrm help config, Configuring WinRM client and service settings.

Row 4: winrm help certmapping, Configuring client certificate access.

Row 5: winrm help remoting, How to access remote machines.

Row 6: winrm help auth, Providing credentials for remote access.

Row 7: winrm help input, Providing input to create, set, and invoke.

Row 8: winrm help switches, Other switches such as formatting, options, and more.

Row 9: winrm help proxy, Providing proxy information.

Next, in the Administator: Windows PowerShell console window, the output of the winrm

quickconfig command is shown. The output includes the note "WinRM service is already running on

this virtual machine. WinRM is not set up to allow remote access to this machine for management.

The following changes must be made: Configure service to allow remote requests. Make these

changes [y/n]?" It is indicated that entering "y" displays the note "WinRM has been updated for

remote management. Enabled remote access."

Next, in the Administrator: Windows PowerShell console window, the output of the winrm

enumerate winrm/config/listener command is shown. The output includes the Listener details. The

Listener details include the Hostname and CertificateThumbprint details. The Listener details are as

follows:

Address = *

Transport = HTTP

Port = 5985

The Hostname details are as follows:

Enabled = true

URLPrefix = wsman

The CertificateThumbprint details are as follows:

ListeningOn = 127.0.0.1, 192.168.2.36, ::1, fe80::100:7f:fffe%14, fe80::5efe:192.168.2.36%13,

fe80::4033:2d63:ce4c:6912%12

Next, in the Administrator: Windows PowerShell console window, the output of the winrm get

winrm/config command is shown. The output includes the Config details. The Config details include

the Client, Auth, DefaultPorts, TrustedHosts, and Service details.

The Config details are as follows:

MaxEnvelopeSizekb = 500

MaxTimeouts = 60000

MaxBatchItems = 32000

MaxProviderRequests = 4294967295

The Client details are as follows:

NetworkDelays = 5000

URLPrefix = wsman

AllowUnencrypted = false

The Auth details are as follows:

Basic = true

Digest = true

Kerberos = true

Negotiate = true

Certificate = true

CredSSP = false

The DefaultPorts details are as follows:

HTTP = 5985

HTTPS = 5986

There are no TrustedHosts.

The Service details are as follows:

RootSDDL = 0:NSG:BAD:P>A;;GA;;;BA><A;;GR;;;IU>S:P<AU;FA;GA;;;WD><AU;SA;GXGW;;;WD>

Next, the Local Group Policy Editor window is displayed. The window includes a standard menu bar

with the File, Action, View, and Help menus. The menu bar is followed by a toolbar with eight icons.

The main area of the window is split into two parts. The left part includes twenty seven folders and

the User Configuration node. The folders are as follows: Shutdown Options, Smart Card, Sound

Recorder, Sync your Settings, Tablet PC, Task Scheduler, Windows Calendar, Windows Color System,

Windows Customer Experience Improvement, Windows Defender, Windows Error Reporting,

Windows Installer, Windows Logon Options, Windows Mail, Windows Media Center, Windows

Media Digital Rights Management, Windows Media Player, Windows Messenger, Windows Mobility

Center, Windows PowerShell, Windows Reliability Analysis, Windows Remote Management

(WinRM), Windows Remote Shell, Windows SideShow, Windows System Resource Manager,

Windows Update, and All Settings. The Windows Remote Management (WinRM) folder includes two

folders, WinRM Client and WinRM Service. The User Configuration node includes three folders –

Software Settings, Windows Settings, and Administrative Templates. The right part includes two

tabs, Extended and Standard. In this example, in the left part, the WinRM Service folder is shown as

selected. In the right part, the Extended tab is shown as selected. In the tab, the WinRM Service

page is open. The page includes a table of many columns and two are visible, Setting and State. The

table includes ten rows as follows:

Row 1: Allow remote server management through WinRM, Enabled.

Row 2: Allow Basic authentication, Enabled.

Row 3: Allow CredSSP authentication, Enabled.

Row 4: Allow unencrypted traffic, Disabled.

Row 5: Specify channel binding token hardening level, Enabled.

Row 6: Disallow WinRM from storing RunAs credentials, Enabled.

Row 7: Disallow Kerberos authentication, Disabled.

Row 8: Disallow Negotiate authentication, Disabled.

Row 9: Turn On Compatibility HTTP Listener, Enabled.

Row 10: Turn On Compatibility HTTPS Listener, Enabled.

In this example, Row 1 is shown as selected. The requirements and description for this setting are

displayed as follows:

Requirements: At least Windows Vista.

Description: This policy setting allows you to manage whether the Windows Remote Management

(WinRM) service automatically listens on the network for requests on the HTTP transport over the

default HTTP port. If you enable this policy setting, the WinRM service automatically listens on the

network for requests on the HTTP transport over the default HTTP port. To allow WinRM service to

receive requests over the network, configure the Windows Firewall policy setting with exceptions for

Port 5985 (default port for HTTP). If you disable or do not configure this policy setting, the WinRM

service will not respond to requests from a remote computer, regardless of whether or not any

WinRM listeners are configured.

In addition, the Edit policy setting link is also provided.

T7: Multi-Server Management and Remote Management P69 (2-56)

Heading: Enabling Remote Management on Downlevel Operating Systems.

To manage Windows Server 2003 or Server 2003 SP1, Windows Management Framework must be

installed on Server 2003 computers. Server 2003 computers should be joined to the same domain as

the Server 2012 computer. In PowerShell with administrative privileges, type the Enable-psRemoting

command and press Enter. To manage Windows Server 2008 or Server 2008 R2, .NET Framework 4,

Windows Management Framework 3.0, and Windows performance update KB 2682011 should be

installed on Server 2008 computers. Server 2008 computers should be joined to the same domain as

the Server 2012 computer. In PowerShell with administrative privileges, type the winrm quickconfig

command and press Enter.

P70 (2-58)

Heading: How to Configure Multi-Server Management?

The Server Manager window, which has been explained earlier, is displayed. At the top of the

window, the path Server Manager > All Servers is shown. In the left part of the window, the All

Servers node is shown as selected. This displays its page in the right part. A part of the page is visible.

The page includes two sections, Events and Services. The Events section includes the TASKS drop-

down list. The drop-down list includes the Configure Event Data and Refresh options. The section

indicates that there are nine events in total. It includes the Filter text field and two icons. Each icon

includes a down-arrow indicating that it consists of more options. The section also includes a table of

six columns – Server Name, ID, Severity, Source, Log, and Date and Time. The table contains many

rows and seven are visible as follows:

Row 1: EASYNOMAD_02, 10149, Warning, Microsoft-Windows-Windows Remote Management,

System, 9/27/2012 3:22:46 PM.

Row 2: EASYNOMAD_02, 129, Warning, Microsoft-Windows-Time-Service, System, 9/27/2012

3:20:48 PM.


System, 9/27/2012 3:20:48 PM.


System, 9/27/2012 3:20:36 PM.

Row 5: EASYNOMAD_02, 5719, Error, NETLOGON, System, 9/27/2012 12:55:11 PM.


System, 9/27/2012 12:55:11 PM.

Row 7: EASYNOMAD_02, 6008, Error, EventLog, System, 9/27/2012 12:55:09 PM.

The Services section indicates that there are ninety five services in total. The section includes a drop-

down list, which is set to TASKS. The drop-down list is followed by the Filter text field and two icons.

Each icon includes a down-arrow indicating that it consists of more options. The section also includes

a table of five columns – Server Name, Display Name, Service Name, Status, and Start Type. The

table contains many rows and two are visible as follows:

Row 1: EASYNOMAD_02, WinHTTP Web Proxy Auto-Discovery Service, WinHttpAutoProxySvc,

Running, Manual.

Row 2: EASYNOMAD_02, Hyper-V Data Exchange Service, vmnickvpexchange, Stopped, Manual

(Triggered).

It is indicated that in the Events section, in the TASKS drop-down list, selecting the Configure Event

Data option displays the Configure Event Data dialog box. The Configure Event Data dialog box

includes the note "These settings determine how Server Manager gathers event data from servers in

the server group that you are currently managing. Changes to defaults that significantly increase the

number of events in the Events tile can result in delayed responses from Server Manager." The note

is followed by four checkboxes representing severity levels. The events will be shown with the

selected severity level. The four checkboxes are named as Critical, Error, Warning, and

Informational. In this example, the Critical, Error, and Warning checkboxes are shown as selected.

The checkboxes are followed by two drop-down lists, Get events that have occurred within the past

and Get events from the following event log files. The drop-down lists are set to 24 hours and

Multiple, respectively. In addition, the dialog box includes the OK and Cancel buttons.

P136 (2-59)


The Server Manager window, which has been explained earlier, is displayed. In the left part of the

window, the Local Server node is shown as selected. This displays its page in the right part. The page

has been explained earlier. The System Properties dialog box is overlapping the window. The System

Properties dialog box includes four tabs – Computer Name, Hardware, Advanced, and Remote. The

Remote tab is shown as selected. The tab is split into two sections, Remote Assistance and Remote

Desktop. The Remote Assistance section includes the Allow Remote Assistance connections to this

computer checkbox and the Advanced button. The checkbox is not selected and the section is

grayed out. The Remote Desktop section includes the note "Choose an option, and then specify who

can connect." The note is followed by two radio buttons, Don’t allow remote connections to this

computer and Allow remote connections to this computer. The Allow remote connections to this

computer radio button is shown as selected. The radio button includes a checkbox, which is titled as

"Allow connections only from computers running Remote Desktop with Network Level

Authentication (recommended)." The checkbox is shown as selected. The section also includes the

Help me choose link and the Select Users button. In addition, the dialog box includes the OK, Cancel,

and Apply buttons.

P137 (2-60)

Heading: How to Configure Multi-Server Management in the Command Line?

The Administrator: C:\Windows\system32\cmd.exe - sconfig console window is displayed. In the

console window, the Server Configuration page is open. The page has been explained earlier. In the

page, it is indicated that selecting option 7 displays the note "(E)nable or (D)isable Remote Desktop?

(Blank=Cancel)." It is indicated that selecting "e" for enabling remote desktop displays two options.

The first option is 1) Allow only clients running Remote Desktop with Network Level Authentication

(more secure). The second option is 2) Allow clients running any version of Remote Desktop (less

secure). The options are followed by the note "Enter selection:." It is indicated that selecting option

1 displays the note "Enabling Remote Desktop." The Remote Desktop message box is also displayed.

The message box includes the message "Remote Desktop enabled for clients only running Remote

Desktop with Network Level Authentication (more secure)." It also includes the OK button.

P138 (2-61)



window, the Dashboard node is shown as selected. This displays its page in the right part. The page

is not visible as the Add Servers dialog box is overlapping it. The Add Servers dialog box includes

three tabs – Active Directory, DNS, and Import. The Active Directory tab is shown as selected. The

tab is split into two parts. The left part includes the Location and Name (CN) text fields, and the

Operating System drop-down list. The Name (CN) text field includes the Find Now button. In this

example, the Location text field contains easynomadtravel. The Name (CN) text field is blank and

prompts you to enter a name or the beginning of a name. The Operating System drop-down list is

set to All. The left part also includes a table of two columns, Name and Operating System. The table

contains three rows as follows:

Row 1: EASYNOMAD, Windows Server 2012 Datacenter.

Row 2: WINDOWS-8, Windows 8 Pro.

Row 3: EASYNOMAD_02, Windows Server 2012 Datacenter.

The table is followed by the note "3 Computer(s) found."

The right part includes the Selected table. The table includes the Computer column. The table

contains no data and is followed by the note "0 Computer(s) found." It is indicated that in the left

part of the window, in the table, selecting Row 3 adds an additional row to the same table. The row

details are as follows: EASYNOMAD_03, Windows Server 2003 Datacenter. This row is shown as

selected. In the right part of the tab, in the Selected table, the EASYNOMADTRAVEL.COM node is

shown. The node includes the EASYNOMAD_03 subnode. In addition, the dialog box includes the OK

and Cancel buttons. The OK button is grayed out.

P71 (2-62)

Heading: Day-to-Day Management Tasks Using Server Manager 2012.


window, the All Servers node is shown as selected. This displays its page in the right part. A part of

the page has been explained earlier. In addition to that, the page includes the Servers section. The

section indicates that there are 3 servers in total. It includes a drop-down list, which is set to TASKS.

The drop-down list is followed by the Filter text field and two icons. Each icon includes a down-arrow

indicating that it consists of more options. The section also includes a table of five columns – Server

Name, IPv4 Address, Manageability, Last Update, and Windows Activation. The table contains three

rows as follows:

Row 1: EASYNOMAD, 192.168.2.16, Online, 9/26/2012 2:38:52 PM, 00184-70310-08597-AA677

(Activated).

Row 2: EASYNOMAD_02, 192.168.2.36, Online, not visible, not visible.

Row 3: WINDOWS-8, blank, Target computer not accessible, not visible, not visible.

In this example, Row 2 is shown as right-clicked. This displays the context menu with eleven options

– Add Roles and Features, Restart Server, Computer Management, Remote Desktop Connection,

Windows PowerShell, Configure NIC Teaming, Configure Windows Automatic Feedback, Manage As,

Remove Server, Refresh, and Copy. The Add Roles and Features option is shown as selected.

P72 (2-63)

Heading: How to Configure Server Core for Remote Management?

The Administrator: Windows PowerShell console window is displayed. The console window shows

the output of the get-command –module netsecurity command. The output is returned as a table of

three columns – CommandType, Name, and ModuleName. The table contains many rows and forty

eight are visible as follows:

Row 1: Function, Copy-NetFirewallRule, netsecurity.

Row 2: Function, Copy-NetIPsecMainModeCryptoSet, netsecurity.

Row 3: Function, Copy-NetIPsecMainModeRule, netsecurity.

Row 4: Function, Copy-NetIPsecPhase1AuthSet, netsecurity.

Row 5: Function, Copy-NetIPsecPhase2AuthSet, netsecurity.

Row 6: Function, Copy-NetIPsecQuickModeCryptoSet, netsecurity.

Row 7: Function, Copy-NetIPsecRule, netsecurity.

Row 8: Function, Disable-NetFirewallRule, netsecurity.

Row 9: Function, Disable-NetIPsecMainModeRule, netsecurity.

Row 10: Function, Disable-NetIPsecRule, netsecurity.

Row 11: Function, Enable-NetFirewallRule, netsecurity.

Row 12: Function, Enable-NetIPsecMainModeRule, netsecurity.

Row 13: Function, Enable-NetIPsecRule, netsecurity.

Row 14: Function, Get-NetFirewallAddressFilter, netsecurity.

Row 15: Function, Get-NetFirewallApplicationFilter, netsecurity.

Row 16: Function, Get-NetFirewallInterfaceFilter, netsecurity.

Row 17: Function, Get-NetFirewallInterfaceTypeFilter, netsecurity.

Row 18: Function, Get-NetFirewallPortFilter, netsecurity.

Row 19: Function, Get-NetFirewallProfile, netsecurity.

Row 20: Function, Get-NetFirewallRule, netsecurity.

Row 21: Function, Get-NetFirewallSecurityFilter, netsecurity.

Row 22: Function, Get-NetFirewallServiceFilter, netsecurity.

Row 23: Function, Get-NetFirewallSetting, netsecurity.

Row 24: Function, Get-NetIPsecDospSetting, netsecurity.

Row 25: Function, Get-NetIPsecMainModuleCryptoSet, netsecurity.

Row 26: Function, Get-NetIPsecMainModuleRule, netsecurity.

Row 27: Function, Get-NetIPsecMainModeSA, netsecurity.

Row 28: Function, Get-NetIPsecPhase1AuthSet, netsecurity.

Row 29: Function, Get-NetIPsecPhase2AuthSet, netsecurity.

Row 30: Function, Get-NetIPsecQuickModeCryptoSet, netsecurity.

Row 31: Function, Get-NetIPsecQuickModeSA, netsecurity.

Row 32: Function, Get-NetIPsecRule, netsecurity.

Row 33: Function, New-NetFirewallRule, netsecurity.

Row 34: Function, New-NetIPsecDospSetting, netsecurity.

Row 35: Function, New-NetIPsecMainModeCryptoSet, netsecurity.

Row 36: Function, New-NetIPsecMainModeRule, netsecurity.

Row 37: Function, New-NetIPsecPhase1AuthSet, netsecurity.

Row 38: Function, New-NetIPsecPhase2AuthSet, netsecurity.

Row 39: Function, New-NetIPsecQuickModeCryptoSet, netsecurity.

Row 40: Function, New-NetIPsecRule, netsecurity.

Row 41: Function, Open-NetGPO, netsecurity.

Row 42: Function, Remove-NetFirewallRule, netsecurity.

Row 43: Function, Remove-NetIPsecDospSetting, netsecurity.

Row 44: Function, Remove-NetIPsecMainModeCryptoSet, netsecurity.

Row 45: Function, Remove-NetIPsecMainModeRule, netsecurity.

Row 46: Function, Remove-NetIPsecMainModeSA, netsecurity.

Row 47: Function, Remove-NetIPsecPhase1AuthSet, netsecurity.

Row 48: Function, Remove-NetIPsecPhase2AuthSet, netsecurity.

P73 (2-64)

Heading: How to Configure Windows Firewall Exceptions for Remote Management?

A page is displayed. The page is split into two parts. The left part is titled as Apps Results for

*firewall*. It includes the Windows Firewall with Advanced button. The right part is titled as Search.

It includes a search field, which contains firewall. The search field is followed by four options – Apps,

Settings, Files, and Internet Explorer. It is indicated that clicking the Windows Firewall with Advanced

button displays the Windows Firewall with Advanced Security window. The window includes a

standard menu bar with the File, Action, View, and Help menus. The menu bar is followed by a

toolbar with seven icons. The main area of the window is split into three parts. The first part includes

the Windows Firewall with Advanced Security node. The node includes four subnodes – Inbound

Rules, Outbound Rules, Connection Security Rules, and Monitoring. The second part shows the page

of the selected node. The third part is titled as Actions. In this example, in the first part, the Inbound

Rules subnode is shown as selected. This displays its page in the second part. The page lists the

details of many inbound rules in a tabular format. The table includes four columns – Name, Group,

Profile, and Enabled. Out of many rows, the details of six are as follows:

Row 1: Performance Logs and Alerts (DCOM-In), Performance Logs and Alerts, Domain, No.

Row 2: Remote Event Log Management (NIP-In), Remote Event Log Management, All, Yes.

Row 3: Remote Event Log Management (RPC), Remote Event Log Management, All, Yes.

Row 4: Remote Event Log Management (RPC-EPMAP), Remote Event Log Management, All, Yes.

Row 5: Remote File Server Resource Manager Management (RPC), Remote File Server Resource

Manager Management, All, No.

Row 6: Remote Scheduled Tasks Management (RPC), Remote Scheduled Tasks Management, All, No.

In this example, row 2, row 3, and row 4 are shown as selected. The third part of the window

includes two collapsible sections, Inbound Rules and Selected Items. The Inbound Rules collapsible

section contains eight options – New Rule, Filter by Profile, Filer by State, Filter by Group, View,

Refresh, Export List, and Help. The Filter by Profile, Filer by State, Filter by Group, and View options

include a right-arrow indicating that they consist of more options. The Selected Items collapsible

section contains five options – Disable Rule, Cut, Copy, Delete, and Help.

P 139 (2-65)


The Windows Firewall with Advanced Security window is open as explained earlier. In the second

part of the window, an additional column of the table is visible – Action. The details for row 2 are

different from the one mentioned earlier. The details are as follows: Remote Event Log Management

(NIP-in), Remote Event Log Management, All, No, Allow.

P140 (2-66)


The Administrator: Windows PowerShell console window is displayed. In the window, the output of

the get-netfirewallrule | select displaygroup -unique | sort displaygroup command is shown. The

output is returned as follows:

displaygroup

BranchCache – Content Retrieval <Uses HTTP>

BranchCache – Hosted Cache Client <Uses HTTPS>

BranchCache – Hosted Cache Server <Uses HTTPS>

BranchCache – Peer Discovery <Uses WSD>

Core Networking

Distributed Transaction Coordinator

File and Printer Sharing

File and Printer Sharing over SMBDirect

iSCSI Service

Key Management Service

Netlogon Service

Network Discovery

Performance Logs and Alerts

Remote Desktop

Remote Event Log Management

Remote Scheduling Tasks Management

Remote Service Management

Remote Shutdown

Remote Volume Management

Routing and Remote Access

SNMP Trap

TPM Virtual Smart Card Management

Virtual Machine Monitoring

Windows Firewall Remote Management

Windows Management Instrumentation (WMI)

Windows Remote Management

Windows Remote Management (Compatibility)

Next, in the Administrator: Windows PowerShell console window, the output of the get-

netfirewallrule | where ($_.displaygroup –eq "Remote Shutdown") command is shown.

The output returns the following details:

Name: Wininit-Shutdown-In-Rule-TCP-RPC

DisplayName: Inbound Rule for Remote Shutdown (TCP-In)

Description: Inbound rule for the Remote Shutdown via dynamic RPC/TCP

DisplayGroup: Remote Shutdown

Group: @firewallapi.dll,-36751

Enabled: False

Profile: Any

Platform: ()

Direction: Inbound

Action: Allow

EdgeTraversalPolicy: Block

LooseSourceMapping: False

LocalOnlyMapping: False

Owner: blank

PrimaryStatus: OK

Status: The rule was parsed successfully from the store. (65536)

EnforcementStatus: NotApplicable

PolicyStoreSource: PersistentStore

PolicyStoreSourceType: Local

Name: Wininit-Shutdown-In-Rule-TCP-RPC-EPMapper

DisplayName: Inbound Rule for Remote Shutdown (RPC-EP-In)

Description: Inbound rule for the RPCSS service to allow RPC/TCP traffic

DisplayGroup: Remote Shutdown

Group: @firewallapi.dll,-36751

Enabled: False

Profile: Any

Platform: ()

Direction: inbound

Action: Allow

EdgeTraversalPolicy: Block

LooseSourceMapping: False

LocalOnlyMapping: False

Owner:

PrimaryStatus: OK

Status: The rule was parsed successfully from the store. (65536)

EnforcementStatus: NotApplicable

PolicyStoreSource: PersistentStore

PolicyStoreSourceType: Local

Next, in the Administrator: Windows PowerShell console window, the following command is shown:

enable-netfirewallrule -name Wininit-Shutdown-In-Rule-TCP-RPC

T9: Print and Document Services P85 (2-70)

Heading: Print and Document Services Overview.

Five new features of Print and Document Services are listed – Type 4 (v4) Drivers, Branch Office

Direct Printing, Print Management Windows PowerShell Module, WSD Secure Printing, and OpenXPS

Support.

P141 (2-71)

Heading: Print and Document Services Overview.

Four roles are listed – Print Server, Distributed Scan Server, Internet Printing, and LPD (Deprecated).

Print Server – Administrators can use Print Server to monitor queues and receive notifications if a

print queue halts. Using Group Policy, administrators can also migrate Print Servers and deploy

printers. This role includes the Print Management snap-in, which can be used to manage print

servers and network printers as well as migrate printers between servers.

Distributed Scan Server – With Distributed Scan Server, users can scan documents using network

scanners and send the scanned documents to specific destinations, while administrators can

configure network scanners with the Scan Management snap-in.

Internet Printing – Internet Printing lets users manage their print jobs through a web site, and lets

users connect and print to network printers, if they have the Internet Printing Client installed.

LPD (Deprecated) –The Line Printer Daemon (LPD) service (deprecated) allows computers using

operating systems that support Line Printer Remote (LPR) printing to print Server 2012 print servers.

It is an additional role that can be installed by administrators using UNIX or other systems that

support LPR. Note, however, that LPD has been deprecated and may not be supported by future

versions of Windows Server.

P86 (2-72)

Heading: How to Install Print and Document Services?

The Server Manager window is displayed. The window is not completely visible as the Add Roles and

Features Wizard is overlapping it.

The Add Roles and Features Wizard has been explained earlier. In this example, in the wizard, the

Server Roles page is open. The page has been explained earlier. In addition to the checkboxes

mentioned earlier in the Roles section, four more checkboxes are visible – Network Policy and

Access Services (Installed), Print and Document Services (Installed), Remote Access, and Remote

Desktop Services. The Network Policy and Access Services (Installed) and Print and Document

Services (Installed) checkboxes are shown as selected, but are grayed out. The Print and Document

Services (Installed) checkbox includes four checkboxes – Print Server (Installed), Distributed Scan

Server, Internet Printing, and LPD Service. The Print Server (Installed) and Distributed Scan Server

checkboxes are shown as selected. The Print Server (Installed) checkbox is grayed out. The

description for the Distributed Scan Server role is given as follows – "Distributed Scan Server

provides the service which receives scanned documents from network scanners and routes them to

the correct destinations. It also includes the Scan Management snap-in, which you can use to

manage network scanners and configure scan processes." It is indicated that clicking the Next button

of the wizard displays the Add Roles and Features Wizard dialog box.

The Add Roles and Features Wizard dialog box allows you to add features that are required for

Internet Printing. The dialog box includes the note "You cannot install Internet Printing unless the

following role services or features are also installed." The note is followed by an area including two

nodes, .NET Framework 4.5 Features and Web Server (IIS). The .NET Framework 4.5 Features node

includes the ASP.NET 4.5 subnode. The Web Server (IIS) node includes Web Server subnode. The

Web Server subnode includes the Common HTTP Features subnode. The Common HTTP Features

subnode further includes many subnodes and four are visible – Default Document, Directory

Browsing, HTTP Errors, and HTTP Redirection. The area is followed by the Include management tools

(if applicable) checkbox. The checkbox is shown as selected. In addition, the dialog box includes the

Add Features and Cancel buttons. It is indicated that clicking the Add Features button displays the

Add Roles and Features Wizard. The wizard has been explained earlier. In the wizard, the

Confirmation page is open. The page allows you to confirm installation selections. It includes the

note "To install the following roles, role services, or features on selected server, click install." The

note is followed by the Restart the destination server automatically if required checkbox. The

checkbox is shown as selected. Below the checkbox is another note "Optional features (such as

administration tools) might be displayed on this page because they have been selected

automatically. If you do not want to install these optional features, click Previous to clear their

checkboxes." The note is followed by an area displaying the selected features. Below the area are

two links, Export configuration settings and Specify an alternate source path. It is indicated that

clicking the Install button of the wizard displays the next page – Results. The Results page allows you

to view the installation progress. In this page, the Install button of the wizard is replaced by the

Close button. The page includes a bar indicating the installation progress. In this example, the bar is

complete and is followed by the note "Configuration required. Installation succeeded on

EASYNOMAD.easynomadtravel.com." Below the note is an area displaying the installed features. In

the area, it is indicated that a post-install task is available for the Distributed Scan Server role

service. The Perform additional configuration link is provided for the same. The area is followed by

the note "You can close this wizard without interrupting running tasks. View task progress or open

this page again by clicking Notifications in the command bar, and then Task Details." Below the note

is the Export configuration settings link.

P 142 (2-73)

Heading: How to Install Print and Document Services with PowerShell?


output of the powershell command is shown. The output is returned as the note "Windows

PowerShell. Copyright (C) 2012 Microsoft Corporation. All rights reserved." It is indicated that the

ipmo servermanager and add-windowsfeature print-server commands are also run. The output is

returned as a table of four columns – Success, Restart Needed, Exit Code, and Feature Result. The

table contains one row with the following details: True, No, Success, (Print Server, Print and

Document Services…

P87 (2-74)

Heading: How to Configure Print and Document Services?



has been explained earlier. The Tools menu is shown as selected, which displays twenty nine options

– Active Directory Administrative Center, Active Directory Domains and Trusts, Active Directory

Module for Windows PowerShell, Active Directory Sites and Services, Active Directory Users and

Computers, ADSI Edit, Component Services, Computer Management, Defragment and Optimize

Drives, DFS Management, DHCP, DNS, Event Viewer, File Server Resource Manager, Group Policy

Management, Health Registration Authority, Internet Information Services (IIS) 6.0 Manager,

Internet Information Services (IIS) Manager, iSCSI Initiator, Local Security Policy, Network Policy

Server, ODBC Data Sources (32-bit), ODBC Data Sources (64-bit), Performance Monitor, Print

Management, Resource Monitor, Scan Management, Security Configuration Wizard, and Services. It

is indicated that selecting the Print Management option displays the Print Management window.

The Print Management window includes a standard menu bar with the File, Action, View, and Help

menus. The menu bar is followed by a toolbar with many icons. The main area of the window is split

into three parts. The first part includes the Print Management node. The node includes three

subnodes – Custom Filters, Print Servers, and Deployed Printers. The Custom Filter subnode includes

four subnodes – All Printers, All Drivers, Printers Not Ready, and Printers With Jobs. The Print Servers

subnode includes the EASYNOMAD (local) subnode. The EASYNOMAD (local) subnode further

includes four subnodes – Drivers, Forms, Ports, and Printers. The second part displays the page of

the selected node. The third part is titled as Actions. In this example, in the first part, the Drivers

subnode is shown as selected. This displays its page in the second part. The page includes a table of

many columns. Four columns are visible – Driver Name, Environment, Driver Version, and Driver

Isolation. The table contains three rows as follows:

Row 1: Microsoft enhanced Point and…, Windows x64, 6.2.9200.16384, None.

Row 2: Microsoft enhanced Point and…, Windows NT x86, 6.2.9200.16384, None.

Row 3: Microsoft XPS Document Write…, Windows x64, 6.2.9200.16384, None.

The third part – Actions – includes the Drivers collapsible section. The collapsible section includes

the More Actions option. The More Actions option includes a right-arrow indicating that it consists

of more options. It is indicated that in the second part, right-clicking the empty area displays a

shortcut menu with eight options – Add Driver, Manage Drivers, Refresh, Export List, View, Arrange

Icons, Line up Icons, and Help. The Add Driver option is shown as selected.

P88 (2-75)

Heading: Add a Print Driver in PowerShell.


following command is shown:

add-printerdriver –name "Lexmark Pro910 Series Class Driver"

P89 (2-76)

Heading: PowerShell cmdlets for Printer Management.

A table of two columns – PowerShell cmdlet and Function – is displayed. The table contains twenty

rows as follows:

Row 1: add-printer, Adds a printer.

Row 2: add-printerdriver, Installs a printer driver.

Row 3: add-printerport, Installs a printer port.

Row 4: get-printconfiguration, Gets a printer’s configuration information.

Row 5: get-printer, Gets a list of installed printers.

Row 6: get-printerdriver, Gets the list of installed printer drivers.

Row 7: get-printerport, Gets a list of installed printer ports.

Row 8: get-printerproperty, Gets a printer’s properties.

Row 9: get-printjob, Gets a printer’s list of print jobs.

Row 10: remove-printer, Removes a printer.

Row 11: remove-printerdriver, Deletes a printer driver.

Row 12: remove-printerport, Removes a specified printer port.

Row 13: remove-printjob, Removes a print job.

Row 14: rename-printer, Renames a printer.

Row 15: restart-printjob, Restarts a print job.

Row 16: resume-printjob, Resumes a suspended print job.

Row 17: set-printconfiguration, Sets a printer’s configuration information.

Row 18: set-printer, Updates a printer’s configuration.

Row19: set-printerproperty, Modifies a printer’s properties.

Row 20: suspend-printjob, Suspends a print job.

T11: Branch Office Direct Printing and Printer Sharing P96 (2-77)

Heading: Branch Office Direct Printing Overview.

Five features of Branch Office Direct Printing are listed. Branch Office Direct Printing lets clients print

directly to devices. It reduces WAN traffic and server workloads. Clients can print even if the server is

down. It is transparent to end users. It can be configured via Print Management console or

PowerShell.

The visual shows two buildings, Branch Office and Headquarters, connected to each other. Branch

Office includes a PC and Headquarters includes a print device. It is indicated that a file from the PC in

Branch Office is sent to the print device in Headquarters. The print device in Headquarters prints the

file.

P143 (2-78)

Heading: How to Configure Branch Office Direct Printing?

The Print Management window, which has been explained earlier, is displayed. In the first part of

the window, the Printers subnode is shown as selected. This displays its page in the second part. The

page includes a table of five columns – Printer Name, Queue Status, Jobs In…, Server Name, and

Driver Name. The table contains two rows. Only the first row is visible as follows: Lexmark Pro910

Series Class Driver, Ready, 0, EASYNOMAD (…, Lexmark Pro910… The row is shown as right-clicked.

This displays a shortcut menu with twelve options – Open Printer Queue, Pause Printing, Remove

from Directory, Deploy with Group Policy, Set Printing Defaults, Manage Sharing, Print Test Page,

Enable Branch Office Direct Printing, Properties, Delete, Rename, and Help. The Enable Branch Office

Direct Printing option is shown as selected. The third part of the window includes two collapsible

sections, Printers and Lexmark Pro910 Series Class Driver. Both the collapsible sections include the

More Actions option. The option includes a right-arrow indicating that it consists of more options.

P97 (2-79)

Heading: V4 Print Class Drivers.

Three features of V4 drivers are listed – enhanced Point and Print sharing, no need to install cross-

platform drivers, and Print Servers no longer driver distribution points.

The visual shows a WSUS server and three client machines. It is indicated that three V4 drivers are

sent from the WSUS server to the client machines. Each client machine installs a V4 driver.

P98 (2-80)

Heading: Driver Isolation.

Driver isolation keeps badly-behaved print drivers from crashing apps. Driver isolation is activated if

enabled by an administrator, if enabled in Group Policy, or if the INF file includes the value

DriverIsolation=2.

The visual shows three PCs connected to a server. The server includes four sandboxes – XP Printer

Driver for LEX, Vista Printer Driver for LEX, 7 Printer Driver for LEX, and 8 Printer Driver for LEX. The

sandboxes are connected to a print spooler. The print spooler is connected to a print device. It is

indicated that the PCs send some data to the server. The server sends that data to their respective

sandbox. The sandboxes send that data to the print spooler. If driver isolation is not activated, the

print spooler crashes. If it is activated, the print spooler sends that data to the print device.

P144 (2-81)

Heading: Configure Driver Isolation.


the window, the Drivers subnode is shown as selected. This displays its page in the second part. The

page has been explained earlier. In the table, row 1 is shown as right-clicked. This displays a shortcut

menu with five options – Remove Driver Package, Set Driver Isolation, Properties, Delete, and Help.

The Set Driver Isolation option is shown as selected. This option includes four suboptions – None,

Shared, Isolated, and System Default (None). The System Default (None) suboption is shown as

selected.

P145 (2-82)

Heading: Driver Isolation Settings in Group Policy.

The Local Group Policy Editor window, which has been explained earlier, is displayed. In this

example, in the left part, the Local Computer Policy node is shown. The node includes two subnodes,

Computer Configuration and User Configuration. The Computer Configuration node includes three

folders – Software Settings, Windows Settings, and Administrative Templates. The Administrative

Templates folder includes six subfolders – Control Panel, Network, Printers, System, Windows…, and

All Settings. The User Configuration subnode includes three folders – Software Settings, Windows

Settings, and Administrative Templates. In this example, in the Computer Configuration node, the

Printers subfolder is shown as selected. In the right part of the window, the Extended tab is shown

as selected. In the tab, the Printers page is open. The page includes a table of many columns. Only

one column is visible, Setting. The table contains many rows. Six of them are as follows:

Row 1: Activate Internet printing.

Row 2: Isolate print drivers from applications.

Row 3: Custom support URL in the Printers folder’s left pane.

Row 4: Extend Point to Print connection to search Windows Update.

Row 5: Add Printer wizard – Network scan page (Managed network).

Row 6: Always render print jobs on the server.

Row 2 is shown as selected and its details are provided next to the table as follows:

Requirements: At least Windows Server 2012, Windows 8, or Windows RT.

Description: Determines if print driver components are isolated from applications instead of

normally loading them into applications. Isolating print drivers greatly reduces the risk of a print

driver failure causing an application crash. Not all applications support driver isolation.

The Edit policy setting link is also provided.

P99 (2-83)

Heading: V4 Driver Design.

V4 drivers support print sharing, ARM, Windows Store apps, and simplified driver development.

Print sharing – V4 printer drivers provide better support for clients (Windows Vista and up) by

reducing administrative overhead and the need for multiple architecture drivers.

ARM – While V3 printer drivers aren’t supported by Windows running on ARM processors, V4 printer

drivers offer print class drivers that run seamlessly.

Windows Store apps – V4 printer drivers take advantage of common user interface functionality

found in the new Windows Store application model, providing a consistent and predictable

experience.

Simplified driver development – V4 drivers support all the features found in V3 and XPSDrv driver

models and can be easily developed using templates in Visual Studio.

P100 (2-84)

Heading: Printer Sharing Overview.

Four features of printer sharing are listed – server provides clients with printer information, Point

and Print to send jobs, V3 drivers still usable, and device-specific V4 drivers from OEMs.

The visual shows three PCs connected to a server. Next to the server is a print device. It is indicated

that the three PCs are sending data to the server.

P101 (2-85)

Heading: Major Changes to the Print Sharing Architecture.

Four major changes to the print sharing architecture are listed – V4 drivers, Point and Print

compatibility driver, Vista and Windows 7 clients will see V4 drivers as enhanced Point and Print, and

clients don’t need to connect to server to print.

T13: Migrating Print Service to Windows Server 2012 P111 (2-86)

Heading: Enhanced Point and Print.

Vista and Windows 7 clients can print to V4 shares without the need for additional software.

Windows 8 clients will try to install a V4 driver. Client installation is performed the first time it

connects to the server. Print jobs are rendered locally.

P112 (2-87)

Heading: Migrating Print Services to Windows Server 2012 Overview.

Printer Migration Wizard migrates print queues, security settings for the installed printer, settings

for shared printers, and printer drivers used by the print spooler. The migration from x86 to x64

requires an x64 driver.

The visual shows two servers with a print device each. The first server can have Windows Server

2003, Windows Server 2003 R2, Windows Server 2008, or Windows Server 2008 R2 installed. The

second server has Windows Server 2012 installed. It is indicated that the first server is sending print

queues, ACL’s (security settings), share settings, and printer drivers to the second server.

P146 (2-88)

Heading: How to Migrate Print Services to Windows Server 2012?

A page is displayed. The page is split into two parts. The left part is titled as Apps Results for

"printmanagement.msc." It includes the printmanagement button. The right part is titled as Search

Apps. It includes a search field, which contains printmanagement.msc. The search field is followed by

many options. Ten of them are visible – Apps, Settings, Files, Bing, Finance, Games, Internet

Explorer, Mail, Maps, and Music.

P147 (2-89)



the window, the Print Management node is shown as right-clicked. This displays a shortcut menu

with three options – Add/Remove Servers, Migrate Printers, and Help. It is indicated that selecting

the Migrate Printers option displays the Printer Migration Wizard.

In the Printer Migration Wizard, the Getting started with Printer Migration page is open. The page

includes two radio buttons. The first radio button is named as Export printer queues and printer

drivers to a file. It includes the note "This option exports printer queues, printer ports, and printer

drivers to a file you specify." The second radio button is named as Import printer queues and printer

drivers from a file. It includes the note "This option imports printer queues, printer ports, and printer

drivers to a file you specify." The first radio button is shown as selected. The wizard also includes the

Back, Next, and Cancel buttons. It is indicated that clicking the Next button displays the next page of

the wizard – Select a print server. The page includes two radio buttons, This print server

(\\EASYNOMAD) and A print server on the network. The A print server on the network radio button

includes the Server name text field. The This print server (\\EASYNOMAD) radio button is shown as

selected. It is indicated that clicking the Next button displays the next page of the wizard – Review

the list of items to be exported. The page includes the note "The following objects will be exported

to the file." The note is followed by an area listing the objects, which will be exported. The objects

include print queues, printer drivers, and printer ports. It is indicated that clicking the Next button

displays the next page of the wizard – Exporting. The page includes a bar indicating the export

progress. In this example, the bar is complete and is followed by the note "The operation completed

with no errors." Below the note is the Open Event Viewer button. In this page, the Next button of

the wizard is replaced by the Finish button.

P149 (2-91)




has been explained earlier. In the page, in the Services section, the table now includes five columns –

Server Name, Display Name, Service Name, Status, and Start Type. It contains many rows and the

first row is shown as right-clicked. The row details are as follows: EASYNOMAD, Print Spooler,

Spooler, Running, Automatic. The shortcut menu includes six options – Start Services, Stop Services,

Restart Services, Pause Services, Resume Services, and Copy. It is indicated that selecting the Stop

Services option displays the Print Management window, which has been explained earlier. In the

first part of the Print Management window, the Print Management node is shown as right-clicked

and the shortcut menu is displayed. The shortcut menu includes three options, which have been

mentioned earlier. It is indicated that selecting the Migrate Printers option displays the Printer

Migration Wizard. The wizard has been explained earlier. In the wizard, the Getting started with

Printer Migration page is open. The page has been explained earlier. In the page, the Import print

queues and printer drivers from a file radio button is shown as selected. It is indicated that clicking

the Next button displays the next page of the wizard – Select the file location. The page includes the

note "Select the file that contains the printer data to import." The note is followed by a text field,

which contains the path C:\printer_backup.printerExport. Next to the text field is the Browse button.

It is indicated that clicking the Next button displays the next page of the wizard – Select a print

server. The page has been explained earlier. In the page, the This print server (\\EASYNOMAD) radio

button is shown as selected. It is indicated that clicking the Next button displays the next page of the

wizard – Select import options. The page includes the Import mode drop-down list, which is set to

Keep existing printers. The drop-down list is followed by the note "If the printer information file

contains a printer that is already installed on the print server, the printer will not be restored. The

existing printer on the server will not be changed." Below the note is the List in the directory drop-

down list, which is set to List printers that were previously listed. The page also includes the Convert

LPR Ports to Standard Port Monitors checkbox, which is not selected. It is indicated that clicking the

Next button displays the next page of the wizard – Importing. The Importing page includes a bar

indicating the import progress. In this example, the bar is complete and is followed by the note "The

operation completed with no errors." Below the note is the Open Event Viewer button. In this page,

the Next button of the wizard is replaced by the Finish button.

P113 (2-93)

Heading: How to Verify the Migration?

Migration can be verified by viewing event logs, verifying print queues, and printing test jobs. The

Windows Server 2012 desktop is displayed. The taskbar is shown as right-clicked. This displays a

shortcut menu with fifteen options – Programs and Features, Power Options, Event Viewer, System,

Device Manager, Disk Management, Computer Management, Command Prompt, Command Prompt

(Admin), Task Manager, Control Panel, File Explorer, Search, Run, and Desktop. The Event Viewer

option is shown as selected.

T15: Configuring Printer Pooling, Priorities, & Permissions P121 (2-94)

Heading: Easy Print Printer Driver Overview.

Five remote printing tasks are listed. First, Terminal Services printing for RemoteApp and Remote

Desktop sessions. Second, legacy driver and new printer driver support without needing to install

drivers on the terminal server. Third, printer enumeration by session instead of by user. Fourth, rich

printing capabilities. And fifth, full print driver capabilities.

The visual shows a server with a print device. The server is connected to a network cloud.

P122 (2-95)

Heading: How to Configure the Easy Print Printer Driver?

The Local Group Policy Editor window, which has been explained earlier, is displayed. In the left part

of the window, in the Remote Desktop Session Host folder, the Printer Redirection subfolder is

shown as selected. In the right part, the Extended tab is shown as selected. In the tab, the Printer

Redirection page is open. The page includes a table of many columns. Two of them are visible,

Setting and State. The table contains five rows as follows:

Row 1: Do not set default client printer to be default printer in a session, Not configured.

Row 2: Do not allow client printer redirection, Not configured.

Row 3: Use Remote Desktop Easy Print printer driver first, Enabled.

Row 4: Specify RD Session Host server fallback printer driver behavior, Not configured.

Row 5: Redirect only the default client printer, Not configured.

Row 3 is shown as selected and its details are displayed next to the table as follows:

Requirements: At least Windows Server 2008 or Windows 7.

Description: This policy setting allows you to specify whether the Remote Desktop Easy Print printer

driver is used first to install all client printers. If you enable or do not configure this policy setting, the

RD Session Host server first tries to use the Remote Desktop Easy Print printer driver to install all

client printers. If for any reason the Remote Desktop Easy Print printer driver cannot be used, a

printer driver on the RD Session Host server that matches the client printer is used. If the RD Session

Host server does not have a printer driver that matches the client printer, the client printer is not

available for the Remote Desktop session. If you disable this policy setting, the RD Session Host

server tries to find a suitable printer driver to install the client printer.

The Edit policy setting link is also provided.

P123 (2-96)

Heading: How to Configure Printer Pooling?



page has been explained earlier. The Lexmark Pro910 Series Class Driver Properties dialog box is

overlapping the page. The dialog box includes seven tabs – General, Sharing, Ports, Advanced, Color

Management, Security, and Device Settings. The Ports tab is shown as selected. The tab includes the

note "Print to the following port(s). Documents will print to the first free checked port." The note is

followed by a table of three columns – Port, Description, and Printer. The table contains many rows.

For each row, a checkbox for the Port column is provided. Seven rows are visible as follows:

Row 1: COM3:, Serial "Port, blank.

Row 2: COM4:, Serial Port, blank.



Row 5: FILE:, Print to File, blank.

Row 6: 192.16…, Standard TCP/IP Port, blank.

Row 7: 192.16…, Standard TCP/IP Port, Lexmark Pro910 Series Class Driver.

The checkboxes for row 6 and row 7 are shown as selected. The table is followed by three buttons –

Add Port, Delete Port, and Configure Port. The dialog box also includes two checkboxes, Enable

bidirectional support and Enable printer pooling. The Enable printer pooling checkbox is shown as

selected. In addition, the dialog box includes the OK, Cancel, and Apply buttons.

P124 (2-97)

Heading: How to Configure Print Priorities?



page has been explained earlier. It is indicated that clicking the empty area of the page displays a

shortcut menu with eight options – Add Printer, Show Extended View, Refresh, Export List, View,

Arrange Icons, Line up Icons, and Help. The View and Arrange Icons options include a right-arrow

indicating that they consist of more options. It is indicated that selecting the Add Printer option

displays the Network Printer Installation Wizard. In the wizard, the Printer Installation page is open.

The page allows you to pick an installation method. The page includes four radio buttons – Search

the network for printers, Add a TCP/IP or Web Services Printer by IP address or hostname, Add a

new printer using an existing port, and Create a new port and add a new printer. The Add a new

printer using an existing port radio button is shown as selected. It includes a drop-down list with

eleven options – LPT1: (Printer Port), LPT2: (Printer Port), LPT3: (Printer Port), COM1: (Serial Port),

COM2: (Serial Port), COM3: (Serial Port), COM4: (Serial Port), FILE: (Print to File), 192.168.2.26

(Standard TCP/IP Port), 192.168.2.26_1 (Standard TCP/IP Port), and PORTPROMPT: (Local Port). The

192.168.2.26_1 (Standard TCP/IP Port) option is shown as selected. In addition, the wizard includes

the Back, Next, and Cancel buttons. It is indicated that clicking the Next button displays the next

page of the wizard – Printer Driver. The page allows you to pick a driver for the new printer. The

page includes three radio buttons – Use the printer driver that the wizard selected, Use an existing

printer driver on the computer, and Install a new driver. The Use the printer driver that the wizard

selected radio button includes a text field, which contains the text "Compatible driver cannot be

found." The Use an existing printer driver on the computer radio button is shown as selected and

includes a drop-down list, which is set to Lexmark Pro910 Series Class Driver. It is indicated that

clicking the Next button displays the next page of the wizard – Printer Found. The page indicates that

the printer is ready to be installed. It prompts you to review the printer settings, and then click Next

to install the printer. The page displays the details of the printer found. The details include Name,

Share Name, Model, Port Type, Port Name, Location, Publish, and Comment.

Next, the Print Management window is displayed as explained earlier. In the second part, in the

table, an additional row is added with the following details: Lexmark Pro910 Series Class Driver

(Copy 2), Ready, 0, EASYNOMAD(… The row is shown as right-clicked and a shortcut menu is

displayed with twelve options – Open Printer Queue, Pause Printing, List in Directory, Deploy with

Group Policy, Set Printing Defaults, Manage Sharing, Print Test Page, Enable Branch Office Direct

Printing, Properties, Delete, Rename, and Help. It is indicated that selecting the Properties option

displays the Lexmark Pro910 Series Class Driver (Copy 2) Properties dialog box. The dialog box

includes seven tabs – General, Sharing, Ports, Advanced, Color Management, Security, and Device

Settings. The Advanced tab is shown as selected. The tab includes two radio buttons, Always

available and Available from. The Available from radio button includes the From and To spin boxes.

The Always available radio button is shown as selected. The radio buttons are followed by the

Priority spin box and the Driver drop-down list. Next to the Driver drop-down list is the New Driver

button. The Priority spin box is set to 1 and the Driver drop-down list is set to Lexmark Pro910 Series

Class Driver. The dialog box also includes two radio buttons. The first radio button is named as Spool

print document so program finishes printing faster. It is shown as selected and includes two radio

buttons, Start printing after last page is spooled and Start printing immediately. The Start printing

immediately radio button is shown as selected. The second radio button is named as Print directly to

the printer. It is grayed out. The radio buttons are followed by four checkboxes – Hold mismatched

documents, Print spooled documents first, Keep printed documents, and Enable advanced printing

features. The Print spooled documents first and Enable advanced printing features checkboxes are

shown as selected. The Enable advanced printing features checkbox is grayed out. Below the

checkboxes are three buttons – Printing Defaults, Print Processor, and Separator Page. In addition,

the dialog box includes the OK, Cancel, and Apply buttons.

P125 (2-99)

Heading: How to Configure Printer Permissions?


the window, the Printers subnode is shown as selected. This displays its page in the second part. In

the second part, in the table, row 3 contains the following details: Lexmark Pro910 Series Class

Driver (Copy 2), Ready, 0, EASYNOMAD(… The row is shown as right-clicked and a shortcut menu is

displayed. The shortcut menu includes twelve options. The options have been mentioned earlier. It

is indicated that selecting the Properties option displays the Lexmark Pro910 Series Class Driver

(Copy 1) Properties dialog box. The dialog box is similar to the Lexmark Pro910 Series Class Driver

(Copy 2) Properties dialog box. In this example, the Security tab is shown as selected. The tab

includes the Group or usernames area. The area lists seven groups or user names – Everyone, ALL

APPLICATION PACKAGES, CREATOR OWNER, Administrator, Administrators

(EASYNOMADTRAVEL\Administrators), Server Operators (EASYNOMADTRAVEL\Server Operators),

and Print Operators (EASYNOMADTRAVEL\Print Operators). The area is followed by the Add and

Remove buttons. The dialog box also includes a table of three columns – Permissions for Print

Operators, Allow, and Deny. For each row, the Allow and Deny columns include a checkbox. The

table contains four rows as follows:

Row 1: Print, checkbox shown as selected, checkbox not selected.

Row 2: Manage this printer, checkbox not selected, checkbox not selected.

Row 3: Manage documents, checkbox not selected, checkbox not selected.

Row 4: Special permissions, checkbox not selected, checkbox not selected.

The table is followed by the note "For special permissions or advanced settings, click Advanced."

Next to the note is the Advanced button. The note is followed by the Learn more about access

control and permissions link. In addition, the dialog box includes the OK, Cancel, and Apply buttons.

It is indicated that clicking the Advanced button displays the Advanced Security Settings for Lexmark

Pro910 Series Class Driver (Copy 1) dialog box.

The Advanced Security Settings for Lexmark Pro910 Series Class Driver (Copy 1) dialog box indicates

that the owner is SYSTEM. The Change link is provided to change the owner. The dialog box also

includes three tabs – Permissions, Auditing, and Effective Access. The Permissions tab is shown as

selected. The tab includes the note "For additional information, double-click a permission entry. To

modify a permission only, select the entry and click Edit (if applicable)." The note is followed by the

Permission entries table. The Permission entries tab includes five columns – Type, Principal, Access,

Inherited from, and Applies to. The table contains eleven rows as follows:

Row 1: Allow, Everyone, Print, None, Special.

Row 2: Allow, ALL APPLICATION PACKAGES, Print, None, Special.

Row 3: Allow, ALL APPLICATION PACKAGES, Manage documents, None, Special.

Row 4: Allow, CREATOR OWNER, Manage documents, None, Special.

Row 5: Allow, Administrator, Manage documents, None, Special.

Row 6: Allow, Administrator, Manage this printer, None, Special.

Row 7: Allow, Administrators (EASYNOMAD…, Manage documents, None, Special.

Row 8: Allow, Administrators (EASYNOMAD…, Manage this printer, None, Special.

Row 9: Allow, Server Operators (EASYNOMAD…, Manage documents, None, Special.

Row 10: Allow, Server Operators (EASYNOMAD…, Manage this printer, None, Special.

Row 11: Allow, Print Operators (EASYNOMAD…, Print, None, Special.

The table is followed by the Add, Remove, and View buttons. In addition, the dialog box includes the

OK, Cancel, and Apply buttons.