This year has a lot less posts as i have stopped doing M365 news in January. I still post in Technology category occasionally and some new articles get some views, but not that many. Also sometimes i repost in LinkedIn and i get some traffic from there. I have decided to post about interesting M365 news directly on LinkedIn. Got tired of collecting all the news and summarizing them. Again a few posts about board games, books. Will use Matomo for page views stats this year again. Because numbers differ from Google Analytics (Matomo has a bit higher count) and it will be better to compare with numbers from the same system.
- Posted 26 entries (-50):
- Technology – 15 (-36), stopped doing M365 news, also decided not to post Firefox release notes, so next year will have even less posts;
- Reviews – 6 (-12), less books read, less movies or TV series watched;
- Movies – 3 (-5), only 3 movies watched during Kinopavasaris, no completed TV series to write about, but i have watched lots of old movies, starting with all James Bond films;
- Books – 2 (-6), bad year for reading, only managed to finish two first books in Dune series;
- Board Games – 2 (-2), only 1 review in LT for Carcassonne and yearly stats, not playing that much either;
- General – 2 (-);
- Artwork – 2 (-);
- Top 10 – 1 (-);
- TV series – 0 (-1).
- No comments this year (-2).
From my understanding the “Japanese IME is not ready yet.” (or Chinese) error started appearing sometime around 1903 was released. There are tons of articles and questions on internet regarding this issue with not many working solutions. Especially for restricted corporate environment. We have started seeing reports about this error while pushing 20H2 version. But it seems such problems were also observed after 1903 update (or maybe even earlier) and some IT staff was “fixing” it by copying IME files from older version into new essentially replacing it. This doesn’t work with latest Windows 10 versions. Not to say this is not a pretty solution anyway. I had to involve Microsoft support recently to tackle this and below are my findings and kind of a solution for this.
With Microsoft hammering down on Basic Auth support in Exchange Online many systems admins are wondering what to do about email function in multi function printers and scanners and other internal systems that have to send emails (SharePoint and similar). Although it seems that SMTP Auth might stay available a bit longer even after the final date in October of 2022. Still, there could be better options to avoid problems when Basic Auth is gone and MFPs cannot send emails directly to Exchange Online using just email and password. I am not 100% sure below provided setup will work all the time, but it was recommended by our MS partners and listed on Microsoft support page. 