4320 error on user login
I have a domain user (unprivileged) that I have added to the access list for their PC as follows:
This has always worked in the past for other users but now when the user tries to login they ...
Forum Discussion
Along this same thread, I just did an install on a pc in our office and immediately had a chain of problems - which I didn't get on other pc's here.
1. After the install, the setup did not recognize the PC as one that uses office 365 credentials (no dedicated local account) - -and hence did not present the option to set up an access code
-->I had to workaround this by manually creating a LogMeInRemoteUser admin account <--
2. Trying to then connect generated the above 4320 error. I then had to manually grant "everyone" full access in the logmein control panel options
->These extra permissions are not necessary on the other office 365 pc's in the office. I'd like to understand why this one was different? Any ideas?
DR
Ok - this is annoying now. Previous installs worked -- I just did another one that also failed to work successfully.
the credentials for this user on the pc are azure active directory (office 365) and based on the email address as login name (e.g. john@precision.com) but Logme in says the login name required is JohnDoe -- which is not an account on the computer or in our azure AD. Previously, the installer would know that this account/install must use an access code to grant remote control.
Is there a better way to get these installs to work? I can work around if I am physically present, but not if it is a link emailed to a remote user.
DR
