Overview
This document outlines how to deploy and license Read&Write for Mac in environments where users cannot sign in with Microsoft or Google accounts.
In these scenarios, licensing is applied locally using a configuration file distributed to each device.
Prerequisites
Ensure you have the following:
Read&Write for Mac installer package (.pkg)
Your organisation’s:
Product Code
Licensed domain
Administrative access to target devices or an MDM solution (e.g. Intune, Jamf)
If you do not know your Product Code, contact your Everway representative and request this before proceeding with deployment.
Deployment Process
1. Deploy Read&Write for Mac
Install Read&Write for Mac using your standard deployment method:
MDM solution (recommended)
Scripted deployment
Manual installation (not recommended at scale)
The application must be installed before licensing is applied.
2. Create the Licensing File
Create a file named:
ReadAndWriteAdmin.rtfAdd the following content:ProductCode=XXXXXXXX
Domain=yourdomain.com- Replace XXXXXXXX with your organisation’s Product Code
Replace yourdomain.com with a licensed domain associated with your subscription
3. Deploy the Licensing File
Copy the ReadAndWriteAdmin.rtf file to the following location on each device:Macintosh HD/Users/SharedThis can be deployed via:
MDM (preferred)
Scripted deployment
Manual copy
4. First Launch Behaviour
When Read&Write is launched:
The application reads the configuration file
The licence is validated against the Product Code and domain
A local licence is applied to the user profile
No user sign-in is required.
Important Notes
Internet access is required on first launch to validate the licence
The licensing file only needs to be deployed once per device
Licensing is applied per user profile after first run
macOS permissions (Accessibility, Screen Recording, etc.) should be pre-configured via MDM for a seamless deployment
When to Use This Method
Use this deployment method when:
Devices cannot authenticate using Microsoft or Google accounts
Environments are restricted (e.g. secure networks or exam settings)
A non-interactive user experience is required