@palehbt Fixed it. Turn off "console Tasks require login" in Admin -> security

@tgilpin Did you ever figure this out?

I finally got the LIE boot to hit my server (was trying WIE, but for some reason can't get the NIC driver to load, even side loading the .ini), and am now getting this.

When I try to hit my server at ip:8888 (same as the LIE environment), I get an Apache looking 403 screen as well.

But I'm currently going to Toems Local Storage, so I don't have the SMB complication.

Asking here as you seem to be the only kindered soul so far.

It says it ran, but the file wasn't added to the target.
{
"Name": "Ignition Backup Deploy",
"Guid": "",
"Hash": null,
"Id": 2,
"Frequency": 0,
"Trigger": 2,
"SubFrequency": 0,
"StartDate": "2023-06-21T04:00:00",
"CompletedAction": 0,
"RemoveInstallCache": true,
"ExecutionType": 0,
"ErrorAction": 0,
"IsInventory": 1,
"RemoteAccess": 0,
"IsLoginTracker": false,
"IsApplicationMonitor": false,
"JoinDomain": false,
"DomainOU": null,
"ImagePrepCleanup": false,
"Order": 0,
"FrequencyMissedAction": 0,
"LogLevel": 0,
"ReRunExisting": false,
"SkipServerResult": false,
"StartWindowScheduleId": -1,
"EndWindowScheduleId": -1,
"CommandModules": [],
"FileCopyModules": [
{
"Guid": "",
"DisplayName": "Ignition Backup Deploy",
"Destination": "C:\Users\Critical\Downloads",
"Order": 0,
"Unzip": false,
"Overwrite": true,
"Files": [
{
"FileName": "",
"FileHash": ""
}
],
"ConditionFailedAction": 0,
"ConditionNextOrder": 0,
"Condition": {
"Guid": null,
"DisplayName": null,
"Arguments": null,
"Timeout": 0,
"RedirectOutput": false,
"RedirectError": false,
"ScriptType": 0,
"SuccessCodes": [],
"WorkingDirectory": null,
"RunAs": ""
}
}
],
"PrinterModules": [],
"ScriptModules": [],
"SoftwareModules": [],
"WuModules": [],
"MessageModules": [],
"WinPeModules": [],
"WuType": 0,
"PolicyComCondition": 0,
"ConditionFailedAction": 0,
"Condition": {
"Guid": null,
"DisplayName": null,
"Arguments": null,
"Timeout": 0,
"RedirectOutput": false,
"RedirectError": false,
"ScriptType": 0,
"SuccessCodes": [],
"WorkingDirectory": null,
"RunAs": ""
}
}

I tried both an EXE, and a VPN config file, just to have a file to load. The file is uploaded to TOEMs. I blanked out the GUID/File name, but they seem to match the configured data fields. IE the GUID's look right, and the file name is correct.

@palehbt I really need to slow down. I see the "destination", which I assume is the target location on the client.

@theopenem_admin I guess I was a little wordy. Basically, can the file copy module target a specific folder on the client machine?

I see most of the rest of my ask is covered, just not the way I was thinking.

Other thing would just be, is there a way I can set up an IFTTT style command to trigger a policy? IE it might not be a "once per x hours/days" kind of thing. Some days I could need this to trigger every 2 hours across a shift, and others I may not need it at all.

Is there a way (only found this software yesterday) to push non-executable files to remote clients?

My goal with this ask is to be able to push project files from our Ignition lab server to our on site temp server(s) as we develop them so the site team can test them as we develop, and not have to develop ON the on site hardware/over a VPN. So ideally, I would have it monitor a folder on the lab server, and if it sees a file, it pushes it to the temp server, and triggers a script on the on site server to "load" the backup, and restart the gateway.

Right now our process to deploy the next revision to a temp server is very slow, and awkward, as one of us in the office has to connect remotely to the on site hardware, and manually swap out the file, so we don't do it very often, and the site team gets annoyed, and complains a lot.

@dangbird I tried this, and it helped, but it isn't the fix for the problem. Especially if the process is bugged, and doesn't complete properly. (IE I did this today, and my setup wasn't correct, so the process died, leaving me stuck with this, as it's handled by some deep level process I can't figure out.)

My machine isn't on a group policy/org policy, as I'm setting up Toem for some machines that leave our org as temp servers on client sites.

@theopenem_admin I admit, I'm new to this side of the world. I'm good with desktop stuff, but getting into the server world is new. I'm a PLC programmer.

When you say "enable the is driver box", is that something that comes up when I load the file into the driver wizard? I have added a file copy module already, as I saw something saying I should have it for the golden image at least.

EDIT: I see the "is driver" now.

I am trying to setup Toem to help us maintain a couple NUCS we send out in the field (IE one golden at the office we keep clean, clear, and up to date, and the rest go out as needed to do various jobs as temp servers until our customers deploy their real server, then wiped, and reimaged). I have collected inventory on the "golden" server, generated a WIM, set up PXE. The Nuc (it's an intel 12th gen i5 nuc) in the PXE environment gets to the part where it pings Toem (in the same network), but the NUC registers NO network connections, other than one that is like a virtual fallback or something. I got pissed off, and needed to get a NUC ready for deployment, so went the old school way of just imaging the SSD, and updating the name/windows license/whatnot by hand.

I'm pretty sure I managed to get everything configured right, at least by the second pass, but the NUC still sees nothing. I tried just doing a PXE boot from bios (configured BIOS to allow for PXE booting, and it seems to work, but PXE still fails to find the NIC after the black screen with a MAC address) I am using hardline, as I didn't want to screw with Wifi, and I know WiFi would be a bad idea for this. It's an Intel 225 ethernet driver, do I need to do this through the "additional drivers" thing?