Installing the MacroView Software
The MacroView desktop software (eg MacroView DMS and DMS Pro) installs entirely on the Client PC.
The installation on a PC can be performed by double-clicking the EXE that is part of the download package.
Alternatively the installation can be performed by using Active Directory Software Install software packages – e.g. SCCM. You will need to extract the MSI from the download package.
Pre-requisites for the MacroView software are listed in the download pages in this Help Centre.
Note that the MacroView desktop software is NOT compatible with the so-called Store version of Microsoft Office.
General user settings can be accessed via the MacroView client interface. Advanced settings can only be updated via the registry directly or the supplied MacroView ADMX group policy template file. All user registry settings used by the MacroView client can be ‘locked down’ via group policy. The MacroView ADMX required for group policy is available for download from the product page in the MacroView Help Centre. Included as part of this download an XLSX file that documents the intended use of all settings.
Microsoft 365 Tenant
There are no MacroView software components to be installed on your Microsoft 365 tenant.
The Microsoft 365 tenant does need to be registered to the MacroView DMS or DMS Pro software on a client PC. This enables activation of your organization’s license for MacroView DMS or DMS Pro. This registration is done by entering the URL of the Microsoft 365 tenant.
To make full use of the advanced search functionality of the MacroView client you need to update the search schema properties at the tenant level. This can only be done by a tenant admin.
Permissions / Data
With the MacroView desktop solutions, no client data – documents, emails or associated metadata - is passed through or retained in MacroView servers or Azure instances. When using the MacroView software all user data is stored on the client machine and the organisation's Microsoft 365 tenant.
MacroView does not communicate directly with the Exchange server and does not use the user’s Exchange credentials.
The MacroView software installs entirely on the Client PC, and all communication triggered by the MacroView software occurs between the Client PC and the Customer’s tenant in Microsoft 365 (Office 365) in an encrypted manner.
The user is authenticated by the Microsoft 365 platform via OAuth 2.0. MacroView does not store any user credentials. No user credentials are ever transferred to or handled by MacroView. The authentication prompt that is displayed is part of the standard Office 365 OAuth 2.0 authentication flow that is handled by Microsoft. It is the same log in process that the user must follow when logging in to Office 365 in the web browser.
Because the MacroView software leverages the standard Microsoft implementation of the OAuth 2.0 protocol by displaying the standard browser login prompt, any MFA configured in Office 365 or Azure AD will automatically apply.
The MacroView desktop software complies with the Microsoft requirement that all traffic between the Client PC and the Microsoft 365 platform is protected by TLS v1.2:
Microsoft is the Software as a Service provider and as such is responsible for the security of the client’s documents and emails and associated metadata that is stored in the client’s tenant in Microsoft 365.