Re: Change public domain name for E-mail and Web on SBS2003

Tech-Archive recommends: Speed Up your PC by fixing your registry

Thanks! I already understood the basics of requesting an SSL cert and
installing it, though that article was helpful in suggesting to create a
temporary web site to make the request so I didn't have to remove the
self-cert from everything while the request was being processed.

The question is more to, assuming I've already got everything set up
correctly with e-mail and SSL certificate with whatever registered domain
name we have now.

The company has changed it's name and thus it's registered domain name.

I need to change the e-mail addresses, and the SSL certificate to match the
new registered domain name.

As I said in my first message I think I've got the e-mail thing down in
general by just running the Connect to the Internet Wizard. And I did see
that when I ran that, it created a new self-signed certificate for me using
the new domain name.

There is one catch on the e-mail. I'm trying to go into the accounts of all
the users and remove the old e-mail addresses. It lets me remove them but
when I go back into the account, the old e-mail address is back. How do I
get it to permanently remove the old addresses?

Then back on the 3rd party SSL certificate idea. Again, assuming I've
already got one installed and working properly with the old registered domain
name, do I just need to resubmit a new request to get a new certificate with
the new domain name and install it the same I way I did the original
certificate?

And just to confirm, there are no other configuration changes I need to make
to the SBS server anywhere, just run the Connect to the Internet Wizard and
request and install the new SSL Cert?

Oh, one other thing. The Remote Web Workplace screen still shows the old
company name. How do I change that?

Thank you again.

"Cris Hanna [SBS - MVP]" wrote:

Everything on your SBS 2003 server depends on the SSL cert being correct. However if it doesn't match..it will still allow you to get by it.
This link should help
http://blogs.technet.com/sbs/archive/2007/08/21/how-to-install-a-public-3rd-party-ssl-certificate-on-iis-on-sbs-2003.aspx


--
Cris Hanna [SBS - MVP]
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.


.

Relevant Pages

  • Re: Certificate Woes
    ... 2.How did you generate the CSR (Certificate Signing Request)? ... 3.How did you install the Certificate? ... Here is an example/video about installing one of the most popular SSL ...
    (microsoft.public.windows.server.sbs)
  • Re: SSL broken after Windows 2003 upgrade
    ... The svchost.exe you reference is "IIS". ... routes them to the appropriate w3wp.exe based on configuration from WAS ... WFetch can make both a normal SSL request as well as a Client-Certificate ...
    (microsoft.public.inetserver.iis)
  • Re: Trend Micro CSM Suite v2 and ISA 2004
    ... SSL is the default, and it should work. ... Run setup - install on IIS is generally the only selection available. ... Accept the client installation for the SBS (installs the Officescan ... then open the admin console. ...
    (microsoft.public.windows.server.sbs)
  • Re: Change public domain name for E-mail and Web on SBS2003
    ... self-cert from everything while the request was being processed. ... I need to change the e-mail addresses, and the SSL certificate to match ... just run the Connect to the Internet Wizard ... request and install the new SSL Cert? ...
    (microsoft.public.windows.server.sbs)
  • Re: SSL broken after Windows 2003 upgrade
    ... > routes them to the appropriate w3wp.exe based on configuration from WAS ... > WFetch can make both a normal SSL request as well as a Client-Certificate ... SSL Diag tells you that SSL should be working assuming the website ...
    (microsoft.public.inetserver.iis)