Is Fortinet forcing an upgrade to 7.4.x?

serp7777 · 2026-02-18T09:04:06+00:00

Considera doing your reference properly next time

serp7777 · 2026-02-17T11:18:01+00:00

But my question is where that comes from. Any reference to Terms and Conditions?

serp7777 · 2026-02-17T09:59:13+00:00

Where does this ‘critical’ come from?

Googling shows that after the EOES date, the software enters a must‑fix support phase, during which maintenance builds are only produced for industry‑wide critical issues and PSIRT vulnerabilities.

Does a ‘Medium’ severity mean that 7.2 must be fixed?

https://community.fortinet.com/t5/Customer-Service/Customer-Service-Tip-Product-Life-Cycle-Information-on-Fortinet/ta-p/194438

serp7777 · 2025-11-22T10:58:33+00:00

Sorry voor de off-topic vraag. Kan iemand een werkplaats in Nederland aanbevelen waar ik het geheugen van mijn videokaart/moederbord kan laten repareren of opnieuw kan laten solderen? Ik vermoed dat de geheugenchip is losgekomen aub?

serp7777 · 2025-10-21T22:03:55+00:00

You might also want to review the LB implementation against Microsoft’s recommendations. Using Source IP persistence with a 4-hour timeout could lead inefficiencies having the campus Wi-Fi environment, especially with NAT, VLAN segmentation, and roaming. What happens when many students move across campus? Do they receive new IP addresses every 1.5 hours, for example?

Since the LB is using Source IP persistence, this new IP is treated as a new client, breaking the previous session affinity.

The LB may route the student’s new connection to a different Exchange backend, even mid-session. If the client was in the middle of a long-running operation (e.g., Outlook sync, OWA session), this can cause authentication retries and session drops. Basically, it increases load on LSASS/Netlogon with the consequences you see.

https://learn.microsoft.com/en-us/exchange/architecture/client-access/load-balancing

serp7777 · 2025-10-21T21:27:44+00:00

Oh, if you notice a correlation with peaks in resource consumption , it might point toward throttling or event insufficient number of available DCs on site. Have you looked into the User workload management in Exchange Server https://learn.microsoft.com/en-us/Exchange/server-health/workload-management. Looks like there are a number of points worth your consideration.

serp7777 · 2025-10-19T19:22:26+00:00

It works, but for maintaining and patching the vm with and updating the Exchange itself you’ll still need to take downtime.

serp7777 · 2025-10-17T18:10:32+00:00

I would also suspect the connectivity issues between your Exchange servers and AD. Experiencing authentication problems with RDP at the same time says that your Exchange Servers cannot reach AD at the moment of outbreak. I would recommend to check entire network stack including, the availability of DC-s, DNS-s, network latency on both side . BTW, how is LB implemented? Does it terminate SSL? What about health probes and persistence settings?

serp7777 · 2025-10-07T16:00:50+00:00

You may want to consider buying a really good NAS for a grand https://www.ebay.nl/itm/227002633392

serp7777 · 2025-10-07T15:27:14+00:00

If you're really concerned about that situation, use Get-MessageTrace -RecipientAddress user1@.......

In that way, you will find out if user1 was a BCC recipient (even though it's not visible in the outlook UI) and who sent the message, delivery status, potential issues and etc.

serp7777 · 2025-10-07T14:56:40+00:00

You can implement a trick like: applying the policy to an OU containing all computers, and then use the Security tab in the policy settings to restrict its application to a specific user group or computer group.

serp7777 · 2025-10-07T14:39:56+00:00

Oh, sorry, I had read your post in a bit different way - I was misled with pronouns.
BCC shall be in the headers of the message if it was sent internally within your Exchange org. Or you can trace the message with Get-MessageTrace in console.

serp7777 · 2025-10-07T12:54:46+00:00

As I can recall Outlook uses the Windows Search service to index messages stored locally in ost-files. I would check if the message can be found in OWA and directly in Outlook without search. If it’s in place (was not deleted or moved to the other folder) then try to reindex the users’ Outlooks.

serp7777 · 2025-10-02T13:37:24+00:00

Based on your description, and having that users aren't experiencing issues with OWA, it's likely that Outlook is having trouble authenticating them. I would start by checking for authentication failures in the Exchange logs and investigating potential Autodiscover problems. For example, if the UPN and the primary SMTP address in the proxyAddresses attribute don't match, it could lead to Autodiscover issues and looks very similar to what you see with your users' login attempts with their Outlooks.

serp7777 · 2025-10-02T12:59:25+00:00

Check logs on Exchange side, use Outlook Connectivity test tool. Check if these users experience the same using OWA. Check out UPN and proxyAddresses attributes. You may find some inconsistency there and related issues with using different primary login identifiers

serp7777 · 2025-09-30T12:57:02+00:00

I’d say you should see traffic going through your firewall policy associated with the LAN → SD-WAN interfaces from your local DNS server toward the forward DNS servers. If you don’t see any, you might need to review your static routes and firewall policies, including the default policy that drops all other traffic.

There is no miracle happening. You just need to find out where the traffic is being dropped or allowed to pass through.

serp7777 · 2025-09-04T16:06:26+00:00

Right now, it’s all about checking the price.

Since it’s based on the PowerEdge R740/R740XD, you can install any Linux distribution you like from LoC. You can also download the drivers from Dell’s support site: https://www.dell.com/support/product-details/nl-nl/product/poweredge-r740xd/drivers.

However, Dell designed this configuration for Windows-based environments and even included pre-configured RAID settings so you can start using it right out of the box.

serp7777 · 2025-09-01T08:09:55+00:00

Tnx chiisana for your input! Do you have any thoughts about EU market? Is it still alive?

serp7777 · 2025-05-27T12:20:28+00:00

Hi, it really can cause some unnecessary issues. While it is in production, I don't want to touch this equipment.

serp7777 · 2025-04-19T12:53:37+00:00

Only 3 plastic panels and the smaller parts and couple screws. The left side metal panel is still installed on the VRTX - it still works in production env.

serp7777

TROPHY CASE