[Bug]: Herd does not work within a Windows domain controlled environment #601
Comments
|
Hi @aran112000 - looks like you are the first one running it in such an environment and while we tried to mitigate the difficulties, some still seem to be there, so let's work through them step by step:
|
|
Hi @sschlein, Thanks for the quick reply!
TIA
|
|
@aran112000 Is it possible to move the path from the admin user to the user who uses the machine or the system path to see if this resolves the issue? We tried chaining them but unfortunately it didn't work that way – so luckily you don't need TLS for most local connections and even if you do, it's one time setup per site. |
|
@sschlein Moving the path across does help, but it only works as an elevated user else you don't have access to the local admin account's home dir where everything got installed and the path is referencing. When I launch Herd and run it as a local elevated admin, I have to reinstall all of the services and they they cause conflicts because they're also installed on the local domain user's profile. |
|
Ah that makes sense – we'll look into this next week to see how we can install everything into the user account and add everything at the correct place in the first place |
|
From our side (running in a domain-controlled environment), it would make way more sense to install the services and keep their binaries outside of a user's profile directory, which hopefully makes this easier too. The rationale, is by default, all files in a user's home dir get synced back to the DC which can make things VERY slow when there are large amounts stored in there, so anything like this, we'd want outside of a user's profile. This would also remove these problems too between different users having different paths on the same system. Would that work for Herd in other environments too? |
|
I think I am having a similar issue. I'm having an issue anyway! I've installed Herd on Windows 10. Here's what I get from my terminal: My env variables are as follows: System: Let me know if there is anymore info I can add. Thanks |
|
OK, I think my issues may have been caused from using Git Bash instead of Powershell... Could that be the case? Is there a way to be able to use Git Bash in Windows or is Powershell required? |
|
@sschlein Just checking in to see if you had any luck with this last week, we've held off deploying Herd Pro across our teams until this is resolved |
|
Hi @sschlein, can we get an update on this please. We've paid for Heard Pro Teams licences to be able to deploy this and haven't been able to get a single day's use from them given these issues. At the start of April you said you'd be looking into this next week, what happened with this? I can't spot any references in the changelog for the releases that've followed since. |
|
Hey, Can you try this version (#727 (comment)) on one of your machines so that we can gather more data? If we get this to work, we can prorate the time that you haven't been able to use it. If we don't get it working or you don't want to wait, we can do a refund. |
|
Hey @sschlein, I've installed, enabled debug, restarted and get basic logs written, but there's nothing to do with any of the issues in there sadly. The logs below were during a time I was staring services again, trying to add a new site which just instantly says success and doesn't do anything at all (as reported in the other Issue too). The same goes for the main.log: |
sschlein
changed the title
|
I am actually not sure what we're going to do here in the short term. This setup is different from the one that most current users have and messing up all their existing setups to support a different group of users seems wrong to me. I'll have to do some research how other tools handle this situation to find a solution that works for both. There are also multiple levels of problems here: We do have a path and permission problem that we could solve in several ways but mainly move stuff to the users directory and it'll work. This would also keep all existing installs intact – but this still leads to your syncing issue or multi-user machines where the services work against each other. We could probably resolve this step by step and get a working setup by properly installing everything for the user but I'll have to discuss this with the team to make sure we don't break anything for thousands of users who rely on this every day. |
|
Hello, I am having exactly the same situation. Trying to install in a school lab where all the students have your own user managed by a Windows domain. The local folders of users are inside D: partition. In my case, seems like the student can start services but can not access "project.test" local domains. In some machines, got the 5000 port issue so we changed this port after SEVERAL attempts inserting some administrator credential. Is there a way to overcome this? Thank you. Best regards. |
|
I was having issue of npm not found after installing Herd and the following commands worked for me
After this command my npm started working |
|
Just as an addition to the above (and probably related to the way the "paths" and "services" are configured). I ran into trouble when using a computer that was shared with another Herd user. The installations interfere with each other, and at first sight, this scenario doesn't look as though it can be supported. It's not a biggie, but just thought it was worth pointing out. |
|
Same problem here. |
Platform
Windows
Operating system version
Windows 11 Pro - 23H2, Build 22631.3374
System architecture
Windows
Herd Version
1.0.1
PHP Version
No response
Bug description
We purchased a Herd Pro Teams licence to try and migrate more of our team to using local development, however, our users have found many major issues in trying to run Herd in our Windows environment. The most likely cause given there doesn't appear to be open issues reporting any of our issues is that all our users are non-administrator users which are managed inside a Windows domain-managed (syncing with our local domain controller).
Even when running the Herd installer and application with elevated Admin permissions we still get many problems, I'll list what we've discovered so far below but this isn't exhaustive as so much isn't working:
php,herd,composer... commands don't workSteps to reproduce
Install on a Windows user (non-admin) account within a Windows domain-managed environment
Relevant log output
No response
The text was updated successfully, but these errors were encountered: