Link to home
Start Free TrialLog in
Avatar of badabing1
badabing1

asked on

Edge Server & CAS Array

Hi,

why is it that i cant create a send connector on Edge server (after edge subscription is enabled with hub transport)? do i have to remove edge subscription first and then create send connector on edge and then create subscription with HUB?

i have two exchange servers, i want to create a CAS ARRAY, how will this work for external users, will i need  a new certificate for with SAN included for both servers as well as cas array name?

ive read some articles on google but kind of still unsure please can someone explain in plain english?

Thanks
Avatar of Akhater
Akhater
Flag of Lebanon image

>why is it that i cant create a send connector on Edge server (after edge subscription is enabled with hub transport)? do i have to remove edge subscription first and then create send connector on edge and then create subscription with HUB?<

No when you have an edge subscription the send connectors should be created from the HUB and not from the edge

>i have two exchange servers, i want to create a CAS ARRAY, how will this work for external users, will i need  a new certificate for with SAN included for both servers as well as cas array name?

Yes you need to install a SAN certificate on both, you don't need the server names in the SAN just an FQDN that you will have to map to the NLB ip
The second part of my answer doesn't sound clear enough

1. the server names do not need to be in the SAN but you can add them if you want
2. the cas array name is not needed in the san certificate and should not be resolvable from outside
3. you need an FQDN, say webmail.domain.com, resolvable from outside to a public IP and that public IP nated to the NLB ip of your CAS server. that FQDN should be in the certificate.
4. yes the certificate should be installed on both cas servers


Avatar of badabing1
badabing1

ASKER

answer to my first part of question is not clear to me-

before edge subscription i had two send connectors, one going over DNS and the other over SMATHOST. now when i created edge subscription it created two connectors automatically. (thats fine) but the connector i have for smarthost dont seem to get created in edge, and im using that for sending email to hotmail as sending over DNS is rejected by hotmail.

if i leave the smarthost send connector on HUB i can carry on sending email to hotmail, but this means that its not going through edge??

second part of question-

currently all the roles are same on both servers - i read somewhere that NLB and cluster cannot coexist on the same server- therefore CAS role has to be on a diffrent server for CAS ARRAY?

Thanks
The connector is created FROM the hub server, while creating it you can choose the edge as source server


for the second part of the question

> i read somewhere that NLB and cluster cannot coexist on the same server-<
WINDOWS NLB cannot be coexist with mailbox servers if these are in a DAG. Do you have a DAG ?
i have a dag.
not clear on the bit for edge you responded, please can you explain?

Thanks
ASKER CERTIFIED SOLUTION
Avatar of Akhater
Akhater
Flag of Lebanon image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ok, brilliant thats worked- im not sure if you are happy to answer another question i have-

if not ill allocate these point to you-

do you know why my OOF reply dont get to my work email and hotmail account- i can receive it fine on Gmail and internally- so surely OOF is working but soemthing is either rejecting it from the above mentioned domain- or else i have missed something in the setup of exchange 2010?

Thanks
there is nothing special to setup for hotmail if it works, it works. do check your tracking logs to know what is happening with the email


Just for info an OOF reply is sent only once so if you got it once on an email you will not get it another time
where would those logs be and which log should i be looking at?

yes - i know the second part of your answer..

Thanks
in the EMC toolbox message log explorer
thanks for all your help!