What controls the publishing of shared printers to the list?


Recommended Posts

Hey guys,

I've been noticing a minor issue here at work. For the past year or so, I have gotten into the habit of adding every printer to the server so that jobs were more easily managed, and printers could be more easily installed on machines. The only thing I don't like about this method is that if you install a printer on a machine this way, it only is installed for the profile you install it under.

One issue I've been having is recent additions do not seem to be getting published in the list. Frequently I will setup a printer on the server for a specific tray as the request comes in. Once it's added and shared, I go to view the printer list and of course I don't see it there; I typically have to then add it by the \\computer\sharename method. I also noted that a printer I added a few weeks ago also is not displaying in the list.

1) What controls how quickly a printer goes from being setup / shared to being published on the list?

2) Is there any way to speed up that process so they are immediately available for addition?

It's always instant for me when creating printer shares. However when searching for printers I search using Active Directory rather than via its share name.

Regarding the printers only on the profile you set it up for this is by design. Typically you would control this via a login script or if your running Windows 2003 R2 via Group Policy.

I have wanted to setup either, using GP or script... however the scripts I was never able to iron out. I think with GP, if I can do this properly (I haven't looked TOO much into it... though now we have PolicyMaker also), I believe I would have to setup a bunch of policies for printing, and only specify them by the users that can use them... instead of breaking up into numerous little sub-groups.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • too bad the "backend" June 2026 ESD files are still at build 26200.8653 and not at the correct build 26200.8655 release. I'll avoid using the MCT for several weeks until late July 2026
    • Qualcomm's new Snapdragon Reality Elite chip brings on-device AI to Android XR devices by Pradeep Viswanathan Qualcomm has been delivering dedicated SoCs for mixed reality and spatial computing devices for several years. The journey started with the Snapdragon XR1, followed by the Snapdragon XR2 in 2019, the Snapdragon XR2 Gen 2 in September 2023, and finally the Snapdragon XR2+ Gen 2 in 2024. Today, Qualcomm announced a major upgrade with the new Snapdragon Reality Elite Platform, which targets premium mixed reality and spatial computing devices. OEMs can use this SoC to power both all-in-one video-see-through headsets and lightweight, tethered optical-see-through glasses. Qualcomm highlighted that the Snapdragon Reality Elite will power the next wave of Android XR devices coming later this year. These wearables will offer better visuals, improved power efficiency, and deeper on-device AI integration compared to the previous generation. The Snapdragon Reality Elite can deliver up to 48 TOPS of AI performance, allowing large language models and large vision models to run directly on the device for the first time. In addition to enabling new spatial AI experiences, these new AI capabilities will improve head and hand tracking, as well as see-through features. On the performance side, the Snapdragon Reality Elite offers up to 60% higher GPU performance, up to 30% higher CPU performance, and up to 160% higher NPU performance compared to the previous generation. The platform supports visuals of up to 4.4K per eye at 90 frames per second for sharper images and smoother motion. Qualcomm is also claiming significant efficiency improvements. The Snapdragon Reality Elite can offer up to 20% longer battery life under the same workload. More importantly, the chipset can run up to 12 degrees Celsius cooler under load, making headsets more comfortable for users to wear for longer periods. The platform also includes improvements to video see-through, featuring lower latency and better image quality. Qualcomm states that its EVA hardware block helps accelerate demanding computer vision workloads, improving how digital content blends with the real world.
    • Umm... GitHub continues to use AWS. That's the story, that's the headline. There's no "new" news here. GitHub continues to require additional capacity beyond the originally-planned Azure allocations. There's nothing special about this; nothing noteworthy. They're still using AWS' infra until the cutover is complete.
    • Hello, Also known for https://www.theguardian.com/technology/2009/jan/29/adware-internet.   Regards, Aryeh Goretsky    
    • Hello, I have used a few TEAM Group SSDs, USB flash drives, and Micro SDXC cards in the past. They all seemed to work fine. Regards, Aryeh Goretsky
  • Recent Achievements

    • Collaborator
      vjlex earned a badge
      Collaborator
    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      182
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!