Endpoint Security Complete

 View Only
  • 1.  Mobile Management port change

    Posted Feb 29, 2012 07:25 AM

    We have the tiny problem, that we run out off public IP adresses for several solutions in a demolab. Most solutions listen on port 443 SSL.

    The question now, could the mobile management server and agent be easily reconfigured to use another port? For the server it should be just a matter of reconfiguring IIS, but how will the Agent and the enrollment on an iOS device for example react?

    Does anyone have experience with this kind of situation so far?

    Thx



  • 2.  RE: Mobile Management port change

    Posted Feb 29, 2012 09:17 AM

    I'd really push you here to modify the other solutions.  While it wouldn't be a problem had a port other than 443 been selected from the start, I'm not exactly sure what mechanism, aside from re-enrollment, you would use to notify managed iOS devices to talk to the server on the new port.



  • 3.  RE: Mobile Management port change

    Posted Mar 01, 2012 03:52 AM

    Thanks for the imput, actually the symantec mm will be the new kid in the demolab. So could start fresh with different port. How to let the Device know during enrollment which port to use? simple as adding it to the enrollement adress with :3443?

    Its just for demoing the solution.(but then again a demo better works well to sell) In productive systems I would rather not stray away from the supported ways. :D



  • 4.  RE: Mobile Management port change

    Posted Mar 01, 2012 12:19 PM

    Ah, that's easy then.  When you install the externally-signed SSL certificate for the MMS SS, just ensure your binding for https uses a port other than 443.  And when you check the box for 'Override server settings,' be sure you put in that same port (not 443) and check the box for https.

    You will want an externally-resolveable DNS name for your externally-accessible MMS SS to go along with your externally-signed SSL certificate.  It's more headache than its worth to configure an internal MMS SS with a self-signed certificate.  Many do not have sufficient certificate infrastructure internally to configure this properly.