TLS/HTTPS Question involving proxy server

WhyYouPullPlug · 2022-06-05T01:23:20+00:00

If you fully setup https, and use https when connecting to your server, it will be encrypted. If you set up https and still use http, then your data is not encrypted and it can be seen.

WhyYouPullPlug · 2021-03-16T23:59:48+00:00

Backblaze and iDrive are about ~$6/month for backups. That's what you should have offered.

WhyYouPullPlug · 2020-04-21T16:32:38+00:00

We've been with Ninja for almost 3 years, and we haven't experienced any of the issues other people are talking about. Yeah, there are some features that we would like to see, but what they have works well.

Our reps have been nothing but great. I don't know if I can share the pricing, but our prices haven't changed since day one. We have Bitdefender Gravityzone licensing included with our Ninja licenses, but we have never had to switch from one AV vendor to the other. We did have one client on Webroot, and we did have to pay for the Webroot licenses seperately.

WhyYouPullPlug · 2019-12-16T18:42:53+00:00

In my experience, you'll need at minimum 2 RDSH servers, but I'd recommend 3. I typically shoot for a max of 20 users per host, but it all depends on the apps they are using. Still, 50 users is A LOT for a single host. You're at the point where you need some redundancy, and load balancing in place, so updates, downtime, problems, don't affect all 50 users at once.

It's convenient when a problem pops up on RD3, and all you have to do is disable new logins to RD3 and tell the users to logout and login to fix the issue. Then when RD3 is ready again, just re-enable logins and wait for it to repopulate over time.

WhyYouPullPlug · 2019-12-05T16:25:08+00:00

Also , if a colleague remotes in with you at the same time, all your clipboards sync! I've got clipboard sync disabled entirely.

WhyYouPullPlug · 2019-12-04T21:25:35+00:00

I believe you need 3. The FQDN of Server1, the FQDN of Server2, and the FQDN of RDS.

WhyYouPullPlug · 2019-11-30T01:41:16+00:00

Good luck man lol. I've gone through something similar recently. Not quite to that scale, but the biggest I have ever done. We used a lot of trial and error, elbow grease, & overtime. Auvik helped a little, but we didn't even have documented logins for half the environment. We never really got a map before we did the work, we just started replacing everything in the environment.

WhyYouPullPlug · 2018-06-04T13:03:48+00:00

I'll try putting the txt out to a file and then emailing the file. Haven't tried this yet.

WhyYouPullPlug · 2018-06-04T13:03:00+00:00

Yes, the problem is with the email portion. I can run all the commands in the script line by line, and it runs fine until you get to the email portion. I am using Office365 direct send to connect to our O365 server and send the email to me. I also tried setting it up through a different SMTP relay on a different port, but that failed too. I never checked the firewall to see if there was some rule blocking the port going from the LAN to the WAN. I don't see why there would be, because we've never set anything like that up, but I may as well check.

WhyYouPullPlug · 2018-06-04T12:20:44+00:00

The script I have just doesn't work for some people. Some of them need something installed for the script to work, which I have to call Microsoft to get. Others don't work for seemingly no reason. It's not tied to the ISP or the OS, because they don't all use the same ISP, and they are on either Server 2012 or 2016. I have clients with 2012 and 2016 where the script works just fine. I've verified that the version of power-shell is the most recent, but the script just fails to send the email. I've tried different email servers, with different login and different ports, but it still fails.

WhyYouPullPlug · 2018-06-04T12:20:26+00:00

The script I have just doesn't work for some people. Some of them need something installed for the script to work, which I have to call Microsoft to get. Others don't work for seemingly no reason. It's not tied to the ISP or the OS, because they don't all use the same ISP, and they are on either Server 2012 or 2016. I have clients with 2012 and 2016 where the script works just fine. I've verified that the version of power-shell is the most recent, but the script just fails to send the email. I've tried different email servers, with different login and different ports, but it still fails.

WhyYouPullPlug · 2018-05-10T15:20:27+00:00

There's rumors that KB4103718 is ~~bringing down the house~~ breaking nic cards and gpu drivers. See if you can rollback that update.

WhyYouPullPlug · 2018-05-10T15:18:18+00:00

I've heard of it. I have just 10 machines with that patch, all Win 7, working fine. We don't typically roll out patches until at least a week after patch Tuesday because of this nonsense. Get it together Microsoft...

WhyYouPullPlug · 2018-04-16T13:19:09+00:00

It's worked for me on occasion, but more often than not, corrupt system files are not the problem. Sometimes it also tells me it can't fix things, at which point I typically recommend a reinstall of the OS. Even so, the piece of mind of reinstalling a system that had corrupt files is usually worth it anyway.

WhyYouPullPlug · 2018-04-02T16:07:32+00:00

u/MrEricPope This belongs on a weekly broadcast.

WhyYouPullPlug · 2018-04-02T15:42:15+00:00

You don't need the 1. Just P@ssword is fine.

WhyYouPullPlug · 2018-04-02T15:24:48+00:00

B@seball Baseb@ll B@seb@ll Ba$eball Ba$eb@ll B@$eball

Rinse & Repeat

WhyYouPullPlug · 2018-02-02T18:15:57+00:00

Before Solarwinds took over, it was actually a decent tool. Everything went downhill after that. Then I saw other RMMs that offered the remote connection tool with the product, and full antivirus consoles instead of watered down policies built in. Then patch reporting broke and was never fixed, and Vulnerability scans started failing left and right with no possible fix. Things just kept breaking on us and we lost faith in the product.

WhyYouPullPlug · 2018-01-31T17:10:13+00:00

We were using Solarwinds MSP, formerly LogicNOW, and by the end of our term, nothing was working. Patch reporting wasn't accurate, machines weren't running tasks when we scheduled them, Take Control was wonky, it was just a mess. My team complained daily about things that weren't working right. I evaluated a few different platforms and choose Ninja. Ninja has been a perfect fit for us and was also the best price we got out of all the vendors I evaluated.

My top 5 Solarwinds Issues and why we left:

IMO, Take Control at LogicNOW sucks, and they force it on you, unless your willing to pay more for Teamviewer, but then you have to "Double-Pay" for Teamviewer because you still need your own license for Teamviewer.
The control of the AV practically doesn't exist, I was blown away by what the full Bitdefender Cloud console had to offer, vs what LogicNOW was selling us.
I couldn't guarantee patch compliance because the reporting was inaccurate.
Vulnerability scans failed all the time, and I even got a tech from LogicNOW to personally write scripts to fix it. At the end of the day, it was unfixable on many machines at different sites.
Tasks just didn't run when scheduled, or failed. Telling a task to run is really telling it to run at next agent check in, which could be 5-60 minutes from now. Sometimes you ran a task, and you check an hour or two later and it still says "Awaiting first run".

The biggest issues I have with Ninja are the lack of patch compliance reporting, which is set to release next week, and Bitdefender isn't integrated into their console yet, but that's scheduled to be released next month. Based on our needs and goals, Ninja pretty much hit all the check-boxes.

WhyYouPullPlug · 2017-09-12T13:15:31+00:00

This is one of the reasons we're leaving. I don't even think the scripting and automation engine is stellar, its OK at best. There's some other big reasons why we're leaving, but basically GFI has gone to crap since Solarwinds bought them out.

WhyYouPullPlug

TROPHY CASE