It took me quite a long time to get through the initial Puppet tutorials. And even then I was missing important pieces that should be used on any production setups. After that Salt was really easy to pick up. I haven't tried Ansible, but people always seem to say it is the easiest.

@360col said in RequestTracker:

Also have a look at https://zammad.org/ free / opensource. They also do a paid hosted version.

Wow this looks like it probably checks all my boxes at work, except for knowledgeable, but it sounds like they should be releasing that feature soon.

The concept of organizations is something that seems to be missing from most solutions, but is crucial for us. And chat is a requirement too.

I wish I knew about this before we got on the verge of spending $15,000-$20,000 on another solution.

@flaxking said in RequestTracker:

@scottalanmiller said in RequestTracker:

@flaxking said in RequestTracker:

One of my dreams is to make a ticketing system on Tryton.

How do they not have one already, they have so much!

Someone did create a 'helpdesk' module, but as far as I could tell it was basically just fetching emails via imap and displaying them, not turning them into some kind of ticket

I just took a peak at the source code for it, and it looks like it should actually be more than that. Maybe I hadn't given it a good enough go when I loaded it up before. Perhaps it could be fork worthy.

@scottalanmiller said in RequestTracker:

@flaxking said in RequestTracker:

One of my dreams is to make a ticketing system on Tryton.

How do they not have one already, they have so much!

Someone did create a 'helpdesk' module, but as far as I could tell it was basically just fetching emails via imap and displaying them, not turning them into some kind of ticket

@black3dynamite said in RequestTracker:

@flaxking said in RequestTracker:

One of my dreams is to make a ticketing system on Tryton.

That's cool, so many options with using Tryton.

Tryton is actually the reason why I chose Python to be the first programming language I learned. But then I got a job in development a lot sooner than I expected and haven't been putting time into any personal projects.

One of my dreams is to make a ticketing system on Tryton.

So you downloaded a git repo, then built the project, and are you running the compiled build from that location?

@pmoncho said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:

@Obsolesce said in Correct license for a Win 10 Veeam backup server on Type-1 Hypervisor:

Straight from the license.rtf in Windows 10:

Doesn't the portion you highlighted make every win 10 PC that shares a printer or file share illegal?

Lower down, in d. iii, it specifically lists file and printer services as exceptions.

@scottalanmiller said in PFsense hardware ?:

@flaxking said in PFsense hardware ?:

@scottalanmiller said in PFsense hardware ?:

@flaxking said in PFsense hardware ?:

I'm using a wyse thin client for my home router.

What did you load into it?

Currently PFSense, but will be switching to VyOS soon.

What proc family is in that? A small AMD64 device? Or is it like ARM or something?

Yeah it's AMD64, something from AMD's Sempron line. The second NIC doesn't fit in the case, so I had to Frankenstein it a bit.

@scottalanmiller said in PFsense hardware ?:

@flaxking said in PFsense hardware ?:

I'm using a wyse thin client for my home router.

What did you load into it?

Currently PFSense, but will be switching to VyOS soon.

I'm using a wyse thin client for my home router.

Is SuiteCRM's Cases feature decent?

I just stumbled across this https://github.com/vyos/vyos-salt-minion
and then did some additional searching to discover that VyOS should be able to run as a salt minion in version 1.2

When I used Puppet, I used Foreman and it would store Facts for viewing. Supposedly Foreman can also be used with Salt, but I hadn't tried it. If I ever am able to run Salt in production again I will be looking into it.

@dyasny said in Monitoring with SaltStack VS Zabbix:

@flaxking You mean actual graphs and reports on stats gathered over time? Grafana is all about that

I mean like if you wanted to report on all the different OSes you have running - which I didn't think was possible using Prometheus + Grafana without determining a numeric value for each OS, but it looks like I'm wrong about that.

@Obsolesce said in Monitoring with SaltStack VS Zabbix:

@flaxking said in Monitoring with SaltStack VS Zabbix:

@dyasny said in Monitoring with SaltStack VS Zabbix:

I do all my monitoring with prometheus and grafana. Stats are saved, everything looks nice, and alerts are fully customizable. Can't complain

What about for monitoring things that aren't naturally represented as metrics?

What kind of monitoring?

@dyasny Hmm, well I guess what I was thinking about probably falls under "reporting" rather than monitoring.

@dyasny said in Monitoring with SaltStack VS Zabbix:

I do all my monitoring with prometheus and grafana. Stats are saved, everything looks nice, and alerts are fully customizable. Can't complain

What about for monitoring things that aren't naturally represented as metrics?

Self hosted screenconnect. Not sure what we will turn to when they stop offering maintenance subscriptions and our version gets too old.

@tonyshowoff said in SQL security over the LAN:

@flaxking said in SQL security over the LAN:

@tonyshowoff said in SQL security over the LAN:

@flaxking That may work and is worth a try, but it's likely not to work because the client is passing along to SQL Server and it's not known whether or not they implemented, or allow, encrypted traffic within their SQL Server connection library. Even if implemented in the library, it doesn't mean the client allows it, and even may be intentionally disabled for God only knows what reason. It isn't an SQL client, it's an application which just connects to SQL Server or passes raw SQL along to an application server to avoid client connection licensing limits.

How would that avoid licencing? The MS SQL licencing doesn't care how a user connects, you have to get CALs for the actual users using it no matter the method used. (Unless using SQL Express)

Because it opens one connection between the application server and the SQL Server rather than a new one for every single client. You can avoid user CAL issues because it's one connection from one user.

I can't speak to there possibility being a point in time when this was true, but it is not true now. You have to get CALs for each actual person, even if they themselves are not in direct communication with the MS SQL Server

SQL Express supports the transport encryption method I gave instructions for.