Bug 43566 – ucs-test: Windows client test: Serverside/Point'n'print printer driver download

Bug 43566 - ucs-test: Windows client test: Serverside/Point'n'print printer driver download


Summary:	ucs-test: Windows client test: Serverside/Point'n'print printer driver download

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	Samba
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:	https://msdn.microsoft.com/de-de/wind...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-02-16 20:03 CET by Arvid Requate
Modified:	2017-02-16 20:03 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2017-02-16 20:03:30 CET

It would be good to have a Windows client test that test the automatic server side printer driver download (Point'n'print).

* On the UCS printserver create a printer share via udm

* Provide a test driver (e.g. generic postscript) for the Windows client via some share (e.g. via Administrator home share).

* Via winexe connect to the Windows client and upload the driver to the UCS server:
Add-PrinterDriver -Name "Driver Name" -ComputerName "printServer"

see https://technet.microsoft.com/itpro/powershell/windows/print/index


* Via winexe connect to the Windows client and connect the printer
([wmiclass]"Win32_Printer").AddPrinterConnection("\\Printserver\Drucker1")

see https://msdn.microsoft.com/de-de/windows/hardware/drivers/print/downloading-driver-specific-files

* Via winexe connect to the Windows client and print something

* Verify that the job gets printed (into a file) on the UCS server