@IRJ said in Joining 2 Windows 10 Machines:
Dual booting is a management nightmare. How often is the secondary OS updated? Who the fuck knows? When the user finally uses the secondary drive, they have to spend 2 hours installing updates.
It makes no sense from a management or productivity standpoint for the user.
Two opportunity to get a BSOD after a update.
:crazy_face:
Use Incognito mode availability > Incognito mode forced
That shouldn't allow anyway of signing in at all.
@EddieJennings said in What Are You Doing Right Now:
Just registered for Red Hat Summit 2021. It's a free virtual conference again this year in April and June.
I keep registering but end up watching the recordings instead. To busy to participate during live session.
@DustinB3403 said in OSX Cli Join hidden network:
@black3dynamite said in OSX cli Join hidden network:
@DustinB3403 said in OSX Cli Join hidden network:
Which is why I said, it adds the connection, but it fails to connect. I can go into the GUI and connect, but that defeats the point.
I want to add the connection, and connect automatically without having to fuss around with the damn gui.
So in the GUI, is auto-join enabled after you add the network?
Yes, but it doesn't connect. Maybe with a reboot. But that would kind of defeat the point I'm hoping for.
Restart the network service instead of rebooting
@MordyT said in Comparing MeshCentral 2 to ScreenConnect:
@NashBrydges said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@JaredBusch it has "delete device". I don't know if it removes the remote agent. But it makes the remote agent useless at least. I've never tested to see what the remote agent does when that option is selected. But it definitely removes it from MC itself.
Interesting behaviour I just observed when I tested this. I can click on the "Delete device" option and it does momentarily remove it from my MC installation however the remote device immediately returns to the MC My Devices dashboard. It looks like there may be a bug that prevents it from being removed if the remote agent is still running on the remote device.
Download the uninstaller, transfer with meshcentral to the pc, run with meshcentral remote commands, delete device from portal?
Would be nice for a button, but in theroy that could work...
Heck, could likely make it all a powersehll script with invoke-webrequest, so you can in 1 script download, run uninstaller, delete installer (maybe). Then it's a matter of deleting from portal...
No need to download the installer.
Create a script with something like this.
$_oFile = 'MeshAgent.exe'
$_oMeshAgentPath = 'C:\Program Files\Mesh Agent'
$_oMeshAgentArguments = @(
'-fulluninstall'
)
Start-Process -FilePath "$_oMeshAgentPath\$_oFile" -ArgumentList $_oMeshAgentArguments -Wait -NoNewWindow
But having a option to delete device and to uninstall meshagent and then delete device would be awesome.
Edit: Fixed path for C:\Program Files\MeshAgent to C:\Program Files\Mesh Agent
Thanks @JaredBusch
Fedora 34 Workstation Beta -- Right after you login.
@JaredBusch said in Copy SSH public key to ssem behind a jump box:
I can SSH in once with password and manually create the authorized_keys files (and the .ssh folder for that matter), but then I need to worry about permissions, etc.
Will something like this work?
cat ~/.ssh/id_key.pub | ssh -J jump.domain.com 10.X.X.X -o IdentitiesOnly=yes 'umask 0077; mkdir -p .ssh; cat >> ".ssh/authorized_keys && echo "Key copied"'
@JaredBusch said in Copy SSH public key to ssem behind a jump box:
@black3dynamite said in Copy SSH public key to ssem behind a jump box:
@JaredBusch said in Copy SSH public key to ssem behind a jump box:
I can SSH in once with password and manually create the authorized_keys files (and the .ssh folder for that matter), but then I need to worry about permissions, etc.
Will something like this work?
cat ~/.ssh/id_key.pub | ssh -J jump.domain.com 10.X.X.X -o IdentitiesOnly=yes 'umask 0077; mkdir -p .ssh; cat >> ".ssh/authorized_keys && echo "Key copied"'Does that give it the right selinux type also? I’m not at a computer now to test.
The correct selinux type should be unconfined_u:object_r:ssh_home_t:s0
@pmoncho said in What Are You Doing Right Now:
Trying to find a way to turn off highlighting in vi when using sudo.
:nohlsearch
Ok, I think I got it working now.
# From your host to your JUMPBOX
# Not needed if your public key is already in placed
cat ~/.ssh/id_ed25519.pub | ssh jump.domain.com 'umask 0077; mkdir -p .ssh; cat >> .ssh/authorized_keys'
# From your host to the host behind your JUMPBOX
cat ~/.ssh/id_ed25519.pub | ssh -J jump.domain.com 10.X.X.X 'umask 0077; mkdir -p .ssh; cat >> .ssh/authorized_keys'
# Connect to your host behind your JUMPBOX
ssh -J jump.domain.com 10.X.X.X
While waiting for Fedora Workstation to finish upgrading to 35, I’ve been wasting time spamming my daughter with Memoji.
USOCLIENT Documentation & Switches
https://www.urtech.ca/2018/11/usoclient-documentation-switches/