- 1 Hyper-V 2012 R2: Pros and Cons of Generation 1 vs. Generation 2 VMs
- 2 Harnessing the Power of Hyper-V Network Virtual Switches
- 3 Working with SSH and Secure FTP Servers in Windows
- 4 Discover Windows 8's Hidden Server Features
- 5 Server Virtualization Customer Reviews: VMware, Hyper-V, XenServer and More
Learn Exchange Server 2000: Exchange System Manager Page 2
Welcome to Exchange Server 2000
So there we have it, the new look and feel of Exchange 2000. But at this point, what we have done is comparable to walking on to a car lot and walking around the car. We are enticed by the lines, we like the colors, it seems to fit us well. But the question that is really nagging at us is, "What's under the hood?". Well, don't just do something, sit there and I will show you! One of the first things that I noticed about Exchange 2000 was its integration with Windows 2000. The two go together like peanut butter and jelly, fish and chips, pretzels and, well, you get the picture. In fact, Exchange 2000 not only requires Windows 2000, but it requires Active Directory as well. Unlike Exchange 5.5, which stored its information in its own directory, Exchange 2000 stores its directory information inside of Active Directory. This provides us as administrators with centralized object management and simplified security management to start.
Exchange 2000 can also use either Security groups or Distribution groups as Distribution Lists, so this eliminates the need to create redundant groups in Exchange 2000. Also, because the Exchange 2000 information is stored in Active Directory, replication of Exchange information occurs as part of the normal AD replication process, improving network efficiency. More on these topics a little later in the series.
Another big change from previous Exchange versions is the integration between Exchange 2000 and IIS 5.0. In previous versions, Exchange actually had its own SMTP, POP3 and NNTP services, amongst others. Not any more. In Exchange 2000, the protocols are all part of IIS, and their functionality is extended with the introduction of Exchange 2000 into the network. Exchange simply worries about the public and mailbox stores, which we will be getting to in a future article. OWA has been enhanced and is now setup by default when you install Exchange 2000. Just direct your browser to http://exchange_server_name.yourdomain.com/exchange, and you are ready to rock and roll. Some of the enhancements to OWA include the ability to place audio and video clips directly into a message and support for public folders that contain contacts and appointments. I am including a look at the interface here so that you can see how much closer OWA resembles the full blown Outlook client than its predecessor.
And while we are at it, you might notice that I have an NDR (Non-Delivery Receipt) that has been sent to the administrator. This question had come up in the newsgroups the other day (thanks Kathy!) so I thought that this might be a great chance to give you a VISUAL indication of what happens when we set up someone to receive an NDR. Normally we probably won't use OWA for this purpose, but it gives us the chance to see how versatile this product is. I open up the NDR report, and you will notice an attachment called Test:
If I open up the attachment, I can see the body of the message that was undeliverable. In this case, it was a test message that I had sent to see how OWA would handle NDR's.
As you can see, I have answered all the questions that I had in my e-mail, and Kathy should be happy to know that she can use either OWA or Outlook to receive NDR reports and view the original messages that had been sent. Outlook handles the process a little more cleanly in my opinion, and if you have questions on how that works, see the post entitled, "NDR Forwarding" from Kathy in the Exchange 2000 newsgroup here at 2000trainers.com.