Some machines just don’t die. You know this, especially if you deal with any UNIX or Linux systems. And maybe you know some UNIX guys and gals whose motto was “mess with my UNIX system over my dead body.” Those guys are still around, too. But compliance requirements are altering their jobs and yours, especially if your IT department manages across platforms.
Now the word from above is “extend Active Directory to UNIX and Linux systems” or maybe the word from above is just “Do it.” Symark Software believes it can help. Its PowerADvantage product offers a unified log-in solution that brings Active Directory (AD) centralized authentication, policy enforcement, and infrastructure management to UNIX and Linux systems.
Web proxies are frequently used to gain access to web sites blocked by corporate or school proxies. Since they usually hide the user's own IP address from the web sites they access through the proxy. I listed around 100 of proxies here. I wont recommend you to login your mail / dating sites through web proxies. Most of the corporate body's and schools are blocking some sites like YouTube, Orkut , MySpace Etc.. Here I attaching an excel file with an updated list of proxies. System administrators Don’t worry ! I am not promoting this sites. You can download this Excel file and block more than 1500 proxies (you will need to register to download this excel sheep and to view the first one hundred!).
but for end users who have administrators who are less than efficent at there job, here is a quick list of 100 sites to get you going to bypass corporate proxies and a 1500 proxy list if they have already gone through those first 100! happy usine, but please be responsible ! ! ! ...
In a previous article I explained that the health of your DNS operations is crucial to the health of your Exchange environment. I covered two types of DNS problems that affect Exchange: connectivity between Exchange servers and DNS servers, and performance of DNS servers. In this article, I explain the importance of DNS server integrity, including zone integrity, Active Directory (AD) DNS, and name resolution. Note that before you can troubleshoot DNS, you must validate connectivity to your DNS service.
DNS is often considered a “black box” in the sense that once you have it configured and working, it’s very hard to figure out why it breaks. Yet the health of your Exchange environment is tied to the health of your network’s DNS operations. There are three classes of DNS problems that can adversely affect Exchange: overall connectivity between Exchange servers and DNS servers, overall performance of DNS servers, and the DNS servers’ integrity—that is, the optimal configuration from both a technical and best-practices standpoint. Every DNS problem you encounter should fall into one of these categories. I’ll provide an in-depth look at DNS, its core components, and the approach you should take when troubleshooting specific classes of issues. Understanding the different classes of DNS issues and the troubleshooting process required to approach a specific type of issue will demystify DNS so that it’s no longer the black box it typically is for Exchange administrators. I’ll begin by looking at DNS’s related connectivity and performance issues, and in an upcoming article, I’ll explore DNS integrity.
Exchange Management Shell is arguably the most significant feature of Microsoft Exchange Server 2007. Built on top of Windows PowerShell and the Microsoft .NET Framework, Exchange Management Shell gives an administrator Exchange 2007 server-management capabilities beyond what the GUI-based console provides. For Exchange administrators, migrating to Exchange 2007 means they’ll need to get used to the fact that a number of administrative tasks can be performed only from the command line, not the GUI console. However, if you’re still on Exchange Server 2003, there’s a way to make the transition easier and get acquainted (or reacquainted) with using the command line. You can use PowerShell in conjunction with Windows Management Instrumentation (WMI) to perform some of the same tasks you can do via Exchange Management Shell in Exchange 2007. By taking this first step, you can get a head start on an impending migration to Exchange 2007 as well as use basic command-line scripting to improve your own productivity as an Exchange administrator.
Howto's 
