It's in two parts, from server side (Exchange 2007 HUB Role) and from outlook side
A- From server Side:
Exchange 2007 by default will block autoreplies and auto forward messages, hence we need to configure this to allow this-like messages
1- open EMC and go to organization configuration
2- navigate to Hub transport and remote domains tab
3- click properties of the remote domains and go to Message format tab
4- check the check box there that allow auto reply (and auto forward if needed) and OK
B- From OUTLOOK
1- Open Outlook.
2- Click Tools, and click Rules and Alerts.
3- Click New Rule, select "Start from a blank rule", select "Check messages when they arrive" and click Next.
4 - Select "Send only to me" and click Next.
5- Select "have server reply using a specific message".
6- In the bottom box, click "a specific message", enter the Subject and body for the autoreply message and click "Save and close".
Now test it by sending a message to the configured account and you will get an autoreply
Thanks To: drkernel
Showing posts with label EXCHANGE COLLECTIONS. Show all posts
Showing posts with label EXCHANGE COLLECTIONS. Show all posts
Configuring OWA in Exchange Server 2003
When Microsoft created Exchange Server 2003, some of the biggest improvements that they made over Exchange 2000 were to OWA. Unlike previous versions of Exchange, OWA now looks and feels a lot like Outlook. In fact, you can do most of the things in OWA that you can do in Outlook. Best of all, OWA is now enabled by default. You can access OWA by opening Internet Explorer and enteringhttp://server's_IP_address/exchange. Before you get too excited though, there are some serious security implications to having OWA enabled by default. In this article, I will explain what you need to know about configuring OWA the safe way.
What are the risks?
Since Microsoft enables OWA by default, it would seem that having OWA enabled is harmless. By itself, OWA is pretty much harmless. After all, OWA is nothing more than a Web site that acts as an interface to a user's mailbox. The security risks have to do with the way that the network is configured.
To understand why an improperly configured OWA instance is such a threat, you must consider the nature of the server that OWA exists on. Exchange Server is publicly accessible by its very nature. If it weren't then no from the outside world would be able to send e-mail to mailboxes residing on the server. The reason why it is possible to send e-mail messages to mailboxes on the server is because the server has a publicly accessible IP address (port forwarding might be used as an alternative, but I will talk about that later). If someone from the outside world wants to send a message to one of your users, their mail client will perform a DNS query to determine the IP address associated with your mail server. Once the client knows the IP address, mail is transmitted to that address using the SMTP protocol.
Like every other server on your network, your Exchange Server is probably behind a firewall. The firewall is responsible for blocking any protocol that you don't specifically allow. However, the SMTP protocol is allowed to reach your mail server because you would not be able to receive external mail without it.
Keep in mind that this very same server is also running OWA. However, if your firewall isn't configured to allow inbound HTTP traffic, then OWA won't be accessible to those outside your network perimeter. You could technically allow the outside world to access OWA by simply allowing the HTTP protocol to pass through your firewall. This is an extremely bad idea though.
Right now you might be wondering why it's safe to allow SMTP traffic to reach the server, but it isn't safe to permit HTTP traffic. The reason for this is that SMTP is an extremely simple protocol. It has one use and one use only; to send and receive messages. HTTP on the other hand is much more complex. There are dozens of known HTTP exploits. If you blindly allow HTTP traffic to pass through your firewall, you are asking for trouble.
The solution
There are several tricks to implementing OWA safely. The first trick is to control how traffic enters your network. You can't really get around permitting inbound HTTP and HTTPS traffic. You can however isolate that traffic so that outsiders can't use HTTP exploits against other parts of your network.
I have seen some people accomplish this isolation by placing an Exchange Server into a DMZ. DMZ stands for demilitarized zone. It refers to an isolated part of your network that the firewall does not protect. I personally think that it's a bad idea to place an Exchange Server into a DMZ because the server will have absolutely no protection. Besides, Exchange Server relies on the Active Directory. A hacker could potentially take over the Exchange Server and then use it as a staging platform for attacks against your Active Directory or against other Exchange Servers in your organization.
When it comes to controlling inbound traffic, I prefer to use a technique called port forwarding. Port forwarding allows you to redirect specific types of traffic to a designated IP address, regardless of the traffic's intended destination. For example, you could create a port forwarding rule that directs all HTTP traffic to your OWA server regardless of which server the packets were actually intended for.
Isolating OWA
Just because you have configured your firewall to direct HTTP traffic to your OWA server doesn't mean that OWA is secure though. You still have a publicly accessible server that is prone to HTTP exploits. Because the server is subject to HTTP based exploits, your best bet is to insure that there is no real data on the server. This means moving all of your Exchange databases to a different server.
This is known as a front-end / back-end configuration. The idea is that the front-end server acts as a sort of buffer against Web based attacks. Internet based users are never given direct access to the servers containing the Exchange databases. Instead, OWA users authenticate into the OWA front-end server (the server without any databases), and the front-end server acts as a proxy that relays information between the user and the back-end server.
The primary reason for implementing a front-end / back-end configuration is that doing so allows you to isolate your Exchange Servers that contain data so that those servers are in no way directly accessible from the outside world. The easiest way of accomplishing this is to multihome your front-end server. You can then attach your front-end server to an isolated segment of your network. Once the front-end server is isolated from the rest of your network, you can connect the server's other NIC to a switch on the network segment that contains your other Exchange Servers.
By connecting the front-end server to the network in the manner that I have described, it becomes accessible from both the Internet and from the private network. Since this is the case, you might be wondering what stops Internet users from passing through the front-end server and accessing the rest of your network.
The reason why you don't have to worry about Internet users accessing the rest of your network through the front-end server is because of a fundamental rule of networking. There is a rule that says that in order for two nodes to communicate on a network, they must share a common protocol. While it's true that the end user, the front-end server, and the back-end server are all using the TCP/IP protocol, they are not all using it in the same way. Remember that TCP/IP is actually a suite of protocols rather than being one individual protocol. The firewall insures that Internet users are only able to access the front-end server by using the HTTP or HTTPS protocol. However, the front-end server does not use HTTP requests to communicate with the back-end server. This prevents an Internet user from passing an HTTP request through an OWA server to the backend network.
In case you are wondering, Exchange actually contains a setting that you can use to designate a server as a front-end OWA server. If you were to open the Exchange System Manager, navigate to Administrative Groups | your administrative group | Servers | your server, right click on the server and select the Properties command from the shortcut menu, you would see that the General tab of the server's properties sheet contains a check box that you can use to designate the server as a front-end server. When you select this check box, Exchange will automatically take care of some of the security requirements pertaining to keeping the Exchange databases isolated.
Encrypting OWA traffic
Another reason why a default OWA installation is a threat to your network's security is because by default, OWA doesn't encrypt anything. Passwords and e-mail messages are both transmitted across the wire in clear text for anyone with a protocol analyzer to read.
As you may know, Internet Information Server offers multiple authentication options. Clients accessing a Web site may use Windows integrated authentication, basic authentication, and anonymous authentication. Anonymous authentication simply won't work for an OWA Web site because OWA needs to know who is logging in so that it can display the correct mailbox.
This leaves basic authentication, which transmits passwords in clear text, and Windows integrated authentication, which is generally a better choice if the person accessing the Web site is running a Windows operating system. The problem is that you have no way of controlling what operating system your users will be running when they access your OWA Web site. That being the case, basic authentication is the only choice that will work.
Basic authentication does transmit passwords in clear text, but you can get around this problem if you encrypt the session using SSL over HTTPS. Using SSL is an ideal solution since users would otherwise be using the HTTP protocol to access the OWA server. Keep in mind though that communications between the front-end server and the back-end servers do not use HTTP and therefore SSL encryption is not an option.
If you happen to have an ISA Server at your disposal, you can make communications between the front-end server and the Internet even more secure. There is a technique by which you can copy the front-end server's certificate to the ISA server. You can then configure the ISA server to impersonate the front-end server. Internet users would never actually communicate with the front-end server directly.
Instead, the users would communicate with the ISA Server (the perimeter firewall's port forwarding feature would have to be configured to pass HTTP and HTTPS packets to the ISA Server rather than to the front-end server). The ISA Server would then act as an application level firewall / proxy. It would screen inbound HTTP and HTTPS requests. If the requests were valid then the requests would be passed along to the front-end server. The server's response would then be relayed back to the user. If the inbound packets are determined to be malicious, then the packets are blocked from ever reaching the front-end server.
Communications between the front-end server and the back-end servers seems to be a touchy issue for some reason. There are a couple of different schools of thought on the subject. Some people believe that since users are authenticated prior to the front-end server ever initiating communications with the back-end server, the user is trusted. Furthermore, the packets are flowing across your own private network, so there is no need to encrypt communications between the front-end server and the back-end servers. On the flip side of the issue, security purists believe that you should encrypt any traffic that's flowing across your network as a way of protecting user's privacy and as a way of guarding the system against security breaches.
I personally believe that whether or not you encrypt front-end to back-end traffic should depend on your own organization's security needs. If you do decide that IPSec encryption is necessary, then you might be interested in knowing that you can't implement IPSec in the usual way.
Windows has three different IPSec policies built in. I don't really want to get into all of the specifics regarding these policies because they are beyond the scope of this article. Generally speaking though, if you activate any of the built in policies, then the policy will apply to all IP traffic flowing in or out of the machines that the policy applies to.
The reason why the built in policies are not appropriate is because you don't want blanket IPSec encryption to apply to the front-end server. Remember that a lot of the traffic that's coming into the front-end server is coming from the Internet and is already encrypted with SSL. You don't want to attempt to encrypt that traffic with IPSec. The back-end server on the other hand can use a blanket IPSec policy. The backend server will never communicate directly with Internet users. Since the back-end server's communications will be limited to the private network, encrypting all inbound and outbound traffic with IPSec is perfectly acceptable.
There are a few different ways that you can get around the blanket coverage problem. What I recommend doing is to create a separate organizational unit within the Active Directory and moving your front-end server into it. The reason why I suggest doing this is because IPSec policies are group policy objects. Group policies can be applied at the organizational unit level. This means that you could have one IPSec policy for your front-end server and a separate IPSec policy for everything else (including your back-end servers).
There is also another side effect to using a separate organizational unit for the front-end server. Having the front-end server placed in a separate organizational unit from everything else allows you to assign the server an entirely different computer level security policy. Since the server will be accessible from the Internet, you have to assume that the server will be attacked on a regular basis. The fact that the server will have its own security policy means that you can defend the server by applying a very rigid security policy without affecting any of your users or any of your other servers.
OK, so we've established that you will need a separate IPSec policy for the front-end server, but you might still be wondering how you would prevent the front-end server from having blanket IPSec encryption. Microsoft gives you a few built in IPSec policies that you can activate, but there is nothing stopping you from creating your own policy. An IPSec policy is nothing more than a collection of rules.
For the front-end server's IPSec policy, you must simply create a policy around rules that tell Windows to encrypt any traffic flowing between the front-end server and the backend server. All other traffic should remain unencrypted. As you create the rule, you will have to specify each backend server by IP address. If you add an additional backend server later on or if the server's IP address changes, you will have to update your rule to match the change.
Download:Troubleshooting Outlook Web Access(OWA) problems
Outlook Web Access (OWA) is an indispensable application in many organizations because it allows users to check their e-mail from anywhere in the world using only a Web browser. Unfortunately, OWA doesn’t always work the way that it’s supposed to. In this Daily Drill Down, I’ll show you what to do when OWA breaks down.
What OWA does
An OWA environment is nothing more than an IIS-based Web application with an interface to the Exchange stores. Clients access the OWA site by making a request to the IIS server over port 80 (HTTP) or port 443 (HTTPS). Once the initial request has been processed, the IIS Server asks the client for authentication credentials. The OWA Server takes these credentials and attempts to authenticate the client. Once they’re authenticated, clients can access their Exchange e-mail accounts.
Problems with OWA
Problems with OWA can usually be traced to one of the following areas:
The client’s Web browser
The client’s connection to the IIS Server
An IIS problem
An Exchange problem
Any one or any combination of these problems can keep OWA from functioning. Naturally, some of the problems that I just described are a little tougher to troubleshoot than others. Therefore, I’ll start with the easier solutions and build up to the more complex troubleshooting issues.
Client problems
There are many different types of OWA problems, but what the client gets often yields clues as to the nature of the problem. For example, a message stating that a Web site can’t be found means something completely different from a message indicating that the page isn’t displaying correctly.
If the client receives a message stating that the OWA Web site can’t be found, there are a number of possible causes to investigate. I recommend troubleshooting such a problem by first trying to access the OWA server from another computer. If other computers can access the OWA site, then the problem is likely with the computer in question’s Internet connection and not with OWA.
On the other hand, if none of the computers that you attempt to access OWA through can attach to the OWA server, then you have a more serious problem. The WAN connection linking the OWA Server to the Internet may be down; IIS could be malfunctioning; or there could be an invalid DNS entry that’s pointing the OWA server’s FQDN to an invalid or incorrect IP address. I’ll discuss these problems in a bit more detail later on.
Another possibility is that the client is able to access the OWA site, but the site displays incorrectly, or the user isn’t allowed to log in. Again, begin the troubleshooting process by trying a different computer. This particular problem is often due to someone using an unsupported Web browser to access OWA. However, if you discover that none of your test computers can authenticate into the OWA Server, it’s likely that you have an authentication problem on the server end rather than a Web browser problem.
IIS connection errors
IIS connection problems and other IIS-related malfunctions are among the most common causes of OWA errors. It’s a lot of work to thoroughly troubleshoot IIS problems, but the necessary steps aren’t especially difficult. I recommend beginning the troubleshooting process by going to the OWA Server and verifying its connection to the Internet. If you can surf the Web from the OWA server, you can rule out a connectivity problem.
Next, go to a computer outside your network and attempt to ping your OWA server. Try pinging first by IP address and then by FQDN. If both pings fail, it probably means that your firewall is set to block ICMP packets and that the server won’t respond to a ping. If this happens to you, I recommend trying the ping test from behind your firewall.
A failure of both pings could also mean that there is no connectivity between the machine that you’re pinging from and the OWA server. This won’t apply in this particular case, though, because you’ve already established that the communications link is good.
If the ping by IP address is good but the ping by FQDN fails, then you likely have a DNS problem. Remember that DNS servers resolve FQDNs to IP addresses. Therefore, if a ping by IP address is successful, you can verify that the communications link is good. If this is the case, then the only thing that should cause a ping by FQDN to fail is if the FQDN isn’t being resolved.
Firewall problems
So far you’ve verified that you’ve got a good communications link and that the DNS server is doing its job. If your clients are still unable to connect to the OWA server, it’s probably either due to a firewall problem or an IIS failure.
Testing for a firewall problem is easy. Just try to access the OWA server from behind your firewall. If both the OWA server and the client machine exist on your private network behind the same firewall, you can use the client machine to test the OWA server without the firewall interfering. If the test is successful, then the firewall is your problem. Verify that ports 80 and 443 are open to inbound traffic.
IIS problems
If the firewall doesn’t seem to be the source of your problems, then there’s a really good chance that IIS is causing the problem. To test IIS, begin by selecting the Programs | Administrative Tools | Services commands from the Start menu. When you do, Windows will open the Service Control Manager. Go through the Service Control Manager and verify that the following services are running:
World Wide Web Publishing Service
IIS Admin Service
Protected Storage
Remote Procedure Call (RPC)
This is also a good time to verify that the various Microsoft Exchange-related services are running as well.
Once you’ve verified that the necessary IIS services are running, open Internet Explorer directly on the OWA Server and enter the OWA Server’s IP address into the browser. If the OWA session starts, IIS is working correctly. If you can’t get OWA to start by entering the IP address, verify that IIS is configured to use the correct IP address.
To verify that IIS is configured to use the correct IP address, select Internet Services Manager from the Administrative Tools menu. When the Internet Information Server console opens, select the OWA Web site from the console tree. Before continuing, verify that the word Stopped doesn’t appear in parenthesis next to the Web site name. If it does, simply right-click the site and select the Start command. If you receive an error message, your OWA site probably has an IP address conflict with another site on the server. To solve this problem, read the following instructions for verifying the IP address, and then try to start the site again.
Verifying the OWA site's IP address
To verify the site’s IP address, right-click the OWA site and select Properties. On the site’s property sheet, select the Web Site tab and verify that the IP address is correct. By default, the IP address will be set to All Unassigned. However, the All Unassigned setting should be used only for the default Web site. The OWA site should have a dedicated IP address. While on the Web Site tab, you should also verify that the OWA site is configured to use port 80.
If all of your settings are correct but you still can’t access the OWA Web site, the best thing to do is to implement a sample Web site to verify IIS’s functionality. To do so, open the Control Panel and double-click the Network And Dial Up Connections icon. When the Network And Dial Up Connections window opens, right-click your main network connection and select Properties.
On the connection’s property sheet, select the TCP/IP protocol from the list and click the Properties button to reveal the TCP/IP property sheet. On the TCP/IP property sheet, click Advanced to reveal the Advanced TCP/IP Settings property sheet. On the IP Settings tab of the Advanced TCP/IP Settings property sheet, click the Add button under the IP Addresses section and add a unique IP address to the server. Click OK on all of the open windows to close them.
Now, create a directory called Test on your hard disk and place a few random HTML files into it. Be sure to name one of the files INDEX.HTM. At this point, return to the Internet Services Manager. Right-click the server name in the console tree and select New | Web Site. This will launch the Web site creation wizard.
Click Next to bypass the wizard’s introduction screen. You’ll then be asked to enter a description of the site. Enter the words Test Site and click Next. On the following screen, select the IP address that you added to the server from the Enter The IP Address To Use For This Web Site drop-down list. Verify that the site is configured to use TCP port 80, and then click Next. On the following screen, enter C:\TEST as the path to the home directory. You should also make sure that the Allow Anonymous Access To This Web Site check box is selected. You’ll then see a screen asking what permissions should be set for the home directory. Accept the default choices by clicking Next, followed by Finish.
When you’ve completed the test site, you’ll see it appear in the IIS tree with the words Stopped in parenthesis next to it. Right-click the new site and select the Start command from the shortcut menu. The site should now be started.
Next, open Internet Explorer and enter the new site’s IP address followed by INDEX.HTM. For example, if you assigned the address 147.100.100.100 to the site, the format would be http://147.100.100.100/index.htm. If you can access your test site, then IIS is functional and you likely have an authentication problem.
If you discover that IIS is malfunctioning, I recommend reinstalling it. You can do so through the Add/Remove Programs applet in the Control Panel. IIS is located in the Windows Components section.
Authentication problems
The authentication portion of Outlook Web Access tends to be one of the trickiest parts to troubleshoot. When troubleshooting authentication problems, it’s helpful to keep in mind that when your users use OWA, they aren’t telling OWA which Exchange server their mailboxes exist on. Instead, OWA is performing an Active Directory query during the authentication process. This query tells OWA which Exchange server to connect the user to.
It’s quite possible that the Active Directory query could be causing the problem. The easiest way to find out is to enter the URL of the OWA site into the Web browser in a way that conveys the name of the user’s mailbox. For example, if you normally enter http://server_name/exchange, try entering http://server_name/exchange/user_name instead. If this technique works, then the problem could be due to the OWA server’s TCP/IP settings not referencing a DNS server that’s aware of your Active Directory. The other possibility is a problem with the authentication protocol, which is what I’m about to show you how to fix.
When it comes to Windows 2000 authentication, the NTLM authentication protocol is more secure than basic or anonymous authentication. However, in an OWA environment, you must use basic authentication. NTLM doesn’t work if your clients are communicating with the server over HTTP or HTTPS. Likewise, anonymous authentication does work, but it would give everyone in the world access to your server. Therefore, basic authentication is your only real choice.
To verify what type of authentication is being used, open the Internet Services Manager, right-click the OWA Web site, and select Properties. Select the Directory Security tab on the OWA site’s property sheet, and click the Edit button found in the tab’s Anonymous Access And Authentication Control section. When you do, you’ll see the Authentication Methods dialog box. Verify that the Anonymous Access check box is not selected. Now, take a look at the Authenticated Access section and verify that only the Basic Authentication check box is selected. As you look at the various check boxes, you’ll notice an Edit button just to the right of the Basic check box. Click the Edit button and verify that the correct authentication domain is selected.
At this point, close all of the open windows by clicking OK in each. You’ve now specified that the OWA Web site will use basic authentication exclusively, and that a specific domain will perform the authentication. The final step in the process is to verify that the OWA server can communicate with the domain that you’ve specified.
You can start out by attempting to ping domain controllers in the specified domain from the OWA server. If the pings are successful, the next step is to verify that the OWA server is configured to use the same DNS server as all of the domain controllers. Unless all of the servers use a common DNS server (or linked DNS servers), the OWA server may have trouble accessing Active Directory information from the domain controller.
If you're still having trouble
OWA is a handy Web application, but it doesn’t always work the way it’s supposed to. If you’re still having problems, Microsoft has an excellent document on OWA troubleshooting at Microsoft’s Exchange Web Site.
What OWA does
An OWA environment is nothing more than an IIS-based Web application with an interface to the Exchange stores. Clients access the OWA site by making a request to the IIS server over port 80 (HTTP) or port 443 (HTTPS). Once the initial request has been processed, the IIS Server asks the client for authentication credentials. The OWA Server takes these credentials and attempts to authenticate the client. Once they’re authenticated, clients can access their Exchange e-mail accounts.
Problems with OWA
Problems with OWA can usually be traced to one of the following areas:
The client’s Web browser
The client’s connection to the IIS Server
An IIS problem
An Exchange problem
Any one or any combination of these problems can keep OWA from functioning. Naturally, some of the problems that I just described are a little tougher to troubleshoot than others. Therefore, I’ll start with the easier solutions and build up to the more complex troubleshooting issues.
Client problems
There are many different types of OWA problems, but what the client gets often yields clues as to the nature of the problem. For example, a message stating that a Web site can’t be found means something completely different from a message indicating that the page isn’t displaying correctly.
If the client receives a message stating that the OWA Web site can’t be found, there are a number of possible causes to investigate. I recommend troubleshooting such a problem by first trying to access the OWA server from another computer. If other computers can access the OWA site, then the problem is likely with the computer in question’s Internet connection and not with OWA.
On the other hand, if none of the computers that you attempt to access OWA through can attach to the OWA server, then you have a more serious problem. The WAN connection linking the OWA Server to the Internet may be down; IIS could be malfunctioning; or there could be an invalid DNS entry that’s pointing the OWA server’s FQDN to an invalid or incorrect IP address. I’ll discuss these problems in a bit more detail later on.
Another possibility is that the client is able to access the OWA site, but the site displays incorrectly, or the user isn’t allowed to log in. Again, begin the troubleshooting process by trying a different computer. This particular problem is often due to someone using an unsupported Web browser to access OWA. However, if you discover that none of your test computers can authenticate into the OWA Server, it’s likely that you have an authentication problem on the server end rather than a Web browser problem.
IIS connection errors
IIS connection problems and other IIS-related malfunctions are among the most common causes of OWA errors. It’s a lot of work to thoroughly troubleshoot IIS problems, but the necessary steps aren’t especially difficult. I recommend beginning the troubleshooting process by going to the OWA Server and verifying its connection to the Internet. If you can surf the Web from the OWA server, you can rule out a connectivity problem.
Next, go to a computer outside your network and attempt to ping your OWA server. Try pinging first by IP address and then by FQDN. If both pings fail, it probably means that your firewall is set to block ICMP packets and that the server won’t respond to a ping. If this happens to you, I recommend trying the ping test from behind your firewall.
A failure of both pings could also mean that there is no connectivity between the machine that you’re pinging from and the OWA server. This won’t apply in this particular case, though, because you’ve already established that the communications link is good.
If the ping by IP address is good but the ping by FQDN fails, then you likely have a DNS problem. Remember that DNS servers resolve FQDNs to IP addresses. Therefore, if a ping by IP address is successful, you can verify that the communications link is good. If this is the case, then the only thing that should cause a ping by FQDN to fail is if the FQDN isn’t being resolved.
Firewall problems
So far you’ve verified that you’ve got a good communications link and that the DNS server is doing its job. If your clients are still unable to connect to the OWA server, it’s probably either due to a firewall problem or an IIS failure.
Testing for a firewall problem is easy. Just try to access the OWA server from behind your firewall. If both the OWA server and the client machine exist on your private network behind the same firewall, you can use the client machine to test the OWA server without the firewall interfering. If the test is successful, then the firewall is your problem. Verify that ports 80 and 443 are open to inbound traffic.
IIS problems
If the firewall doesn’t seem to be the source of your problems, then there’s a really good chance that IIS is causing the problem. To test IIS, begin by selecting the Programs | Administrative Tools | Services commands from the Start menu. When you do, Windows will open the Service Control Manager. Go through the Service Control Manager and verify that the following services are running:
World Wide Web Publishing Service
IIS Admin Service
Protected Storage
Remote Procedure Call (RPC)
This is also a good time to verify that the various Microsoft Exchange-related services are running as well.
Once you’ve verified that the necessary IIS services are running, open Internet Explorer directly on the OWA Server and enter the OWA Server’s IP address into the browser. If the OWA session starts, IIS is working correctly. If you can’t get OWA to start by entering the IP address, verify that IIS is configured to use the correct IP address.
To verify that IIS is configured to use the correct IP address, select Internet Services Manager from the Administrative Tools menu. When the Internet Information Server console opens, select the OWA Web site from the console tree. Before continuing, verify that the word Stopped doesn’t appear in parenthesis next to the Web site name. If it does, simply right-click the site and select the Start command. If you receive an error message, your OWA site probably has an IP address conflict with another site on the server. To solve this problem, read the following instructions for verifying the IP address, and then try to start the site again.
Verifying the OWA site's IP address
To verify the site’s IP address, right-click the OWA site and select Properties. On the site’s property sheet, select the Web Site tab and verify that the IP address is correct. By default, the IP address will be set to All Unassigned. However, the All Unassigned setting should be used only for the default Web site. The OWA site should have a dedicated IP address. While on the Web Site tab, you should also verify that the OWA site is configured to use port 80.
If all of your settings are correct but you still can’t access the OWA Web site, the best thing to do is to implement a sample Web site to verify IIS’s functionality. To do so, open the Control Panel and double-click the Network And Dial Up Connections icon. When the Network And Dial Up Connections window opens, right-click your main network connection and select Properties.
On the connection’s property sheet, select the TCP/IP protocol from the list and click the Properties button to reveal the TCP/IP property sheet. On the TCP/IP property sheet, click Advanced to reveal the Advanced TCP/IP Settings property sheet. On the IP Settings tab of the Advanced TCP/IP Settings property sheet, click the Add button under the IP Addresses section and add a unique IP address to the server. Click OK on all of the open windows to close them.
Now, create a directory called Test on your hard disk and place a few random HTML files into it. Be sure to name one of the files INDEX.HTM. At this point, return to the Internet Services Manager. Right-click the server name in the console tree and select New | Web Site. This will launch the Web site creation wizard.
Click Next to bypass the wizard’s introduction screen. You’ll then be asked to enter a description of the site. Enter the words Test Site and click Next. On the following screen, select the IP address that you added to the server from the Enter The IP Address To Use For This Web Site drop-down list. Verify that the site is configured to use TCP port 80, and then click Next. On the following screen, enter C:\TEST as the path to the home directory. You should also make sure that the Allow Anonymous Access To This Web Site check box is selected. You’ll then see a screen asking what permissions should be set for the home directory. Accept the default choices by clicking Next, followed by Finish.
When you’ve completed the test site, you’ll see it appear in the IIS tree with the words Stopped in parenthesis next to it. Right-click the new site and select the Start command from the shortcut menu. The site should now be started.
Next, open Internet Explorer and enter the new site’s IP address followed by INDEX.HTM. For example, if you assigned the address 147.100.100.100 to the site, the format would be http://147.100.100.100/index.htm. If you can access your test site, then IIS is functional and you likely have an authentication problem.
If you discover that IIS is malfunctioning, I recommend reinstalling it. You can do so through the Add/Remove Programs applet in the Control Panel. IIS is located in the Windows Components section.
Authentication problems
The authentication portion of Outlook Web Access tends to be one of the trickiest parts to troubleshoot. When troubleshooting authentication problems, it’s helpful to keep in mind that when your users use OWA, they aren’t telling OWA which Exchange server their mailboxes exist on. Instead, OWA is performing an Active Directory query during the authentication process. This query tells OWA which Exchange server to connect the user to.
It’s quite possible that the Active Directory query could be causing the problem. The easiest way to find out is to enter the URL of the OWA site into the Web browser in a way that conveys the name of the user’s mailbox. For example, if you normally enter http://server_name/exchange, try entering http://server_name/exchange/user_name instead. If this technique works, then the problem could be due to the OWA server’s TCP/IP settings not referencing a DNS server that’s aware of your Active Directory. The other possibility is a problem with the authentication protocol, which is what I’m about to show you how to fix.
When it comes to Windows 2000 authentication, the NTLM authentication protocol is more secure than basic or anonymous authentication. However, in an OWA environment, you must use basic authentication. NTLM doesn’t work if your clients are communicating with the server over HTTP or HTTPS. Likewise, anonymous authentication does work, but it would give everyone in the world access to your server. Therefore, basic authentication is your only real choice.
To verify what type of authentication is being used, open the Internet Services Manager, right-click the OWA Web site, and select Properties. Select the Directory Security tab on the OWA site’s property sheet, and click the Edit button found in the tab’s Anonymous Access And Authentication Control section. When you do, you’ll see the Authentication Methods dialog box. Verify that the Anonymous Access check box is not selected. Now, take a look at the Authenticated Access section and verify that only the Basic Authentication check box is selected. As you look at the various check boxes, you’ll notice an Edit button just to the right of the Basic check box. Click the Edit button and verify that the correct authentication domain is selected.
At this point, close all of the open windows by clicking OK in each. You’ve now specified that the OWA Web site will use basic authentication exclusively, and that a specific domain will perform the authentication. The final step in the process is to verify that the OWA server can communicate with the domain that you’ve specified.
You can start out by attempting to ping domain controllers in the specified domain from the OWA server. If the pings are successful, the next step is to verify that the OWA server is configured to use the same DNS server as all of the domain controllers. Unless all of the servers use a common DNS server (or linked DNS servers), the OWA server may have trouble accessing Active Directory information from the domain controller.
If you're still having trouble
OWA is a handy Web application, but it doesn’t always work the way it’s supposed to. If you’re still having problems, Microsoft has an excellent document on OWA troubleshooting at Microsoft’s Exchange Web Site.
crash course in the Exchange 2010 Control Panel
When Microsoft created Exchange Server 2007, it gave Outlook Web Access (OWA) a much-needed overhaul — becoming
a lot more like Outlook — and even added some modest management utilities. In Exchange 2010, Microsoft has once again made a lot of changes to OWA, greatly extending the management functionality with the addition of the Exchange Control Panel (ECP).
Before I get into more detail with ECP, I want to point out that there are other changes in Exchange 2010 OWA, starting with its name. Even though OWA has stood forOutlook Web Access for as long as I can remember, the folks in Redmond decided to rename OWA to Outlook WebApp. Generally speaking though, users who are used to OWA 2007 won’t have too much trouble finding their way around OWA 2010. Looking at Figure A, you can see that OWA 2010 looks very similar to OWA 2007.
Figure A
Click to enlarge.
This is what the Outlook WebApp looks like.
The most significant change that Microsoft has made to OWA doesn’t appear in the figure above though. If you look at it, you will notice an Options link, just to the left of the search box. While this link did exist in OWA 2007, its functionality has been greatly extended in OWA 2010. The Options link takes you to the ECP.
Figure B shows you the view when you click on the Options link. As you can see, the entire interface changes. Incidentally, if you need to get back to your Inbox, you can do so by clicking on the My Mail link that now replaces the Options link.
Figure B
Click to enlarge.
Another thing that I want to point out about this screen is the drop-down list in the upper left corner of the screen. You will notice that this drop-down list is presently set to Myself. You have three options; Myself, My Organization, and Another User.
Myself
The Myself area of the ECP is designed to act as a self-service portal for users. Assuming that they have the proper permissions, users can use the ECP to keep their contact information up to date, as shown in the figure above. Users also have the ability to change their password, enable the Out of Office feature, or even modify Inbox rules through this interface. Like OWA 2007, users can also use this area to manage some general OWA settings.
My Organization
Selecting the My Organization option reveals the true power of ECP. Figure Cillustrates how ECP allows you to manage things like mailboxes, groups, and even user and administrative roles through the OWA interface. While there doesn’t seem to be a mechanism in place that would allow you to create a mailbox through the ECP, you can view and edit many of the mailbox attributes.
Figure C
Click to enlarge.
The Exchange Control Panel allows you to manage mailboxes, groups, and even administrative and user roles.
You will also notice that the tree on the left in Figure C contains a Reporting option. Clicking on this option takes you to a screen that allows you to perform message tracking. This is my favorite of the new OWA / ECP features. You can see what the reporting and message tracking options look like in Figure D.
Figure D
Click to enlarge.
You can now perform message tracking through OWA’s ECP.
Another User
The Another User option is similar to the Myself option. This feature allows you to perform the same basic operations on another user’s account that you can perform on your own account by using the Myself option.
Conclusion
As you can see, the Exchange Control Panel should make managing Exchange remotely a lot easier. In case you are wondering though, the various administrative functions are only displayed to users who have the proper permissions.
TrainSignal - Exchange Server 2007 Training Videos @reuploaded for user request
TrainSignal - Exchange Server 2007 Training Videos
Here are some of the training topics you will find in our Exchange Server 2007 Training Videos:
Pre-Installation Preparation
* Hardware Requirements for Exchange Server 2007
o Creating Infrastructure
o Physical Disk Configuration
o DNS Setup in Exchange Server 2007
o AD Installation (Dcpromo)
o Domain Registration
* Requirements for Active Directory and older Exchange organizations
* Active Directory Schema Changes
* Readiness Scan
* Editions and CAL types
* Wrap-up
Installation Overview
* Installing Exchange Server 2007
o Pre-install Splash
o Error Reporting
o Install Type and Roles Selection
o Server Name
o Client Settings
o Readiness Check #2
* Verifying Install
* Finalize Deployment Tasks List
* End-to-End Scenario Tasks List
* Editing Installed Roles
* Installing SP1
Exchange Server Management Console
* Console Layout of Exchange Server 2007
* Architecture
* Role Delegation
* Grand Tour
* Finalization Tasks
* Toolbox and Extras in Exchange Server 2007
* 32-bit Edition
Exchange Management Shell
* Shell Usage Overview
* Getting Help With Syntax
* Modifying a Mailbox With the Shell
* Pipelining
* Modifying Lots of Mailboxes with the Shell
* Other Management cmdlets
Exchange Server 2007 Database
* Exchange Server 2007 Database Overview
* What's changed from Exchange Server 2003?
* Storage Groups and Databases
* Limitations
* Best Practices
Going Live With Exchange Server 2007
* Scenario
* Checklist
* Checking DNS
* Checking Listening Ports
* Testing Email Flow
Working with Recipients in Exchange Server 2007
* Configuring Mailboxes in Exchange Server 2007
* Working with Contacts
* Creating and Using Distribution Groups
* Working with Rooms and Equipment Mailboxes
* Using Recipients Filtering
Configuring Public Folders in Exchange Server 2007
* Public Folder Architecture
* Scenario
* Tools for Managing Public Folders
* Creating New Public Folders in Exchange Server 2007
* Assigning Public Folder Permissions
* Allowing Public Folders to Receive and Send Mail
Configuring Address Lists in Exchange Server 2007
* How Server Side Address Lists Work
* Creating a Custom Address List
* How the Global Address Book Works
* Brief Bit on Offline Address Books
* Dynamic Distribution Groups
* Best Practices For Using This Stuff
Configuring Outlook - AutoDiscover
* What is AutoDiscover?
* How Does It Work?
* How Do I Set It Up?
* How Do I Set Up Outlook?
* Best Practices
Configuring the Client Access Server
* CAS Role Overview
* IIS Virtual Directories for Exchange Server 2007
* Outlook Anywhere Architecture
* Setting Up Outlook Anywhere
* Active-Sync Architecture
* New Active-Sync Features in Exchange Server 2007
* Active Sync Configuration
* Best Practices
Outlook Web Access
* New Outlook Web Acces (OWA) Features
* Request From Management Relating to OWA Experience
* Light and Premium Versions
* Authentication Options
* Accessing Server-Based Shares and SharePoint Sites
* Changing the Base URL for Outlook Web Acces (OWA)
Working with POP and IMAP
* Protocol Architecture
* Management Requests
* Settings on the CAS Server
* Settings on the Hub Transport Server
* User-Specific Permissions
* Setting Up the Client
* Best Practices
Looking at Hub Transport
* Mail Flow and Routing Architecture
* Management Requests
* Working with Domains and Email Addresses
* Creating Transport Rules
* Using Send Connectors
* Using Receive Connectors
* Setting Size Limits and Delivery Restrictions
* Using the Queue Viewer
Meeting Compliance Requirements with Exchange Server 2007
* Management Requests
* Intro to Journaling
* Planning and implementing Journaling
* 3rd Party Products
* Other Compliance Issues
Edge Transport Role
* Management Requests
* A Look at Edge Transport
* Edge Setup Requirements
* Installing the Edge Role
* Securing the Edge Server
* Best Practices
Configuring Edge Anti-Spam Components
* Architecture
* Installing the Edge Anti-Spam Filters on the Hub Transport
* Connection Filtering
* Sender Filtering
* Recipient Filtering
* SPF Records
* Content Filtering in Exchange Server 2007
* Attachment Filters
* Transport Rules
* Address Rewrite Agent
* Safe list Aggregation
* Best Practices
Anti-Virus and Exchange Server 2007
* Architecture
* Supported Vendors
* ForeFront Overview
* Installing ForeFront
* Testing AV
* Best Practices
Configuring Exchange Server 2007 Backups
* Database/Backup Architecture
* Knowing What to Back Up
* Using NTBackup
* Volume Shadow Copy
* Local Continuous Replication
* Standby Cluster Replication
* Recommendations
Exchange Server 2007 Disaster Recovery
* A Look at Scenarios of Increasing Cruelty
* Walk-through Several Types of Recovery
* Best Practices For Recovery
Transport Layer Security
* Management Requests
* TLS Architecture
* Setting Up TLS
* Recommendations
Exchange Tools and Troubleshooting Techniques
* Scenario Drivers
* Using the Best Practices Analyzer (BPA)
* Interpreting BPA Results
* Using the Message Tracking Center (MTC)
* Tips and Tricks On How To Troubleshoot Exchange Server 2007
o Errors in Application Event Log
o Protocol Logging
o Event IDs Lookup
* Proactive Tips
CD1
http://www.mediafire.com/?jayiftbvdbx
http://www.mediafire.com/?n8ayyjxnmno
http://www.mediafire.com/?dwukkgog52y
http://www.mediafire.com/?bblage14xhg
OR
http://www.rapidspread.com/file.jsp?id=z7dnj2qv9j
http://www.rapidspread.com/file.jsp?id=z8l8dqi2wc
http://www.rapidspread.com/file.jsp?id=tdef82eas0
http://www.rapidspread.com/file.jsp?id=ttiqf00pip
CD2
http://www.mediafire.com/?220lky2ebjv
http://www.mediafire.com/?igltmvxdzny
http://www.mediafire.com/?osk1zcqxocb
OR
http://www.rapidspread.com/file.jsp?id=gkvsmhuayb
http://www.rapidspread.com/file.jsp?id=msyf7cot6r
http://www.rapidspread.com/file.jsp?id=uc74elsvsv
Use FFSJ and 7zip for extract.
Code:
http://www.jaist.ac.jp/%7Ehoangle/filesj/
http://www.7-zip.org/download.html
password : www.softprovn.net
Enable an Outlook Web Access Logon Page On Exchange 2007
By default, forms-based authentication is not enabled for Outlook Web Access in Exchange2007. Forms-based authentication stores the user’s user name and password in a cookie instead of in the browser. When the user leaves an OWA session or after the expiration of the inactivity period, the cookie is cleared. As a result, the user must re-authenticate to use OWA again. This is a good security measure.To enable the Outlook Web Access logon page, do the following:
- Open the Exchange Management Console.
- Choose Server Configuration > Client Access.
- Click the “Owa (Default Web Site)” entry.
- From the Action pane, choose the Properties option.
- From the Owa (Default Web Site) Properties page, click the Authentication tab.
Under the “Use Forms-Based Authentication” option there are three options for enforcing a particular logon format. The Domain\User Name option is self-explanatory and is useful if you have multiple domains. The User Principal Name (UPN) option, or e-mail address format, is probably the easiest for users to remember since they use it all the time. The User Name Only option is the last option, which is also self explanatory. If you choose the User Name Only format, you also need to choose a Logon Domain. - Click OK
Because this change affects IIS, you must restart IIS. From a command line on the Outlook Web Access server, issue the command iisreset /noforce.
Winstructor Exchange 2003
Exchange Server 2003 contains the following Training Videos:
Introduction to Exchange Server 2003
Duration: 2:28
In this Video we show Introduce Exchange Server 2003 and discuss the requirements you’ll need to satisfy before installing your first server.
Installing Exchange Server 2003
Duration: 12:59
In this Video we show you how to install Exchange Server 2003 on a Windows 2003 Server.
Post Installation Configuration
Duration: 20:32
In this Video we show you how to create a Service Account to manage the Exchange 2003 Services and Use the Delegation of Control Wizard to assign Exchange Permissions to your Senior Administrators, Day-to-Day Administrators and Helpdesk Staff members. We then move on to discuss the steps required to install the Exchange System Management Tools on your local Workstation so you can manage your Exchange Configuration from your desk.
Removing an Exchange Server from an Organization
Duration: 6:06
In this Video we show you how to remove an Exchange 2003 Server from an Exchange Organization. The removal process doesn’t always go smoothly, so with that in mind, we also demonstrate how to forcibly remove Exchange in the event something goes wrong.
Cached Exchange Mode
Duration: 4:03
In this Video we show explain the Cached Exchange Mode feature of Outlook 2003. Cached Exchange Mode gives you the advantage of caching a copy of your Exchange Profile and Offline Address Book, so when your Exchange Server is not available, you can keep working.
Internet Mail Wizard
Duration: 4:22
In this Video we show you how to use the Internet Mail Wizard to configure your Exchange 2003 Server to send and receive Internet Mail.
Front End and Back End Servers
Duration: 5:18
In this Video we show you how to configure Front End End Exchange Servers.
Administrative Groups
Duration: 5:29
In this Video we show you how to create Administrative Groups to simplify the management of your Exchange Server 2003 Organization.
Routing Groups
Duration: 3:48
In this Video we show you how to create Routing Groups to manage the Communication between Exchange Servers within your Exchange Server 2003 Organization.
Managing Policies
Duration: 10:20
In this Video we show you how to use Policies to Manage Mailbox, Public Folder and Server Settings.
Managing Address Lists
Duration: 12:22
In this Video we show you how to Create and Manage Address Lists and Offline Address Lists.
Managing Users, Contacts and Groups
Duration: 12:59
In this Video we show you how to Create and Manage Exchange Users, Contacts and Groups.
Public Folders
Duration: 21:04
In this Video we show you how to Create and Manage Exchange Public Folders from the Exchange System Manager, from the Outlook Client and from Outlook Web Access. We talk about Public Folder Security, then we move on to creating new General Purpose Public Folder Trees and finish with a discussion on Replication.
Backup and Restoring Exchange 2003
Duration: 7:54
In this Video we show you how to backup your Exchange Server in Case of Disaster. When the time comes, you’ll also need to know how to restore your Exchange Server as well. We show you how!
Monitoring Exchange 2003
Duration: 17:17
In this Video we show you how to proactively Monitor all aspects of your Exchange Server so it runs at maximum performance.
download :
Learnkey - Exchange Windows 2003 Server Design [2 CD]
Learnkey - Exchange Windows 2003 Server Design [2 CD] | Video Tutorial | Official Website
The Exchange Server 2003 Design course from LearnKey prepares IT professionals to analyze business messaging requirements and design an appropriate Exchange Server 2003 messaging infrastructure. Expert instructor Aaron Spurlock takes you through analysis and design of Active Directory integration, Exchange Server 2003 infrastructure, routing topology and security. Your working knowledge of networking principles and Internet protocols or experience with Windows Server 2003 will put you on the path to a successful experience and prepare you for MCP exam 70-285.
CD 1 [File type: ISO | Size: 277 MB]
http://rapidshare.com/files/158577511/netbks.com_70-285_Exch2003_Design1.part1.rar
http://rapidshare.com/files/158577376/netbks.com_70-285_Exch2003_Design1.part2.rar
http://rapidshare.com/files/158577260/netbks.com_70-285_Exch2003_Design1.part3.rar
CD 2 [File type: ISO | Size: 183 MB]
http://rapidshare.com/files/158577419/netbks.com_70-285_Exch2003_Design2.part1.rar
http://rapidshare.com/files/158577346/netbks.com_70-285_Exch2003_Design2.part2.rar
Exam-Pack 70-238: Deploying Messaging Solutions with Microsoft Exchange Server 2007
Exam-Pack 70-238: Deploying Messaging Solutions with Microsoft Exchange Server 2007
Training for Microsoft Certified IT Professional (MCITP)
Trainer: J. Peter Bruzzese (Trainer Comments)
Running Time: 6 Hours
Exam information from Microsoft [microsoft.com]
Want to manage your Exchange 2007 organization from the ground up? This training offers you the details on how to make it happen.
Peter Bruzzese covers the transition from Exchange 2003 to Exchange 2007, including the period when both systems are running. He tells you exactly what to do as you move things over to your new structure, and then, how to operate this great messaging server day-in and day-out.
Transport Rules. Peter focuses heavily on one of Exchange 2007's coolest features: Transport Rules. Because all messaging goes through the Hub Transport servers, Transport Rules allow you to apply rules to messages in transit.
PowerShell. The PowerShell command-line interface is another great feature of Exchange 2007 and is prominently featured on the certification exam. Peter's training transforms you into a PowerShell expert.
Throughout this series, Peter also highlights how Exchange interacts with other servers and services, such as ISA Server, MOM, ForeFront and more. He covers the real issues you'll face as you deploy your Exchange 2007 installation, whether from a previous version of Exchange or another messaging system.
Every IT administrator looking to deploy Exchange in their real-world environment will benefit from this video series. Peter's training prepares you for Microsoft's 70-238 exam, while giving you the skills you need to deploy Exchange in your own real-world environment.
Passing this exam tells employers that you've got the ultimate level of knowledge in Exchange 2007 deployment.
The Exam-Pack 70-238: Deploying Messaging Solutions with Microsoft Exchange Server 2007 video series contains:
70-238 Introduction
70-238 Requirements and Skills
Planning Exchange 2007 Upgrade Implementation (free video!)
Transitioning Co-Existence
Finalizing Your Transition
Migrating to Exchange 2007
Hosted Exchange Solutions
Planning for High Availability Implementation
Planning a Backup/Recovery Solution (Part 1)
Planning a Backup/Recovery Solution (Part 2)
Storage Group Deployment
Server Role Deployment
Managed Content Settings and ActiveSync Policies
Additional Servers to Deploy with Exchange 2007
Planning AntiSpam and AntiVirus Implementation
Plan Transport Rule Implementation
Planning Network Security
Exchange Infrastructure Improvements
Plan for Configuration Changes
Plan for Patch and Service Pack Implementation
Plan for Testing, Monitoring and Reporting
Download:
http://rapidshare.com/files/142506487/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part08.rar.html
http://rapidshare.com/files/142506475/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part07.rar.html
http://rapidshare.com/files/142506359/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part06.rar.html
http://rapidshare.com/files/142504516/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part05.rar.html
http://rapidshare.com/files/142504510/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part04.rar.html
http://rapidshare.com/files/142504506/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part03.rar.html
http://rapidshare.com/files/142504518/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part02.rar.html
http://rapidshare.com/files/142504508/CBT_Nuggets_-Deploying_Messaging_Solutuions_with_Microsoft_Exchange_Server_2007-.part01.rar.html
Exchange server 2007 -Trainsignal Video Tutorials
CODE
rapidshare.com/files/99160317/TSExSv2007CD1.part01.rar
rapidshare.com/files/98996183/TSExSv2007CD1.part02.rar
rapidshare.com/files/99137597/TSExSv2007CD1.part03.rar
rapidshare.com/files/99351756/TSExSv2007CD1.part04.rar
rapidshare.com/files/99376072/TSExSv2007CD1.part05.rar
rapidshare.com/files/99384820/TSExSv2007CD1.part06.rar
rapidshare.com/files/99393420/TSExSv2007CD1.part07.rar
rapidshare.com/files/99402574/TSExSv2007CD1.part08.rar
rapidshare.com/files/99412997/TSExSv2007CD1.part09.rar
rapidshare.com/files/99424560/TSExSv2007CD1.part10.rar
rapidshare.com/files/99738395/TSExSv2007CD1.part11.rar
rapidshare.com/files/105130122/TSExSv2007CD1.part12.rar
Download
CD2:
rapidshare.com/files/106316658/TSExSvr2007CD2.part01.rar
rapidshare.com/files/106323596/TSExSvr2007CD2.part02.rar
rapidshare.com/files/106338053/TSExSvr2007CD2.part03.rar
rapidshare.com/files/106347156/TSExSvr2007CD2.part04.rar
rapidshare.com/files/106360462/TSExSvr2007CD2.part05.rar
rapidshare.com/files/106370880/TSExSvr2007CD2.part06.rar
rapidshare.com/files/106381671/TSExSvr2007CD2.part07.rar
rapidshare.com/files/106390838/TSExSvr2007CD2.part08.rar
rapidshare.com/files/106400080/TSExSvr2007CD2.part09.rar
rapidshare.com/files/106410022/TSExSvr2007CD2.part10.rar
rapidshare.com/files/106416389/TSExSvr2007CD2.part11.rar
rapidshare.com/files/99160317/TSExSv2007CD1.part01.rar
rapidshare.com/files/98996183/TSExSv2007CD1.part02.rar
rapidshare.com/files/99137597/TSExSv2007CD1.part03.rar
rapidshare.com/files/99351756/TSExSv2007CD1.part04.rar
rapidshare.com/files/99376072/TSExSv2007CD1.part05.rar
rapidshare.com/files/99384820/TSExSv2007CD1.part06.rar
rapidshare.com/files/99393420/TSExSv2007CD1.part07.rar
rapidshare.com/files/99402574/TSExSv2007CD1.part08.rar
rapidshare.com/files/99412997/TSExSv2007CD1.part09.rar
rapidshare.com/files/99424560/TSExSv2007CD1.part10.rar
rapidshare.com/files/99738395/TSExSv2007CD1.part11.rar
rapidshare.com/files/105130122/TSExSv2007CD1.part12.rar
Download
CD2:
rapidshare.com/files/106316658/TSExSvr2007CD2.part01.rar
rapidshare.com/files/106323596/TSExSvr2007CD2.part02.rar
rapidshare.com/files/106338053/TSExSvr2007CD2.part03.rar
rapidshare.com/files/106347156/TSExSvr2007CD2.part04.rar
rapidshare.com/files/106360462/TSExSvr2007CD2.part05.rar
rapidshare.com/files/106370880/TSExSvr2007CD2.part06.rar
rapidshare.com/files/106381671/TSExSvr2007CD2.part07.rar
rapidshare.com/files/106390838/TSExSvr2007CD2.part08.rar
rapidshare.com/files/106400080/TSExSvr2007CD2.part09.rar
rapidshare.com/files/106410022/TSExSvr2007CD2.part10.rar
rapidshare.com/files/106416389/TSExSvr2007CD2.part11.rar
Trainsignal Exchange Server 2007
Build your own email infrastructure
* Learn Exchange Server 2007 by watching it Configured on a Live Network
* Get certified! Exam Coverage for MCTS 70-236: Microsoft Exchange Server 2007, Configuration
* Become a pro at Installing, Configuring, and Managing Exchange Server 2007
* Learn at your own pace and at a fraction of the price compared to classroom learning!
* Taught by a Microsoft MVP with an MCSE and over 10 years of real world experience
* Discover how to Develop Secure, Efficient Systems and how to Integrate OWA
* Learn how to Backup and Restore your Exchange Server 2007
* Master all the new features that come with Exchange Server 2007
* The Most Effective Way to Learn Exchange Server 2007...See Why!
* Prepare for MCSE Certification MCSE Training Information
CD1
CODE
http://rapidshare.com/files/116761123/Party2.part1.rar
http://rapidshare.com/files/116761122/Party2.part2.rar
http://rapidshare.com/files/116761520/Party2.part3.rar
http://rapidshare.com/files/116761420/Party2.part4.rar
Pass: Grab&Go
CD2
CODE
http://rapidshare.com/files/116991984/Party2-2.part1.rar
http://rapidshare.com/files/116991996/Party2-2.part2.rar
http://rapidshare.com/files/116992029/Party2-2.part3.rar
http://rapidshare.com/files/116991689/Party2-2.part4.rar
Pass: Grab&Go
* Learn Exchange Server 2007 by watching it Configured on a Live Network
* Get certified! Exam Coverage for MCTS 70-236: Microsoft Exchange Server 2007, Configuration
* Become a pro at Installing, Configuring, and Managing Exchange Server 2007
* Learn at your own pace and at a fraction of the price compared to classroom learning!
* Taught by a Microsoft MVP with an MCSE and over 10 years of real world experience
* Discover how to Develop Secure, Efficient Systems and how to Integrate OWA
* Learn how to Backup and Restore your Exchange Server 2007
* Master all the new features that come with Exchange Server 2007
* The Most Effective Way to Learn Exchange Server 2007...See Why!
* Prepare for MCSE Certification MCSE Training Information
CD1
CODE
http://rapidshare.com/files/116761123/Party2.part1.rar
http://rapidshare.com/files/116761122/Party2.part2.rar
http://rapidshare.com/files/116761520/Party2.part3.rar
http://rapidshare.com/files/116761420/Party2.part4.rar
Pass: Grab&Go
CD2
CODE
http://rapidshare.com/files/116991984/Party2-2.part1.rar
http://rapidshare.com/files/116991996/Party2-2.part2.rar
http://rapidshare.com/files/116992029/Party2-2.part3.rar
http://rapidshare.com/files/116991689/Party2-2.part4.rar
Pass: Grab&Go
70-237 Exchange 2k7 design
70-237 Exchange 2k7 design
70-237 Exchange 2k7 design
http://rapidshare.com/files/91972700/CBT_Nuggets_Exchange_70-237.part2.rar
Exchange Server 2007 -EXAM DETAILS FOR FRESHERS
The Microsoft Certified Master: Exchange Server 2007 program provides the most in-depth and comprehensive training that is available today for Microsoft Exchange Server 2007. This three-week training program is delivered by recognized experts from Microsoft and Microsoft Partner organizations.
Training deepens and broadens the technical skills of experienced messaging professionals
Microsoft Certified Master training—a mixture of presentations, white-board discussions, and goal-based labs—covers the individual core Exchange Server 2007 technologies as well as broader architectural and operational areas, such as high availability of a messaging service, co-existence and migration, performance analysis, management, and operations. Candidates complete an independent lab exercise as a part of their training, which allows them to develop and apply their learning in an environment where instructor and peer support is readily available.
Certified individuals prove their technical mastery
Candidates who successfully complete the program can expect to have a greatly improved understanding of the Microsoft Exchange Server 2007 platform. Microsoft Certified Masters can design and build customer-specified messaging solutions, and they understand how design decisions affect the final solution. They can troubleshoot and diagnose configuration and performance issues, and they have the detailed knowledge and skills that are required to successfully operate and manage an enterprise-class Exchange Server 2007 infrastructure
Prerequisites
Applicants must meet or exceed the prerequisite requirements for their chosen program track in order to be accepted into a Microsoft Certified Master program. Required exams and certifications will be verified.
Experience
• Five or more years of hands-on experience with Microsoft Exchange Server 2003: installing, configuring, and troubleshooting
• One or more years of hands-on experience with Microsoft Exchange Server 2007: installing, configuring, and troubleshooting
• A thorough understanding of Microsoft Exchange Server design and architecture
• A thorough understanding of Active Directory, Domain Name System (DNS), and other core network services related to Exchange Server
• Ability to speak, understand, and write fluent English
Successful completion of the following exams and certifications
•
Exam 70-236: TS: Exchange Server 2007, Configuring
•
Exam 70-237: PRO: Designing Messaging Solutions with Microsoft Exchange Server 2007
•
Exam 70-238: PRO: Deploying Messaging Solutions with Microsoft Exchange Server 2007
Additionally required:
•
Microsoft Certified Systems Engineer (MCSE) on Windows Server 2003
or
Exam 70-640: TS: Windows Server 2008 Active Directory, Configuring
Training deepens and broadens the technical skills of experienced messaging professionals
Microsoft Certified Master training—a mixture of presentations, white-board discussions, and goal-based labs—covers the individual core Exchange Server 2007 technologies as well as broader architectural and operational areas, such as high availability of a messaging service, co-existence and migration, performance analysis, management, and operations. Candidates complete an independent lab exercise as a part of their training, which allows them to develop and apply their learning in an environment where instructor and peer support is readily available.
Certified individuals prove their technical mastery
Candidates who successfully complete the program can expect to have a greatly improved understanding of the Microsoft Exchange Server 2007 platform. Microsoft Certified Masters can design and build customer-specified messaging solutions, and they understand how design decisions affect the final solution. They can troubleshoot and diagnose configuration and performance issues, and they have the detailed knowledge and skills that are required to successfully operate and manage an enterprise-class Exchange Server 2007 infrastructure
Prerequisites
Applicants must meet or exceed the prerequisite requirements for their chosen program track in order to be accepted into a Microsoft Certified Master program. Required exams and certifications will be verified.
Experience
• Five or more years of hands-on experience with Microsoft Exchange Server 2003: installing, configuring, and troubleshooting
• One or more years of hands-on experience with Microsoft Exchange Server 2007: installing, configuring, and troubleshooting
• A thorough understanding of Microsoft Exchange Server design and architecture
• A thorough understanding of Active Directory, Domain Name System (DNS), and other core network services related to Exchange Server
• Ability to speak, understand, and write fluent English
Successful completion of the following exams and certifications
•
Exam 70-236: TS: Exchange Server 2007, Configuring
•
Exam 70-237: PRO: Designing Messaging Solutions with Microsoft Exchange Server 2007
•
Exam 70-238: PRO: Deploying Messaging Solutions with Microsoft Exchange Server 2007
Additionally required:
•
Microsoft Certified Systems Engineer (MCSE) on Windows Server 2003
or
Exam 70-640: TS: Windows Server 2008 Active Directory, Configuring
CBT Nuggets Deploying Messaging Solutions with Microsoft Exchange Server 2007
Want to manage your Exchange 2007 organization from the ground up? This training offers you the details on how to make it happen.
Peter Bruzzese covers the transition from Exchange 2003 to Exchange 2007, including the period when both systems are running. He tells you exactly what to do as you move things over to your new structure, and then, how to operate this great messaging server day-in and day-out.
Transport Rules. Peter focuses heavily on one of Exchange 2007's coolest features: Transport Rules. Because all messaging goes through the Hub Transport servers, Transport Rules allow you to apply rules to messages in transit.
PowerShell. The PowerShell command-line interface is another great feature of Exchange 2007 and is prominently featured on the certification exam. Peter's training transforms you into a PowerShell expert.
Throughout this series, Peter also highlights how Exchange interacts with other servers and services, such as ISA Server, MOM, ForeFront and more. He covers the real issues you'll face as you deploy your Exchange 2007 installation, whether from a previous version of Exchange or another messaging system.
Every IT administrator looking to deploy Exchange in their real-world environment will benefit from this video series. Peter's training prepares you for Microsoft's 70-238 exam, while giving you the skills you need to deploy Exchange in your own real-world environment.
Passing this exam tells employers that you've got the ultimate level of knowledge in Exchange 2007 deployment.
The Exam-Pack 70-238: Deploying Messaging Solutions with Microsoft Exchange Server 2007 video series contains:
70-238 Introduction
70-238 Requirements and Skills
Planning Exchange 2007 Upgrade Implementation (free video!)
Transitioning Co-Existence
Finalizing Your Transition
Migrating to Exchange 2007
Hosted Exchange Solutions
Planning for High Availability Implementation
Planning a Backup/Recovery Solution (Part 1)
Planning a Backup/Recovery Solution (Part 2)
Storage Group Deployment
Server Role Deployment
Managed Content Settings and ActiveSync Policies
Additional Servers to Deploy with Exchange 2007
Planning AntiSpam and AntiVirus Implementation
Plan Transport Rule Implementation
Planning Network Security
Exchange Infrastructure Improvements
Plan for Configuration Changes
Plan for Patch and Service Pack Implementation
Plan for Testing, Monitoring and Reporting
Here's what you'll learn in each video of the Exam-Pack 70-238: Deploying Messaging Solutions with Microsoft Exchange Server 2007
series:
Video 1 - "Introduction to Exchange 2007" - This nugget explains how Exchange and Active Directory work together and lays the foundation for future nuggets that discuss preparation and installation of Exchange 2007. There is a discussion of Exchange Clients that can be used in Exchange 2007. It also explains the 5 new Server Roles: Mailbox Role, Client Access Server, Hub Transport Server, Edge Transport Server and Unified Messaging Server.
Video 2 - "Preparing and Installing Exchange 2007" - This nugget discusses the preparation needed within your AD infrastructure, including information about your Schema preparation (preparation switches), permissions that need to be given to the correct individuals and so forth. For the official installation we discuss the hardware and software requirements to install Exchange 2007 on a particular server. And we walk through a stand-alone installation of Exchange 2007.
Video 3 - "Managing Storage Groups and Databases" - This nugget focuses on the Mailbox Server role, providing an overview of storage architecture (including Storage Groups and Databases) using the Exchange Management Console and Exchange Management Shell.
Video 4 - "Configure Public Folders" - Discusses the use of Public Folders in an Exchange 2007 environment. Covers the steps to adding new folders through Outlook or the Exchange Management Shell, and explains how replicas are established for increased availability to your users of the public folder structure as well as a greater level of fault tolerance.
Video 5 - "Managing Recipient Objects: Mailboxes" - This nugget discusses the many types of recipient objects that exist (mailbox users, mail-enabled groups, resource mailboxes, mail contacts, linked mailboxes and so forth). The main focus in this nugget is the creation, configuration and management of the Mailbox recipient object. Moving mailboxes is also covered in this nugget.
Video 6 - "Managing More Recipient Objects" - This nugget continues the theme of recipient object configuration and management with instructions on how to work with mail-enabled accounts, resource mailboxes (such as conference rooms and shared equipment) for the purpose of scheduling meeting requests, distribution groups and linked mailboxes.
Video 7 - "E-mail Policies, Accepted Domains and Address Lists" - This nugget addresses further Mailbox Server Role configuring by ensuring that you can establish e-mail policies for your organization. A discussion of accepted domains explains more complicated layouts for your Exchange organization, including authoritative domains and relay domains with multiple SMTP addresses. Finally, we discuss the Global Address List (GAL) and the creation of additional address lists for your organization.
Video 8 - "Configuring Your Client Access Server (CAS)" - In this nugget we discuss the Client Access Server (CAS) role in greater detail. We explain the configuration of Outlook Web Access for users who need to access their mailboxes through a browser, and ActiveSync for users with appropriate mobile devices. We discuss both server-side configuration and client-side connectivity.
Video 9 - "Outlook Anywhere and POP/IMAP Configuration" - This nugget is the follow-up to the "Configuring Your Client Access Server" nugget. It's purpose is to walk through the server-side configuration for Outlook Anywhere and POP/IMAP. It also explains the client connectivity configuration that is necessary. The nugget also discusses the various CAS services such as Autodiscover, the Offline Address Book (OAB) and the Availability Service.
Video 10 - "Configuring Disaster Recovery" - This nugget explains backup methodology and provides information on how to configure backups, recover messaging data, and recover server roles. There is also an important discussion regarding Recovery Storage Groups.
Video 11 - "Configure High Availability" - This nugget explains the purpose of High Availability for your Exchange environment and reviews possible high availability scenarios for your Exchange mailbox server. The discussion includes an overview and demonstration of Local Continuous Replication (LCR) and Cluster Continuous Replication (CCR) with a review of Single Copy Clusters (SCC).
Video 12 - "Understanding Message Transport" - This nugget describes the purpose of a Hub Transport Server and reviews the transport pipeline so that you can understand what is happening on your Exchange Servers behind the scenes when a message is sent within the organization and to persons outside of the organization. The nugget also explains the function of Send/Receive SMTP Connectors and AD Site Connections to ensure mail is flowing in the direction you want it to.
Video 13 - "Troubleshoot Message Transport" - This nugget reviews the use of the Mail Flow Tools, found in our Toolbox through the Exchange Management Console. These tools can be used for monitoring and troubleshooting and they include the following: Mail Flow Troubleshooter, Message Tracking (which helps you perform message tracking) and Queue Viewer (to monitor mail queues). The nugget concludes with protocol logging for your SMTP Send/Receive connectors.
Video 14 - "Configuring Your Edge Transport Role" - In this nugget we discuss the purpose of an Edge Transport server and explain the need to place this role on a stand-alone server at your network perimeter using ADAM for a directory database as opposed to Active Directory. We set up the connection between our Hub Transport and Edge Transport Servers through the EdgeSync process that involves exporting the configuration from the Edge Transport Server and important it onto the Hub Transport Server. We also explained the need to secure the Edge Transport Server while still allowing necessary ports to be open for communication to take place. We reviewed the use of the Security Configuration Wizard (SCW) to establish both the security and opening of needed ports.
Video 15 - "Finalizing Edge Transport" - In this nugget we finalized the configuration of our Edge Transport Server by creating a postmaster mailbox, configuring our DNS (both public and private configuration was discussed and demonstrated) and reviewed briefly anti-spam/anti-virus needs, connectors, transport rules, accepted domains, and... the pièce de résistance... address re-writing.
Video 16 - "Configuring Anti-Spam:" - The anti-spam system includes a very intense process of filtering that we discuss step-by-step in this nugget. We review the configuration of all of the settings within the system on our Edge Transport Server. Then we review the possibility of establishing these same settings on our Hub Transport Server.
Video 17 - "Analyze and Monitor Exchange 2007" - In this nugget we look into all the best monitoring and reporting tools in Exchange 2007. This include, of course, the Exchange Best Practices Analyzer, Disaster Recovery Tools (as well as the command-line tools ESEUTIL and ISINTEG), Performance Monitor and Troubleshooter, and the Microsoft Operations Manager (MOM).
Video 18 - "A Look At Unified Messaging" - Although not an exam topic, per se, we completed our understanding of all 5 server roles with this discussion on Unified Messaging. We reviewed all of the necessary hardware requirements and telephony requirements to get UM up and running within your organization. Then we discussed the configuration of both the UM server and the UM clients.
Video 19 - "Troubleshooting Your Exchange Environment" - This nugget establishes basic troubleshooting procedure for Exchange-related issues that may arise using Diagnostic Logging, the Exchange Troubleshooting Assistant and the Exchange Management Shell, including some key PowerShell cmdlets (like Test-) that will help you keep your Exchange environment up and running, as well as, help you on the exam.
Video 20 - "PowerShell, From 0 to 60" - A great deal of the exam revolves around your knowledge of PowerShell. But not just the commands. It also covers navigation, pipelining, scripts and other concepts that revolve around the new command-line interface (CLI) from Microsoft. We need to become experts in PowerShell if we plan on passing this exam. This nugget will help you build upon what you already know, by ensuring that your foundation is solid.
Video 21 - "Exam Prep" - This nugget is a full review of all exam oriented materials to assist the viewer in preparing further for the 70-236 Exchange Server 2007 Configuring exam.
Download:
http://u-cmj53r0vv.urlcash.net
http://u-wmj53sn21.urlcash.net
http://u-hmj53t0do.urlcash.net
Cbt.nuggets.configuring.exchange.server.2007.exam.pack.70-236-, CBT for 70-236 - Exchange 2007 exam
Load up and watch the videos or load into your CBT Nuggets Archive server
and watch the videos. Either way, Enjoy and learn. (Thanks Fred)
Exam-Pack 70-236: Exchange Server 2007, Configuring contains:
- Series Intro
- Introduction to Exchange 2007
- Preparing and Installing Exchange 2007 (free video!)
- Managing Storage Groups and Databases
- Configure Public Folders
- Managing Recipient Objects: Mailboxes
- Managing More Recipient Objects
- E-mail Policies, Accepted Domains and Address Lists
- Configuring Your Client Access Server
- Outlook Anywhere and POP/IMAP Configuration
- Configuring Disaster Recovery
- Configure High Availability
- Understanding Message Transport
- Troubleshoot Message Transport
- Configuring Your Edge Transport Role
- Finalizing Edge Transport
- Configuring Anti-Spam
- Analyze and Monitor Exchange 2007
- A Look At Unified Messaging
- Troubleshooting Your Exchange Environment
- Using PowerShell
- Skills Measured by Exam 70-236
Download
http://u-6ku0pf6ec.urlcash.net
http://u-7ku0pgqqj.urlcash.net
http://u-oku0phxn6.urlcash.net
http://u-kku0pin74.urlcash.net
http://u-iku0p0xl7.urlcash.net
http://u-aku0p1qs1.urlcash.net
http://u-oku0p2cu2.urlcash.net
http://u-rku0p3hgt.urlcash.net
http://u-tku0p4zgo.urlcash.net
http://u-wku0p51yb.urlcash.net
http://u-2ku0p6123.urlcash.net
http://u-rku0p73yh.urlcash.net
http://u-sku0p8wga.urlcash.net
Exchange 2007 related documentations
http://rapidshare.com/files/97890142/exchange2007UMemail.zip
http://rapidshare.com/files/97901859/Exchange_Whitepaper_-_Solving_.PST_Management_Problems_in_Microsoft_Exchange_Environments.pdf
http://rapidshare.com/files/97901860/Microsoft_ES2007_whitepaper.pdf
http://rapidshare.com/files/97901862/Creating_Disclaimers_in_Exchange_Server_2007.doc
http://rapidshare.com/files/97904885/Generating_Active_Directory_Accounts_from_an_Exchange_Database.doc
http://rapidshare.com/files/97904887/How_to_install_Exchange_Server_2007__in___different_scenarios.doc
http://rapidshare.com/files/97906960/Introduction_to_Exchange_2007_Server_Roles_email_routing_etc.doc
http://rapidshare.com/files/97907769/Deploying_an_Exchange_Resource_Forest.doc
http://rapidshare.com/files/97910797/Ex2007_Msg_Rec_Mgt_Msg_Classifications.doc
http://rapidshare.com/files/97912107/Exchange_2007_Transport_Rules_and_journaling_rules.doc
http://rapidshare.com/files/97912727/Backing_Up_Exchange_Databases_via_the_Passive_Node_in_an_Exchange_Server_2007_CCR_Cluster.doc
http://rapidshare.com/files/97901859/Exchange_Whitepaper_-_Solving_.PST_Management_Problems_in_Microsoft_Exchange_Environments.pdf
http://rapidshare.com/files/97901860/Microsoft_ES2007_whitepaper.pdf
http://rapidshare.com/files/97901862/Creating_Disclaimers_in_Exchange_Server_2007.doc
http://rapidshare.com/files/97904885/Generating_Active_Directory_Accounts_from_an_Exchange_Database.doc
http://rapidshare.com/files/97904887/How_to_install_Exchange_Server_2007__in___different_scenarios.doc
http://rapidshare.com/files/97906960/Introduction_to_Exchange_2007_Server_Roles_email_routing_etc.doc
http://rapidshare.com/files/97907769/Deploying_an_Exchange_Resource_Forest.doc
http://rapidshare.com/files/97910797/Ex2007_Msg_Rec_Mgt_Msg_Classifications.doc
http://rapidshare.com/files/97912107/Exchange_2007_Transport_Rules_and_journaling_rules.doc
http://rapidshare.com/files/97912727/Backing_Up_Exchange_Databases_via_the_Passive_Node_in_an_Exchange_Server_2007_CCR_Cluster.doc
Configuring_Exchange_Server_2007-video tutorial
http://rapidshare.com/files/101290221/Sybex.MCITP.Microsoft.Exchange.Server.2007.Messaging.Design.and.Deployment.Study.Guide.Jan.2008.pdf http://rapidshare.com/files/82282796/syngress_configuring_exchange_server_2007.pdf
http://rapidshare.com/files/82282026/Sybex_Mastering_Microsoft_Exchange_Server_2007.chm
http://rapidshare.com/files/84851420/CBT_Nuggets_70-236_-_Configuring_Exchange_Server_2007.part1.rar
http://rapidshare.com/files/84853929/CBT_Nuggets_70-236_-_Configuring_Exchange_Server_2007.part2.rar
http://rapidshare.com/files/82282026/Sybex_Mastering_Microsoft_Exchange_Server_2007.chm
http://rapidshare.com/files/84851420/CBT_Nuggets_70-236_-_Configuring_Exchange_Server_2007.part1.rar
http://rapidshare.com/files/84853929/CBT_Nuggets_70-236_-_Configuring_Exchange_Server_2007.part2.rar
Exchange Server 2003 Training Videos
* How to Install Exchange Server (the right way!)
* Setup Mailboxes for your Active Directory Users
* How to Configure MX Records in DNS
* Configuration of Outlook to work with Exchange
* Outlook Configuration to work with POP3 & IMAP4
* Setup Exchange to Receive Email for Multiple Domains
* How to Setup Exchange to Work Behind a Firewall
* How to Use GFI Mail Security to Scan Email for Viruses
* Setup Outlook Web Access (OWA) for Remote Email
* How to a Install SSL Certificate and Secure OWA
* Configure Message Filters to Block SPAM
* Use of Storage Groups & Mail Stores in Exchange 2003
* How to Setup a Public Folder Structure
Download:
CD1
http://rapidshare.com/files/86039563/Lab_18_-_Exchange_Server_2003_CD1.part1.rar.html http://rapidshare.com/files/86235954/Lab_18_-_Exchange_Server_2003_CD1.part2.rar.html http://rapidshare.com/files/86236913/Lab_18_-_Exchange_Server_2003_CD1.part3.rar.html http://rapidshare.com/files/86238109/Lab_18_-_Exchange_Server_2003_CD1.part4.rar.html http://rapidshare.com/files/86238977/Lab_18_-_Exchange_Server_2003_CD1.part5.rar.html http://rapidshare.com/files/86239700/Lab_18_-_Exchange_Server_2003_CD1.part6.rar.html
CD2
http://rapidshare.com/files/86240743/Lab_18_-_Exchange_Server_2003_CD2.part1.rar.html http://rapidshare.com/files/86241797/Lab_18_-_Exchange_Server_2003_CD2.part2.rar.html http://rapidshare.com/files/86242940/Lab_18_-_Exchange_Server_2003_CD2.part3.rar.html http://rapidshare.com/files/86243429/Lab_18_-_Exchange_Server_2003_CD2.part4.rar.html
Pass : www.warez-bb.org
