Ruan

Can only think it's pants drivers, have ended up having to put on Kyoceras generic PCL driver for it and now have to run PaperCut for accounting, seems to fix all the issues we originally had - just poor "KX" drivers by Kyocera!

Exactly the same happened again Cannot work out this problem, even with different driver versions it's doing the same thing, on different servers it's happening, I can only think it's an inherent fault with the drivers that isn't fixed by different releases!

Hello all, Got a primary school running x2 03SP2 Servers with a Kyocera TaskAlfa 400Ci printer in their reception, where all their printing is done. They have enabled the "Prompt for Job Accounting ID" option, so when something is printed it prompts the user for the number for where it will be charged to. Works ace as the kids can't print unless the teacher is there. However it constantly seems to lose this setting and revert to not entering the ID - hence the printer doesn't print as there's no account... We originally had an issue where it kept losing the drivers, you'd go into the Printer Properties tab, we even had workstations bluescreen, give addressing errors etc whilst trying to open the Printer Properties... All sorts of wierd issues, but it seemed to actually be Sophos deciding the driver was a nasty and promptly removing it... It's never been quite right since! I've tried holding the printer on either server and it's always the same issues. It usually works for about 4 days or so and after that it'll stop. Any help is appreciated! Thanks

I'll definitely give that a go now... Though I'll admit our Print Server is due for upgrade to 2008R2, we'll give this one last go, if we still get issues then I expect we'll just go straight for an upgrade and pray that helps. Thanks for everyone's help.

1. Only ever windows 7, we have XP machines on the same network, but these never get this problem. 2. Probably once a day, I could probably replicate it with logging on and off a few times! 3. Usually less than a week, it's fairly common. 4. A while ago, probably a few months, but nothing really seemed to set it off? 5. Printers are deployed to OUs with the machines inside of them.# Thanks for your help so far!

1. It seems to error out when it connects via GPO, then will not connect via directory either. 2. Same as above, gives the error when you try and add it via the directory, or even if you add it via the UNC path. 3. Not readily, seems to be random. 4. Fairly random, some machines are worse than others, but I think that might be co-incidence that people print and therefore notice it from those machines more. 5. Not that I can see, server nor client. 6. Definitely works at times but then will randomly break again, restart the machine and it'll usually be OK, but might require 2 restarts to make it work.

No ideas on this?! I'm completely stumped with regards to this now, I know a few teachers are getting a bit upset at there often being no printers installed!

Hi all, We've currently got a single print server running 2003 R2 with all of our printers on, the printers are deployed via GPO, though on some machines, often certain machines, but generally random, the printer won't be added... Sometimes you can just go to the Directory and add the printers and they will be fine, but most of the time it'll start adding and come up with "Windows cannot add this printer, The Specified Port is Unknown" - usually the user has to do a restart and sometimes the printer will come back, other times they'll have to use a different machine to even print... It does it to all sorts of printers - Kyoceras, Canons, HPs, Epsons, it doesn't seem to be just one printer which makes me think it's not a driver issue, however I'm not going to rule it out... Any help would be amazing! Thanks, Ruan

OnError 0 1 .\Images\PBEC\win7image-(2).wim /image/index 1 false 16 1024 60 768 OnError true en-US 0409:00000409 en-US en-US en-US true http://lalala.lalla.cornwall.sch.uk false EnableAdmin 1 cmd /c net user Administrator /active:yes UnfilterAdministratorToken 2 cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f 0409:00000409 en-US en-US en-US 0 "" 1 9 9 1 "" "" "" Default 1 lalalalal true Temp account Temp account Users TempAccount true Administrator . lalalalala true 999 32 1024 60 768 cscript.exe C:\MININT\Scripts\LiteTouch.wsf /start Lite Touch new OS 1 cscript.exe D:\MININT\Scripts\LiteTouch.wsf /start Lite Touch new OS 2 cscript.exe E:\MININT\Scripts\LiteTouch.wsf /start Lite Touch new OS 3 cscript.exe F:\MININT\Scripts\LiteTouch.wsf /start Lite Touch new OS 4 true Work 1 true Pool Business and Enterprise College ICT Dept 0409:00000409 en-US en-US en-US \Drivers Hope this helps!

It would appear that only on certain machines whilst installing Windows 7 Pro (some HP DC5850s only) the install all goes fine and under Applying System Settings it will error out with: Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup] I've ran it on some older Dell GX520s and they seem to image absolutely fine, it only seems to be certain DC5850s, we spent a good few hours playing about with the answer file originally assuming it had generically "broken", but then found some other machines would image fine...? Any ideas? I can post the unattend file if needed. Cheers, Ruan