Unsolved
This post is more than 5 years old
3 Posts
0
4310
May 24th, 2019 13:00
When using a fresh image of 1809 and ImageAssist the loaded laptops cannot view domain printer properties.
We use VM and Image Assist to build our image which I manually load on our Dell laptops. Works great with 1803 as I loaded many of the company's apps and created an image with no issues. I then load that onto laptops and finish setup for the user. I recently tried upgrading that image to 1809 and received errors so decided to do a fresh load of 1809 for a new image. After using ImageAssist something seems to break some of my domain printers for that new image. Upgrading a working 1803 imaged laptop to 1809 also gives the error. A fresh direct install of Windows 10 1809 on the laptop and then loading software at this point does not seem to cause the issue. When clicking on a printer you do not see three options as the broken printers just show manage and remove device with open queue missing. Clicking on manage gives SystemSettings.ViewModel.SettingEntry message with nothing else I can do. Nothing I could find on the Internet gave me any useful information on this error. Comparing the printers with the issue and without doesn't seem to show a pattern nor does reinstalling the driver locally or anything like that help. I was expecting to find a reg change or some other tweak like usual but I am stumped. I upgraded from 1803 to 1809 on my laptop (non-imaged laptop) and I can see everything fine. Any thoughts of things I could try? I have thought about permissions and other items but everything seems apples to apples between the printers.
Oliver_D
1 Rookie
•
2 Posts
0
May 26th, 2019 22:00
Please try this:
rundll32 printui.dll PrintUIEntry [BaseParameter] [ModificationParameter1] [ModificationParameter2] [ModificationParameterN]
Rundll32 printui.dll,PrintUIEntry http://technet.microsoft.com/en-us/library/ee624057.aspx
If the printer driver gets corrupted by SysPrep then install the printer at the end of OOBE phase by unattend.XML
Tim-OH
3 Posts
0
May 29th, 2019 05:00
The printers are not installed during the image process they are added later via GPO which works fine on any image I created upto 1803. Using an fresh 1809 image the printers via GPO show up but are as I had described above. Or upgrading a Dell Image Assist 1803 image to 1809 also causes the same issue. Fresh installs of windows to 1809 or from 1803 to 1809 do not have the issue.
Tim-OH
3 Posts
0
June 11th, 2019 13:00
After some additional testing I noticed that my GPO applied printers show up in two areas under device manager on working laptops. Some show up under Print queues and others under Printers but on a Dell Imaged 1809 system the printers do not show up under "Printers" in device manager but the other working printers do show up under Print queues and work fine. This is using an old DIA and the updated software. Actually there is no Printers category in device manager at all unless I tell the system to search for printers and then it findings them on the network in their generic sense and adds them under Printers. At that point some of them work correctly and others are still missing the Manage option. Any thoughts of why certain printers show up under one area or another in device manager? Might shed some light on other things I need to change somewhere.
Jkett
1 Message
0
January 6th, 2020 10:00
Was there ever a fix for this? We are experiencing this issue also.
DELL-Tyler M
Moderator
•
342 Posts
0
January 7th, 2020 09:00
This is reproducible this without using ImageAssist. Microsoft Sysprep runs as part of ImageAssist process. Manually Sysprepping results in same issue. If you need to have the print queues integrated in the image, take a look at the workaround Oliver mentions in this post. Another option to use GPO's. Here's a recent how-to article that appears to document it.
ScottP.
1 Message
0
October 5th, 2020 09:00
@DELL-Tyler M
We are also running into this issue as the OP.
To confirm, we are not installing printers before creating the image, the image does not have any other printer drivers installed other than the Microsoft default ones. But when we install some of our HP printers, we cannot "Manage" or access the "Printer Properties" or the "Print Preferences" as these options are not there.
Is there any workarounds or fixes for this issue?
Everything works properly before using Dell ImageAssist, but if we lay down the image onto a Dell laptop or desktop, add it to the domain and install the print queue off the server, then this issue comes up. There are some other printers that work properly though.
We also use VMWare to create the image at the recommendation of Dell ImageAssist. I created the image using the Windows 10 2004 ISO and then customized for our environment. For us, this only happens on certain print queues that use the HP drivers.
tkoscielniak
52 Posts
0
October 16th, 2020 08:00
Hello Scott,
Being that the issue you are having is occurring post deployment, after a domain join and print queue is added, and some printers work and others do not, we may not be able to replicate or isolate the issue, anytime soon anyway. I do suggest making sure, if not already done, that the reference image is fully patched before capture and the systems encountering the issue have the latest firmware/bios.
The biggest change to the image that ImageAssist does is running sysprep. Sysprep (A Microsoft tool) has been known to change some things in the image and every now and again break things. I suggest taking the reference image and running sysprep manually (C:\windows\system32\sysprep\sysprep.exe) and check generalize. Then using this image as a test to see if after domain join, it has the same issues. I'm just not sure what else in the ImageAssist process could be causing such an issue.