Well that host has not gone off line from the colocated file server computer that I had used to get to it before. I don't know if one of the reboot attempts I sent it actually worked and it never came back up or if it had a full melt down. If anyone can tell there can determine anything further I could provide the internet id for it to be checked in the RU ID servers. Ya'll have emails from me.
After a re-install, the taskbar icon is left in a bad state. The old desktop icon is still on the desktop. Attempt to pin that icon does not update the taskbar. I have to go into the windows menu, into the viewer folder, drag the icon to the desktop, until the old icon, and pin the new icon. The installation needs some work.
I executed that remote restart of the screen shot of the last email. I waited. Then I connected full screen. I got connected but the PC is inoperable still in its frozen state. So it appears the reboot did happen. The Windows GUI is not responding. Health stats look ok when it froze. I'm looking at the zombie screen now. I tried the menu based "sent ctrl alt F12 but no effect. (I think I can't get that to pass through my in-between viewer) I'm still trying to regain control of the computer... Its in a school and access will be poor over the holidays, so hence I was counting on ability to resolve issues remotely :(
Update: the computer in question was able to be accessed by a viewer of a colocated computer which is also a host I have access to. I logged into the colocated computer and used its view to log into the playout computer that refused to connect to me across the internet.
The computer is running OBS and the output of that is on air and is frozen. So the application or windows is in some kind of hung state. The host is showing online, but when I try connecting, (tried full, fie xfer, and power control) but the host then goes offline while connection attempts are made, which all fail. But then the host comes back online. I'd accept that the machine was sufficiently crashed that maybe host wouldn't work, but it reporting its only suggests it should be functional- at least enough to give the the power to reboot the machine. Everything is version 126.96.36.199
It seems to be always over the "OK" and "Cancel buttons of dialog boxes. Often times it is hard to see or read the buttons underneath this message. Can you consider make the message more transparent? Perhaps it could fade up and down, like a "breathing" led indicator. That might make it a little less disruptive but just as informative. Bottom line, if you have to put it there, please consider good options to make it less disruptive. After all, if someone doesn't heed the warning, then its on them.
Hi - I wasn't clear on the "run as admin". I was trying to ask about whether there were problems with the systems operation if the software was not installed with "run as admin", I meant general operability, not the throughput performance. I have seen some applications that came around to insistting that one performs their install with "run as admin". And possibly also modifying the run mode of the program to be "run as admin" . I figured something is different with respect to privilege access of updaing system files and running tasks... but just a guess.
Wow that's a lot of great information. - Remote Settings... how cool, I learned something there. I'll keep that feature handy. - corrupted installation - yes could be- I'll try it. - local mouse pointer config - I would not have thought it was config related as all the machines are configure the same in this respect but behave differently, but I'll check. Perhaps the difference is due to a corruption also.
Give me a bit to work that through. I will post about the experience soon.
ONE QUESTION- ARE YOU SEEING ANY DIFFERENCE IN PERFORMANCE WHEN INSTALLS ARE DONE with "RUN AS ADMINISTRATOR" AND / OR THE PROGRAM IS RUN WITH "ADMINISTRATOR MODE" SET IN ITS PROPERTIES ? It seems Windows 10, even if you have an admin type account, has something different from Windows 7 in perhaps it still limits some privileges of admin accounts requiring the addition of "RUN AS ADMINISTRATOR" in the actions. Do you agree? I ask in case something like this could be contributing to corruption or different behavior in these cases.
Edited:Douglas Crawford - Dec 09, 2021 6:36:15 pm EST
So to recap where I'm at: Monitor 1 (Gus Transcode) can now open #1, #2, & #3 just fine. The problem opening #2 was ID reference error. However, opening File Server actually opens #2 instead, though the IDs are correct in the connection and in thi hosts. Monitor 2 can now see all four of the hosts in question and can open fully #1,2, &3, (issue with #2 offline was an ID error) but connection to File Server never completes. I triple checked the IDs in the connection definition and the File Server Host. The mouse pointer is a small box.