Forum Replies Created
-
Posts
-
I was able to figure out the issue. The installer doesn’t like UAC. To get it working, I had to remove my machine from the domain, remove the UAC policy, disable UAC, then install the software and rejoin the domain. No issues with UAC once the software is already installed.
Needless to say, this is kind of painful. It’d be great if you guys could update your installer accordingly to prevent requiring UAC to be disabled.
Anyhow, thanks a bunch for your help!
I uninstalled NoMachine and rebooted. The nx user account was properly removed by the installer. I reinstalled the software and rebooted. Tried connecting – no dice.
The NoMachine installer creates the nx user account, but it still throws an error trying to create the home directory. Either way, I’m in the same boat.
For what it’s worth – I specified the path to the profile/home directory for the local user and restarted the NoMachine service, to no avail.
Hi Cato,
Thanks for getting back to me. We don’t have NoMachine installed on a domain controller, but the workstation is joined to the domain. I’m able to confirm that the local NX user does exist on the machine, although admittedly, the home folder does not have a path specified. That said, when I compare it to the one machine that does have NM working, the nx user doesn’t have a home folder specified there either.
Esan, Britgirl: I’m an idiot; my apologies.
I thought I was responding to my thread. I emailed my logs last week, but hadn’t received an update from Cato yet, although if I had to guess – we might be experiencing the same issue.
Sorry for the confusion.
That’s where I sent them last week. I intentionally didn’t attach them to the thread. I’ll resend the email shortly.