Avoid necessary registry correction after Click To Run Office update

At our company the unit responsible for deploying software knows about the article KB01529 (Errors with PI DataLink when updating or upgrading Click To Run Office).

But they state: According to OSIsofts problem with PI and Office 365 click to run we can not offer a solution which fits within our IT guidelines.

- Our Windows Update process is completely managed automatically. We use several Windows Update rings. Users have the ability to self update their machine.

So the Windows Update time is different for each machine. Our applications and updating tool SCCM, does not provide a trigger which can be run after a Windows Update.

We want to give our users the ability to update their machine on a moment which suits to the user. This way the users can do their daily job without any major downtime/update time of their laptop.

- Our update process is completely managed automatically. In the near future we do not use SCCM for our Windows Updates but we are going to use Microsoft Autopatch.

When we are using Microsoft Autopatch, all the patching work is done by Microsoft. If there are any issues with an update, Microsoft will stop the update.

But they will not stop the update for PI, because of the reasons mentioned in the KB article.

- We try to limit the use of startup scripts, because they slow down your computer. We try to learn from the issues we had in the past. Startup scripts are often used for quick fixes.

But the fixes will be there for a long time. Overtime the startup scripts will be longer and longer, and it will take more and more time to logon on. We have seen this by many companies.

Besides that, we want to keep our baseline as simple as possible. No exceptions.

- Mandatory SCCM deployments do not fit within the IT Guidelines. We only use mandatory deployments for core applications (Antivirus/Cato).

- We do not build custom services which checks registry settings etc. Because this is not really a solution, and it does not offer a predictable workspace.

So currently Datalink users first must recognize the issue when they have a PI error in an Excel sheet. This is diffecult if they just use sheets built by others.

When recognized they have to (re)instal the registry correction. So we don't have an automated solution for the users (instead we get tickets and have to explain to user unfamiliar with this issue).