Your network contains an Active Directory domain named contoso.com. The domain
contains two servers named Server1 and Server2 that run Windows Server 2012 R2.Server1
has the Group Policy Management feature installed. Server2 has the Print and Document
Services server role installed.
On Server2, you open Print Management and you deploy a printer named Printer1 by using
a Group Policy object (GPO) named GPO1.When you open GPO1 on Server1, you discover
that the Deployed Printers node does not appear.
You need to view the Deployed Printers node in GPO1.
What should you do?
A.
On Server1, modify the Group Policy filtering options of GPO1.
B.
On a domain controller, create a Group Policy central store.
C.
On Server2, install the Group Policy Management feature.
D.
On Server1, configure the security filtering of GPO1.
Explanation:
To use Group Policy for printer deployment you will need to have a Windows Active
Directory domain, and this article assumes that your Domain Controller is a Windows 2008
R2 Server. You will also need the Print Services role installed on a server (can be on your
DC), and you will be using the Print Management and Group Policy Management consoles
to configure the various settings. It is assumed that you have already followed Part One and
have one or more printers shared on your server with the necessary drivers, ready to deploy
to your client computers.
The question does not mention if GPMC is installed on server 2, so I assume that it does not
deploy the GPO because it had no GPMC on server 2.
GPMC is not installed by default.
Is the answer mentioned correct?
0
0
it’s true Monu.
0
0
C
0
0
I believe this answer is true.
However where does it say we are using an Windows 2008 R2 Server as DC?
0
0
could someone please clarify this for me?, if server1 can open gpo1 means server2 has created a domain gpo and therefore has group policy management installed isn’t it?
so the problem would be the gpo1 filtering details…?
0
0
Correct Answer: C
Section: (none)
Explanation
Explanation/Reference:
Explanation:
To use Group Policy for printer deployment you will need to have a Windows Active Directory domain, and this article assumes that your Domain
Controller is a Windows 2008 R2 Server. You will also need the Print Services role installed on a server (can be on your DC), and you will be using the
Print Management and Group Policy Management consoles to configure the various settings. It is assumed that you have already followed Part One and
have one or more printers shared on your server with the necessary drivers, ready to deploy to your client computers. The question does not mention if
GPMC is installed on server 2, so I assume that it does not deploy the GPO because it had no GPMC on server 2.
GPMC is not installed by default.
0
0
When a printer gets deployed via GPO using “Print Management” console, it creates “PushedPrinterConnections” object in AD under the targeted policy. GPMC tool is not required for deployment.
“Deployed Printers” node does not appear in GPMC if “Remote Server Administration Tools\Print and Document services Tool” feature on server (or RSAT on Windows 8.1) is not installed. Once installed, node appears in GPMC even if no printers are deployed.
Answer C can not be correct.
0
0
Correction.
Answer C (GPMC & Print management on same server ) allows management of deployed printers using GPMC console on Server2. It does not fix the issue on Server1.
None of the other answers make sense.
Correct answer C.
0
0
Correct. It says “You need to view the Deployed Printers node in GPO1.”, it does not specify you need to see it on Server1. With C, you will be able to view the Deployed Printer node on Server2.
0
0
Fernando and OSA are correct, The other approach (which was not available) would be install the print management RSAT tool on the Policy server. I tried it and when I opened the GPO the “Deployed Printers” showed up where it hadn’t before. Tricky little question.
0
0
I just passed the exam and had this question.
The correct answer is not listed here and is: “Install the Print & Document Services role on Server1”
0
0