@Pete-S said in New server q's:

@siringo said in New server q's:

Those last 2 posts are spot on Scott.

If I were to deploy a solution that was different to what everyone else was deploying, even if it was cheaper, better, faster, more resilient etc, I'd be lambasted by others simply because it was different and more likely, not understood.

That can lead to unhappy management, which can then lead to all sorts of grief for me.

This is obviously, not what I want.

Thanks for all the info & advice, it is greatly appreciated.

So you should buy the same old server model from 2016 to stay consistent with what they currently know 🙂

Unfortunately yes.

It comes under the job preservation title. I live in area where IT work is extremely hard to secure due to there not being much of it, so rocking the boat is not a good move.

@scottalanmiller said in ps2 to usb adapters:

If I really think about is, most keyboards prior to PS/2 were using more traditional serial adapters. Which were digital. Duh.

Actually the first IBM PCs used the same type of electrical interface but a different connector, a 5 pin DIN.

The mouse was a real 9-pin serial DSUB at first though. If my memory is correct LOL

@scottalanmiller said in SSH jump server access control?:

The challenge is really that you have to identify a person on the network separately from their identity to applications. Generally networks are not user aware.

I believe the user-based network restrictions only extends to the target server(s). So outbound from the jump server. (As you said one jump server / IP per user and then firewalled off would be one way to do it).

So someone could potentially move laterally efter they have logged in to the target server. But other servers will probably only accept connections from jump servers so it would be hard. Which is on purpose of course.

Youtube Video

this goes back to 2016, but sounds just like what you're experiencing:

*Symptoms

After you apply this update on a Remote Desktop Session (RDS) host, some new users cannot connect to an RDP session. Instead, those users see a black screen, and they are eventually disconnected. This issue occurs at unspecified intervals.*

https://support.microsoft.com/en-us/kb/3179574

Chrome is managed by GPO,… but computer not moved. We had another computer pop up with the issue Friday so issue is growing.

@Obsolesce said in Miscellaneous Tech News:

@scottalanmiller said in Miscellaneous Tech News:

Jaja, yay I got sort of referenced

The "weird systems users": hobbyists who offer virtualization to non-profit and charity users, using old, out-of-maintenance hardware that had been inherited or passed on to them. Enthusiast users, with no funds to buy licenses?

That too.

Make sure to update firmware.

@JaredBusch said in KVM networking with libvirt (virsh) questions:

I assume that Debian 11 uses NetworkManager? I don't have a clean Debian system running KVM to check.

If so nmcli and its related commands are your friend.

Thanks Jared.

Reading about nmcli and seeing your screenshots led me to understand that macvtap devices are only active when the VM is actually running.

Using ip link I can now see the macvtap device on the host. One for each VM connected.

7ad85ba6-1b7b-40a2-aa7a-d8e12988683f-image.png

@Pete-S said in Save shell session to disk?:

That's why you should launch ssh like this:
ssh [email protected] -t screen -RR
If you don't have a session going it will create one.
If you had a session going but it was interrupted, it will reconnect to it automatically.

@JaredBusch said in Save shell session to disk?:

I do not like to launch screen for no reason.

@travisdh1 said in Microsoft Finally Deprecated WINS:

But WINS was always painful.
Just avoid additional pain.

Most people use and rely on it without realizing it. You'd be amazing how many networks use it for discovery still and no one in IT has even heard of it.

The problem is an ID 10 T issue