We have had success with the Admin user being remote and connecting to the EU Computer inside the office, as SCCM seems to be more stable this way, but when both users are at home, SCCM connection can be inconsistent after a restart. The safe step of having the EU at the office for either a Helpdesk employee to physically install on the laptop, or to deploy remotely on their end after a test connection to SCCM first ensures no downtime outside the standard installation process, which is around 20 minutes.ġ. This process requires Admin-level credentials, and should be attempted only when the end-user is physically in the office, as it's a 2-step process (Uninstall, and then a restart before reinstallation), and if SCCM connection is lost before the 32-bit install is complete, the end user will be without any Office products, which will end their business productivity until the application is reinstalled. MS Office is now a package install, where it used to have multiple installs for Outlook, Excel, Etc the entire MS Office package must be completely uninstalled to replace it, which requires a proprietary Microsoft Application called Microsoft Support And Recovery Assistant, commonly referred to as SARA. Hyland will also utilize 32-Bit Office protocols as well, so this fix will be pervasive over the upcoming migration from Acro to Hyland. After much troubleshooting, the problem seems to come from 64-bit Office installations conflicting with Acrosoft's 32-Bit MAPI interface. We have recently solved the issue of MAPI errors coming up for Acro Docs/WM users when attempting to send a file via email from within Acrosoft products.
How to Uninstall 64-Bit Office/Reinstall 32-Bit Office on Windows 10 (Acro/Hyland Mail/MAPI issue)
0 kommentar(er)
