Requesting that lan connection to corporate network is present before applying profiles

When applying profiles that affect wifi connections such as certificate payloads, network configurations, or even domain joins if an asset checks policy and recieves new policy while on wifi it will lose it's wireless connection and will be unable to communicate to parallels to complete the process until it's plugged into a wired network that has access to the parallels server. This leaves an asset in an unmanaged state until it has a chance to get on a lan that has connectivity to the parallels server. Rather than blinding applying policies I think that the parallels client should be able to check if the lan connection is present and able to communicate with parallels on that lan connection prior to attempting to apply policies or at least cache the profiles before applying them. since most macs are wireless today and most users don't have a physical network adapter on them you can see why this would be problematic.