A while ago I had the chance to review GFI Webmonitor, an ISA Server add-on that enhances significantly the possibilities for web access and download control. Now, GFI introduces a great and brand new option within web monitor possibilities: GFI WebMonitor version that does not require an ISA Server installation. You can download the free 30-day trial here. And […]
For those that never heard about GFI WebMonitor; it’s an ISA Server (2004 or 2006) “add-on” that helps you monitor in real time the network traffic inside your organization, it also complements with ISA Server giving you the chance to directly configure white/black lists, set some access rules to the internet and scan all the traffic for virus and malware. In this post I’ll try to review the functionality, pros and cons, as well as the process of installing and configuring. GFI WebMonitor 2009 Requirements I’m evaluating the GFI UnifiedProtection Edition (that combines WebFilter and WebSecurity) in one package. Hardware Processor: 1.8ghz Memory: 2GB RAM Hard Disk: 10/15 GB free Operating System and Software Windows Server 2000 SP4 / Windows Server 2003 ISA Server 2004 SP3 / ISA Server 2006 Internet Explorer 6 or later .Net Framework 2.0 GFI WebMonitor Installation You can download the trial version for GFI WebMonitor from this link. The installation process it’s simple, you shouldn’t have any problem with this. Access Permissions. Here you can set from which of the IP address the GFI web configuration will be accessible. Take note that you can specify the users that can access it. Mail Settings. Configure it to receive mail notifications about when, for example, a user is trying to infringe a configured policy in WebMonitor. Testing mail notifications. Once the installation is complete, two new access rules are configured in your ISA Server Firewall […]
Publishing a TFS within an ISA Server basically depends on creating three rules for web sites: One will use the TFS default port (8080), the second will use SharePoint (on port 17012) and the other one is for the common HTTP port (80). A small comment about this: The same configuration described here, can also work for Team Foundation Server 2008. It’s very important that you already have defined your public name for the TFS Server and even more important that this public name can be resolved by the ISA Server and over the Internet. Let’s start then: 1 – Publish TFS Services 1.1 – Select “Publish Web Site” and use the proper name for that rule. 1.2 – Select “Publish a single Web Site or load balancer”. 1.3 – If you are not going to use SSL the just select “Use non-secured connections…” 1.4 – In this step you must indicate the FQDN that the clients will use to connect with the Team Foundation Server. Remember that this name should be already accessible for the ISA Server. 1.5 – No selection on Path and select “Forward the original host header…” 1.6 – Select “Accept Requests for: This domain name (type below)” and use the public TFS name again. 1.7 – On the next window you will need to create a Web Listener, which will be accepting the incoming requests for TFS Services port. 1.8 – Select again what kind […]
Technology and user experience enthusiast, book author, customer-focused in the Dell Technologies family. Sharing a few thoughts around evaluating, designing, implementing and managing IT solutions
Augusto Alvarez 