kidtrebor

The information you've been provided with from your provider isn't accurate. There's a file named client.conf.toml in the following directory: C:\Program Files\PaperCut MF\providers\print-deploy\win\data\config\ In here is a setting called UserIdentityMethod which you should change to "AUTO". UserIdentityMethod = "AUTO" That will allow you to automatically install a printer queue through Print Deploy which originally came from Mobility Print, without having to manually sign in. I assume you're following Papercut's guidance on this page to deploy Mobility Print queues through Print Deploy, perhaps as a way to install drivers without admin rights. I note that this doc also says you can't bypass the login prompt, but I assure you it's possible. I'm doing it in both the schools I manage.

Hi there, I am wondering if anyone has experience of this. At my organisation, teachers noted (no pun intended) that they were no longer able to use cross-notebook distribution since the beginning of term - specifically, they were having problems sharing from a staff notebook to class notebook. After doing a bit of digging, I became aware that an additional plugin is needed to make this work in the current version of the OneNote app; installed it and it worked as expected. Great! I’m now trying to distribute this via InTune as an intunewin package, and the deployment is working, but I’m not sure what detection rule to use so that InTune can confirm success. Does anyone have any experience of doing this? Many thanks indeed. The plugin in question is this one: https://support.microsoft.com/en-gb/topic/install-class-notebook-add-in-for-onenote-app-8d30736e-39ac-40d4-84a9-d6a0b2138182

I have noticed that the print deploy clone tool doesn't recognise a printer queue using a type 4 driver. At my organisation we are keen to move away from using type 3 drivers due to the legacy of Print Nightmare and are reticent to give users admin rights, much less disable the fix Microsoft put in place 3 years ago. Has anyone been able to work around this limitation and deploy type 4 Papercut follow-me queues? Are there plans to address the issue with the cloner queue directly by Papercut? Many thanks indeed. Regards, Robert

Hi, As part of a recent rollout of Windows 10 computers for my client I was asked to include additional keyboards. I did this through group policy user preferences registry keys by adding a new key for each keyboard identifier; for example, 0000040c for French AZERTY keyboard layout. So far so good and I was able to deploy 8 keyboards. There is a 9th keyboard that's in the group policy though - Chinese (Simplified), which I'd also like to deploy, but which isn't selectable from the list of keyboards. It seems like the reason for this is because Windows treats east Asian characters differently from others and the necessary input method editor isn't installed by default, but the only way I can see to set that up is by adding a Chinese keyboard, negating the need for the policy in the first place. I'd like to be able to make this keyboard selectable without end-user input; I can't do it by hand myself because the end-users could log on to any of hundreds of machines in the client's company. I think Group Policy is the only way to achieve it - I tried to add it to the reference image but the config was lost during capture. I'm not sure what else in Group Policy needs to be configured to make this work and wonder if anyone has any experience on this subject? I found this page on Spiceworks and tested importing the registry key - after looking it over I can at least discern that it references the Chinese (zh-CN: Microsoft Pinyin - Simple Fast) IME, but applying the key by the hand to a test computer doesn't achieve the desired result - I can only assume the how-to was relevant for Windows 7 but not 10, which seems, in both concept and execution, to think about keyboards differently than older versions of Windows. My test machine is Window 10 64-bit Education (1909). Regards, Robert