Firewall builder skynet how to#
Firewall builder skynet install#

To make sure these ports are accessible, we can manually connect to each one using Internet Explorer.

The second (9801) is used by Workbench itself to query information about deployments being monitored. The first of these ports (9800) is used by computers being deployed to send progress events. The monitoring service listens on the two ports that you specified. If not, contact Microsoft Support for assistance. ) to see if it provides any further clues. But if you know the ports are not in use and the service still won’t start, capture a trace using DebugView ( While it’s always possible that there could be some other reason the service fails, I haven’t seen any other causes. (If you want to know what’s using the ports, use a tool like TCPView, available from If you try to start the service and it won’t start, that most likely means the ports you chose were already in use.

Firewall builder skynet install#

It’s designed to be easy to install and run. NET to host a web server as part of the service process, and it uses a SQL Compact database (basically a set of DLLs, which ship with MDT, that run in the service process) to store the monitoring information. So there’s no dependency on IIS or SQL Server. Fortunately, MDT will happily use other ports.) But it is possible to have another application use them. (Generally that’s not an issue either, as 98 aren’t commonly-used TCP ports. The ports you specified need to be available for use.

That shouldn’t be an issue, because you can’t install MDT 2012 without. Because of a peculiarity with the way Workbench works, if you make any changes to the Rules tab after you’ve clicked the “Enable monitoring” checkbox but before you’ve clicked OK, it’s possible that the changes made on the Rules tab overlay the EventService entry in CustomSettings.ini, but it’s easy enough to put it back manually. Make sure the entry was added to CustomSettings.ini by looking at the Rules tab. If it’s installed but not running, try to start it. If it’s not installed and it should be, you can uncheck the box, click apply, then check the box again and click apply to reinstall it. Make sure the “Microsoft Deployment Toolkit Monitor Service” is installed and running.

Firewall builder skynet how to#

So what was actually done? Two things:Ī new “Microsoft Deployment Toolkit Monitor Service” service was installed on the computer and started.Īn additional entry was added to the section of CustomSettings.ini telling the clients how to contact the server, with an entry such as:

You’ve checked the checkbox and can’t see that anything happened. Make sure the name you specify in Workbench can be resolved to the IP address of the current machine. If you are specifying a different server and see this error, then it’s having problems communicating with that other server. If you think you specified the local computer name and got that error, then Workbench couldn’t figure out that it was the local computer name (something that’s harder to do than you might think). If you look closely at the error “tip” at the end of the “Monitoring host” line, you’ll see a message like “Unable to connect to the specified server and port”. If it is, great if it isn’t, you’ll see an error message: If you specify a name that Workbench doesn’t think is local (because Workbench itself can’t resolve the name back to an IP address assigned to the current machine), it won’t try to install the monitoring component instead, it will try to contact that server to see if monitoring is running on that computer. It doesn’t really matter if you specify an IP address, a short host name, or a fully-qualified host name, as long as the clients can resolve whatever you specify. When you use Deployment Workbench on that computer and check the box to enable monitoring, Workbench will first check to see if the specified monitoring host name is local: You have to enable monitoring on a computer that has MDT 2012 installed. If you haven’t reviewed that post, you might want to check it out first at I mentioned a while back that I wanted to do a blog post talking about how to troubleshoot the new MDT 2012 monitoring feature for Lite Touch deployments, but first I had to actually describe it. First published on TechNet on May 10, 2012