Jump desktop not loading before login Catalina 10.15.4
So I have the latest version of jump desktop connect, and just updated to the latest point release of Catalina. I can no longer connect remotely before login and have to manually launch jump desktop connect on the machine in order to access it remotely.
Effectively this means I can no longer reboot the machine from remote.
I am very glad I only upgraded 1 out of my 5 machines to Catalina. What a nightmare.
Any ideas on what I can try to get the service auto launching prior to login?
-
It's happening on all my Catalina 10.15.4 machines.
On the machine, I see a login prompt. On JumpDesktop I see a spinning. wheel on a blank screen, followed by the "Computer is offline" message.
One of my machines is a brand new install with only Jumpdesktoip (and SOPHOS home) installed so no other influences.
As soon as as the account is logged in, JumpDesktop works.
This is also true for machines with multiple accounts (each account must be logged in for JumpDesktop to work on that account).
Maybe this is a new issue with 10.15.4?
-
In my case after rebooting the remote machine behaves as if it is offline (greyed out in the interface). I have to physically login and launch the jump desktop connect app in order for my remote machines to be able to connect. This is the case for both my iOS and macOS client apps.
-
I am on the latest update of Catalina. I believe it's 10.15.4.1.
And yes "start when computer starts" is checked.
I should add that the Mac in question is very rarely rebooted, so it's possible that this is an issue with earlier versions of Catalina as well and I just never realized.
I should also add that I tried reinstalling connect already.
-
OK, this is 100% something to do with FileVault.
I just switched it back on, and again I could not logon with Jump Desktop after restarting. Looking at the local monitor, it was sitting happily at the login screen.
I then switched FileVault back off, and Jump Desktop worked a couple of seconds after it booted up (showing the login screen).
The only thing I haven't tried (or should note) is that I was using FileVault with my iCloud ID, not with a separate recovery password.
-
Ok - so there a way to configure FileVault to not log you in to your desktop - but we're going to skip that because I don't think you've done this.
Now: With FileVault enabled, when you reboot - the computer should be marked as OFFLINE in Jump when you see the FileVault login prompt. Do you see this?
-
@James Right - sorry about the confusing terminology. So you are right: When you have FileVault enabled and you restart the machine, the disk will be encrypted completely - at that point nothing can / is running except a very, very minimal shell of macOS which prompts you for your password. When you enter the password, macOS uses that to unlock the disk and proceed to load the OS - which happens to include Jump. So this is expected - though this hasn't changed in Catalina. This is something that's always been there since FileVault 2 was released in macOS 10.9.
Also useful tip: if you want to reboot a Mac without the FileVault prompt getting in the way, on the command line use this: fdesetup authrestart
-
OK, thanks. So not being able to restart an unattended remote machine with FileVault enabled is expected behaviour?
Are you saying that the workaround to this is to use the command "fdesetup authrestart" which allows me to restart an unattended FileVault enabled Mac remotely and still get Jump to work? ...so my only problem only arises with a power cut or an unexpected reboot?
-
> So not being able to restart an unattended remote machine with FileVault enabled is expected behaviour?
Not exactly: You can restart it, but you need a way to unlock the disk _before_ the restart to make sure the OS loads up. If the disk is locked, nothing on the machine runs (including Jump or any other apps you've installed) until the disk is unlocked.
> workaround to this is to use the command "fdesetup authrestart"
Right - this command is used to unlock the disk _before_ the restart.
> so my only problem only arises with a power cut or an unexpected reboot?
Correct. Unfortunately with full disk encryption - this is how it works. This is not a Mac limitation - this is how it works on Windows as well.
Please sign in to leave a comment.
Comments
36 comments