We have both the Dell USB-C docks and a couple of the Thunderbolt models. So far we have had no problem with the USB-C. I even use one for my machine. The Thunderbolts were a bit problematic around the first part of 2017, but after several firmware updates they seem to have stabilized.

@dbeato - Thanks. Maybe it didn't used to be in red.

@kelly - Yeah. I think Jamf have a 25-device minimum. I was looking at it for the 6 Macs we had. I don't know if it makes sense to do the iPhones MDM on it, since we also have Android devices that I need to manage. Hmm

@wrx7m said in Shared HP Printers - Apply Preferences/Settings to Clients:

I figured it out. You have to use the Printer defaults button on the advanced tab. It opens the same window as shown in the OP, but it will apply it to the clients.
0_1530920108014_751c2e82-b84e-4108-ba2c-63f37353bf8d-image.png

Yes, that is where you always do it. Remember that when you change printer drivers you need to change it all over.

You may not have LoS to the building from your current location but I had a similar issue with a client and we were able to negotiate with the property management of a nearby apartment building that did have LoS. My client rents access to the building roof where we installed fiber internet access and a Poit-to-Point network. There's about 2km between the PtP devices and we managed to get about 175Mbps speeds using Ubiquiti gear. Would that be an option you could investigate? Easy to setup VPN between locations at that time.

@IRJ said in Wazuh - Agents.Error. globalAgent is null:

@wrx7m said in Wazuh - Agents.Error. globalAgent is null:

I didn't get the error when looking at the list of agents today. Looks like the update or reboot of the Wazuh server fixed it.

I know this is a necropost, but it's good to mention that mismatched version of manager and agent will almost always cause issues. It is recommended to comment out the repository until you are ready to update agents and manager at the same time.

That is interesting. I have been upgrading some of the agents on Linux systems when they are released, and later, upgrading the server side (I comment out/disable the repos for the server side, per their docs).

@wrx7m I'm not sure. If all else fail, they do have chat room to let them know.
https://gitter.im/snipe/snipe-it

@obsolesce Right, I am having to add a group of computers to the printers' security permissions with allow printing enabled to get the GPP to actually deploy the printer to the user.

UNC pathing to the printer by a member of the PrintersChecksUsers (while the user is logged in) allows them to install and print to the printer.

The GPO shows as applied in the RSOP, but with item level targeting, I don't see any info on why it wasn't actually installed/applied. Maybe it shows it somewhere else.

The key is the shared printer's security tab on the print server, itself. That is where I have to allow the specific group of computers, as well as the specific group of users. I need both, the computers and users groups to have at least printing allowed.

@wrx7m Cool, good luck

@wrx7m that vendor sounds like GE or UTC. These companies employ the most ridiculous procedures and requirements in the name of security. I think it all comes down from gov oversight, so dumbasses on top audit you, then you need to implement some retarded procedure that does nothing, but makes lives miserable for everyone you deal with.

@wrx7m said in Wazuh on Fedora 28:

Thanks @JaredBusch

That seems to have solved the initial problem. For other newbs - After disabling SELinux, you should reboot.

Well, that depends on how you disable it.

@black3dynamite said in Installing Fedora 28 on ESXi 6.0 - Which Guest OS Version??:

Isn't all those Guest OS versions, mainly to help with pre-configuring the VM config?

Yes

@DustinB3403 said in What is the Latest With SodiumSuite?:

Any update on this, just thought about it and wanted to see where this project is at.

Sadly, nothing for the foreseeable future.

@emad-r said in CentOS 7 - Why Did [Almost] Everyone Switch to Fedora?:

the other guy who is knowledgeable but not as nice as Scott

Hahahahahahahahahahh

I finally found the GPO setting that caused this issue-

Computer Configuration>Policies>Windows Settings>Security Settings>Local Policies>User Rights Assignment

Load and unload device drivers - Enabled with Everyone and NT Authority\Authenticated Users listed.

I had to change it to Not configured.

0_1528315769936_2b6b6a24-bede-47d1-bd4d-3df40eb2c368-image.png

I submitted the ticket yesterday and they upgraded my site overnight. 🙂

@wrx7m said in Ubiquiti Unifi APs - Do You Need a Controller?:

Can you run two APs in mesh with just the mobile app setup? I.E. one connected via Ethernet and the other just powered on and uplinked to the other AP?

Not sure, I have only tried through the controller which does work.

@kelly said in Google DNS Issues and Super Slow Office 365 Portal- Anyone Else?:

For future reference, doing a traceroute and noting what the typical path is for your traffic can help you when it slows down. Then you can rerun the trace and see if the path is different. If a node goes down or has issues you may be rerouted on the larger internet. This doesn't work as well as it did in the past as we move into virtualized networks and things appear and disappear on demand, but it may work for you. I would usually choose a target logically closer than a public DNS.

Yeah, I did a tracert to see if there was any obvious issue at the various hops, but it came back with reasonable results at first.

@wrx7m said in Webroot SecureAnywhere Business Replacement?:

@momurda said in Webroot SecureAnywhere Business Replacement?:

This task Manager behavior is from Webroot?
I see it occasionally; one developer in particular says it is always a problem.

https://community.webroot.com/t5/Webroot-SecureAnywhere-Complete/Task-Manager/td-p/309032

According to the most recent post in that thread (edit - the most recent post is currently 2 weeks old), a beta release fixes this issue. Being that the thread started in December of 2017, it goes to show how long it takes them to fix things.

yes, that is also what we found out, especially in Windows 10.