GaryPad

EXE to MSI has a free version if you still want an MSI.

You could try adding a new printer, use LPT1, and for the driver select "Generic" in the manufacturer and "Generic / Text Only" for the printer and ensure when printing that you print to file. That will at least get you text output, although you might have to get Excel to format it nicely depending on the structure. Sorry but I don't knwo Accelerated Reader so I don't know what options it has for export or print.

This product is pretty good too SwiftView

Unfortunately Method I saves all the emails into a single PDF file. I think that selecting multiple emails in Outlook and then printing always puts them into a single file. If your email is local, i.e. not in 365, you could look at scripting the MAPI interface but as far as I can tell it will only save to text or HTML so you'd still have to do some sort of conversion, e.g. using Word. Below is a VBScript which if you save it to a file with a .VBS extension, edit it in a plain text editor (like NotePad or better NotePad++) and change the lines which are in bold (or make sure there is a C:\test folder) and also for what exactly to search for in the email subject, it should output to HTML and then get Word to save the email to PDF. Open a command prompt to where you've saved this VBScript and run it with CScript.EXE Set objOutlook = CreateObject("Outlook.Application") Set objFSO = CreateObject("Scripting.FileSystemObject") Set objNamespace = objOutlook.GetNamespace("MAPI") Set objFolder = objNamespace.GetDefaultFolder(6) ' 6 is the Inbox folder Set colItems = objFolder.Items Set colFilteredItems = colItems.Restrict("[subject] = 'My SAR request'") intMessage = 1 strOutputPath = "C:\test\Email " For Each objMessage In colFilteredItems strHTMLFile = strOutputPath & intMessage & ".htm" Set objFile = objFSO.CreateTextFile(strHTMLFile, True) objFile.Write objMessage.HTMLBody objFile.Close Set objWord = CreateObject("Word.Application") objWord.Visible = False Set objDoc = objWord.Documents.Open(strHTMLFile) objDoc.SaveAs2 strOutputPath & intMessage & ".pdf", 17 ' 17 is the constant for wdFormatPDF objDoc.Close False objWord.Quit If objFSO.FileExists(strHTMLFile) Then objFSO.DeleteFile strHTMLFile,True intMessage = intMessage + 1 Next If you want to use a different folder to one of the standard ones, like the InBox, then you change line 5 to: Set objFolder = objNamespace.Folders("[email protected]").Folders("SARs").Folders("Joe Bloggs") Where the first is your email mailbox, the second is sub-folder "SARs", and the third could be another sub-folder for "Joe Bloggs". Hope this helps.

Commercial - based in Cheltenham - are a good local dealer (I know Stephen Lockyer there). I'm not sure of the whole range of manufacturers they sell, but they definitely do Canon, and I know of a couple of schools they've supplied if you want references.

Whilst Printix would provide good cloud print connectivity, you still have a to select a print driver, and this is where you appear to have a problem. "Our outsourced IT support say the printers are local TCP/IP port installed." - ouch! So you have up to 40 staff all doing direct printing? Not nice to manage! Your first problem to resolve is the choice of print driver. I suggest you install 2 print queues on 1 PC for that C7120; one printer using the PCL6 driver, and the other using the PostScript driver. Both can use the same output TCP/IP port. Then print the same test document to both. If they output identically then you can rule out the driver as the reason for the colour difference. You can then get your outsource IT (who will probably call on Xerox) to come in and tweak the colour matching on that device as it won't have been done on installation. As to which driver to use going forward I would suggest that if you do lots of printing of Office documents then PCL6 is fine. If you do lots of PDF printing or high quality image output, then PostScript gives you more flexibility on colour profiles (I'm guessing PCL will be perfectly fine). How are you deploying these new devices? A print server would be the solution, and this doesn't have to be an actual server, just any PC which is invariably on can host shared print queues so rather than users connecting direct, they print instead to the server which mean your configuration for drivers etc. is all in one place. Plus users don't need additional rights to install local printers on their PCs. I don't know anything about XDA I'm afraid. Looking it up, this is Xerox Device Agent and yes, it's Windows software. It appears to do meter readings and I guess replacement toner ordering, and both your models are supported. This boardroom laptop appears to have been suggested as the place to install XDA but again any always on PC would do the trick. The reason "old printers are still showing up." is because every user has their own direct connection to printers, which is a nightmare to manage, so any old devices will unfortunately need to be deleted manually, as indeed any new devices also need to be installed manually. This is where something like Printix would make deployment much easier, but as you say, it's more software and more cost.

There's a central cost for the print room software which is priced per server (so invariably 1!) and then you buy blocks of client licences depending on how many users need to send ticketed jobs, so the cost per user for larger organisations is pretty cost effective. I don't have pricing I'm afraid as we don't usually sell direct, but it's sold by several channel partners of ours including Ricoh, Sharp, ASL, Apogee, Agilico, UTAX etc. If your current MFD supplier cannot provide you with a quote then please PM me and I'll get someone to contact you.

Can I suggest you have a look at docQticket? It's a proper job ticketing solution, so it's not just about submitting a job with a ticket: it provides full management in the print room. Jobs are automatically priced, and best of all it also integrates with PaperCut (and others like Equitrac / Kofax, MyQ, SafeQ, Streamline NX, aQrate) so you can have the print room jobs automatically charged back to shared accounts and reported on within PaperCut. Full disclosure: my company makes this. Ticketed jobs can be submitted via printing (from Windows or Mac), uploaded via the browser, or emailed, and it will work with any Windows supported printer in Reprographics.

I'd second Daveit2005. If inkjets aren't used for any length of time then the heads clog up on the cartridges so you have to replace them. Laser buying costs are higher than inkjet, but running costs are considerably lower, and you can have one idle for months and it will still work (although the paper might dry out and jam ). Unless the SLT member can justify colour printing I would get them a cheap monochrome laser; doesn't even have to support duplex, and then force them to print to a departmental colour MFD when they have jobs that need it.

If you go into the Sharing option on the print server (select printer, Properties), what do you have for the checkbox "Render print jobs on the client computer" (it's normally enabled)? Try disabling it and make sure under the Advanced tab that "Enable advanced printing features" is enabled. If it's actually configured as I've suggested, then reverse it! i.e. enable rendering on the client and disable the advanced printing features.

"Have they suddenly become useable" ... debatable! The idea is that Type 4 are effectively managed by a text file and all the heavy lifting is built into the o/s. That means the attack surface of the printer driver is almost zero. Unfortunately manufacturers don't see the need to invest in print driver development anymore because they did all that years ago. Type 4 drivers, whilst maybe not as fancy as Type 3 (although they could be if the manufacturer could be bothered) should still have the same accessory support for finishers, folders, punchers etc though. If you install a Type 4 "Class" driver (i.e. it works for a whole range of models and uses bi-directional chat to work out what the device on the end of the line can do) it then reconfigures the driver options automatically. It's worth checking on the Lexmark website as they might not have bothered going through Microsoft's validation programme and instead offer it from themselves direct. If you can find a signed monolithic driver - i.e. model specific - that will invariably look better and have all the options (and be more "usable" ). Also try the Microsoft Update button which is on the "Choose your printer from the list" dialog as part of adding a new printer.

Ouch! MS likes all Type 3 drivers to be signed these days (after the PrintNightmare fiasco). Old drivers are probably not signed. See if you can find a Type 4 driver for the Lexmarks. Otherwise shout very loudly at your print provider! Kyo drivers will not be compatible with Lexmarks so you can't just leave them in place.

Change the default printer to something else. It might narrow down which printer driver is causing this.

PCL-XL over PCL5. PCL5 came in 2 flavours - one for colour (5c) and one for mono (5e) - whilst PCL-XL / PCL6 doesn't differentiate; PCL-XL produces more efficient code; has better graphics compression support; supports more colour spaces including spot colour; handles vector drawing better (PCL5 married the older PCL4 format page description with the old pen plotter HP/GL language to produce a hybrid language whereas PCL/XL started from scratch to do away with any inefficiencies). It was just a shame it got tagged as "PCL6" even though it's a completely different page description language. And yes you can just swap the driver in use on the queue through the Advanced tab (for an existing v3 Windows driver).

If you open up the queue Properties on the server and under Advanced tick the option for "Keep printed jobs" you should be able to see if they even arrive on the queue (turn this off after testing and delete all the kept jobs). The other useful tip is to run the event viewer (EVENTVWR.EXE) and expand Applications and Service Logs | Microsoft | Windows | PrintService, then right click on Operational, and under Properties you can Enable logging. This will add to the event log all future print activity so you can see what's going on (if anything!). If all that activity looks good - so jobs are arriving on the queue and then being printed - then you might need to check the logs on the printer itself, normally accessible through the printer's web page or printing off a log from the front panel if you can log in as an admin. Possible reasons why the printer will fail to print include: 1. Wrong driver (which would be consistent for all users) 2. Not enough memory (vary by job, especially affects wide format and / or printing multi-layered PDFs especially printing PDFs natively within Chrome / Edge) 3. Corrupted print data (v rare these days but not unheard of!) 4. Print release enabled in the driver (some drivers support PIN printing - much like a print management tool) so the job will go to the printer and be held there There are 2 settings on the queue properties which can have an effect as well. Under Advanced is "Enabled advanced printing features" and under Sharing is "Render print jobs on client computer". If the former is unchecked or the latter is checked then the job will be rendered to a printable version on the client. Otherwise it's done on the server. I've seen Xerox drivers in the past not like booklet jobs rendered on the client, so to fix it we had to enable advanced printing and disable rendering on the client. Worth a shot. Also try to determine which jobs are failing and where they are printed from - e.g. if PDFs in the browser then try opening them and print from Acrobat instead.

Open the Xerox print queue, go to the Advanced tab, and try turning off the checkbox at the bottom for "Enable Advanced printing features".

You say the paper guides are correct, so if you look at the front panel or access the browser then does it show the paper size correctly and which way round it is (it might say something like LEF meaning Long Edge Feed as opposed to Short Edge Feed; basically portrait feeding rather than landscape feeding)? If they've been set the wrong way round then this will cause this error. Otherwise as it's happening on both trays it could be a pick sensor. They're basically sensors that shine a light across the feed path of the paper so when the beam is broken the printer knows that the paper is in transit and when the light shines again it knows that it's gone passed and therefore hasn't jammed. If you've got paper dust on the face of the sensor then it could be detecting a rogue jam. Look for these sensors throughout the feedpath and use alcohol to clean the face of them. I don't know if the fuser unit is replaceable on that model but a common area of jams is torn paper being stuck between the fuser rollers. A quick test is to swap the fuser unit with a working printer.

Sorry but I don't think the colour detect feature is what you're after. It's just reporting whether the page has any colour on it or not, not the percentage coverage. Your best bet would be something like the Print Archive and then analyse the resulting images for coverage. The only problem is that this process isn't going to be fast so is unlikely to work real time enough to block a job. It may sound odd but does it actually matter? Unless you have an inkjet so you're paying for the ink used, if it's a laser printer then you're just paying for a click charge which doesn't care about how much toner is on the page.

I don't believe there is a specific policy for this. You can mitigate, for example the policy Local Computer Policy | Computer Configuration | Administrative Templates | Printers | Limits print driver installation to Administrators - might help. There's also User Configuration | Administrative Templates | Printers | Prevent addition of printers which "Prevents users from using familiar methods to add local and network printers....However, this setting does not prevent users from using the Add Hardware Wizard to add a printer. Nor does it prevent users from running other programs to add printers." so users should be able to add network queues by mapping to \\print_server\share_name or by having scripts do this for them, but they would lose the familiar Add Printer wizard.

PCounter uses a custom port monitor, and as part of the transition from Type 3 drivers in Windows to Type 4 class drivers, my understanding is that these will no longer be supported (you're supposed to use the print pipeline instead). It's possible that Windows 11 mandates against custom port monitors completely? Can you set up a shared test printer that just uses a Standard TCP/IP port and try adding the connection to that? If you can then it must mean an issue with the custom port monitor. If you're not using the PCounter popup utility you could try using an interim queue to print to: with that shared test printer, change the port on it to be a local one: \\server.fdqn.edu\Sample Printer and then see if your Windows 11 clients can print to that. It means doubling up on your queues - so clients print to that one which spools and then prints to the actual queue with the Pcounter port monitor on it, but as it's all local on the server it should be pretty quick. Check with PCounter as to whether Windows 11 is a supported operating system.

I don't know if this is of any help but this PowerShell script will create a self-signed certificate (SHA256) and assign it to HTTPS (port 443) on IIS. It also exports a .CER file to the desktop which can be distributed to clients. It will also restart IIS so you might want to do it out of hours. Obviously change the name of it from "My Certificate" to the name of your choice, and the password for importing the .CER file. A better solution is, as suggested by Norphy, a publically signed certificate. $CertName = "My Certificate" $CertPassword = "password" $DefaultSite = "Default Web Site" $PC = hostname # Get defaults like Fully Qualified Domain Name, and Present Working Directory $FQDN = [system.Net.Dns]::GetHostByName((hostname)).HostName; $PWD = Get-Location | %{$_. Path }; $Destination = [Environment]::GetFolderPath("Desktop"); # Certificate location $CertRoot = "cert:\LocalMachine\My" # Generate encrypted password $Password = ConvertTo-SecureString -String $CertPassword -Force -AsPlainText; # Generate certificate $Thumbprint = New-SelfSignedCertificate -DnsName $PC,$FQDN -CertStoreLocation $CertRoot | FL Thumbprint | Out-String | %{ "{0}" -f $_.Split(':')[1].Trim() }; # Set the friendly name for it $Certificate = Get-Item -Path "$CertRoot\$Thumbprint" $Certificate.FriendlyName = $CertName # Bind to the website Import-Module WebAdministration $Binding = (Get-WebBinding -Name $DefaultSite | where-object {$_.protocol -eq "https"}) if($Binding -ne $null) { Remove-WebBinding -Name $DefaultSite -Port 443 -Protocol "https" } New-WebBinding -Name $DefaultSite -IPAddress "*" -Protocol "https" -Port 443 (Get-WebBinding -Name $DefaultSite -Port 443 -Protocol "https").AddSslCertificate($Thumbprint, "My") Start-Process "iisreset.exe" -NoNewWindow -Wait # Export to the desktop Export-Certificate -Cert Cert:\LocalMachine\My\$Thumbprint -FilePath "$Destination\$CertName.cer" Note that if clients still attempt connection on HTTP then the server will still accept those requests. If you want to redirect all HTTP traffic to HTTPS then you will need to install the IIS URL Rewrite module (Google where to download that from) and edit the web.config file for your web site (usually somewhere within the C:\inetpub\wwwroot folder) to add in the following inside the //configuration/system.webServer node:

It might be worth logging into the web server on the MFDs as an Admin to see if there is an override possible on them to convert Letter to A4. AFAIK PaperCut cannot modify the paper size of the job so you would have to just delete it. This script should do the job: /* * Cancel jobs that print Letter size */ function printJobHook(inputs, actions) { if (!inputs.job.isAnalysisComplete) { return; } if ( inputs.job.paperSizeName === 'LETTER'){ actions.job.cancelAndLog('Not allowed to print Letter sized print jobs.'); // send a message to the user actions.client.sendMessage('Letter sized job DELETED.\nPlease reprint as A4.'); // log a message for debugging actions.log.debug('Cancelling job from user ' + inputs.job.username + ' because the paper size is ' + inputs.job.paperSizeName); } }

Looks like your file has been saved incorrectly. I've uploaded it to here: http://www.filedropper.com/word2pdf just remember to turn on popup blocker as this site is quite annoying! Right click and choose Edit once you've downloaded it to check it's the same content as I posted above. I would recommend looking at a decent text editor like NotePad Plus Plus as sometime NotePad can save text files as an incorrect type (annoyingly not all text is the same!).

Copy the following code into NotePad and then save it as a file with a .VBS extension (VBScript). As long as you have Word installed you can just drag and drop a folder onto this file and it should 1) Open Word, 2) Add each .DOC and .DOCX file from that folder into it - in alphabetical order - and then 3) Prompt you for the name of the PDF to save it as; in the same folder. It's pretty simplistic but does the job. The only issue I've noticed is it doesn't cope if the first page it adds is landscape, but if subsequent ones have landscape content then it sets the orientation fine for those. Set Args = WScript.Arguments strStartFolder = Args.Item(0) Const wdFormatPDF = 17 Const wdDoNotSaveChanges = 0 Const wdPageBreak = 7 Set objWord = CreateObject("Word.Application") objWord.Visible = True Set objDoc = objWord.Documents.Add() Set objSelection = objWord.Selection Set objFSO = CreateObject("Scripting.FileSystemObject") Set objFolder = objFSO.GetFolder(strStartFolder) Set colFiles = objFolder.Files For Each objFile in colFiles Set objFSOFile = objFSO.GetFile(objFile.Path) strExtension = UCase( objFSO.GetExtensionName(objFSOFile) ) If strExtension = "DOCX" Or strExtension = "DOC" Then objSelection.InsertFile(objFile.Path) objSelection.InsertBreak(wdPageBreak) End If Next strOutputFile = InputBox("What name do you want to save the PDF as?","PDF NAME",objFolder.Name & ".pdf") If strOutputFile <> "" Then strSaveAs = strStartFolder & "" & strOutputFile If objFSO.FileExists( strSaveAs ) Then objFSO.DeleteFile strSaveAs,True objDoc.SaveAs2 strSaveAs, wdFormatPDF , , , False , , False , True End If objWord.Application.Quit wdDoNotSaveChanges

I believe if you login with your cached AD credentials then if you are not a local admin then you cannot add local printers - only network shared queues. Local login bypasses that so you can usually install local printers.