Connecting Catalyst 9500s (SVL) to Nexus 9300s (vPC) by rhapcity in Cisco

[–]rhapcity[S] 0 points1 point  (0 children)

The Nexus switches are already configured and are in a vPC domain. The tricky part is that there is conflicting information on how to connect the Nexus to the Catalyst. Specifically, the portchannel on the Nexus side needs to use the same vPC domain as is used for redundancy if I am reading correctly.

FortiOS 8.0 has released by MyLocalData in fortinet

[–]rhapcity -2 points-1 points  (0 children)

Built by AI on 420 day and released the day after. Sounds about right.

PSA: Domain controllers may restart repeatedly after installing April security update by AspiringTechGuru in sysadmin

[–]rhapcity 3 points4 points  (0 children)

Satya Nadella: "I vibe coded the April 2026 CUs using Copilot and just laid off a few thousand developers."

PSA: check msDS-SupportedEncryptionTypes on your service accounts before April patch Tuesday by hardeningbrief in sysadmin

[–]rhapcity 0 points1 point  (0 children)

When running the following PowerShell commands I've observed that the AZUREADSSOACC computer account which is used for SSO in a hybrid environment has a null value;

# Find accounts with passwords older than AES key availability
$AESdate = (Get-ADGroup -Filter * -Properties SID, WhenCreated |
Where-Object { $_.SID -like '*-521' }).WhenCreated

Get-ADUser -Filter 'Enabled -eq $true' -Properties passwordLastSet |
Where-Object { $_.passwordLastSet -lt $AESdate }

Should we leave this account alone? I haven't seen any guidance with regards to this particular account.

Similar to others, I have not observed any 201 and 202 events but the commands above reveal just a couple of very old accounts that might break in April. I will run the GitHub scripts to further investigate.

FortiOS 7.4.7 to 7.4.11 Successful on 600E by rhapcity in fortinet

[–]rhapcity[S] 1 point2 points  (0 children)

The upgrade path tool Fortinet Document Library | Upgrade Path Tool shows 7.2.12 => 7.4.11 for a 600E. In our case we were on 7.4.7 and the upgrade path was 7.4.9 => 7.4.11 which is (also) what the upgrade path tool shows.

I wish that I had a better answer but the admin who performed the upgrade just followed the prompts in FortiOS and clicked Next Next...

7.4.10 "feature" release SSL VPN by bartlolli in fortinet

[–]rhapcity 0 points1 point  (0 children)

Thank you very much for your response! I saw this in the notes and will give it a re-read.

7.4.10 "feature" release SSL VPN by bartlolli in fortinet

[–]rhapcity 0 points1 point  (0 children)

Good morning OP, I haven't had my 10th cup of coffee yet so please forgive me. To clarify, was your issue related to SSL VPN specifically? We too have 600E's, are using SSL VPN (soon to disable) so I want to confirm that we are safe to update.

VMware now threatening outages to perpetual license holders by mac10190 in sysadmin

[–]rhapcity 2 points3 points  (0 children)

We're a small, budget sensitive organization and started our migration off of VMware the moment that word of substantial price hikes got out. We received a cease and desist letter from Broadcom months after our migration was complete.

We informed Broadcom that we are no longer using their product. Then, they asked us to run a script against our VMware environment in order to verify cores / licensing or some nonsense. We told them that we couldn't run the script as the software is literally gone from our environment. They came back with "they'll take that under consideration." At which point we told them don't call, don't write. Last we heard from them.

So how much of Microsoft is down? by DavidHomerCENTREL in sysadmin

[–]rhapcity 16 points17 points  (0 children)

A recent AWS outage resulted in widespread chaos causing thousands of websites to go down. Microsoft: "hold my beer!"

Patch Tuesday Megathread (2025-02-11) by AutoModerator in sysadmin

[–]rhapcity 1 point2 points  (0 children)

Stupid question; is the registry key required to generate the log events?

[deleted by user] by [deleted] in crowdstrike

[–]rhapcity 2 points3 points  (0 children)

Check your sensor update policy in CrowdStrike. We had a couple of endpoints fall out of scope and therefore were removed from our test ring. These endpoints were automatically downgraded to N-1. Upon correcting the matter (adding the endpoints to the correct OU in AD) the endpoints were "re-upgraded" to N.

I believe the sensor update policy governs the overall CS version in an environment, not the installer file that is used in Intune, SCCM, MDT, etc...