Boatvan

+1 to the FOG client as well. Some people have a big aversion to it, but it has become quite the helpful utility. Super light weight and pretty much unnoticeable if you keep it hidden from users. My environment uses it to name the PC, Join the domain, and even install software or run scripts on demand over the network (Snapins they are called). I would highly recommend the FOG forums (biased because I'm a mod there lol). The developers troubleshoot issues quickly and work directly with the users. https://forums.fogproject.org/ Like newpersn, our unattend is very small and does very little compared to the client.

I dabble in answer files a little. Fist off, what are you using to generate the answer file? I highly recommend using the Windows System Image Manager found in the Windows ADK for your windows 10 version you are installing (if you are using Windows 10 1903 or 1909, download this patch, extract it after the ADK install and follow the directions in the readme (here): https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install Once this is all set up, follow the directions here to get started: https://www.windowscentral.com/how-create-unattended-media-do-automated-installation-windows-10 For the unattended domain join components, look at the screenshot here: The highlighted choice in the lower left is what is needed. Right click that and choose "Add Setting to Pass 2". After that, right click again and choose "Add setting to pass 4" You'll then notice that in the central window of WSIM labeled Answer File, you see these options placed under pass 2 and 4. You can choose each blue box and enter domain credentials and options. As for enabling the built in admin account, there are a couple of methods. What I would recommend is setting the password in the unattend file itself instead of leaving it blank. You can do this by right clicking on the below screenshot'ed components in the lower left box and choosing "Add setting to pass 5" This will be added to your Answer file and you will then use the new blue boxes in the center to set the password and enable the account. You will need to use the Autologoon section to enable the account, but you don't have to have it actually auto login. Then you can specify options these places in the answer file So this should now take care of both the join and the admin account. You can explore other things in the Windows SIM for endless options. Hope this helps!

@Spence_101 I have a thread here with more info and other people's suggestions Ignore the fellow telling me to switch software. I don't know in what world that helps our specific issue lmao

@Spence_101 , I am having the same issue with the latest release. Opened a case with Smart Technologies. Case is now escalated to the product development team from t1 then t2 support. I am running 1903 with the latest .net updates for 1903 as well. Same exact error in event viewer. Will keep you posted after the long weekend. I don't really have an answer as to what to do yet from support

Fellow IT guys, I know this has sat dormant for a long time, but the below method is working flawlessly for me. Thank you to all that gave suggestions. I will quote my post that I was first attempting this with. "1: (Computer Configuration>Administrative Templates>System>Group Policy) Configure user Group Policy loopback Processing mode ----> Enable and set to "Merge" 2: (User Configuration>Preferences>Control Panel Settings>Printers) A: New Shared Printer for the printer you would like deployed (set to Create in properties) B: New Shared Printer again for the printer you would like deployed (exact same settings, but set to Replace in properties)" I posted detailed instructions in another forum and I hope it is OK to post this link: https://www.techpowerup.com/forums/threads/windows-10-1803-gpo-printers-inconsistent.250182/ It is a little ways down and posted by Boatvan (with Screenshots!!!!) I wish I could dig into the "why" further, but I think we are on the right track with improper deletion of profiles. I hope this may help someone in the future.

Hi there, Ironically, we thought we had a workaround until just recently. We are again testing methods to get the printers to consistently add. Our original remedy was to add a scheduled task to gpupdate /force at login while adding the printers in Deployed Printers under computer settings. We have been migrating to Windows 10 Education v1803 over the past few months. We also switched from guest accounts for students to persistent profiles that are pruned after 10 days of not logging in on that machine, so in a way, still a temporary profile, albeit a little less temporary. I am currently testing a very very messy workaround in a few of our labs to see if it works. My new fix is as follows and boy is it ugly. Please note I am still testing the validity of this fix!!! Attempt at the risk of wasting a lot of time if this ends up not working!!! These steps are assuming you are creating a new policy for each formerly deployed printer. If policies exist, edit and remove the deployed printer in the computer settings and do as follows to the existing policy: 1: (Computer Configuration>Administrative Templates>System>Group Policy) Configure user Group Policy loopback Processing mode ----> Enable and set to "Merge" 2: (User Configuration>Preferences>Control Panel Settings>Printers) A: New Shared Printer for the printer you would like deployed (set to Create in properties) B: New Shared Printer again for the printer you would like deployed (exact same settings, but set to Replace in properties) So there it is possibly. You have to create then replace the printer for the blasted thing to appear. I will update with screenshots and verification that it works in the coming week. I am currently awaiting testing results from the users from my test labs. I pray to the printing gods that this works because I have a lot of PO'ed users at the moment...

We're in the process of testing using the VB script listed and Loopback processing as a means of deploying printers in labs. Seems to be working on our test environment. We're hoping an alternative method can be found without the use of scripting. Lastly, we have several labs. Is it best to enable loopback processing in every single group policy for each lab? Or set loopback processing at the domain level and then just have each lab GPO include the VB script only?

Hi KK20, I think you may have misread my workflow. I don't blame you, it is quite confusing. An existing temp profile is the one not getting the printers. New guests get it right away. I also would like to mention that as a Domain Guest, no trace of the user should be left once they log off anyway. Everywhere I look, the permissions are the same for a domain user and a domain guest. If you have a particular spot in mind to look, please let me know. As for the .vbs workaround, I would consider that an absolute last resort. Our district is large and the complexity of setting up scripts and accompanying policies would be monumental. I also know that eliminating domain guests would fix it, but it is either that or pay for Deep Freeze, which also causes some odd issues.

Hi there, We are an odd case because we assign printers by computer instead of by user. To my knowledge, there isn't a way to assign printers on startup using scripts. As described in my Technet thread linked above, I think it is less of a GP thing and more of a Domain Guest issue. Please see my below workflows for the conditions that cause the printer to not add. Maybe this will clarify. It is quite hard to explain otherwise. REBOOT--->Sign in as "Existing" Temp Profile--->NO PRINTERS--->LOG OFF--->LOG BACK IN AS SAME USER--->PRINTERS ADD REBOOT--->Sign in as "New" Temp profile--->PRINTERS ADD REBOOT--->Sign in as "New" Non-Guest profile---> PRINTERS ADD REBOOT--->Sign in as Existing Non-Guest profile--->PRINTERS ADD An "existing" Guest is a domain guest that has logged onto that particular pc in the past. A "new" guest is one that has never logged into that particular PC before. This issue does not affect regular profiles.

Hi Michael. I appreciate your quick replies! LTSB 2016 is what is on the "production" PC's. I was mistaken on the other one, it was Windows 10 Pro, not education on a test machine. The version of the Pro Test machine was 1709. Also, yes, we did do both NETBIOS and FQDN names in GPP, even the IP address of the server in the FQDN. Same error across the board.

Hi Michael, The issue is make/model independent. We have had a Kyocera copier with this error as well as HP printers. We tried both older and newer signed drivers from the vendors. All of our clients are 64 bit. We do however have a mixed Win7 and Win10 environment. We are currently seeing this issue only on the Win 10 machines. We have the same issue on both LTSB and full fledged Win 10 Education. We have tried the FQDN with GPP with the same 513 error. The details of this error are vague. It reads "the parameter is incorrect".

Hi All, I have an open thread on Technet, but I wanted to try here too as I am not really getting much in the way of suggestions. Please see below for the thread I made there that explains my issue and everything we've tried: https://social.technet.microsoft.com/Forums/windowsserver/en-US/105c614d-8f53-4b69-885c-cb8f0d8c25bc/windows-10server-2012-r2-printer-gpo-issues?forum=winserverprint#105c614d-8f53-4b69-885c-cb8f0d8c25bc Basically, we are trying to deploy printers to windows 10 machines from a print server. We have tried both our original Windows Server 2012 R2 and a brand new Windows Server 2016 print servers with the same result. We have tried both Group policy Preference deployment and Deployed printers. The users being affected are domain guests (students). This means the profile is removed from the local machine each time a domain guest logs out. We are getting error 513 in the event logs when the printers try to add. For any further details, please refer to the link. To retype it all would make this a wall of text.