04-24-2012 07:11 PM
Is it evident to anyone else from the supplied documentation that your UDS server needs to be in a DMZ so it can be accessed from the outside? It makes total sense but very little is noted in the documentation about this. After spending 4 hours with BES support on the phone yesterday I'm really discouraged about ths product.
04-24-2012 10:31 PM
If you can point out what doesn't make sense in this documentation i'm sure someone can help you.
page 10 of the install guide for ports on the communication server (see external):
page 9 of feature and tech overview for a diagram of a DMZ install:
04-27-2012 12:13 AM
Our UDS is definitely not sitting in our the DMZ and is communicating fine. You just need to ensure that the SSL traffic can get through from the outside to the UDS server.
Couldn't you potentially have more issues with it being in a DMZ, like EAS communication?
04-27-2012 08:50 AM
In my Fusion setup, I have the UDS core/console services installed on a box on my local lan and the communication module for UDS in the DMZ, and all works fine. As long as you have all the appropriate ports opened to/from the box on your local LAN, and outbound from the box in the DMZ you should be good.
04-27-2012 09:51 AM - edited 04-27-2012 09:52 AM
I'm using a Digicert UC cert and have no issues. As long as the CN for your cert is the externally accessible DNS record you should be ok. I have other domains on that cert too and have no issues.
I uploaded the CSR from IIS7 to digicert and exported the server certificate (in crt format instead of cer, as there is a IIS7 bug for .cer cert imports) and all was well. Then you export the certificate from IIS with a password and use it to continue through the UDS communication module install.