Indeed, it’ll make the job.
Btw, i was trying to avoid to use a username and his password in the script.
Not sure there’s an another solution ;(.
Hello Tom, thank you for your answer.
In fact, i want to be able to restore a client computer, join the domain and deploy an antivirus software which is located on a remote smb share.
By default on a windows client, fog’s service is running under the local user HOSTNAME\System and Fog server got the configuration needed to join this computer on the domain (with DOMAIN\my_user account).
Restore and joinning the domain are working fine, but unfortunately, it seems that fog service account (HOSTNAME\System) on the client computer is used to access to the remote samba share which is managed by a Ldap authentification process.
Thus, the snapin fails cause samba is rejecting the authentification.
i’ve got a question about fog client account:
everything is working very well by default (ie, clone, restore, join the domain, local snapin etc).
But … if i make a snapin who need to access to a network share (samba in our case), fog client need to use a domain account to access to the files.
If i update fog user account’s service under windows with a domain admin account, everything is working.
Unfortunately, if i make a new image with theses settings (fog client user modification), the computer is not able to join the domain anymore (seems logic cause fog client is trying to run with an unknown user).
Is there a workaround for this ?