Darylrese

Nope. We have turned most our printers mono only but admin need to switch between them. Could do a mono driver and colour but i don't think they will be happy keep switching printers!

Anyone please?.... Got the drivers working now, just need to get the user prompt for colour / mono sorted.

Hi All, We just got a fleet of HP P55250DW printers which have colour capabilities, however i only want people to print in colour if they really need to. Is there a way to script PaperCut to pop up and ask if the user would like to convert the print job to greyscale or continue to print in colour? I have tried a couple of the built in recipes such as convert email to greyscale from outlook but although it says your printing has been converted to greyscale, it still prints in colour anyway!

WOOHOO it's building! Just need to check if there are any drivers missing once complete.

OK think im getting somewhere. I just made another clean x64 boot image with no drivers atall, then it said no network driver found. I installed only the newest network driver and its started!!!! I'm going to add the drivers 1 by 1 until i find the culprit. Looks like a conflicting driver somewhere.

Yep working fine if i run the installer.

Already got that one injected mate, not working. I tried manually dismounting the image and adding it and that didn't work either.

OK strange. So i built the SSD in another machine, put it into the ProDesk 400 and the KB and mouse dont work because no USB 3.0 driver. Installed that using a PS2 keyboard and the network driver is already installed and working without installing one from my USB. So here is a screenshot of device manager after installing all the drivers i have. The only thing i can see is missing is PCI drivers. In the driver info for the network adaptor, it lists PCI\VEN_10EC&DEV_8168&SUBSYS_8062103&REV_15 but in the .inf for the driver that is not present; ; 8168 %RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&REV_01 %RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_816810EC&REV_01 %RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_30B6103C&REV_01 ;HP Notebook %RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&SUBSYS_30CC103C&REV_01 ;HP Notebook

OK so the Windows 7 x86 boot image didnt work either. I'm going to install Windows 7 on the SSD in another computer and install it back into the ProDesk 400 to see if the driver is missing once complete. I'll then try and install the driver once i am in Windows 7 to verify its the correct one. I only have 1 of the new ProDesk 400's at this point as i was trying them out before i bulk order. At this rate ill be buying some older chipset PC's just to avoid all the hassle!

Nope, i have already tried a new boot image with only the drivers for this PC and no luck. Just trying a 32 bit boot image as we speak to see if it likes the 32 bit driver

I just tried a Windows 8.1 boot image and that has the same error. I'm going to also create a x32 boot image for Windows 7 just to test. I cant get into Windows to check the driver ID at the moment as i wiped the SSD when installing Windows 7 through the Windows 10 boot image.

Thank-you. It said the command was successful but still has no address or network adaptor listed when performing ipconfig Its a x64 boot image and x64 Windows image. I have added the drivers to the driver packages, thern right clicked on boot.wim and add driver packages to it. Still no luck. Worth mentioning again, it works fine with a Windows 10 boot image and builds but gets stuck in a loop when performing the OOBE stage.

Thank-you very much, that's very kind of you! This looks like the exact driver i have injected already, however i just added it anyway but unfortunately its still coming up with the same error I'd say its 100% the correct driver too. Basically, i am adding the driver package using the Windows Deployment Services Snap in, then right clicking on the boot image and adding drivers to that. It seems to have done the trick for USB 3.0 drivers, display drivers etc its just the network adaptor thats having the issues. Are your HP ProDesk 400's the i5 6500 model? Many thanks again

Excellent thank you very much

I don't have a 32bit image, it's a 64bit boot image and a 64 bit Windows 7 image. Yes I've tried downloading drivers from HP, Realtek and other sites. My next idea was a USB or add in card network adaptor and see what happens but that's not practical if we are going to buy them in bulk

Still no luck with this. Its making a lovely expensive paperweight in my office at the moment. I have injected all Windows 7 drivers for the PC from Hp's website and the RealTek website. They only work in conjunction with a Windows 10 boot image but we aren't running Windows 7 at the moment.

I have created a Windows 10 boot.wim, booted from that and its working. Its just installing Windows 7 x64 now but i expect it wont work as above.

1) Yes all other devices build fine 2) Yes all up and running 3) Yes and works for all hardware except this new PC 4) I have both x32 and x64 drivers, no luck. I might just buy a PCI-E NIC and build it with that in. Once its up and running remove it and install network driver. Bit of a pain especially if we were to roll these out across the site.

Ah man. Can you build a Windows 10 Boot.wim and deploy Windows 7 image within it?

Already done that, no joy.

sorry, i found that screenshot on google images as i couldnt be bothered to take a screenshot and upload myself The boot.wim is Windows 7 Enterprise x64 Yes its Skylake, HP ProDesk 400 G3 SFF. i5-6500, 4GB Memory, 128GB SSD

Morning all, Before I throw this PC out the window, anyone know what's going on here? Got a brand new PC and trying to install a WDS image of Windows 7 onto it but keeps coming up with this error I have injected all the drivers into the boot.wim including all NIC drivers for that PC from HP's website. All other PC's and laptops are imaging fine so it's not a problem with the deployment or images themselves. I have checked device manager to see what driver is currently installed and working on the PC's standard Windows 10 build and it matches the drivers i injected into the boot Many thanks

Not confirmed no but the member of staff checks her home email at work so i think it came through on an email. It renamed everything to .mp3 including all her documents, all SIMs docs and system files and some of the shared drive. Luckily for me i take good daily backups and just restored everything over night and we were back up and running.

Excellent! We had it about a month ago and it encrypted our SIMs drive and a staffs home directory, was a total pain! Glad to hear its no longer a real threat.

Hi All, Just recently, on start up a lot of machines are hanging on 'Applying Wireless Group Policy Policy' for at least 10 minutes on start up. However, this policy does not exist anywhere in my group policy structure. If I reformat a machine, this GPO is not processed at all and login is as expected. I have been through ALL of my GPO's and none of them have wireless settings specified. Nor have I ever pushed out wireless settings via GPO. Any ideas?