Your network contains an Active Directory domain named contoso.com. The domain contains three
member servers.
The servers are configured as shown in the following table.
All client computers run Windows 8. All client computers receive updates from Server2.
On Server3, you add a shared printer named Printer1. Printer1 uses a Type 4 driver that is not
included in the Windows 8 installation media.
You need to ensure that when users connect to the printer for the first time, the printer driver is
installed automatically on their client computer.
What should you do?
A.
From the Windows Deployment Services console on Server1, add the driver package for Printer1.
B.
From the Update Services console on Server2, import and approve updates.
C.
From Windows PowerShell on Server3, run the Add-PrinterDriver cmdlet.
D.
From the Print Management console on Server3, add additional drivers for Printer1.
B
1
0
b
1
0
D
0
0
Just incase this is really confusing anyone I’m copying what someone else said from a older version of this test:
““At the core of the Windows Server 2012 printing experience is a new driver model known as the Type 4 (v4) print driver model. The v4 driver model includes changes to printer sharing known as enhanced Point and Print, eliminating the need to install cross platform drivers and eliminating the scenario where a Print Server is a driver distribution point.”
“The v4 print driver model provides a simple but flexible management experience. V4 print drivers can be distributed via Windows Update or Windows Software Update Services (WSUS), but are not distributed to print clients from the print server.”
http://technet.microsoft.com/en-us/library/jj134171.aspx“
0
0
IMO its D. Type 4 print drivers via WSUS are Server 2012 only and in this example the WSUS server is running 2008. You would still have to push drivers via print management from the print server
0
0
Correct, tricky tricky 🙂
0
0
NOT correct. Answer already provided by Leanne.
“The v4 print driver model provides a simple but flexible management experience. V4 print drivers can be distributed via Windows Update or Windows Software Update Services (WSUS), but are not distributed to print clients from the print server.”
http://technet.microsoft.com/en-us/library/jj134171.aspx“
0
0
“The v4 print driver model provides a simple but flexible management experience. V4 print drivers can be distributed via Windows Update or Windows Software Update Services (WSUS), but are not distributed to print clients from the print server.”
https://technet.microsoft.com/en-us/library/jj134171.aspx
0
0
B.
“The v4 print driver model provides a simple but flexible management experience. V4 print drivers can be distributed via Windows Update or Windows Software Update Services (WSUS), but are not distributed to print clients from the print server. (https://technet.microsoft.com/en-us/library/jj134171.aspx)
0
0
It is D
Windows Server 2008R2 doesn’t support v4 type drivers.
https://technet.microsoft.com/en-ca/library/jj590748.aspx
0
0
Definitely Not D
https://technet.microsoft.com/en-us/library/jj134171.aspx
Disabling Driver Distribution
As described previously, the Microsoft enhanced Point and Print compatibility driver is provided to clients running a previous version of Windows to enable printing to a queue shared with a v4 driver.
There is no actual API used by existing clients to retrieve driver binaries from the server. Existing servers make driver files available under the \\server\print$ share, and the information about what driver is in use for a queue and what files are needed is retrieved by clients through the GetPrinterDriverEx API. Existing Windows clients call GetPrinterDriverEx for the remote printer to get details about the remote driver, and then simply use filesystem APIs to copy the files from the server share to the client over SMB.
Instead of disabling the print$ share since it is still necessary for distributing the Microsoft enhanced Point and Print compatibility driver to downlevel clients, GetPrinterDriverEx does not provide the driver information so that clients will be unable to use the returned information to find drivers under print$, and are forced to try other methods of procuring drivers.
Enhanced Point and Print
Complementing the v4 driver model are changes to the printer sharing model. The updated printer sharing mechanism is referred to as enhanced Point and Print, and it allows print clients to print to v4 shares without downloading the manufacturer-provided device driver from the print server.
When a computer running Windows 8 connects to a shared print queue on the server, it checks locally for a v4 print driver that has a HardwareID that is the same as the PrinterDriverID defined in the server’s print driver. It may also check Windows Update at connection time or later for a matching driver on Windows Update. If it finds a match, the client downloads that driver and connects using client-side rendering (CSR). If the driver includes a customized UI, then that UI will be shown to the user.
Otherwise, the client connects using the enhanced Point and Print driver. If the client does not have this driver already, it downloads it from the server. At this point, the client downloads configuration data files from the server and associates them with the client print queue. When the user prints, they are provided with a localized, Microsoft standard UI, unless the user acquires a printer extension or a Windows Store device app is automatically downloaded. The print job will be rendered on the client into XPS and include the user’s settings as a PrintTicket. This is then sent to the server and rendered into PDL using the server’s print driver.
From
0
0
hi so what one is it ?
0
0
Leanne is correct. I’d have guessed D before looking into it further.
https://blogs.technet.microsoft.com/askperf/2012/11/03/windows-8-windows-server-2012-whats-new-with-printing-in-windows-8/
0
0
To clarify – the answer is B
0
0