problem with running basic snapins

Server

FOG Version: 1.3.0 SVN Revision: 6050

OS: Debian 8

Client

Service Version: 0.11.7

OS: Windows 7 SP1

Description

Hellow. I’m using FOG since 2014 and still have a problem with creating snapins. In my enviroment, my windows machines all works with single user, no domain, and user have admin rights. Its student@1. We are using them in classes and security is not and don’t care about security. So, i have some tasks that i need to execute after image deployment, throught snapins.
For example, i need to add login and password for single host in credentials store on single computer.
I’ve made a cmd-file with “cmdkey /add:HOSTADDRESS /user:LOGIN /pass:PASSWORD” inside it. When i run this file localy from target computer, it works fine and adds credentials. But, when i make a snapin, it does nothing.

I have the same issue with creating shortcuts on desktop with either vbs or ps scripts. Scripts works perfectly and creates shortcut. It creates a shortcut on network share. When i ran them localy, everything works as intended, but when i run them throgh snapins, it creates the shortcut, but after clicking on it, nothing happens. I just cannot enter that folder.
I’ve checked properties of the shortcut and they are the same as the normal one. Security permissions also looks the same.
And i can go on on this. Almost all snapins that make simple staff, have the same issue. For example, i have 2 or 3 different scripts that changes desktop wallpaper. All of them works perfectly when ran manually from the machine, but changes nothing when ran through snapins.
On the other hand, vbs-script to turn on WoL, work fine. Windows and Office activation scripts also works fine.

Can somebody help me, please?

Server

FOG Version:

OS:

Client

Service Version:

OS:

Description

Server

FOG Version: 1.3.0

OS: Debian 8

Client

Service Version: 11.7

OS: Windows 7

Description

Hellow. I’m using FOG since 2014 and still have a problem with creating snapins. In my enviroment, my windows machines all works with single user, no domain, and user have admin rights. Its student@1. We are using them in classes and security is not and don’t care about security. So, i have some tasks that i need to execute after image deployment, throught snapins.
For example, i need to add login and password for single host in credentials store on single computer.
I’ve made a cmd-file with “cmdkey /add:HOSTADDRESS /user:LOGIN /pass:PASSWORD” inside it. When i run this file localy from target computer, it works fine and adds credentials. But, when i make a snapin, it does nothing.

I have the same issue with creating shortcuts on desktop with either vbs or ps scripts. Scripts works perfectly and creates shortcut. It creates a shortcut on network share. When i ran them localy, everything works as intended, but when i run them throgh snapins, it creates the shortcut, but after clicking on it, nothing happens. I just cannot enter that folder.
I’ve checked properties of the shortcut and they are the same as the normal one. Security permissions also looks the same.
And i can go on on this. Almost all snapins that make simple staff, have the same issue. For example, i have 2 or 3 different scripts that changes desktop wallpaper. All of them works perfectly when ran manually from the machine, but changes nothing when ran through snapins.
On the other hand, vbs-script to turn on WoL, work fine. Windows and Office activation scripts also works fine.

but when i run them throgh snapins, it creates the shortcut, but after clicking on it, nothing happens. I just cannot enter that folder.

Right click on it, go to the security tab, click advanced. There should be a place to take ownership of the file. Do this and see if it lets you into the shortcut or not. If it does, you’ll also have to have the script set permissions on the files it places.