Hi folks,
I am new to the forum but I had a question for you.
I installed on all our machines an image of Win 11 with Node-Red on board, this machine was not in domain and so following the directions from the site I installed everything under the user profile which we will call User1.
Unfortunately on the machines where I installed the Win11 image they don't have the correct pointing to the node-red.bat file because it doesn't know where to look for it.
How can I make it possible for User2 to launch the node-red.bat file by reading the original installation folder?
I can see that I can change the variables but even putting them under System by running the Node-Red command on Cortana it goes to error.
I don't understand.
Where did you obtain an image of WIndows with Node-red already installed?
Is Node-red on one PC or several?
If several, why? Do you want everyone to have their own discrete installation?
Why do you want User2 to launch Node-red?
Isn't it better for it to run automatically when the machine boots up?
The way to do that is (briefly) described on the page you linked to, using either PM2 or Task Scheduler.
The image is from a Sysprem on a test machine with all the educational SWs needed.
I installed all the SWs under a non-domain account called User.
The app is installed on all machine because every student need to have his istance.
I need User2 to access the app because is the domain user that the students log in with.
I will look at the end of the page that i didn't see it at all.
Do you know how can i do this via Group Policy from my server?
AD GPO's isn't something that will be covered here much (if at all)
It sounds to me - you have installed Node RED under a local account, but needs accessing by AD Users.
My suggestion is this.
Install Node RED, to a directory that can be accessed by all users C:/Users/Public/NodeREDApp
As part of your sys prepped image, add a shortcut to the cmd file that starts node red to C:/Users/Public/Desktop (seen by all users)
When students starts it up (shortcut will appear on their desktop) - it will start up their instance of Node RED - it Creates C:/users/<Logged-In-user>/.node-red for them
In Node RED, the installed location, is different from the working directory when its running