In short, no.
An endpoint appears in Computer Management with a Connection Type of Local if and only if it is successfully able to contact the SmartDeploy API Service that is running on that specific console using its local API Service URI:
https://consolehostname:8080 (e.g.).
If the endpoint is running on the same local network as the console host, then you should expect it to appear with a Connection Type of Local if it is able to access this URI and port successfully.
Whereas if the endpoint is off-site and unable to reach the console over its local API service URI, then it will reach out via the SmartDeploy online API service and appear in the console with a Connection Type of Cloud instead. A Cloud-connected device can only receive deployments using files that exist in a cloud distribution point.
If you have an endpoint that you expect to be Local and it unexpectedly appears as Cloud, this likely indicates a communication problem that needs to be addressed within your network - i.e. the endpoint is unable to communicate with the console via the local API service URI.
See Force a Cloud Connection for further details.
