@Daniel-Miller it was indeed some permission issue coming from the application. I will try to manually reset it and see if it works. Thanks a lot for your help!

@Sebastian-Roth thanks, I’ll take a look!

@Daniel-Miller
Thanks for such a quick reply!

1. Yes, there is a proxy on both server and client. Fixed this one now!
2. Script is trying to set environmental variables using [Environment]::SetEnvironmentVariable Method for “Process”, “User” and “Machines”. I see, so there is no way I can set it at the machine using snapins?
3. Script is using New-ItemProperty method in powershell. I forgot to mention that it succeeds in setting values in HKLM:\SYSTEM (but not HKLM:\SOFTWARE).

I am mainly using powershell scripts and some batch scripts that trigger other powershell scripts. It is run on Windows 10.

Hello everyone,

I am trying to use Snapins to execute some scripts on the client machine and I am running into following issues:

1. One of the scripts should be downloading some files from web, but it complains that “remote name cannot be resolved”, even though I can access it from both client machine and FOG server. So my question would be: is it more likely to be an issue with my script, or do snapins in general lack functionality of accessing web?

2. Other script that I am triggering with snapins is supposed to be setting environmental variables, but it doesn’t. I am guessing it is because snapins are run from SYSTEM user account? Is there any work around you could recommend? I’ve tried using runAs, but it freezes because of prompts for password (the account on client machine does not have any password), so only way would be to disable a UAC, which I would rather avoid doing.

3. Last script should be accessing HKLM/SOFTWARE and setting values there, but it cannot. Again, I’m guessing it is because of the SYSTEM account?

I apologize if those questions are trivial or have been asked before(though I could not find anything similar on the forum).
Thanks!

@george1421 Thanks for quick response!
What I need is for some of the powershell scripts to execute on the host machines after the deployment. They are quite complex and Windows specific, so it is not desired to convert them into bash scripts.
I was actually reading through this forum and somewhere it was written that Snapins associated with the host get executed after deployment (I initially thought they were just sent, but not executed). Could you please confirm that this is correct? I tested on one machine and it looks correct, but I would feel safer if you could confirm.
If so, my problem would be solved by using snapins!

Hello everyone,
I am new to FOG and imaging in general, so any help would be appreciated!

I am getting familiar with post download scripts through this article: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script
and I was wondering if it would be possible to execute a Powershell script on a target machine using post download scripts?
Or would it be possible to trigger a Snap-in (that is pretty much that same powershell script) using post download scripts?

Thanks!