We currently have no Web filtering at all. I was hoping to find a dns pointer type program like opendns that would just integrate with the Microsoft setup we have, without having to install a new server or deal with Linux I don't mind configuring a Linux box, I'm familiar with Linux enough.
I was just hoping for something that didn't require the extra server. But, that's fine. If that option doesn't exist, or is complicated, I'll go with Untangle!
Since it's a school, why not give ol' K9 a shot? It's been around since years, and it's used by tons of schools.. Pretty solid, and best of all - it's FREE. I could be wrong but I don't believe the free Untangle will block SSL sites so it's pretty easy to breach.
Give NXfilter a try. It's a dns blocker like Opendns but you run it locally. Runs on both Windows or Linux. It works well, not to hard to setup. Since it blocks by dns you may have issue's blocking file downloads.
Thanks for the nxfilter idea. I'll check it out! This is mostly just to monitor illegal sites and porn sites at the school. Downloads and such are pretty locked down through group policy limitations! United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows Server General Forum. Sign in to vote. Is there a way we can: 1. IIS setup will select the features that are required.
On the Role Services page, select any additional role services that you want to install. When you install IIS for the first time by selecting Web Server IIS , you will get at least the default installation that includes a minimum set of role services. You can see at this point that those default services are preselected on the Server Roles page. For a list of the server roles available, and which roles are installed by default, see Modules in IIS 8.
You will have the chance to select more role services later in this procedure. You can also deselect role services that were selected by default when you selected Web Server. However, at least one role service must be selected for Web Server to be selected and installed. If you selected a role service that requires other role services or features to be installed, a page will be opened indicating the role services or features to be installed.
Leave Include management tools if applicable selected to select the install management tools associated with the server role. You may not need the management tools on the destination server if you plan to manage the role remotely. Click Add Features to add the required role services or features. After you have added the role services that you need on the Role Services page, click Next. On the Confirmation page, verify the role services and features that are selected. Select Restart the destination server automatically if required to restart the destination server if the settings need to take immediate effect.
To save the configuration information to an XML-based file that you can use for unattended installations with Windows PowerShell, select Export configuration settings , move to the appropriate path in the Save As dialog box, enter a file name, and then click Save. When you are ready to start the installation process on the Confirmation page, click Install. The Installation Progress page is displayed. You can close the wizard without interrupting running tasks.
You can view task progress or open the page again by clicking Notifications in the notification area, and then clicking Task Details.
On the Results page, verify that the installation succeeds, and then click Close. After you have installed the Web Server role on a running physical server for the first time, you can run through the installation process again to install additional roles, role services, and features. On the Server Selection page, select Select a server from the server pool , and then select a server; or select Select a virtual hard disk server , select the server to mount the VHD on, and then select the VHD file.
Servers in a server pool will be available only if they have been added by the Add other servers to manage command in the Server Manager. Select the role service.
Those roles, services, and features that have already been installed will be identified by 'Installed' in parentheses after the name, and the name will be grayed out. To remove a role, service, or feature, see Uninstall IIS 8. Note, however, that you can expand the lower-level entries under a node even when the node is grayed out. For a list of the server roles that are available, and which roles are installed by default, see Modules in IIS 8. If the role service that you selected requires other role services or features to be installed, an Add Features page will be opened listing those required role services or features.
Click Add Features to add the required role services or features to the installation. Add only the modules that are necessary to minimize the IIS installation footprint and the attack surface.
When you have selected all required role services, and their dependencies, on the Server Roles page, click Next. On the Features page, select any features that you need to be installed. Any features required to be installed for role services that you selected in step 6 will already be selected. In the Add Roles and Features wizard of Server Manager, you cannot delete existing features that have already been installed. On the Server Selection page, select the server from the server pool, and then click Next.
On the Remove Server Roles page, clear the check box of any server role or role service that you would like to remove. If you uncheck a role service that has feature dependencies, the Remove Features dialog box will be displayed showing the dependencies. Click Remove Features to remove them.
On the Remove Server Roles page, select any other role or role service that you want to remove, and then click Next. On the Features page, uncheck any feature that you would like to remove. If you uncheck a feature that has feature dependencies, a dialog box will be displayed showing the dependencies. On the Features page, click Next. On the Confirmation page, verify that the roles, role services, and features to be removed are correct, and then click Remove.
It is recommended that you do a restart if you are prompted to do so, unless you have other activities that you want to do before the restart takes place.
A restart is especially important when you remove roles, role services, or features. The Removal Progress page is displayed. You can install IIS 8. Note that DISM and PowerShell have different namespaces for installation parameters, so the parameter names used in their commands will be different.
For more information, see Modules in IIS 8. Automating the installation of IIS by using unattended scripts is very useful if you need to deploy multiple Web servers and want to ensure that each of the Web servers is set up with identical components and services. In Windows Server R2, DISM is used for unattended scripts, letting you install or uninstall optional features from a command prompt or scripts.
To use DISM, you must make sure you have administrative user rights on the computer. If you do not explicitly include in the DISM code a feature that the IIS installation has a dependency on, the installation will fail, and will not generate an error message. For a list of dependencies required, see Feature Dependencies.
0コメント