none
printer hide rules - assign CLIENTNAME RRS feed

  • Question

  • Hi

    is this a supported scenario? It seems the rule applies to all sessions regardless of CLIENTNAME.

    Further I remove frx and fra files but the created rules remain active.

    FSLogix creates coresponding registry rules automactically like:

    HKLM\SYSTEM\*\Enum\SWD\PRINTENUM\{1BDA714D-BC63-4387-B3DD-73664C22EC49} -> [Hide]

    How can I delete these? frx.exe delete-rule -src-parent wont find it.

    best regards

    Markus

    Wednesday, September 4, 2019 9:44 AM

All replies

  • Hello,

    I have double checked and when the rule and assignment files for a printer hiding rule are removed from the rules folder (c:\program files\fslogix\apps\rules) then the rules are removed from the system. Run at the command line the command (from c:\program files\fslogix\apps) frx list-rules. Run this when the rule files are there and then after they are removed and you should see a difference.

    Also I have tested applying the rules to a user and not another user and that appears to work properly as well.

    When the rules are removed you may not see a change in the printers list until to you close possibly all the explorer windows and then open one and go to control panel. But in general this is not a common use case. Printer hiding rules are built to be applied at the start of a session and then removed at logoff.

    If this is not working as explained then double check what you are doing to see if it matches as above. And if you are still having issues please file a ticket at: https://support.fslogix.com/

    Regards


    Wednesday, September 4, 2019 7:37 PM
    Owner
  • I reproduced like this:

    Hide Printer Rule. (local Printer, Network or Masquerading Printers all same result)

    Assign Rule -> Everyone No; UserA Yes   


    1. install Rules.  Printers not hidden for UserB as expected

    2. REBOOT Machine

    3. Printers hidden for UserB

    There are a lot of ID 13,14 in Administrative Log and 26 in operational.

    (26 = cannot find file specified)
    (13,14 = Applying Printer Security failed)


    best regards

    Markus


    Saturday, September 7, 2019 5:44 PM
  • Is anyone using the printer hiding rules in productive?

    I could see them working sometimes until a reboot of the machine with printer hiding rule in place. 

    Inconsitencies even without reboot when hiding and unhiding a printer. I tried with user assignment only.

    Errors in operational log:

    ID26 : Failed to send message to driver (AddRuleAssignment) (cannot find file specified)

    ID26 : Failed adding rule assignment for key HKLM\SYSTEM\*\Enum\SWD\PRINTENUM\{934101D7-E24D-4478-B7BA-42EE18B81B61} (cannot find file specified)

    FSLogix Service Version 2.9.7117.27413

    best regards

    Markus

    Tuesday, September 10, 2019 8:18 PM
  • I tried FSLogix 1909. (2.9.7205.27375)

    Similar results. With the local Administrator - create a local printer - add rule. The printer is not hidden. After reboot ID26 errors in log. Removing rules the printer remains dysfunctional. (no access to printer properties)

    Server 2019 german, on nutanix ahv and citrix vda software installed.

    [23:07:07.916][tid:00000c70.00000dd0][INFO]           ===== Begin Session: Printer Rule Added
    [23:07:07.916][tid:00000c70.00000dd0][INFO]            Printer Citrix with GUID {470BB45C-BC48-4932-A933-06563E78F01A} selected for applying key hiding rules
    [23:07:08.557][tid:00000c70.00000dd0][ERROR:80070002]  Failed adding rule assignment for key HKLM\SYSTEM\*\Enum\SWD\PRINTENUM\{470BB45C-BC48-4932-A933-06563E78F01A} (Das System kann die angegebene Datei nicht finden.)
    [23:07:08.557][tid:00000c70.00000dd0][ERROR:80070002]  Failed adding rule assignment for key HKLM\SYSTEM\*\Control\DeviceContainers\{b44fd80d-0f75-f376-e371-86a4d8c9a947} (Das System kann die angegebene Datei nicht finden.)
    [23:07:08.557][tid:00000c70.00000dd0][ERROR:80070002]  Failed adding rule assignment for key HKLM\SYSTEM\*\Control\DeviceClasses\{0ecef634-6ef0-472a-8085-5ad023ecbccd}\##?#SWD#PRINTENUM#{470BB45C-BC48-4932-A933-06563E78F01A}#{0ecef634-6ef0-472a-8085-5ad023ecbccd} (Das System kann die angegebene Datei nicht finden.)
    [23:07:08.557][tid:00000c70.00000dd0][ERROR:80070002]  Failed adding rule assignment for key HKLM\SYSTEM\*\Enum\SWD\PRINTENUM\{470BB45C-BC48-4932-A933-06563E78F01A} (Das System kann die angegebene Datei nicht finden.)
    [23:07:08.557][tid:00000c70.00000dd0][ERROR:80070002]  Failed adding rule assignment for key HKLM\SYSTEM\*\Control\DeviceContainers\{b44fd80d-0f75-f376-e371-86a4d8c9a947} (Das System kann die angegebene Datei nicht finden.)
    [23:07:08.573][tid:00000c70.00000dd0][ERROR:80070002]  Failed adding rule assignment for key HKLM\SYSTEM\*\Control\DeviceClasses\{0ecef634-6ef0-472a-8085-5ad023ecbccd}\##?#SWD#PRINTENUM#{470BB45C-BC48-4932-A933-06563E78F01A}#{0ecef634-6ef0-472a-8085-5ad023ecbccd} (Das System kann die angegebene Datei nicht finden.)
    [23:07:08.573][tid:00000c70.00000dd0][INFO]           ===== Begin Session:  Updating Printer Visibility

    Monday, September 30, 2019 9:59 PM
  • We're experiencing the same issue - I have a ticket open with FSLogix support but haven't gotten any useful feedback.

    The behavior we're seeing (Win10 1809) is that the printers are hidden from Printers and Scanners, but not in the print management console or if you attempt to print from another software. The printer will still be listed, but the print option is greyed out.

    Once it's hidden, if you are the administrator, you can go into the printer management console and take ownership of the printer. Once ownership is taken, you will see that the printer permissions are explicity denying the print options for the user. If you remove your account from the permissions, the default Everyone allow permissions will take affect and allow you to print.

    This is strange behavior since I did not think that FSLogix sets any permissions when masking items.

    I'll update this thread once FSLogix provide some useful info.

    • Edited by Ch0n3 Friday, October 25, 2019 12:40 PM
    Friday, October 25, 2019 12:33 PM