3 Replies Latest reply on May 20, 2020 12:46 AM by danielkrause

    AppVolumes 4.0 / Writable / Network Printers

    Moluxtery Novice

      Hi everyone.

       

      I have the following issue with writable AppVolumes a network printers mapped by GPO:

       

      When the writable volume is attached network printer are note getting mapped. When I try to install them manually i getting this error message:

      printer_install_faile.PNG

      With writable volume disabled the printers getting mapped without a hassle. I also tried a custom snapvol.cfg with the following lines:

       

      exclude_uwv_reg=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider

      exclude_uwv_file=%SystemRoot%\System32\DriverStore\FileRepository

      exclude_uwv_file=%SystemRoot%\INF

      exclude_uwv_reg=\REGISTRY\MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers

      exclude_uwv_reg=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Printers

       

      But I can't really verify if the snapvol.cfg has an effect or not. The snapvol.cfg file is saved under C:\Program Files (x86)\CloudVolumes\Agent\Config\Custom

      Any help or advice appreciated. Thanks.

        • 1. Re: AppVolumes 4.0 / Writable / Network Printers
          Ray_handels Master
          Community WarriorsvExpert

          We had the exact same issue but without the writable.

          Could you try and not attac the writable and create a snapvol.cfg in the following location.

           

          C:\Program Files (x86)\CloudVolumes\Agent\Config\Custom\app\

          And then add these lines in it, that did the trick for us.

           

          exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider

          exclude_path=%SystemtRoot%\System32\DriverStore\FileRepository

          exclude_registry=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Printers

          exclude_registry=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\DeviceContainers

           

          # This should always be the last line in the policy

          os=any

           

          If this works try and attach the writable and see if it works.

          If that does not work I'd suggest adding that exact same file in the following folder.

           

          C:\Program Files (x86)\CloudVolumes\Agent\Config\Default\uia_plus_profile (or profile or uia only, depending on the template you are using for the writable).

          3 people found this helpful
          • 2. Re: AppVolumes 4.0 / Writable / Network Printers
            danielkrause Enthusiast

            Hi interesting arcticle, we have an issue connecting Printers from a script when an AppStack is connected.

             

            Will try to add the exceptions in the snapvol.cfg

            • 3. Re: AppVolumes 4.0 / Writable / Network Printers
              danielkrause Enthusiast

              Thank you so much!

               

              This solved our issue with Printer Mapping and App Volumen 4.0.

               

              We had an issue with an App Stack and not with a writeable, so we used the snapvol.cfg in the default directory instead:

              C:\Program Files (x86)\CloudVolumes\Agent\Config\Custom

               

              After inserting the following keys printer mapping works as expected:

              exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider

              exclude_path=%SystemtRoot%\System32\DriverStore\FileRepository

              exclude_registry=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\Print\Printers

              exclude_registry=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\DeviceContainers

               

              # This should always be the last line in the policy

              os=any

              2 people found this helpful