Search the Community
Showing results for tags 'Network Printers'.
Found 2 results
Having trouble pulling the mapped network printers for a user; here’s what I have done so far: On a test computer ran the attached (zipped) SCCM_REGINI.txt (with regini.exe) to build a registry structure to pull the users network printers (from the CURRENT_USER hive) to a hive called SCCMINV (in LOCAL_MACHINE). Ran the attached VBS script (SCCM_PRINTER_INV.vbs) to copy the network printers to said hive. Modified the ‘configuration.mof’ file to look in the hive for the information. Modified the client agent settings to pull information (classes) from that hive. I still can’t seem to find the SQL table in my SCCM DB. Anyone have any ideas on where to start? I have verified the classes being copied on the test client logs: All the scripts are taken from: http://myitforum.com/myitforumwp/2011/11/23/howto-printer-inventory-script-w-network-printers/ See attached ZIP file.And verified with: http://schadda.blogspot.se/2012/02/sccm-2012-customize-extend-hardware.html SCCM_Printer_Inventory1.zip
Hi all, I created a USMT scenario which worked fine for data/setting transfers between Windows 7 and Windows 10 (1511.) I've updated our image to the new Windows 10 (1607). From then on the problems with the migration started. In my test case, only 1 of the 7 printers are transfered to the new Windows 10 (1607) image. Bofore that (transfer to 1511), all worked fine. I use the following xml code for the transfer: <!-- This component migrates network printers --> <component type="Documents" context="User"> <displayName>Mapped Printers</displayName> <role role="Data"> <rules> <include> <objectSet> <pattern type="Registry">HKCU\Printers\Connections\* [*]</pattern> <pattern type="Registry">HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows [Device]</pattern> </objectSet> </include> </rules> </role> </component> The loadstate.log is exactly the same on Windows 10 1511 and Windows 10 1607. It seems that Windows 10 1607 handles the printers (or drivers?) differently? Is anyone else having problems with printer migration to Windows 10 (1607)? PS: Already tried the USMT from ADK 1511 and USMT from ADK 1607, both give the same issues.