Windows 10 1703 and network printers
-
I've deployed 1703 on about a dozen PCs so far.
Two of them use an old ass Gestetner 415 printer. The printers had disappeared from the user profiles after the upgrade. I tried to add them back afterwards and got an error about lack of permissions.
I tried a few things, removing old printer drivers, old ports (not really there) and then tried readding. No go.
I then manually created the IP port and installed the ancient 2008 x64 driver and then I was able to print fine.
Today I've upgrade another machine and now my Konica C552 is in the same boat. I can't map the network printer (from Windows Server 2012 R2).
Googling lead me to this article:
https://partnersupport.microsoft.com/en-us/par_clientsol/forum/par_win/windows-10-1703-manage-printer/8dc270e9-73f6-48a7-b92c-e4d14633ee85
Which to me implies that MS is aware there is some form of network printing issue in 1703.
Anyone else seen this yet?
-
There was also printing problem with 1607 with some type of printers were Domain Deployed printers did not keep their printing preferences see below. (I have all my printers being Xerox, Kyocera and Samsung)
https://support.microsoft.com/en-us/help/3201130/printing-preferences-from-the-print-server-don-t-synchronize-in-windows-10-version-1607There is quite a bit of open issues with Creator's Update
http://www.windowscentral.com/windows-10-creators-update-common-problems-and-fixes -
@dbeato said in Windows 10 1703 and network printers:
There is quite a bit of open issues with Creator's Update
http://www.windowscentral.com/windows-10-creators-update-common-problems-and-fixesThe new version of IE in 1703 broke a ton of shit for crappy old web portals from some vendors.
But this month's Cumultative update resolved them.
-
OK turns out a GP I setup to allow users to install their own printers was now being much more restrictive.
As seen below, I add to add the hostname of the print server, not just the FQDN. Now I can install printers all I want.
-
Nice find!
-
@Dashrender said in Windows 10 1703 and network printers:
OK turns out a GP I setup to allow users to install their own printers was now being much more restrictive.
As seen below, I add to add the hostname of the print server, not just the FQDN. Now I can install printers all I want.
That's a hefty GPO!
-
@Tim_G eh? Hefty? If you say so.
If you're implying that these things should be split apart into multiple GPOs, I probably can, but at the same time, I know that having more than a few GPOs applied to machines can really adversely affect logon times. Consolidating to just a few reduces that problem.
-
@Dashrender said in Windows 10 1703 and network printers:
@Tim_G eh? Hefty? If you say so.
If you're implying that these things should be split apart into multiple GPOs, I probably can, but at the same time, I know that having more than a few GPOs applied to machines can really adversely affect logon times. Consolidating to just a few reduces that problem.
I mean having multiple GPOs should not affect logon times, is the same amount processing. That is a lot that you have on the same GPO with Chrome AMDX too.
-
@dbeato said in Windows 10 1703 and network printers:
@Dashrender said in Windows 10 1703 and network printers:
@Tim_G eh? Hefty? If you say so.
If you're implying that these things should be split apart into multiple GPOs, I probably can, but at the same time, I know that having more than a few GPOs applied to machines can really adversely affect logon times. Consolidating to just a few reduces that problem.
I mean having multiple GPOs should not affect logon times, is the same amount processing. That is a lot that you have on the same GPO with Chrome AMDX too.
Oh that's not correct. When you have multiple GPs, it has to apply them one at a time. When it's one GP (or at least a small number) it's less because you're applying the single policy. Less overhead.
The overhead in processing say 30 policies versus 3 is significant, or at least can be. It might be less of an issue today with 1 gb connections.
-
@Dashrender said in Windows 10 1703 and network printers:
@dbeato said in Windows 10 1703 and network printers:
@Dashrender said in Windows 10 1703 and network printers:
@Tim_G eh? Hefty? If you say so.
If you're implying that these things should be split apart into multiple GPOs, I probably can, but at the same time, I know that having more than a few GPOs applied to machines can really adversely affect logon times. Consolidating to just a few reduces that problem.
I mean having multiple GPOs should not affect logon times, is the same amount processing. That is a lot that you have on the same GPO with Chrome AMDX too.
Oh that's not correct. When you have multiple GPs, it has to apply them one at a time. When it's one GP (or at least a small number) it's less because you're applying the single policy. Less overhead.
The overhead in processing say 30 policies versus 3 is significant, or at least can be. It might be less of an issue today with 1 gb connections.
I never got this line of thinking.
No matter how many policies you have, the number of settig are the same. Unless you have some poorly designed overlapping settings. So everything should take about the same amount of time either way.
-
@Dashrender Take a look below:
https://blogs.technet.microsoft.com/grouppolicy/2013/05/23/group-policy-and-logon-impact/
https://helgeklein.com/blog/2015/11/how-group-policy-impacts-logon-performance-1-cses/
https://helgeklein.com/blog/2015/12/how-group-policy-impacts-logon-performance-2-internals/Performance change is minimal as we are talking about milliseconds
-
@Dashrender said in Windows 10 1703 and network printers:
@dbeato said in Windows 10 1703 and network printers:
@Dashrender said in Windows 10 1703 and network printers:
@Tim_G eh? Hefty? If you say so.
If you're implying that these things should be split apart into multiple GPOs, I probably can, but at the same time, I know that having more than a few GPOs applied to machines can really adversely affect logon times. Consolidating to just a few reduces that problem.
I mean having multiple GPOs should not affect logon times, is the same amount processing. That is a lot that you have on the same GPO with Chrome AMDX too.
Oh that's not correct. When you have multiple GPs, it has to apply them one at a time. When it's one GP (or at least a small number) it's less because you're applying the single policy. Less overhead.
The overhead in processing say 30 policies versus 3 is significant, or at least can be. It might be less of an issue today with 1 gb connections.
Have you timed this? What is the system doing that would cause this? Is there some kind of parallelism inside one GPO but not between them?
-
Thank you JB for shaming me into looking this up.
When thinking about how many GPOs are too many, keep in mind that policy processing only occurs during changes, and "expensive" CSEs like Software Installation, Folder Redirection, or handling a large number of registry policies or setting permissions on large file or registry trees take up the most time. The time spent querying Active Directory for the list of GPOs during core processing is often the smallest part of the processing cycle. So, 30 GPOs that apply to a given user but do minimal registry policy changes and don't change frequently could take less time to process than 5 GPOs that are running expensive CSEs on a regular basis because those GPOs are changing frequently.
https://technet.microsoft.com/en-us/library/2008.01.gpperf.aspx
I stand mostly corrected.
-
While I'm happy to assimilate this new information, I know I specifically read in one of my MSCE books (a long while ago) that it was recommended to have fewer GPOs instead of more granular ones.
Regardless - I have new information in hand and will use it.
-
@Dashrender said in Windows 10 1703 and network printers:
While I'm happy to assimilate this new information, I know I specifically read in one of my MSCE books (a long while ago) that it was recommended to have fewer GPOs instead of more granular ones.
Any chance that it was a third party book and not the MS ones? Sometimes those things inject author's opinions instead of vendor ones. That said, sometimes third party authors know more than the vendors so that isn't a totally definitive statement of anything. But things like MS Press tend to have heavily peer review than other publications and tend to have insider knowledge to double check some things of this nature.
-
@scottalanmiller said in Windows 10 1703 and network printers:
@Dashrender said in Windows 10 1703 and network printers:
While I'm happy to assimilate this new information, I know I specifically read in one of my MSCE books (a long while ago) that it was recommended to have fewer GPOs instead of more granular ones.
Any chance that it was a third party book and not the MS ones? Sometimes those things inject author's opinions instead of vendor ones. That said, sometimes third party authors know more than the vendors so that isn't a totally definitive statement of anything. But things like MS Press tend to have heavily peer review than other publications and tend to have insider knowledge to double check some things of this nature.
Pretty sure it was MS Press that I was reading for 2008 stuff.
