This problem sounds familiar.
It's not a normal.dot type problem is it? Where the originator used normal.dot as their doc tempate, saved it as .dot again and it's screwing up everyone's normal.dot that reads / alters the document.
This is working on several machines now. But @romo reports that it is still hit or miss, it's not a reliable or permanent fix, but it more reliable than other attempts. It remains, as MS has stated, somewhat random.
Just had a very large client reach out and ask for LibreOffice again after moving to MS Office because they found Excel too difficult to get data in correctly. So they are going to LibreOffice for exactly the reason that everyone claims that "everyone" chooses MS Office... LO is easier to use and has better compatibility 🙂
They own licenses for both, so purchase cost is not a factor. They've used MS Office more time in the last three years. Given less time with LibreOffice and zero "price" incentive, they've chosen it as the superior product for them - with zero prompting from IT. Out of the blue the managers chose it as the better product.
I won't have any Win 7 systems by that time. At least that is the goal. I was thinking it was Jan 20, 2020. Guess I just confabulated that based on the year being 2020. Still have about 40 systems to issue to replace them.
There was a contact us email address in VLSC. I wrote them, included my license key and business information. They wrote back today indicating that they would create my key and I would receive it in a separate email. Additionally it would be added to my VLSC account.
I actually received the email with the KMS key before this email, and sure enough, the KMS key is now in my VLSC account.
Holy crap. Where was this a few months ago when I was building my click-to-run installer? Thanks for the info.
Right?! You can even upload your own and tweak it using that interface instead of going back and forth between notepad and the crappy TechNet doc lol.
Another useful script there (and I have to find it to link it) is a reverse engineering script. So let's say you have a C2R deployment out there that you can't determine the current settings easily, it will build an XML file from that individual installation to tell you what's installed, update location, etc.. It's pretty cool stuff.