Shared Printers with Disk Protection enabled? RRS feed

  • Question

  • How do I make shared printers show up and stay under any profile on a machine that is Running SS with disk protect turned on. These machines are part of a domain but it's seem sthat no mattter what I do the printer do not stay after I have added them. This is even after turning Disk protect off, adding the printer as the local admin, and then turning Disk protection back on. How do I solve this issue since I do not know who will be logging on to the computer?

    Thursday, December 13, 2007 8:45 PM


  • Hi Peter,


    Thank you for posting here!


    Does this issue occur if you configure WDP to “Retain all changes permanently”?

    Does this issue persist if you have WDP disabled?


    I also performed a local test:


    1. Before adding my test machine to domain, network printers (within domain) cannot be found by local admin (through Add printer wizard)

    2. Add the test machine to a domain. Network printers still cannot be found by local admin.

    3. Log on as domain account. Add a network printer. Log off.

    4. Log on as local admin, network printers still cannot be found. Configure WDP to “Retain all changes permanently”. Restart the computer.

    5. Log on as domain account, network printer is there. Log on with other local accounts or domain accounts, no printer was found.


    Based on my experience, if another domain account logs into the system at the first time, the user needs to add the printer manually. However, based on your situation, it’s not possible to retain changes for every domain account.



    One possible workaround is configuring default printer for the domain accounts from the server side. I found some articles for your reference:

    How To Set a User's Default Local Printer with a Logon Script



    How to Add a Default Printer Using a Visual Basic Script



    Assign a Default Printer



    How To Set Which Printer Is the System Default Printer



    If you need further assistance from the server side, you can also post your inquiry to Windows Server Newsgroup:




    The reason why we recommend posting appropriately is that you will get the most qualified pool of respondents, and other customers who read the newsgroups regularly can either share their knowledge or learn from your interaction with us.  Thank you for your understanding.



    Please also understand that, SteadyState was not designed for Domain environment to deploy. It doesn't have central management console either. If you have hundreds of machines to manage within a domain, Group Policy and Microsoft Systems Management Server (SMS) are always recommended. You may need to think twice whether WDP is the most suitable manner.


    Best Regards,

    Friday, December 14, 2007 6:02 AM