In many situations we need to reset the Local Administrator password and add Domain Admins to the Local Administrator group on a server or client machine without visiting each machine. If you don’t know the password and don’t have access to the severs, you can run this simple script as a Startup/Shutdown script in conjunction with Group Policy.
Sometimes we need to use custom providers to create MOM Rules. Here is an example of creating a custom provider to return free hard drive space information from drive H.
As we all know, ISA Server 2004 is a firewall and its function is to block all unnecessary traffic. But sometimes it is also necessary to bypass the traffic without going through the ISA Server. The following section will explain the options available on ISA Server 2004 and on the client side to achieve this.
We are all familiar with creating firewall access rule policies on ISA Server 2004. Let’s say we want to create a two way Firewall access rule. How do you do it?
Do you install and configure Active Directory Connector (ADC) before or after the user migration? The answer to this “complicated” question is either you can install and configure ADC and Connection Agreements (CAs) before or after the user migration. Here are my explanations for both scenarios.
I heard the following comment from a few clients: "ISA Server is ignoring my server publishing rule and it is always using the default rule". This will happen especially if you are working on a complicated network where the ISA firewall and the application servers are on different subnets. Check out this article for an explanation why this happens and a solution.
I am sure we have all either encountered or heard of this "problem" one time or another if the ISA Server is part of the Active Directory Domain. Is it a problem? No, it is by design. To block all unnecessary traffic is the job of the firewall. I know Domain Controller traffic is not unnecessary unreachable traffic, but we have to "explain" to the ISA Server that DC traffic is reachable.