We have Spiceworks setup. People email an address we have setup for help. Spiceworks sucks in the email and creates the ticket. Other than when we respond out of it people don't know anything about the ticketing system. You can really change how and when Spiceworks sends out emails, making it almost invisible to the end user. I recommend some type of ticketing system just for tracking purposes.
Hello from SpiceWorld Austin 2016! The welcome session just wrapped up so I wanted to take a second to provide the full recap on the product improvements and new tools that were announced on stage this morning.
Zooming out, our focus has always been to develop the tools and resources you need to do your job better - every day. For example, over the last year you’ve seen us rapidly develop a series of new butt-based tools including Butt Help Desk, Port Scanner &Tester, Subnet Calculator, Butt Cost Monitor, Blacklist Check and IP Reputation, and others that are purpose-built for the task at hand and incredibly easy to get started with, allowing you to get value from them immediately.
The response to our new tools has been incredible, and we’re looking into new and exciting ways to add even more value to your day. For instance, we’re working to better integrate our butt-based tools with the Community to provide a seamless experience that not only helps you manage your environment but also connects you with the relevant content and people who can help you tackle whatever comes your way.
Below, check out our updates to current tools, as well as our upcoming tools, including the Spiceworks IP Scanner, Internet Outage Heatmap, and next-generation Traceroute tool. We are also updating our apps, our product pages, and introducing a multi-OS agent.
Hello Guys, I seem to have found the solution to this issue. By default, Azure has no ports open and that was why i was getting the errors. To solve this problem, i had to create an endpoint for the Virtual machine that had Spiceworks installed in it and open ports 389 and 636 TCP.
Now spiceworks syncs and authenticates with the AD on Azure and on premise.
that's why I was asking for specific VPN details. A VPN on the servers bypasses the Azure ports. A site to site VPN hits the "outside" of the servers and has ports blocked.
Awesome, so I can't even approach the OP publicly to let them know that other conversations are going on.
David can eat a bag of *****
Welcome to my world. I have 100% stopped posting "over there" because of that f[***]bag [moderated]. I swear he sits and rubs himself while he smugly deletes posts. I was so hoping he was one of the 12%, but no such luck.
If they are all on the same controller, why does rebooting affect the others? Isn't the controller suppose to managing that?
The point of auto is to have the AP detect what channels are in use around it and pick the best one. That will obviously be different each time any AP reboots. When the first one reboots, it will immediately affect the ones next to it as the signal drops and the unit around it detect a difference. Then once it powers back on, it has to detect what is around it and then determine what channel to use.
High density deployments are much different beasts than an office building with 3 or 4 AP scattered around for coverage.
I swear by SoftPerfect's Scanner. You can save your scans and it can do a LOT - - to the point where you can load up custom OID's for SNMP scanning, alternate credentials for WMI scanning, configure right-click options on your scan results, etc. I use it all the time.
When we migrate our remote sites to new IP schemes, I use it to inventory the subnet, then I'll come back and scan again (you can import your prior scans and merge them). The SNMP integration is great. I am getting printer serial and model numbers - - otherwise, I would have to connect to each manually.
It's portable in that you can simply copy the folder to a USB drive and it will work, but I don't know if it's 'proper portable.'