Just posting some CISA links for my own reference.
BOD 26-04: Prioritizing Security Updates Based on Risk | CISA
Known Exploited Vulnerabilities Catalog | CISA
Just posting some CISA links for my own reference.
BOD 26-04: Prioritizing Security Updates Based on Risk | CISA
Known Exploited Vulnerabilities Catalog | CISA
Seems that creating a new local user in Windows 11 isn't quite as easy as you'd expect. But PowerShell makes it fairly simple. To create a new local "backup/emergency" user you can issue these commands from an Admin PowerShell. Of course, make sure to use a good solid password. The second command will add the user to the local Administrators group.
PS>New-LocalUser -Name BackupUser -AccountNeverExpires
cmdlet New-LocalUser at command pipeline position 1
Supply values for the following parameters:
Password: **********
Name Enabled Description
---- ------- -----------
BackupUser True
PS>Add-LocalGroupMember -Name Administrators -Member BackupUser
It should be noted that is you are looking to utilize Remote Desktop on this machine, it will need to be Windows 11 Pro. You can get that info with this command.
Get-WmiObject win32_operatingsystem | select Caption, Version
Caption Version
------- -------
Microsoft Windows 11 Home 10.0.26100
And, to grab your MAK, there's a command for that too:
(Get-WmiObject -query 'select * from SoftwareLicensingService').OA3xOriginalProductKey
I have been struggling with passkeys lately for a couple of reasons.
I have been working fully remotely for many years now and enjoy the flexibility of being about to do this work from just about anywhere I have access to a computer with high speed access to the internet. This means that I can almost sit down in any location with any computer and do the majority of my work without any additional software or hardware aside from my cell phone.
As long as I have access to a web browser, I can do 75% of my daily workload. That means email, Teams, Outlook, and access to a support portal. As you can guess, this requires secure authentication to these services. Secure authentication has changed a LOT over the years and lately it has taken a turn towards "Passkeys".
Now I don't mind depending on a hardware device such as a phone, FIDO key, or other Authenticator service (app) that exchanges anonymous (random) data to allow access to a system (two factor auth). I do have a problem with a service that holds that data along with other data about me and has control over how that data is shared and who has control over that data (myself or the vendor).
Here is a good explanation of the benfits and pitalls of using these Passkeys along with some alternatives.
Here's a great way to validate an RSS feed. It allows you to test and validate the feed as well as offering suggestions to make the feed more readable for a wide range of readers.
https://validator.w3.org/feed/
Here is a great tool for looking up RSS Feeds. I have a couple PowerShell scripts built into PowerNews (https://github.com/loatswil/PowerNews) that do this but it's nice to have a much more thorough online version.
https://www.rsslookup.com/
Is it possible that Microsoft is once again embracing the RSS feed?
Over the years, RSS feeds have come and gone so often that many of them are no longer valid. They seem to change weekly. I have always been on the hunt for new feeds and even written PowerShell modules that pull them, parse them, and spit out a local page for viewing. It's very easy to tailor the feed to your needs including Blocklists and Allowlists.
For a long time now many people have used a popular social media site to display updates when we already had a simple and easy way to publish this stuff. Now it appears that Microsoft at least is moving away from this social media method and back to RSS. Here's the "new" Azure status link complete with "rssfeed" in the URL.
https://rssfeed.azure.status.microsoft/en-us/status/feed/
Let's hope it's the start of a new trend.
How to get information on a Form in M365:
*************************************************
Follow these instructions to clear the cache in the new Outlook for Windows:Close the new Outlook app.
Open the Run dialog by pressing the Windows + R keys together.
Type or paste the following command in the Run box and click OK:
olk.exe --devtools
Be sure to include a space before the two dashes if typing the command manually.



Work Experience :10 - 15 years
So, to break down that sentence, I need to be able to "Own the design of a design".
- Own the definition, design, and delivery of a functional design
Competencies (Knowledge, Skills, Abilities)
Schedule/Attendance
- Ability to work long hours
More times than not, you can fix an Outlook issue by either clearing the cache or starting up with a special switch.
Microsoft allows for many switches that can be run from startup to solves a variety of issues. Here's the link to the page that covers many Microsoft apps.
https://support.microsoft.com/en-us/office/command-line-switches-for-microsoft-office-products-079164cd-4ef5-4178-b235-441737deb3a6#Category=Outlook
I've been working with Teams for years and this is the first time I've seen this method. Perhaps it's a new feature.
Basically, just ctrl-alt-shift-1 will prepare a directory with all of the needed files. You can zip it up and send it off to support.
https://learn.microsoft.com/en-us/microsoftteams/log-files
So, in keeping with the cache clearing theme, here are some instructions on clearing the cache for your local version of Outlook. This can be helpful for a large number of reasons.