mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #370] Suggestion of wiki page about windows service #297
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#297
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JmirY on GitHub (Jul 24, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/370
Suggestion
I want to append some contents to wiki.
The comment below would be helpful for someone gets 'ipc connection error' on Windows.
Sorry for my bad English🤦♂️
It would be great someone polish some sentences.
@JmirY commented on GitHub (Jul 24, 2019):
barrierd.exemust run in background so as to barrier work properly.To ahceive this.
barrierd.exehas to be registered in Windows Service.Run command prompt in admin and input as below
Use
net startcommand to execute registered service@shymega commented on GitHub (Aug 14, 2019):
That sounds like a good addition. I'm reopening this issue so we can add this to the wiki 😄
@bobpaul commented on GitHub (Jan 21, 2020):
Some comments/questions:
I installed via the chocolatey repo and my barrier is already running as a service. Is this standard now for barrier installs or is this something that the chocolatey package maintainers are adding?
I wasn't able to use barrier to type my password at the login screen nor click UAC prompts. This was annoying. I fixed this (mostly) via Services -> Barrier -> Log On -> Log on as: "Local System account" + "Allow service to interact with desktop."

After 2, I'm now able to click UAC prompts and enter my password at the Windows Login screen on Windows clients. The mouse does exit the screen (and jump back to the server) when a UAC prompt appears and it takes a second or two before I'm able to move the mouse back onto the Windows machine's screen, but it does work and I'm no longer reaching for the other keyboard.
@eliumoraes commented on GitHub (Mar 23, 2020):
It worked after i did this. You should add this part to the wiki.