Is there an existing issue for this?
Describe the issue
Trying to execute a startup script with ADsys, but get the error of "Can't apply scripts policy: can't save assets to /run/adsys/machine/scripts/scripts: no assets attached". I have created a script and a GPT.ini file and placed it in SYSVOL\ubuntu\scripts. Wanted to know if anyone knows the fix to this error?
Steps to reproduce it
Place script and GPT.ini in SYSVOL\ubuntu\scripts directory. Enable the GPO while calling out the script then ran a policy refresh on the linux machine.
Ubuntu users: System information
No response
Non Ubuntu users: System information
Environment
- adsys version: please run
adsysctl version
- Distribution: (NAME in
/etc/os-release)
- Distribution version: (VERSION_ID on
/etc/os-release):
Log files
Please redact/remove sensitive information:
adsys service logs can be acquired by running `adsysctl service cat -v`.
You can increase the amount of information displayed by increasing the verbosity level (-v) to -vv or -vvv.
Application settings
Please redact/remove sensitive information:
Paste the contents of your adsys.yaml file here, if you created one.
Additional information
No response
Double check your logs
Is there an existing issue for this?
Describe the issue
Trying to execute a startup script with ADsys, but get the error of "Can't apply scripts policy: can't save assets to /run/adsys/machine/scripts/scripts: no assets attached". I have created a script and a GPT.ini file and placed it in SYSVOL\ubuntu\scripts. Wanted to know if anyone knows the fix to this error?
Steps to reproduce it
Place script and GPT.ini in SYSVOL\ubuntu\scripts directory. Enable the GPO while calling out the script then ran a policy refresh on the linux machine.
Ubuntu users: System information
No response
Non Ubuntu users: System information
Environment
adsysctl version/etc/os-release)/etc/os-release):Log files
Please redact/remove sensitive information:
Application settings
Please redact/remove sensitive information:
Additional information
No response
Double check your logs