Hello,
I have a single application Win2003 server that I intended to sit in our
cage at the ISP along with our Win2003 web server. This server is only for
processing email newsletters and reminders to clients using Campaign
Enterprise software.
Because I wasn't intending to keep it in house I set it up without joining
our company's NT4 domain. In other words, it is stand-alone with it's own
Workgroup name. Now, I am having a great deal of difficulty accessing an
Exchange mailbox to process the bounceback emails. So until I can drive
upstate for the 3-hour trip I want to try putting this email newsletter
server into our NT4 domain so that I can use the bounceback email feature
temporarily.
In the end however, I absolutely want to move this server up to the ISP and
put it in the cage behind the firewall with it's brother Win2003 web server.
At that time I will probably configure Win203 POP and SMTP to send and
receive newsletter emails and bouncebacks.
I have previously joined 3 Win2003 web server to our NT4 domain with no
problems. Can anyone think of any difficulties I might have by temporarily
joining the domain with this server and then pulling it out and moving to
the ISP and reestablishing it's status as Workgroup instead of our company
domain?
Thanks much, Jerry
|
Similar Threads
Linear Mode
