This would have happened on Server 2012 R2 as well, dual scan has been around and causes a lot of problems as you noted.
It is strange that I didn't have these issues in 2012 R2. I essentially copied the same GPO for 2012 R2 and made some minor changes to it to convert it for 2016. My 2012 R2 show the correct default service.
Weird, I have various Server 2016and now 2019 with WSUS and while dual scan was an issue for me on Server 2012/ 2012 R2 not anymore.
To add to this- I have an error that started appearing after updating their Fedora 29 and 30 instances. Further testing found that the error appears in different regions using their server type template installers or even a custom iso option that I used with net install. All I have to do is deploy, run dnf update and reboot. The error is present in every boot after the update. https://mangolassi.it/topic/19903/fedora-29-and-30-edac-skx-can-t-get-tolm-tohm-error-on-vultr
I don't think bridging will cause any problems in this case. Traffic is intermittent and low speed so even if there are more broadcast traffic sent over the VPN links, compared to a routing solution, I don't think it will have any impact.
But I'll probably set up some kind of test to make sure before deploying.
When away from the desk, the headset will ring if somebody calls in, but you are not able to answer the call from the headset. So, you have to run back to the desk and answer the call in Skype for Business soft phone, which then connects the call and works over the wireless headset.
This isn't a Skype for Business issue - this is just a lack of pickup button on the headset issue, or is there a button that works with other software, just not S4B?
As mentioned - real professional gear like Sennheiser and Plantronics work well in this space.
Works like a charm. We've had it for close to ten years now.
It's set up to space after each scan and CAPS so that all serials are identical across the board.
I suggest setting up a single sheet print-out of 0-1 and A-Z (if needed) along with the bar codes for setup. Then, when it comes time to pair you're not frustrated by the default ENTER (we remove this) during pairing. We enable SPACE post pairing.
For complex builds nothing beats it.
Wasp units are nice.. but since I'm paying for this out of MY pocket,.. that is about 3x more then I want to spend.
Just curious as to why you're paying for this out of your pocket?
Any time I can improve my personal tool box I’m happy to. As long as it isn’t some mega expensive item.
A small scanner that is multi function, inexpensive and such - all the better
I would guess there are better alternatives out there that can be run on Linux servers
All enterprise Forex software runs on Linux (and generally UNIX, and nothing else.) On the Forex floors they sometimes use Windows desktops, but all the analytics comes from UNIX systems (including Linux.) Windows is only used as a GUI for the trades to be places, and generally isn't used even for that.
What is it causing on your Zimbra? mine are unaffected.
For me, everything is working smooth, the only thing I worry about is restart notice messages that are written to zimbra.log every minute.
Jul 2 00:47:20 mail zmconfigd[24959]: Fetching All configs
Jul 2 00:47:20 mail zmconfigd[24959]: All configs fetched in 0.07 seconds
Jul 2 00:47:26 mail zmconfigd[24959]: Watchdog: service antivirus status is OK.
Jul 2 00:47:26 mail zmconfigd[24959]: All rewrite threads completed in 0.00 sec
Jul 2 00:47:26 mail zmconfigd[24959]: All restarts completed in 0.00 sec
Jul 2 00:48:26 mail zmconfigd[24959]: Fetching All configs
Jul 2 00:48:26 mail zmconfigd[24959]: All configs fetched in 0.10 seconds
Jul 2 00:48:33 mail zmconfigd[24959]: Watchdog: service antivirus status is OK.
Jul 2 00:48:33 mail zmconfigd[24959]: All rewrite threads completed in 0.00 sec
Jul 2 00:48:33 mail zmconfigd[24959]: All restarts completed in 0.00 sec
Perhaps, such a behavior is OK (zmconfigd fetches configs,checks them for not being changed and assumes no restarts needed for services)?
I think so. Nothing in there suggests a restart happened.
Us too, as the one exception to the above "direct" piece. It's a highly secured jump box in a data center. And the customer systems are tied solely to it, not open in general.
So equipment that is not a PC (for instance switches, network appliances, printers) are managed through the computers on-site or through the jump box? Or perhaps not managed at all?
Either through tooling (e.g. not directly), or via an on site machine (local jump station.) In lots of cases for us, Ubiquiti gear can be managed through its own centralized consoles.
