Well I logged a ticket. The support engineer said they were willing to help, but that if they couldn't resolve the issue then I'd need to refer to upgrade support. He would have helped check that our configuration met the prerequisites (they do, to the best of my knowledge). We're SaaS so there may be console settings that I as a customer can't change and would need upgrade support's help to change. Since I have 4 other SEGs still running Classic SEG, I didn't want to risk anything that might compromise the other SEGs. Also SEG V2 doesn't yet support certificate based authentication, which we don't currently use, but we may need later.
I am not pursuing V2 for the time being. It's a new product and I don't think it's yet ready for prime time.
' Connectivity between AirWatch & SEG' issue here too, although email and management functionality is working as should.
External settings on email configuration page have not basically changed since SEGv1:
https:// SEG-FQDN /segconsole/management.ashx is continued as it was in SEGv1.
Afaik , this part of the FQDN used to be used in the SEGv1 connection test,
https:// SEG-FQDN/segconsole
it obviously does not work anymore.
Anyone got this fixed?