1. Correct answer: C
A. Incorrect: With one physical disk in the pool, you can provision only simple volumes . At least three physical disks are needed if you plan on creating resilient volumes in a failover cluster containing two file servers.
B. Incorrect: With two physical disks in the pool, you can provision resilient vol- umes, but at least three physical disks are needed if you plan on creating resilient volumes in a failover cluster containing two file servers.
C. Correct: At least three physical disks are needed if you plan on creating resilient volumes in a failover cluster containing two file servers.
D. Incorrect: At least three physical disks are needed if you plan on creating resilient volumes in a failover cluster containing two file servers. The fourth volume can be used but is not required .
2. Correct answer: D
A. Incorrect: The Get-StoragePool cmdlet returns either a specific storage pool or a set of StoragePool objects from all storage subsystems across all storage providers, or optionally it returns a filtered subset based on specific parameters.
B. Incorrect: The Get-VirtualDisk cmdlet returns a list of VirtualDisk objects across all storage pools and across all providers, or optionally it returns a filtered subset based on provided criteria .
C. Incorrect: The Get-PhysicalDisk cmdlet returns a list of all PhysicalDisk objects visible across any available Storage Management providers, or optionally it returns a filtered list.
D. Correct: The Get-StorageSubsystem cmdlet returns a single StorageSubsystem object or a set of Subsystem objects, depending on the parameters given . The returned information includes the friendly name, health status, and operational status of each storage subsystem on the server .
3. Correct answers: A, C, and D
A. Correct: You can use either Server Manager or Windows PowerShell to extend a virtual disk .
B. Incorrect: You cannot shrink a virtual disk .
C. Correct: You can use either Server Manager or Windows PowerShell to detach a virtual disk
D. Correct: You can use either Server Manager or Windows PowerShell to delete a virtual disk
4. Correct answer: A, B, and C
A. Correct: Use the SMB Share - Quick option if you need to create a general- purpose SMB share for file sharing.
B. Correct: Use the SMB Share - Advanced option if you need to configure quotas on your share or implement file classification.
C. Correct: Use the SMB Share - Application option if the share will be used by Hyper-V hosts for shared storage, by a database application, and for other server applications .
D. Incorrect: Create an NFS share if you need to use file sharing in heterogeneous environments that include both Windows and non-Windows computers .
Lesson 3
1. Correct answers: A, B, and C
A. Correct: In the Windows Server 2012 implementation of an iSCSI initiator, the initiator IQN looks like this:
iqn.1991-05.com.microsoft:<initiator_server_FQDN>
Because “srv4-finance-target” is not in the proper form for a FQDN, the string cannot be the IQN of the iSCSI initiator .
B. Correct: In the Windows Server 2012 implementation of iSCSI Initiator, an initiator IQN looks like this:
iqn.1991-05.com.microsoft:<initiator_server_FQDN>
Because “srv4-finance-target” is not in the proper form for a FQDN, the string cannot be the IQN of the iSCSI initiator .
C. Correct: In the Windows Server 2012 implementation of an iSCSI target server, the target IQN looks like this:
iqn.1991-05.com.microsoft:<target_server_name>-<target-name>-target
Because “srv4-finance-target” is of this form, the string is the IQN of an iSCSI target named “finance” on a target portal named “srv4.”
D. Incorrect: In the Windows Server 2012 implementation of an iSCSI target server, the target IQN looks like this:
iqn.1991-05.com.microsoft:<target_server_name>-<target-name>-target
Because “srv4-finance-target” is of this form, the string is the IQN of an iSCSI target.
However, “finance” is the name of the target, not the target portal. The name of the target portal is “srv4 .”
2. Correct answers: A, B, and C
A. Correct: Challenge Handshake Authentication Protocol (CHAP) is a basic level of iSCSI security that is used to authenticate the peer of a connection and is based upon the peers sharing a secret .
B. Correct: Remote Authentication Dial-In User Service (RADIUS) is a standard used for maintaining and managing user authentication and validation . Unlike CHAP, authentication with RADIUS is not performed between peers, but between a RADIUS server and a client . To use this level of security with iSCSI, you must have a RADIUS server running on your network, or you must deploy one .
C. Correct: Internet Protocol security (IPsec) is a protocol that enforces authentica- tion and data encryption at the IP packet layer . IPsec can be used in addition to CHAP or RADIUS authentication to provide an added level of security for iSCSI .
D. Incorrect: Configuring your iSCSI targets to allow connections from initiators with an IQN of “IQN:* ” actually weakens the security of your environment because it allows any initiator to access the target .
3. Correct answers: A, B, and C
A. Correct: The Get-IscsiConnection cmdlet gets information about connected iSCSI initiator connections . The output of this command does not include the LUN mapping for an iSCSI target .
B. Correct: The Get-IscsiServerTarget cmdlet obtains iSCSI targets and their associated properties from the local server or specified computer. The output of this command includes the LUN mapping for the iSCSI targets on the target server . C. Correct: The Register-IscsiSession cmdlet registers an active iSCSI session to be
persistent using the session identifier as input. The output of this command does not include the LUN mapping for an iSCSI target .
D. Incorrect: The Get-IscsiTarget cmdlet returns information about connected iSCSI targets . The output of this command does not include the LUN mapping for an iSCSI target .
C H A P T E R 9
Print and document services Managing printers and print servers isn’t one of the more exciting jobs of the IT
administrator, but it’s an important one. The so-called “paperless office” might never arrive, despite the numerous advances in both computer hardware and software in recent years. As a result, administrators still need to know how to deploy, configure, and manage Microsoft Windows print servers in enterprise environments . And that’s what this chapter is all about .
Lessons in this chapter:
■ Lesson 1: Deploying and managing print servers 431
■ Lesson 2: Managing print servers using Windows PowerShell 450
Before you begin
To complete the practice exercises in this chapter
■ You need to know how to perform a clean install of Windows Server 2012 and perform initial configuration tasks like configuring the server’s TCP/IP settings for Internet connectivity .
■ You need to know how to promote a server running Windows Server 2012 as a domain controller .
■ You also should have at least rudimentary knowledge of using Windows PowerShell on earlier versions of Windows Server .
Lesson 1: Deploying and managing print servers
You can use Server Manager to centralize the deployment of Windows Server 2012 print servers . Once the Print And Document Services role has been installed on remote serv- ers, you can then use the Print Management console to configure and manage your print servers, printers, and printer drivers . You can also use the console to deploy and manage printer connections for clients on your network .
After this lesson, you will be able to
■ Use Server Manager to install different role services of the Print And Document Services role .
■ Use Server Manager to install the role management tools for Print And Document Services .
■ Use the Print Management console to manage print servers, printer drivers, and printers .
■ Deploy printer connections to users and client computers using Group Policy .
■ Be aware of the tools used for migrating print queues and printer drivers from print servers running earlier versions of Windows Server .
Estimated lesson time: 30 minutes
Deploying print servers
Deploying print servers in an enterprise environment involves performing the following tasks:
■ Installing the Print Server role service and, optionally, other role services of the Print And Document Services role on target servers in your environment .
■ Installing the Print And Document Services Tools feature on the computer or computers you will be using to manage the print servers and printers in your environment .
The following sections show how to perform these tasks using Server Manager .
Installing the Print Server role service
You can use the Add Roles And Features Wizard to deploy print servers on the local server or on remote servers running Windows Server 2012. For example, to configure the local server as a print server, perform the following tasks:
1. Launch the Add Roles And Features Wizard from the Manage menu on the Server Manager toolbar .
2. Select Role-Based Or Feature-Based Installation, and then select the local server from the server pool .
3. On the Select Server Roles page, select the Print And Document Services role and click OK when prompted to install the management tools for this role .
4. On the Select Role Services page, select the Print Server role service and proceed through the remaining steps of the wizard .
To use Server Manager to configure a remote server as a print server, perform these steps:
1. Make sure the remote server has been added to the server pool on the computer you are running Server Manager on .
2. Launch the Add Roles And Features Wizard from the Manage menu on the Server Manager toolbar and select Role-Based Or Feature-Based Installation .
3. Select the remote server from the server pool and then proceed through the remain- ing steps of the wizard .
NOTE DEPLOYING REMOTE PRINT SERVERS
When you configure a remote server as a print server, you don’t need to install the management tools for the Print And Document Services role on the remote server if you plan on administering all the print servers in your environment from a central location.
Installing other role services
As Figure 9-1 shows, there are additional role services of the Print And Document Services role that you can install when you configure a server running Windows Server 2012 as a print server . These other role services are optional and provide the following capabilities:
■ Distributed Scan Server This role service provides a service that can receive scanned documents from network scanners and route the documents to their correct destinations . When you install this role service, the Scan Management snap-in is also installed, and you can use this snap-in to manage network scanners and configure scan processes . Because a snap-in is installed together with this role service, you cannot install Distributed Scan Server on a Server Core installation of Windows Server 2012 . Distributed Scan Server was first introduced in Windows Server 2008 R2 and has not significantly changed in Windows Server 2012. For more information on this feature, see http://technet.microsoft.com/en-us/library/jj134196 .
■ Internet Printing This role service installs the Web Server (IIS) role and creates a new website that users can use to manage their print jobs . Internet Printing also allows users that have the Internet Printing Client installed on their computers to use a web browser to open http://<server_name>/printers in order to connect and print to shared printers on a Windows print server using the Internet Printing Protocol (IPP) . Client computers running Windows 7 and later can install Internet Printing Client as an optional in-box feature .
Internet Printing and IPP were first introduced in Windows Server 2003. The feature was enhanced in Windows Server 2008 and has not significantly changed since then.
For more information on this feature, see http://technet.microsoft.com/en-us/library/
ee126092(v=WS.10).aspx .
■ Line Printer Daemon (LPD) Service This role service enables UNIX-based and Linux-based computers to use the Line Printer Remote (LPR) service to print to shared
printers on a Windows print server. LPD and LPR were first introduced in Windows 2000 Server as part of the Print Services for Unix component . For information on using LPD and LPR, see http://technet.microsoft.com/en-us/library/cc976747.aspx .
Beginning with Windows Server 2012, the LPD and LPR services are now considered deprecated . This means that support for these services will likely be removed in future versions of Windows Server .
FIGURE 9-1 Configuring a server as a print server .
REAL WORLD DEPRECATED FEATURES
An important aspect of the IT administrator’s job is to plan for the future. Because of this, it’s important for you to know which features are deprecated in Windows Server 2012 so that you can find alternate methods for implementing their functionality if this is still required. For a list of features removed or deprecated in Windows Server 2012, see http://technet.microsoft.com/en-us/library/hh831568.
Installing the Print And Document Services Tools feature
The Print And Document Services Tools is a subfeature of the Role Administration Tools section of the Remote Server Administration Tools feature . You don’t need to install the Print And Document Services Tools on the remote servers on which you install the Print Server role . Instead, install the Print And Document Services Tools feature on the computer you will be using to manage all of the print servers in your environment . This computer might be one of the following:
■ A server running Windows Server 2012, in which case you can use the Add Roles And Features Wizard, as shown in Figure 9-2, to install the Print And Document Services Tools feature on the server .
■ A client computer running Windows 8, in which case you can install the Remote Server Administration Tools (RSAT) for Windows 8 and enable the Print And Document Services Tools feature on the computer .
FIGURE 9-2 Installing the management tools for print servers .
Installing the Print And Document Services Tools on a computer installs the following tools for managing print servers and printers:
■ Print Management Microsoft Management Console (MMC) snap-in
■ PrintManagement module for Windows PowerShell
The remainder of this lesson focuses on using the Print Management snap-in to manage the print servers and printers in your environment, while Lesson 2 later in this chapter describes how to use the Windows PowerShell cmdlets in the PrintManagement module for doing the same .
Quick check
■ You plan on deploying the Internet Printing role service to allow users to manage their print jobs from a webpage. Is this a good idea?
Quick check answer
■ Not really. The Internet Printing role service is now deprecated and might therefore be removed in the next version of Windows Server. So it’s best if you find some other solution that can meet your printing needs.
Managing printers using Print Management
The Print Management snap-in was first introduced in Windows Server 2003 R2. The snap-in was then enhanced with new functionality and performance and scalability improvements, first in Windows Server 2008 and then in Windows Server 2008 R2. The snap-in has not significantly changed, however, in Windows Server 2012. This is good news for Windows administrators because it means they can make use of their existing knowledge of how to manage print servers running previous versions of Windows Server . As a result of this, the following discussion about how to use this snap-in to manage print servers and printers will be concise and will cover only the following tasks:
■ Launching Print Management
■ Managing print servers
■ Managing printer drivers
■ Managing printers
■ Deploying printer connections
■ Migrating print servers
Launching Print Management
Installing the Print And Document Services role and its role management tools results in a new page called Print Services being added to Server Manager . (See Figure 9-3 .) Using this new page, you can do the following:
■ View printing-related events
■ Restart the Print Spooler service if needed
■ Start performance counters on the print server
■ View a list of installed role services for the Print And Document Services role
FIGURE 9-3 The Print Services page in Server Manager .
You can also launch the Print Management console from the Tools menu in Server Manager . When Print Management is opened on a print server, the local host is visible in the console tree unless it has been removed . You can add other print servers to the console so that you can manage them by doing the following:
1. Right-click the Print Servers node, and select Add/Remove Servers to open the Add/Remove Servers dialog box:
2. If the local server is not visible, click Add The Local Server .
3. In the Add Servers text box, type the name of a remote print server you want to manage, and click Add To List . You can also browse for other print servers on the network .
4. Click OK when you are finished.
For example, Figure 9-4 shows Print Management being used to manage two print servers:
■ The local server named HOST4
■ A remote server named HOST7
FIGURE 9-4 Managing print servers using the Print Management console .
The console tree of Print Management has the following nodes:
■ Print Management This root node allows you to add or remove print servers and to migrate printers .
■ Custom Filters This node allows you to quickly view all printers, all printer drivers, all printers that are not ready to print, or all printers that have pending print jobs . You can also use this node to create new filters of your own for filtering printers or printer drivers according to conditions you specify .
■ Print Servers This node displays all print servers being managed by the console as subnodes . You can also use this node to add or remove print servers from the console as described previously .
■ <servername> Each node that displays the name of a print server allows you to manage the print server, add printers to it, and perform other management tasks . Each print server node also has four subnodes that allow you to view and manage printer drivers, printer forms, printer ports, and printers .
■ Deployed Printers This node allows you to view printers that have been deployed using Group Policy .
The sections that follow provide more details for performing some of these tasks .
Managing print servers
By right-clicking on a print server and selecting Properties, you can view or modify the print server’s properties. For example, Figure 9-5 shows the Security tab, which you use to config- ure permissions for different groups and users in your environment to control such things as whether they should be allowed to print to the server . For example, if you want to restrict the use of printers on a particular print server to users in a certain department, you could remove
the Everyone permissions entry that appears in the Group Or User Names area and add a new entry for a security group to which users in that department belong .
FIGURE 9-5 Configuring print permissions for a print server .
Other management tasks you can perform using the Properties page of a print server include
■ Creating new forms for special print requirements—for example, for printing to note cards or poster paper .
■ Adding new printer ports, including both local ports and standard TCP/IP ports. For example, before connecting a new network printer, you should create a standard TCP/
IP port for it .
■ Adding new printer drivers to the server—for example, when you will be deploying new printers for which Windows Server 2012 has no in-box drivers .
■ Changing the location of the spooler folder—for example, if the volume the folder is currently on is almost full .
■ Displaying or hiding informational notifications for printers.
MORE INFO CONFIGURING PERMISSIONS
For detailed information about the different print permissions for a print server and how to configure them, see http://technet.microsoft.com/en-us/library/jj190062.