Important
To filter the blog, please use theses tag:
General news.
Website related post
website.
parental-control about technology.
technology post.
Note
All blog links are archived here.
Hi
Today I will share a tip if you need to reset a lot of printers share to the default security.
It come handy to me as if you secure too much your pritnqueue,it might block per computer GPP in example.
First, choose a printer that will be the template for all others.
Make sure Administrators, Everyone, Creator Owner, Print Operator and Server Operator is listed.
It should look that way;
First picture in workgroup, and second you add those accounts in domain.


After your template is done, you need a small powershell script, it look that way;

$printerperms = (Get-Printer -ComputerName PrintSvr -Name admin-printer -Full).PermissionSDDL
$allprinters = Get-Printer -ComputerName PrintSvr -Name * | Select name -ExpandProperty name
foreach ($printer in $allprinters)
{Set-Printer $printer -PermissionSDDL $printerperms -ComputerName PrintSvr}
Make sure to replace PrintSvr with your print server and make sure to replace admin-printer with the printer that you used as a template.
Thats all, Thanks for reading!
Hi
Today I wanted to talk about a small bug you might encounter if you do printers GPP per computers. Such GPP create a local printer port, usually TCPIP, but need a printer share to set the driver and option.
The error is not documented much, but it's the error 0x800700005.

That error is caused by a lack of security for the computer account to access the printer's share for the initial setup. I seen that case on customers where the printer share are more restricted between users.
To resolve the issue you need to set back everyone into the printer security, like shown there;

Make sure that everyone is there (and CREATOR OWNER too)
That change should make your GPO work
If you install that update on a Domain Controller, please make sure you install the outofband update KB5010791 !
It apply to Windows 10 Enterprise 2019 LTSC, Windows 10 IoT Enterprise 2019 LTSC, Windows 10 IoT Core 2019 LTSC and Windows Server 2019
Information Link; January 18, 2022—KB5010791 (OS Build 17763.2458) Out-of-band
Hi everyone !
Today I wanted to share another tip. It's something I see a lot in help desk call, and sometimes it make call a lot longer to not know that one.
It's for the managed credential in the Windows Account's store.
You could be renaming an account on a Domain Controller, or it can be a pass through user set for authentication, but changing it can break thing.
The tip is just to never forget to go there and delete the cached credential that give you problem;
You can see my answer there, and it's something useful to know :)
Hi everyone
Today I wanted to share a small tip that can help if your server is stuck on reboot with a Windows patch that don't want to terminate.
Please use with precaution the tip to not loose data or break the OS.
In my case it was useful on a Windows Server 2019, as it was stuck for 3 hours and more, and the CBS log was growing indefinitely.
You can use ps exec, but we have tasklist that support a remote computer.
To use that way;
tasklist /s remote_computer with the username and password. /u domain\username /p password
tasklist /s remote_computer /u domain\username /p password
After the command we got a list with all PID.
To stop the Windows Update, in my case I had to close Windows Installer service.
The command is the same, except we give to it the PID, or we could use the /im parameter to target the executable image name. (/f force the closure)
taskkill /s remote_computer /u domain\username /p password /pid PID /f