@ConJon Yes that is already part of the scripts at the link provided in a previous post below. I’ll link it again here: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed
Its covered in the fog.updateunattend script section. You will probably want to remove the non-value added parts of that script like connecting to AD and such.
@jameto333 said in SketchUp 2017 snap-in:
SketchUp 2017
It looks like you picked a hard application to deploy in an unattended manner (with any deployment tool including FOG).
I found several examples here:
https://community.spiceworks.com/topic/863861-sketchup-2015-silent-install
https://www.manageengine.com/products/desktop-central/software-installation/silent_install_SketchUp-Make-2017-(x64).html
I would probably follow the manage engine path and use the provided vbs file. You will then with FOG need to create a snapin pack (zip file) with all of the files you need to deliver to the target computer during imaging.
The fog snapin pack wiki page is pretty good: https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks
@Technolust said in New Fog Server - /images location:
I setup samba on both servers so I can do in GUI or I can scp the files…
How very windows-ick way of thinking. On both the source and destination servers the /images directories are shared via NFS. No need for samba, just mount the remote nfs share.
I’m just messing with you, do what ever you need to get the job done. If samba was your answer and it did what you needed, it was the perfect fit.
@Technolust Remember (or know) that with FOG there are 2 parts to the image.
You can rsync the files over, but you will need to create the metadata by going in and manually create a new image definition in the new FOG server. Create it manually by copy and pasting from the source FOG server. I would say export and import but I don’t know the impact of changing the /images directory when you import. Its just easy enough to copy and paste between the two servers.
Just call up the old server and the image definition and then create a new server definition on the new server and copy between.
@Technolust Ah the fog prerequisites were not met. OK, good you had that bit figured out as well as the permissions.
So are you 100% good now?
@Technolust Does the IP address in the default storage node configuration point to the right IP address?
I would do a test capture to ensure the image capture process completes correctly. If it does then do a deploy back to the same computer. If both work then we’ll bring the devs in to see if there is something “under the hood” wrong.
@Technolust said in New Fog Server - /images location:
touch /fogserver/dev/images/.mntcheck
Ok looks like /fogserver/dev/images doesn’t exist. Is this supposed to be /fogserver/images/dev?
OK its time for either another cup of coffee or for me to just go back to bed. The path /fogserver/dev/images is of course wrong. I should have typed /fogserver/images/dev
It looks like you have the check file in the proper paths from your ls command. But after a reboot your storage node is still showing off-line?
@Gamienator Thank you for the feedback and info, I will get the tutoral updated right away.
@Technolust I don’t have a clue about the storage node on the home screen. But from your ls command you are missing 2 check files. If you run ls -la on the old /images directory you will see a file called .mntcheck and the second one of the same name needs to be in /images/dev. Those will need to be recreated in your new location paths. You can simply do:
touch /fogserver/images/.mntcheck
and
touch /fogserver/dev/images/.mntcheck
its ok if they are already there, that touch command will just update the last time the file was access, or create it if it wasn’t there.
@Technolust What does the content of the default storage node look like?
Also did you reboot the fog server after you made all of those changes? Some values are only loaded at boot time.