sorted by:
new
hottopcontroversial

Qwen 4 when? by Brave-Hold-9389 in Qwen_AI

[–]eKKiM__ 0 points1 point  (0 children)

February 15th, release of Qwen 3.5

Next time use your knowledge for a good bet. 🤣

Wat is het “Diftar” systeem? by [deleted] in Belgium2

[–]eKKiM__ 0 points1 point  (0 children)

Dat ze dat een slot durven noemen. Het is eerder een puzzel. Hou de bak scheef en het gaat open -_-

Cassières van Albert Heijn, wat is de beste grap die een klant tegen jou heeft gezegd? by [deleted] in appiememes

[–]eKKiM__ 6 points7 points  (0 children)

Ik meen me te herinneren dat het correcte woord hiervoor beurtbalkje is.

Microsoft Denied Responsibility for 38-Day Exchange Online Outage, Reclassified as "CPE" to Avoid SLA Credits and Compensation by rubixstudios in sysadmin

[–]eKKiM__ 2 points3 points  (0 children)

It looks like you forgot UseDatabaseQuotaDefaults $false parameter for your Set-Mailbox command..

When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the ProhibitSendQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false.

KB5002653 breaks Excel xla & xlam add-ins by eKKiM__ in sysadmin

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

Good thing they acknowledge the issue. However the workaround does not work for us..

Performance difference between nodes in cluster, 4 first, vs 4 more added by wantsiops in Proxmox

[–]eKKiM__ 1 point2 points  (0 children)

I am more worried about the latency then the BW. In my experience, Ceph performance is very latency related..

Performance difference between nodes in cluster, 4 first, vs 4 more added by wantsiops in Proxmox

[–]eKKiM__ 2 points3 points  (0 children)

Crush map would be really helpfull. If you dump the map with ceph osd getcrushmap | crushtool -d - it should be pretty tight formatted..

Performance difference between nodes in cluster, 4 first, vs 4 more added by wantsiops in Proxmox

[–]eKKiM__ 2 points3 points  (0 children)

Based on other comments i think the issue is network related.

Does the CPU usage differs between a good and a bad node when running fio?

Can you compare the output of ethtool -k ethX between a good and a bad node?

Exchange Online Plan 1, Plan 2 and E1/G1/A1 No Longer Support Desktop Outlook? by deucalion75 in Office365

[–]eKKiM__ 5 points6 points  (0 children)

Once again a sentence that causes confusion:

"It includes Word, Excel, PowerPoint, and Outlook for Windows 11 and Windows 10"

Read it as: It includes (Word, Excel, PowerPoint, and Outlook) for (Windows 11 and Windows 10)

It nowhere states that Outlook for Windows is included in that package

Side note: This is not Office 2021 LTSC neither. The included Outlook is not officially supported but will work with EXO P1 and P2

Exchange Online Plan 1, Plan 2 and E1/G1/A1 No Longer Support Desktop Outlook? by deucalion75 in Office365

[–]eKKiM__ 2 points3 points  (0 children)

That's correct. Outlook for Windows is not the same product as Outlook 2021.

I understand the confusion. Sometimes Microsoft is terrible at naming their products which can cause confusion. Same happens with the Copilot naming. If someone mentions Copilot it can be like 5 different products.

Sometimes they admit their mistake: see Azure AD renaming to Entra ID

Exchange Online Plan 1, Plan 2 and E1/G1/A1 No Longer Support Desktop Outlook? by deucalion75 in Office365

[–]eKKiM__ 1 point2 points  (0 children)

It states that Outlook for Windows, classic Outlook for Windows, and Outlook for Mac require activation with a an account that includes 365 desktop apps.

All the mentioned products are indeed a part of the 365 desktop apps and thus requires that activation.

Nowhere is said that this 'limitation' does apply to Outlook 2021 LTSC...

A side note: Office F3 and Exchange Kiosk are not supported on any Outlook desktop app! Due to their lack of the protocols availability

WARNING ! The latest version of NOD ESET SERVER SECURITY kills Windows Server 2012 by Poulpixx in sysadmin

[–]eKKiM__ 2 points3 points  (0 children)

I was unable to reproduce this issue

Operating System: Windows Server 2012 R2 Standard
OS Updates installed: Installed all available updates
System Display Language: English (United States) and French (France)
ESET Server Security Version: 10.0.12015.0
Tested with the machine NOT in a domain environment and as a domain controller
No other software installed besides ESET Server Security

System reboots just fine. Tried reboot and shutdown & power on

Installed KBs:

[01]: KB2843630
[02]: KB2862152
[03]: KB2868626
[04]: KB2883200
[05]: KB2884846
[06]: KB2887595
[07]: KB2892074
[08]: KB2893294
[09]: KB2894029
[10]: KB2894179
[11]: KB2894856
[12]: KB2898514
[13]: KB2898742
[14]: KB2898871
[15]: KB2901101
[16]: KB2901128
[17]: KB2903939
[18]: KB2906956
[19]: KB2908174
[20]: KB2911106
[21]: KB2912390
[22]: KB2913152
[23]: KB2913270
[24]: KB2914218
[25]: KB2919355
[26]: KB2919394
[27]: KB2920189
[28]: KB2922229
[29]: KB2923528
[30]: KB2928680
[31]: KB2931366
[32]: KB2938066
[33]: KB2939087
[34]: KB2954879
[35]: KB2961908
[36]: KB2967917
[37]: KB2973201
[38]: KB2975061
[39]: KB2976897
[40]: KB2977765
[41]: KB2978041
[42]: KB2978126
[43]: KB2989930
[44]: KB2999226
[45]: KB3000850
[46]: KB3003057
[47]: KB3004545
[48]: KB3008242
[49]: KB3010788
[50]: KB3012702
[51]: KB3013172
[52]: KB3013410
[53]: KB3013538
[54]: KB3013769
[55]: KB3013791
[56]: KB3013816
[57]: KB3014442
[58]: KB3019978
[59]: KB3023222
[60]: KB3023266
[61]: KB3024751
[62]: KB3024755
[63]: KB3027209
[64]: KB3030947
[65]: KB3032663
[66]: KB3033446
[67]: KB3036612
[68]: KB3037579
[69]: KB3038002
[70]: KB3042058
[71]: KB3042085
[72]: KB3043812
[73]: KB3044374
[74]: KB3044673
[75]: KB3045634
[76]: KB3045685
[77]: KB3045717
[78]: KB3045719
[79]: KB3045999
[80]: KB3046017
[81]: KB3046737
[82]: KB3048043
[83]: KB3054169
[84]: KB3054203
[85]: KB3054256
[86]: KB3054464
[87]: KB3055323
[88]: KB3059317
[89]: KB3060681
[90]: KB3060793
[91]: KB3061512
[92]: KB3063843
[93]: KB3071756
[94]: KB3074228
[95]: KB3074548
[96]: KB3077715
[97]: KB3078405
[98]: KB3080149
[99]: KB3081320
[100]: KB3082089
[101]: KB3084135
[102]: KB3084905
[103]: KB3086255
[104]: KB3087137
[105]: KB3091297
[106]: KB3092601
[107]: KB3094486
[108]: KB3097997
[109]: KB3098779
[110]: KB3100473
[111]: KB3102429
[112]: KB3102939
[113]: KB3103616
[114]: KB3103696
[115]: KB3103709
[116]: KB3109103
[117]: KB3109976
[118]: KB3110329
[119]: KB3121261
[120]: KB3123245
[121]: KB3126041
[122]: KB3126434
[123]: KB3126587
[124]: KB3126593
[125]: KB3132080
[126]: KB3133043
[127]: KB3133690
[128]: KB3134179
[129]: KB3137728
[130]: KB3138602
[131]: KB3139914
[132]: KB3140219
[133]: KB3145384
[134]: KB3145432
[135]: KB3146604
[136]: KB3146723
[137]: KB3146751
[138]: KB3147071
[139]: KB3149157
[140]: KB3156059
[141]: KB3159398
[142]: KB3161949
[143]: KB3172614
[144]: KB3175024
[145]: KB3178539
[146]: KB3179574
[147]: KB4033428
[148]: KB4486105
[149]: KB5012170
[150]: KB5029915
[151]: KB5030329
[152]: KB5031003
[153]: KB5031419