IIS 6.0, Spiceworks, and WSUS question

K

klesik

Weaksauce
Joined
Nov 20, 2007
Messages
69
Hi, I have a strange question for you guys. I'm the admin for a small company and we currently have 2 servers running. One is the DC and the other is a SQL Server for an application. On the DC I have WSUS running with IIS 6.0, and the other day I found a pretty cool network monitoring / helpdesk application: Spiceworks. It has a website that allows users to submit issues into the helpdesk and create tickets. I want to run it on the DC as well, but I don't want to interfere with the WSUS site.

The caveat is that the Spiceworks intranet site works on any port, but by default you have to access the DNS name of the server to get into it. For example, http://dc05 or http://dc05:85 or anything like that. Is there a way in IIS to get the intranet site to resolve to a different internal name such as http://support.companyname or just http://helpdesk? One other thing to note is that I haven't been able to find an HTML file thats hosted locally to map to. The software seems to work as if you utilize Spiceworks website but with your local URL and local settings.

Is it possible to do this via IIS, or should I just find an old spare computer and use that for the software?

Any help or suggestions greatly appreciated!
 
I didn't think spiceworks used iis but if it does all you need to do is modify the site in the iis manager.

As far as the name goes in the dns server you can make a refrence to helpdesk and give it the ip address of your dc. That should work although if you need to use a seperate port you would still need to enter it. ie http://helpdesk:82.

I'm guessing your using wsus on the default port of 80 and thats why you need to run this on another port.
 
You are right, Spiceworks doesn't use IIS. It has its own hosting service. I didn't think of the DNS idea of yours, but is there a way to be able to host the site without the user having to type in a port number?

In your opinion, does it matter if I change the default port on WSUS from 80 to simplify things? I was thinking of possibly having Spiceworks on 80 and WSUS on a different port because it gets provisioned by Group Policy anyways. Is that a good route to follow?
 
You don't necessarily have to put it on a different port, you can use host headers and A records in dns to point to the different sites.

Here's a site that explains how to do it, if you're not familiar with them.

Edit: in your case, it might just be easier to put WSUS on a different port.
 
klesik said:
You are right, Spiceworks doesn't use IIS. It has its own hosting service. I didn't think of the DNS idea of yours, but is there a way to be able to host the site without the user having to type in a port number?

In your opinion, does it matter if I change the default port on WSUS from 80 to simplify things? I was thinking of possibly having Spiceworks on 80 and WSUS on a different port because it gets provisioned by Group Policy anyways. Is that a good route to follow?
Click to expand...

That would prob be the easy way to do it.
 
You must log in or register to reply here.
Back
Top