trflmiuser
Active Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Username for remote controlling AzureAD/Entra/Intune computers seem inconsistent and unpredictable.
I still have a lot of Windows 10 computers on my network that are domain joined. LogMeIn Central is very easy with those. I can sign in with my (domain admin) username and password to access any of these computers. I'm talking about the "Sign in as you would if you were sitting at the remote computer" prompt here. When I buy new Windows 11 computers, I do not join them to the domain. I just sign in to 365/Entra/whatever the right terminology is. If my initial sign in name is my own username and password, then I can remote control with that. If my initial sign in name is the user's, there is no guarantee that their username and password (which I do not have and do not want to ask for) will work, and I have to create a local admin account and remote with that. If I sign in as myself later, again, no guarantee that it will work. One one instance, the only username that is accepted is AZUREAD\UsersFullName. This is super wacky because UsersFullName is neither their username, their UPN, nor their email address. Clearly I am doing something wrong when provisioning these devices for LogMeIn. Any advice?156Views0likes1CommentBlock IP from logging into all computers?
I had a very weird attack scenario just happen. One of my Central users received a phishing email asking for the passwords to login to the computers to which they have Central access. I think the only way someone would know which specific computers someone has access to is to login to Central. The user has 2FA enabled, making this extra distressing. So there's obviously the IP block for individual computers after three failed logins, but is there an organization-wide way to block IPs from logging into Central at all?601Views0likes1CommentBest practices for using Central to remote assist computers on Windows 11/Azure AD? (Non-domain)
I plan to start deploying computers without joining them to the domain. Users will sign in with their Microsoft 365 credentials to get into the computer and their apps. When a computer is on the domain, I can put in my own credentials when remote controlling a user's PC. This doesn't work with a 365-only PC, and it's bad practice to ask a user for their credentials. So how are you managing this?Solved699Views0likes1CommentPlay sound remotely but not locally?
Scenario: I am at home I connect to a host computer in the office and launch a training video. Via remote sound, I can hear the video at home. But the physical host computer's speakers are blasting the video and creating a lot of noise pollution in the office. How do I mute the host machine only, while still listening to the video at home?1.2KViews0likes1CommentHow long for changes to Desktop Preferences Packages to take effect?
I set up a Desktop Preferences Package and deployed it to a test group. No complaints. I rolled it out wider and got a few complaints that the connection seemed slow and that the desktop image was missing. Checked the Preference Package and I had mistakenly set the color depth and background image settings. (these are just easy examples that you can see when you log into the hosts) I changed the settings and rebooted the hosts. No change. I removed the computers from the package and rebooted the hosts. No change. I suppose it just takes some time for this to take effect? Is it known how long it takes for these settings to take effect?614Views0likes1CommentMultiple complaints from end users since recent automatic update to LMI Client
It seems that the 1.3.5282 update has introduced a few issues in my environment that I am having trouble tracking down. Wonder if others are seeing these things. These issues are on home equipment that I do not manage but support on a best effort basis, so I'm limited in what I can/am willing to do. Home equipment (clients) is a mix of OSes. All hosts are Win 10. The more severe of the two issues is that the client application simply will not launch. You launch the application, you see the process for a moment in Task Manager, but then it closes immediately with no feedback. This has occurred on Windows 10 computers and a Windows 7 computer. I uninstalled the application, deleted all LMI folders from programdata and appdata, and installed an older version I fortunately had saved and instructed the users to not install updates when prompted. The other issue is that the remote computer looks blurry. We've gone through all the resolution options on the host and client side, as well as changing color depth and zoom settings to no avail. This has happened on Windows 10 and Mac clients.2.2KViews1like5CommentsRe: Updated client to 1.3.5282 - screen blank behavior has changed.
No, not all host PCs. Just clients where the client machine has 3 monitors. If I remember correctly, in the spring there was an update wherein the update notes said that it made screen blanking available for more users. In my environment we always had the ability to use screen blanking; maybe it's a different license type. When this update rolled out, there were two consequences if screen blanking was turned on: 1) A laggy mouse cursor and 2) The client user would have more monitor windows than the host machine had monitors. The latter was seen as a positive change. I taught the users how to remove "extra" monitors (they appeared in the Windows 10 display settings dialog), but there were a few who grew to enjoy this change (or bug as it were). The "extra monitors" thing did appear on several computers in our domain. Not all or even most.1.2KViews0likes0CommentsRe: Updated client to 1.3.5282 - screen blank behavior has changed.
Looked back to see if I had any responses and realized I forgot to actually ask a question. Hah. Is there a way to return to the behavior whereby the LogMeIn Client will give me three virtual monitors when the host only has two?1.2KViews0likes5Comments