Posts made by michael_f

@Wayne-Workman Thank you for clarifying this for me!

@Jbob That would mean, i could securly put my arguments here:

and in the script I connect my share like

net use \\share\folder  /user:%1 %2 

That would be a great feature!

@ITSolutions I am using network shares too, and agree with you that deleting the connection at the end and using a restricted account is a quite good idea.

But I still can’t see the security risk in putting the credentials in the script:
The script is stored on the fog server, which should be secure.
It is afaik sent to the client encrypted if using the new fog client.
On the client-side the script is executed with system-privileges, so an eventually logged in user can’t access the script? Or is the script saved readable in a temporary file?
If the credentials are sent encrypted to the server by the “net use”-command (which I assume), how can somebody get access to the credentials?

Maybe I got something wrong? I would really apreciate, if someone could clarify this.

@ITSolutions said in Snapin script interrupted by Hostname Changer before completion (I think):

… my other example of passing credentials over a snap in is not the best security practice by any means.

@ITSolutions Thats interesting, could you please elaborate on this a bit? Does the “net use”-command send passwords in plain text?

@Wayne-Workman Good to know that the new client works smoother.
I just upgraded to trunk a few days ago and didn’t have the time to test yet.

@fry_p In this case you could try Double Driver: http://boozet.org/dd.htm
You install the driver on a computer (not your master) and save the driver with DD on a usb-drive.
Afterwords you restore the driver on your master.
DD saves the driver in a way, that windows can install it via inf-file.
By restoring the driver you define a destination, where the driver-files are being stored. DD adds the path to registry so that windows can find it.

I agree with @Wayne-Workman , meanwhile you could use setupcomplete.cmd as a workaround.
Do the following steps:

• Before Sysprepping disable Fogservice as described here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

• Create a file setupcomplete.cmd in C:\Windows\Setup\scripts and put your code inside

• Add the lines
  sc config FOGService start= auto
  net start FOGService
  after your code

setupcomplete.cmd is called by windows after setup is finished. As the fogservice is disabled, it can’t interrupt your script.
The last two lines enable and start the service.

@Wayne-Workman setupcomlete.cmd has to be placed under C:\Windows\Setup\scripts in the master system.
As the name indicates, the script is called by windows just after setup has finished.

Btw. l set the Fog service to delayed start, ie I put
sc config FOGService start= delayed-auto
into the script.
I don’t know, if this is really necessary with the new fogclient, but it doesn’t harm.
Reason for this is i’ve got some computers which require delayed start with the legacy client (afair network doesn’t come up fast enough)

@Wayne-Workman OK, I thought about installing the fog client after imaging by calling the msi-package from setupcomplete.bat, but this way is even easier.

I can confirm this working for me.

Thank you!

@zpoling I think I ran into the same problem:
As I move fog to a new server I took the chance to upgrade Fog from 1.2 to trunk.

With Fogserver 1.2 I used to install the legacy fog client in the image which worked without problems.

The new fog client, at least v0.10.6 seams to break windows setup. Uninstalling the client in the image solved the problem with the windows setup for me.

@Tom-Elliott Thank you!

Hello,

i have got a similar problem. When I try to add a new snapin i get the following PHP-Error:
Fatal error: Call to a member function save() on null in /var/www/fog/lib/pages/snapinmanagementpage.class.php on line 161.

As i am moving to a new server, i did a fresh installation from svn on ubuntu server 14.04, FOG version ist 7575.
Importing clients and pushing / pulling an image is working.