If the question is well understood, the solution unless it is implemented properly using FQDN, DNS to certain point will have nothing to do with what the user is trying to accomplish, the user is trying to simplify how users connect to the help desk using a method simpler than h ostname:port number, this can be achieved easily if SpiceWorks can run on that particular machine on port 80. Same thing, you can change it with SpiceWorks or directly editing (not hacking), the Apache configuration file, I like to know the stuff I deal with in and out, giving a pointer to others doesn't really mean to make it hard or easy, it is passing information across, sometimes is nice to know how things happen in the backend, from a technical perspective, that really helps to understand things that are not so obvious. This will not work if you have something else running on ports 80/443 so in that case as suggested earlier, have a website that does respond to port 80 redirect to the proper port. Why try to hack the config files for your method - just change the spiceworks app to run on the standard ports (80/443) using the standard procedure.ĭon't make it harder on people - make it easier. Be sure to first backup the original file in case you need to go back to that configuration. Look under C:\Program Files\SpiceWorks/httpd/conf and edit the file nfig, once changes restart Apache and try. The URL only work locally (LAN), I never asked the SpiceWorks gurus what would be the consequences of changing the port were Apache listen, but you may try changing to defaul 80 if Apache is the only web server running in the machine, and see if SpiceWorks will still working with all the functionality, if that works the users will enter or a virtual name to access the help desk. I think that's exacly what i've said, if you have another web server running on the same machine you will run SpiceWorks, the installation will set the web server in a different port, what is more, even if you are not running any web server in the installation machine, the installation will set SpiceWorks to be served on port 9675, this automatically avoids the installation to fail. If that was the case, he could have just changed the ports to be the common 80/443 and everything would work. This will not work if you have IIS running on port 80 - apache will not run on port 80 as well. If them remembering the users have a problem remembering the port number, then provide them a landing page where you can put a shortcut to the URL. I assume your users will access the Help Desk area inside your network, not from Internet, if that is the case you may naot need to do anything with DNS, it is the host name and the port what the users will access, so as long as they can find the host by name you are fine. In IIS at the properties of the website, under We site identification/Advanced. What would I have to do in terms of the DNS record to complete this?įor this particular case, SpiceWorks sets a port other than port 80 to avoid conflicts with users running other web server which typically will run on port 80, with Apache you can also change the port a web site will be served, just edit the nfig file, change the port and restart Apache. I was thinking possibly they can enter "helpdesk" into their browser instead Right now to login to create a ticket they need to enter in their web browser http:/ / aserve:9675/ login I want it to be easy for user to access this help desk.
However a lot of my users are not remember to use it because of the address they need to type. We have recently initiated a helpdesk system through SpiceWorks.
Neither he nor his management has responded to requests for comment.I am trying to create a DNS record for users in my company.
More Springsteen tickets go on sale this week. This is similar to how airline tickets and hotel rooms are sold.” Ticketmaster reported in its pricing policy documentation that “some events on our platform may have tickets that are ‘market-priced,’ so ticket and fee prices may adjust over time based on demand. The “platinum” tickets appeared to have settled at around $2,000 instead of the initial higher price, presumably in response to demand slowing down after the initial excitement of sales started. According to the figures, only 11.2% of sales involved the “dynamic” tickets, with only 1.3% of those sold for over $1,000, while 56% were sold for under $200 including 18% for under $99.īut Variety reported that “fans quickly figured out that the first ones to get through the queue each day were able to buy in the $60-400 range … only to have those immediately snapped up, leaving the more exorbitantly priced ducats - with values inflated as much as 10 times the original value - as what most would-be buyers see when they log in.”
0 kommentar(er)
