VMWare Workspace One - Not Scanning

[stevce_brazeau]

Hi all,
We're in the process of implementing VMWare Workspace One, and we're trying to get Lansweeper (v 8.0.130.38) to scan it.
We've gone through the process notated here: https://www.lansweeper.com/knowledgebase/airwatch-scanning-requirements/
And the account we're using should have the required permissions, but, we keep getting an error stating "No valid credential found."
There doesn't appear to be any other error that we can find.

The obvious inclination is that there's something wrong with the credentials, but we're pretty sure we've double and triple checked those.

Has anyone seen this before?

[simoncwhitfield]

Managed to get the Airwatch and Lansweeper integration working in the end.

Even though the error in Lansweeper was stating that no valid credentials found, it was actually the URL for the API link that was the problem.

When you look in Airwatch at the list of websites for your instance it has one for the REST API service. It is listed as something like this https://as{instance}.awmdm.co.uk/API.

It was that URL I was putting into the config in Lansweeper.

After numerous attempts and speaking to our Lansweeper managed service provider I couldn't get it working. Then one day when taking another go I noticed that the screenshots in the Lansweeper setup guide didn't include the /API part of the URL, I thought that this was just because it was an example screenshot.

I decided to try removing the /API, so the URL was just https://as{instance}.awmdm.co.uk, and it started talking to Airwatch.

We now have a fully working Airwatch Lansweeper integration and all our mobile devices are now showing in Lansweeper.

[nnewton]

---

@simoncwhitfield wrote:
I decided to try removing the /API, so the URL was just https://as{instance}.awmdm.co.uk, and it started talking to Airwatch.

---

Thankyou! I have spent way to long trying to figure out why my v7 > v10 upgrade no longer liked my Airwatch credentials. v7 is apparently fine with the trailing /api, not v10 though. Would have been nice if the upgrade installer changed this automatically if it was no longer valid.

[cscherrey]

I'm looking at purchasing VMware Workspace ONE but I was looking to make sure it is supported from Lansweeper just like AirWatch was. So is connecting to VMware Workspace ONE an issue with Lansweeper?

[Mark_Payton]

cscherrey wrote:
I'm looking at purchasing VMware Workspace ONE but I was looking to make sure it is supported from Lansweeper just like AirWatch was. So is connecting to VMware Workspace ONE an issue with Lansweeper?

Did you ever get an answer to this? Intune isn't really an option for us and I see not evidence that Lansweeper is adding support for any other MDM, so Workspace ONE is the only possibility to help manage iPads--if it even works.

[cscherrey]

MarkPayton wrote:

cscherrey wrote:
I'm looking at purchasing VMware Workspace ONE but I was looking to make sure it is supported from Lansweeper just like AirWatch was. So is connecting to VMware Workspace ONE an issue with Lansweeper?

Did you ever get an answer to this? Intune isn't really an option for us and I see not evidence that Lansweeper is adding support for any other MDM, so Workspace ONE is the only possibility to help manage iPads--if it even works.

Nope, no response. Eventually, I plan to get a trial of Workspace ONE and test this myself but I haven't had time.

[mkruer]

https://kb.vmware.com/s/article/50121184

This time without the period.

[brandon_jones]

I get a 404 message when I go to the link. Do you happen to have the correct link?

[mkruer]

The issue may be related to https://kb.vmware.com/s/article/50121184 In a nutshell, if Lansweeper and Airwatch are on the same network range, the Defaults of Airwatch redirects URL requests to use the local IP address of the Airwatch box making any login invalid.

Removed the period form the URL

[simoncwhitfield]

Matthew Kruer wrote:
The issue may be related to https://kb.vmware.com/s/article/50121184 In a nutshell, if Lansweeper and Airwatch are on the same network range, the Defaults of Airwatch redirects URL requests to use the local IP address of the Airwatch box making any login invalid.

Removed the period form the URL

Thanks but for me at least this will not be the issue as we don't use On Prem Airwatch.