thebicesterschool

10 x blue secugen biometric readers, RFIDEAS converter, power injector and associated leads to connect a thumb print reader to your MFD's usb port. and mount brackets for kyocera 7 x 2551, 1 x 5551 and 2 x 8001 printers. we used these on our kyocera printers with papercut software for 3 years, works well most of the time, as with all biometric stuff, but we're moving to contactless cards, because its easier and cheaper. bio readers are obsolete according to secugen and NRS don't want them back (we own them btw, they aren't leased), and i believe the kyocera taskalfa xxx1 series printers stop production nearly 3 years ago, so there's realistically no way i can sell these. free to anyone who will collect them from Bicester (OX26 2NS) or Brackley (NN13 area) pictures available for anyone who wants them. contact me at the bicester school for more info. [email protected] 01869 354301

I should also add, changing the gpo wallpaper file/name etc doesnt kick it into action (seen that work before on various file related policy settings over the years), neither does setting the policy to copy/replace the wallpaper file - should you choose to copy the file to the machine then apply via gpo, rather than point to a file on a server. Not that we should have to try these common workarounds in the first place. oh, and the bug doesn't seem to be hardware specific, tried a VMware test, physical test on a dell optiplex 380, and dell optiplex 3020.

well the update finally came out on the evening of 25th May, and the fix for this isn't working properly as far as i'm concerned. If you build a new machine, update it, then add to the domain, when it receives the logon/lock wallpaper gpo it applies successfully, so that part is fixed. however if you update an existing domain joined machine, the update installs successfully and afaik fixes a few bugs (scroll bar on logon being one of mine), but the wallpaper is still not fixed. I'm not rebuilding 90 machines that already have this policy guess we'll have to wait another month for them to fix it properly, this issue and Edge browser being a totally unresponsive pain, are the only things holding the rest of my deployment back.

Hi John, I'm doing the same thing and missing out 8/8.1 altogether, i'm a little further ahead of you and just ironing out yet more bugs in the 1703 version of windows 10, but it sounds like you are having one of the same issues i had a while back. First thing i would do before even attempting to configure Windows 10, is get your domain up to at least 2012R2 level and import the .admx files for windows 10 1703. If you're using the start menu .xml file then i'm guessing you have a version of Windows 10 admx files imported already?, there are a few useful updates in the 1703 .admx file, especially for Edge browser, so well worth installing anyway if you haven't. To solve your issue of missing applications, change the GPO setting "Allow deployment operations in special profiles" to Enabled. Located in Computer Configuration/administrative Templates/Windows Components/App Package Deployment.