server online but grayed out
- Thread starter hhspiny
- Start date
I have replied to your previous post. It looks like the same case. We need to dig deeper as it works as it should on several machines in our labs (Admin account green after reboot).
What is not ok is that you have the "administrator" account greyed out but it is not "offline" but "online".
The "online" state is only an intermediate state and should switch to "green"/ready for connection almost instantly.
But here is a strange state where it says "online".
What is not ok is that you have the "administrator" account greyed out but it is not "offline" but "online".
The "online" state is only an intermediate state and should switch to "green"/ready for connection almost instantly.
But here is a strange state where it says "online".
continue from above.
login into admin account, "remotly_boot_svc.exe" is active.
turn "start with windows" off, "remotly_boot_svc.exe" is gone.
turn on "start with windows (minimized)", "remotly_boot_svc.exe" does not return.
reboot, before login, the admin shows both gray and offline.
login to admin, "start with windows (minimized)" is still selected. but there is no "remotly_boot_svc.exe" process.
logout of admin, gray and offline.
this is 1.27.1
all login done with remote desktop.
login into admin account, "remotly_boot_svc.exe" is active.
turn "start with windows" off, "remotly_boot_svc.exe" is gone.
turn on "start with windows (minimized)", "remotly_boot_svc.exe" does not return.
reboot, before login, the admin shows both gray and offline.
login to admin, "start with windows (minimized)" is still selected. but there is no "remotly_boot_svc.exe" process.
logout of admin, gray and offline.
this is 1.27.1
all login done with remote desktop.
tried quite a few combinations. here is how to re-produce the problem. the issue is with remote desktop session.
reboot computer from within remote desktop session. the "admin" instance shows as gray and offline.
login via remote desktop to admin account, then logout. now can connect to login screen via remotely.
another observation.
inside remote desktop session, turn off "start with windows" kills the remotly_boot_svc.exe process. but turn on "start with windows" does not stat the remotly_boot_svc.exe process. at this point, if reboot from within remote desktop session, the "admin" instance shows offline.
then, remote desktop to admin account, then logout, "admin" instance shows offline again.
Go to console and login to admin account, then remote login to admin account and logout from admin account. Now, remotly can connect to the login screen.
reboot computer from within remote desktop session. the "admin" instance shows as gray and offline.
login via remote desktop to admin account, then logout. now can connect to login screen via remotely.
another observation.
inside remote desktop session, turn off "start with windows" kills the remotly_boot_svc.exe process. but turn on "start with windows" does not stat the remotly_boot_svc.exe process. at this point, if reboot from within remote desktop session, the "admin" instance shows offline.
then, remote desktop to admin account, then logout, "admin" instance shows offline again.
Go to console and login to admin account, then remote login to admin account and logout from admin account. Now, remotly can connect to the login screen.
We have the same problem... It never happened before. We are checking if this is connected with Windows updates.
After restart with "Start with Windows" selected we cannot connect to admin account with or without admin account logged in.
The PC state is "online".
After logging in the host manually (not remotely because it cannot be done in this state) the full version starts and host is again visible as "ready for connection"
After restart with "Start with Windows" selected we cannot connect to admin account with or without admin account logged in.
The PC state is "online".
After logging in the host manually (not remotely because it cannot be done in this state) the full version starts and host is again visible as "ready for connection"
(( It happens when the login is done less than 60 seconds from system boot. It's related with random number generation.