Perhaps you have the admin share disabled in your environment.

Super thanks a lot for the reactivity

Hello,

I just tested setting the policy trigger to “login” and can confirm the script now runs in the context of the signed-in user—works perfectly on my end.

Being able to reference Custom Attributes as argument would be an extremely handy.

Thanks again to you for building and actively improving such a solid tool!

Just create a new policy,set the completed action to reboot, set the trigger to once per week, set the day of the week, and set frequency missed action to scheduleday only, then apply policy to groups you wan to reboot.

To restart toec, just create a script module with
net stop toec
net start toec

Assign it to a policy to run.

@theopenem_admin I believe that fixed the issue. I stopped the proxy DHCP service, removed option 60 from the DHCP server, and switched off proxy DHCP in the settings page and set it to ipxe 64-bit. My old device is now loading! I would test the new HP 440 device, but we had to send it off. I'll have to test that device later, but I'm confident it will work now. Thanks for all the help!

@theopenem_admin Thank you for clarification. Will look into it.

Thanks, I was trying to replicate this and was unable to, I'll update to latest security updates and try again.

It means you have a duplicate computer name or install ID, or that computer needed to re-provision for some reason. Just apply that reset request and if it goes away you are good, if it then knocks off a different computer then those 2 computers are somehow duplicated.

Please Help Me, I Can't

@theopenem_admin

Good morning, tested and works ok. We have found only one ‘anomaly’. When you boot the computer with a dock or NIC via USB, ipxe boots without problems but when it loads the kernel it only tries to assign IP via DHCP on eth0, which in case the computer has an internal NIC, causes it to retry several times without success. If the machine has only one NIC, it works without any problems. Thanks for the quick solution. I hope it will help to fix this problem in future kernel versions.

Best regards.

These are the 3 intel rst drivers that most people need for dell drive detection in RAID.

https://www.intel.com/content/www/us/en/download/720755/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-11th-up-to-13th-gen-platforms.html

https://www.intel.com/content/www/us/en/download/19512/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-10th-and-11th-gen-platforms.html

https://www.intel.com/content/www/us/en/download/19755/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-8th-and-9th-gen-platforms.html

There is also one newer one 20.1 I think, it's hard to track down.

@theopenem_admin Ah no problem - Thanks!