ozy @high Ich denke mahl das sollte ein neues Ticket werden, da dieses problem neu ist und mit OL update zusammen hängt, und warschienlich nichts mehr mit dem älteren Ticket zu tuen hat. PS: Wenn es heisst das das "seit längst behoben ist", kann man ja noch in den Ticket dem link zu diesem community thread senden. Wir sind mindestens 5 Leute mit dem gleichen Problem hier.
WalterH ozy "seit längst behoben ist" Vor längerer Zeit gab es ein ähnliches Problem, das wurde behoben. Aktuell ist das Problem extrem ähnlich entsteht aber komplett anders.
high ozy das war auch mein Ansatz den link habe ich gepostet. Antwort, sie können nicht auf den link klicken und forum lesen ;-) ich habe dann die texte raus gesucht und rein kopiert. es kommt leider am ticket gar nix. weder Antwort noch info ob es ein problem ist ob es nachvollziehbar ist. keine Rückmeldung einfach und das ist sehr sehr schlecht. wir haben die troubles, tappen im dunkeln weil einfach kein informationsfluss vom support kommt.
mwilliams Analysis shows: 365 Version 2311 (Build 17029.20068): partially affected Version 2311 (Build 17029.20108): not affected Version 2310 (Build 16924.20150): affected Version 2310 (Build 16827.20278): not affected 2016 C2R / 2019 Version 1808 (Build 10405.20015): not affected Version 2311 (Build 17029.20108): not affected Version 1808 (Build 10404.20013): affected Version 2311 (Build 17029.20068): affected Version 2310 (Build 16924.20150): not affected Version 1808 (Build 10403.20013): not affected Generally, we couldn't see any issues with the monthly or half-yearly enterprise channels. Release information of MS: https://learn.microsoft.com/en-us/officeupdates/current-channel As per this result, we simply recommend you to update your Office. After intense debugging (see above) we can confirm it is not a grommunio issue. However, we keep on investigating to see whether we can provide mechanisms to prevent such behaviour of a faulty update from Microsoft.
WalterH My customers uses the Click to Run installation, the C2R installs all updates automatically. So I assume this installations are always up to date and we see this issues. OL 2019 and OL 2021.
externa1 WalterH No they do only auto update if its not disabled in office - i do not have any issues with the latest versions
weini I updated 3 of my client installations to 20108 yesterday and re-activated the cache mode (deleted the OST). Now I hope that the issue will not come back. I would say this is also a good time to apologize, that I always consider Grommunio being the source of issues when something is not working as expected. Many thanks to the Grommunio team for investigating the Outlook issue and providing the results of their checks with the different Outlook versions.
ozy Indeed, I also (wrongly) assumed that something could be wrong with Grommunio's gromox OX implementation. @mwilliams Thank you for that detailed report that's really helpful. I am as of today a community user (3 servers for very small companies, one being mine), and try to contrib back in various ways (grommunio-archive installer patch, csv2vcard open source tool, workaround in this thread...). I am really glad that Grommunio allows community usage, since it offers small companies like mine "real data sovereignity" without needing to go the bloated MSExchange + AD route. So for what it's worth, thank you Grommunio, and I'll keep contributing in every way I can until I'll grow big enough to need more than community version 😉