Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 485
  • Last Modified:

Exchange Server 2010 Setup/Configuration

Hey guys,

I've recently setup Windows Exchange Server 2010, on Windows Server 2008 on a Virtual Machine.

I've managed to get all the pre-requisites, and have installed exchange successfully. OWA seems to be working good, and I have logged in with my users. I've also setup the send/receive connectors, and have configured the ports on my router. I am also able to send out emails.

I will be using this with an external domain. Before I change my DNS to point to my Exchange server, did I miss any steps before launching?

Another question is the OWA address has HTTPS on it, but they don't have a security certificate to use. Can I just change the domain in the Exchange Manager from "https://domain.com/owa" to "http://domain.com/owa" - or do I need to do something else?

Also what should I change my DNS too on my external domain? And will it take affect immediately?

Any help is appreciated.

Thanks.
0
barbs1
Asked:
barbs1
  • 18
  • 10
1 Solution
 
praveenkumare_spCommented:
if u want to use https u have to get a certificate, if ur fine not using SSL u can go to IIS manager , select the owa Virtual directory and select SSL settings and uncheck the option which says "Require SSL"

and internal DNS change is immediate , but external DNS change can take a maximum of  72 hours

make ur owa url to point to exchange 2010 server
0
 
barbs1Author Commented:
Are you able to describe "make ur owa url to point to exchange 2010 server"

Also, are there any other steps I missed other then that?

On my external domain to I make a new A record and name it OWA and point to my exchange server? How about for POP/IMAP/SMTP? What name/type do I put them as?
0
 
barbs1Author Commented:
Also, I unchecked "Require SSL" from the owa sub-site and I still need to type in HTTPS? Should I also remove this anywhere else (so they don't require SSL for IMAP/POP/SMTP??)
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
praveenkumare_spCommented:
also remove the "Require SSL" from the Default web site

in exchange 2010 u just need to take care of owa as, mostly IMAP/POP will use the same url

by "make ur owa url to point to exchange 2010 server" i mean to say to create a external host A record such that when users type thier OWA url they are taken to ur Exchange server
0
 
barbs1Author Commented:
Should I worry about changing the MX records on the external domain? Or can I create OWA, and point IMAP/POP/SMTP to that too?
0
 
barbs1Author Commented:
Also, I have unchecked SSL from the Default Website and still same thing.. I have restarted IIS too.
0
 
praveenkumare_spCommented:
are u sure that "Default web site" and owa Virtual directory have "Require SSL"  unchecked and has client certificates to ignore ???


what is the url that the clients use for accesssing owa ??
0
 
barbs1Author Commented:
Yes..

The address they are using is https://XX.XX.XX.XX/owa

Would like it to be http://XX.XX.XX.XX/owa

Should I change the domain on EMC to http:// instead of https:// for it?

Also, what address will I use for POP/IMAP/SMTP? Same as OWA?
0
 
praveenkumare_spCommented:
ya the address will be same as owa

ya we have to change in EMC also to http rather than https
0
 
barbs1Author Commented:
Thanks, but it still requires us to type https even after that change.
0
 
praveenkumare_spCommented:
what happens when u type http ?
0
 
barbs1Author Commented:
Gives me a 404 error (page not found).
0
 
barbs1Author Commented:
My fault.. now neither HTTP or HTTPS work??
0
 
praveenkumare_spCommented:
did u try recreating the owa VDs

Remove-OwaVirtualDirectory "exchange (default web site)"
Remove-OwaVirtualDirectory "public (default web site)"
Remove-OwaVirtualDirectory "exchweb (default web site)"
Remove-OwaVirtualDirectory "owa (default web site)"


New-OwaVirtualDirectory "exchange" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Mailboxes -WebSiteName "Default Web Site"
New-OwaVirtualDirectory "public" -OwaVersion Exchange2003or2000 -VirtualDirectoryType PublicFolders -WebSiteName "Default Web Site"
New-OwaVirtualDirectory "exchweb" -OwaVersion Exchange2003or2000 -VirtualDirectoryType Exchweb -WebSiteName "Default Web Site"
New-OwaVirtualDirectory -name "owa" -OwaVersion Exchange2007 -WebSiteName "Default Web Site" –InternalURL https://internalURL/owa -ExternalURL https://externalURL/owa 
0
 
barbs1Author Commented:
I am running on Exchange 2010, are you sure that will work?
0
 
barbs1Author Commented:
And as I've told you before, it still shows the OWA internally/externally on EMC as HTTPS.
0
 
barbs1Author Commented:
OK, so OWA doesn't work internally or externally anymore..

Does anyone else have a suggestion??
0
 
praveenkumare_spCommented:
when running this command

New-OwaVirtualDirectory -name "owa" -OwaVersion Exchange2007 -WebSiteName "Default Web Site" –InternalURL https://internalURL/owa -ExternalURL https://externalURL/owa 

did u change the URLs or did u blindly used the command
0
 
praveenkumare_spCommented:
if yes then go to EMC and under client Access in server configuration

change them to indicate the proper internal and external url
0
 
barbs1Author Commented:
Still doesn't work whether its http OR https.. And OWA still doesn't work internally or externally.. can anyone please provide with a solution??
0
 
barbs1Author Commented:
Yes, that is what I've been talking about the entire time.. even when I change that to http or https OWA still doesn't work internally and externally.. It was working originally.
0
 
barbs1Author Commented:
Actually OWA does work when I punch in http://192.0.0.110/owa
0
 
barbs1Author Commented:
But it's just not working from the external IP address now..
0
 
barbs1Author Commented:
OK, seem to have got OWA back-up now.. I didn't have port 80 open on my router...

Now, my final question.. (as part of my original)...

 I've also setup the send/receive connectors, and have configured the ports on my router. I am also able to send out emails.

I will be using this with an external domain. Before I change my DNS to point to my Exchange server, did I miss any steps before going live in my orginization? Or is all thats required now is changing the DNS records?

If so, what do I change the DNS records too? Can I also use "exchange.domain.com" for POP/IMAP/SMTP instead of "owa.domain.com".. Please advise whether I use A/AAA/CNAME/MX?

Thanks for all the help!
0
 
praveenkumare_spCommented:
what happens if u type in http://cas-servername/owa ?

what is the external Ip address of ur owa ?

if ur IP address is not taking you to OWA , it means the External A record is not created properly that points to this server
0
 
barbs1Author Commented:
That issue has been resolved as http://XX.XX.XX.XX/owa now works.. Please advise to my above question (ID: 35203680)
0
 
barbs1Author Commented:
wasn't straight forward or concise at all. never really answered any questions fully.
0
 
praveenkumare_spCommented:
sorry i made a mistake by posting so many questions and trying to help u resolve the issue , never have i asked so many questions for any query posted in expert exchange
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 18
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now