The old one you have to go where the application install and remove the config file you don't want
\Program Files (x86)\Sophos\Sophos SSL VPN Client\config
I know I could use a tool like Create-Synchronicity to force 1 other directory to match the source, but I would prefer to find and list the differences in the directories.
Maybe powershell can help?
Yeah, PowerShell can help with this in the same way closing the front door of a house will fix a fire inside of it.
Cockpit looks nice and all that, but the version I tried didn't seem to have as many features or as much control like webmin does.
Tried Cockpit on Ubuntu? If so, you probably been using a old version because the only distro that I know that always has the latest version is Fedora.
Yep I'm a Debian/Ubuntu guy. I could probably add the repository for the latest version to try out if it does have more features. I'm normally straight up do everything through cli but wanted to try it out. then I tried webmin out which I haven't touched in over 8 years. They have defiantly improve things on their panel.
The instructions seem pretty straight forward. Did you give the send connector enough time to sync, or force it manually?
Yeah so, sorry for not following up. The instructions do work, but spam filters (sophos at least) puts this information back...... some great security there.
Anyways... yeah...
I was able to reduce the hop count printer in message analyzer from 5 to 3, which would remove the information. But the damn spam filter....
So it may be a wash to even consider this.
Spam filter can't be made to drop everything before it? We assume the spam filter is at the edge of your network, so the outside world shouldn't NEED to know about anything behind it.
Can it be, maybe does this use case say to do anything with it, no. Security Scan is what called this out. So remediating the item mentioned is the goal, not "fixing" the issue.
Things to consider if you do this yourself, once you disable a device if you don't enable it again, it will remain disabled in device manager between subsequent removal/installation.
So it's critical to enable any disabled devices after the fact, or you'll have to manually enable the device through device manager.
@DustinB3403 Yeah, Exchange 2013 and over. You have to also be on the last 2 Cumulative Updates from Exchange 2013, 2016 or 2019. For 2019 You only can get the updates through Microsoft Volume Licensing.
Yeah, a customer attempted an update from 2016 CU15.1 to CU19, it errored out on the last step, they restored (bad move) and had some mail flow issues for a bit.
@Dashrender I'm a 3rd party to the end customer here. Acting as the middle man as the customer's IT department wanted to engage outside support to try and vet different products.
I candidly told the customer that while this product will work, it won't work with all of the features they want without some substantial changes to their infrastructure and that the support (at least from this vendor) is pretty awful.
The simple approach here is to not integrate RFID/HID's to the system and simply use the AD Integration with the built-in QR codes that each member is assigned.
Just because something may be supported, doesn't imply that it is support.
Except in this case the vendor very clearly has stated they support you adding custom attributes within AD.
You can have replication if you have Starwind Clustering on the hosts (That's how I have some customers). That said, even on those situations I have a DC on the Local Host Hyperv of one of the servers or have a Site to Site VPN with a DC on Azure or AWS as a failsafe.
