Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, November 16, 2016 3:14 PM
Hi,
I am trying to diagnose a printer mapping issue with Windows 10. So far I have tried 3 different drivers. We are trying to deploy with Group Policy Preferences (User). We have run is logged on user context ticked, we have tried deploying with \IPADDRESS\PrinterShare... I thought this fixed it, but after monitoring for 3 days we had the error/warning on one of the machines today.
The warning is in the application log, event id 4098
Group Policy Object did not apply because it failed with error code '0x80070057 The parameter is incorrect.' This error was suppressed
I don't know what else to try we have around 100 machines on Windows 10 so OK this isn't happening very often, but it shouldn't be happening at all. If the user logs off and on again they get the printer mapped.
All replies (11)
Tuesday, December 13, 2016 8:38 PM âś…Answered
I went back to the Group Policy Preferences as had other problems with the other route. I seem to have solved this by regular deletion via script of the Client Side Rendering registry keys.
Wednesday, November 16, 2016 8:43 PM
In Event Viewer does Application and Service Logs-Microsoft-Windows-GroupPolicy/Operational offer any clues?
Wednesday, November 16, 2016 8:57 PM
isn't happening very often
Sounds like when it happens that it keeps happening until you try your workaround (user logs off). So, you could try capturing what is happening with ProcMon on the second try. That won't capture how it happens but at least it may give you more insight about why, so then perhaps help find a less invasive workaround to deal with it.
FWIW it sounds like a state error rather than a "parameter" error. And saying that has just reminded me that you could check the state of your printer with either wmic printer list brief or Get-Printer (problem devicename) | fl * (in PowerShell).
Good luck
Robert Aldwinckle
Thursday, November 17, 2016 2:49 AM | 1 vote
Hi John555444,
Instead of logging off and logging on again will work, please try to run "gpupdate /force" then check the symptom again.
Try to enable the "Always wait for the network at computer startup and logon" gpo.
Computer Configuration\ Administrative Templates\System\Logon
To analyze the issue deeply, we could try to enable the gp log.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Diagnostics]
"GPSvcDebugLevel"=dword:00030002
The resulting log file will be:
%WINDIR%\debug\usermode\gpsvc.log
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, November 17, 2016 11:12 AM
Hi All,
Gpupdate /force does solve it too, but can't do this on most accounts as they have command prompt etc disabled.
Can't find anything related in the operational log.
By state error I guess you mean the state of the machine ie the spooler isn't ready to map a printer? Or you do you really mean state of the printer? The printer is a follow me virtual queue and have tried many different Ricoh Drivers which are supposidly compatable with Windows 10.
Kind Regards,
John
Thursday, November 17, 2016 2:35 PM
do you really mean state of the printer?
I mean whatever clues you can glean from those two commands I suggested. The WMIC one makes it obvious because it shows all at once, so you could notice a state difference between your problem printer and any others which might be working. Because I showed piping a printer object into Format-List * I tried to indicate how you might code the PowerShell one. So, for a more specific example for syntax purposes, let's say your problem printer is named Problem Printer, then you would code:
Get-Printer "Problem Printer" | FL *
and see much more detail than you would want to list for all your printers at one time. However, it should be easy to see then how you would code some output which would be more similar to the WMIC result.
To get you started on that we can find objects with Stat in their name
Get-Printer | Select -First 1 | FL * | Out-String -Stream | Select-String "Stat"
Then perhaps this pipeline would be a sufficient comparison
Get-Printer | FT Name, PrinterState, PrinterStatus -AutoSize
Heh. Looks like WMIC does a better job of informing me about PrinterState. PowerShell seems to be trying to give us an interpreted version of the same values but missing ones that it does not know. E.g. for a wireless printer which is owned by another machine I see from WMIC PrinterState 128 and PrinterStatus 1. PowerShell only reports PrinterStatus Offline. YMMV.
Robert Aldwinckle
Friday, November 18, 2016 8:58 AM
Hi John555444,
Have you tried the gpo as I suggested before? Have you enabled the log for more information to troubleshoot this issue?
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, November 22, 2016 12:24 PM
Hi all,
We already have the Always Wait group policy enabled...re the printer state it doesn't seem to return a state as it is a virtual queue not physical.
I have now used the rundll32 printui.dll,PrintUIEntry /ga command to globally add the printer at startup on the machines which seems to be more reliable, although occasionally they don't get the printer as default (set via registry key).
However I now have printers showing up in control panel with their locations as in the registry, they are not available to print too but they show up in control panel and settings, its as if they have not been correctly removed.
If I map the printer manually that is showing up it then throws an error first time and then maps the second I can then properly remove it. I need an automated solution to do this for all the users though... I have no idea how many are facing this, If they are they may not have realised as I doubt many go into devices and printers etc.
Kind Regards,
John
Friday, November 25, 2016 6:58 AM
Hi John555444,
The printers are now shown, right? Are there any new error messages recorded in the Event Viewer?
For the new issue symptom, please ensure the printer is compatible with Windows 10.
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, April 11, 2018 5:27 PM
Which registry keys? I have the same problem. If I use powershell add-printer in a login script, the error is "InvalidArgument: (MSFT_Printer:ROOT/StandardCimv2/MSFT_Printer) [Add-Printer], CimException". It seems to happen with new profiles.
Tuesday, November 20, 2018 1:30 PM
GIVE FULL PERMISSION FOR THE TEMP FOLDER IN C
Path: C:\Users\sajeer\AppData\Local
In the local you can see temp folder . Give full permission by right click the temp folder and edit it ; allow full permission for the temp folder. Then click OK. Then your can start printing the files from printer.
Regards
Sajeer Hajib