@scottalanmiller said in List Windows Printers from PowerShell Command Line CLI:

If you need to remote into a Windows machine and get a list of printers without interrupting the user, this powershell command is quick and easy...

Get-Printer | Format-Table

Make it easier Get-Printer | FT

@gjacobse You should consider publishing this and others (sanitizing of course) to GitLab or GitHub. It can serve as a reference for you as well as a bit of a portfolio. I know for a fact my GitLab stuff had a positive effect with helping me land my current gig.

@syko24 said in Move FSMO Roles Using PowerShell | Active Directory Domain Controller AD DC:

I'm a fan of the one liner assuming you are transferring all roles to the same DC.

Move-ADDirectoryServerOperationMasterRole -Identity "DC-Server" -OperationMasterRole 0,1,2,3,4 0: PDCEmulator 1: RIDMaster 2: InfrastructureMaster 3: SchemaMaster 4: DomainNamingMaster

Me too. This is what I normally use. SOOOO helpful.

Not sure why powershell made it so complicated to find who has the roles.
netdom query fsmo was so easy.

There is a ppd you can use for cups in the Mac driver.

Primera LX900 - ColorLabelSugned - Payload~~ - Library - Printers - PPDs - Contents - Resources - CL900.ppd

@Pete-S using your little snippet did not clean up the pinned start menu of the initial admin user that ran it, nor the non admin user account that I subsequently created.

f2e6d053-0b72-4407-9ba8-b1d9dd3d75c8-image.png

It xbox was still in the start menu, but the rest looked gone.
da69b05a-32c4-40e7-ba6d-03ae78e2b092-image.png

@DustinB3403 depending on what you want, you can also:

$app = Get-ChildItem -Path 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall' | Get-ItemProperty | Where-Object -Property DisplayName -EQ "Microsoft Edge" $installDate = $app.InstallDate

As an update the solution for Windows 11 now also works for Windows 10 if you are on Windows 10 22H2 and fully updated.

3ecd352e-4e80-4d97-bb2a-742ae38d326a-image.png

@dashrender said in Server 2012 R2 not installing Updates:

@scottalanmiller said in Server 2012 R2 not installing Updates:

@dashrender said in Server 2012 R2 not installing Updates:

Of course though - this thread is about Windows Server, not desktop - where this should be MUCH less of an issue with properly designed code.

Same code, they don't make it twice. Less hardware hotplugging, but probably just as many lines of code in use.

Less desktop apps on the platform, but you're right - the base code is the same.

Fewer desktop apps, maybe. But in the Windows world, server often is treated as a desktop (like 90% of the time) so the reduction is rarely what you'd hope. And there tends to be lots of server-only code too, often running as desktop apps.

@obsolesce

That is pretty cool. I will give that a try this morning.

@obsolesce said in Use powershell to create a scheduled task to reboot computers on schedule:

@pete-s said in Use powershell to create a scheduled task to reboot computers on schedule:

@jaredbusch

For logistics, I would also place scheduled tasks that I created in their own task folder. Just like Microsoft and others have.

That way I know the tasks in there is not generated by something else.

One could also fix the description to say the source of the task. I get the appeal of placing them in their own folder nested somewhere in that mess, but it's so much easier to deal with them in the top level directory.

I guess you could fix the name. But it's mostly misbehaving apps that put tasks in the top level directory. I mean Microsoft added the folder structure for task organization. It wasn't there in the old days.

But yeah, it works regardless.