Moving LogMeIn Resolve MDM to single domain URL structure
LogMeIn Resolve MDM has moved to single domain URL structure to be more compliant with the requirements of certain browsers, to improve security, and to provide better service for our customers in the future.
The new URL structure of LogMeIn Resolve MDM
The URL of LogMeIn Resolve MDM was changed to single domain architecture, meaning that all customer sites are now under a single domain: https://mdm.gotoresolve.com. The <sitename> in the new structure is defined as a subdirectory, as in https://mdm.gotoresolve.com/<sitename>.
Check the following examples to see how the URLs change in the new, single domain structure:
Old URL: https://<sitename>.mdm.gotoresolve.com
New URL: https://mdm.gotoresolve.com/<sitename>
In the following example, <sitename> is 'mysitename'.
Old URL: https://mysitename.mdm.gotoresolve.com
New URL: https://mdm.gotoresolve.com/mysitename
What do I need to update?
To continue using LogMeIn Resolve MDM, update the following as soon as possible:
- Update browser bookmarks for LogMeIn Resolve MDM to use the new URLs.
- If you use API, update the URLs in the API requests.
- If you use our Active Directory (AD) integration, replace the old AD connector with the latest version.
For more information, read the subsections in this article.
Updating bookmarks with the new URLs
In your browsers, update the LogMeIn Resolve MDM bookmarks by replacing the old URLs with the new ones.
Updating the URLs in API requests
Select one of the following options to update the URLs in your API requests:
- Include <sitename> in the new URL as a subdirectory.
- Include <sitename> in the HTTP header.
Learn more about the LogMeIn Resolve MDM API.
Including <sitename> in the URL as a subdirectory
Move <sitename> from the old base URL to be a subdirectory in the new URL.
Old URL: https://<sitename>.mdm.gotoresolve.com/api/v2/<endpoint>
New URL: https://mdm.gotoresolve.com/<sitename>/api/v2/<endpoint>
API request example
In the following API v2 example, <sitename> is mysitename and the Device endpoint is called to post the lock request on the device identified by {id} in the URL.
POST https://mysitename.mdm.gotoresolve.com/api/v2/Device/{id}/LockPOST https://mdm.gotoresolve.com/mysitename/api/v2/Device/{id}/LockIncluding <sitename> in the HTTP header
Use https://mdm.gotoresolve.com (without <sitename>) as the base URL and provide <sitename> in the X-Instance-Name header.
API request example with CURL
In the following CURL command example, <sitename> is mysitename and the Device endpoint is called to post the lock request on the device identified by {id} in the URL.
curl -X POST https://mysitename.mdm.gotoresolve.com/api/v2/Device/{id}/Lockcurl -X POST -H "X-Instance-Name: mysitename" https://mdm.gotoresolve.com/api/v2/Device/{id}/LockUpdating the AD connector
In LogMeIn Resolve MDM, navigate to: .
To update the AD connector, download the new version (1.5.0.0) and overwrite the old .exe and configuration files with it. To check the version number of the connector, right click the .exe file, select Properties and check the Details tab.
If you need assistance with updating the AD connector, contact the LogMeIn Resolve MDM Support Team.
Learn more about importing users.