Posts made by astrugatch

@altitudehack

Right, I upload a .bat and use the batch snap-in template

@george1421

If the system is already bound to AD and the share is on an AD bound system it should still work. I push AutoCAD this way for one-offs (as a snapin). Just a UNC path with no net use.

IF EXIST "C:\Program Files\Autodesk\Revit 2020" goto _End
"\\SHARE\GPO Installs\Revit2020\Img\Setup.exe" /W /q /I \\SHARE\GPO Installs\Revit2020\Img\REVIT2020.ini /language en-us
:_End

FOG is agnostic to the difference. You could go pata spinning disk to sata ssd and it won’t matter as long as FOS can boot on your system and see the drives, and as long as the OS has the drivers for the system, or they are available to it.

@altitudehack

The Share is read/change for everyone, but NTFS permissions is only read and execute for everyone.

Mind you I have the script in my snapins, but I usually use it as part of group policy and its a startup script with logic to look for an existing install.

The way I do it, is that the script goes into FOG but the install files live on a different share that I can call from a UNC path. so the guts to my script are:

\\installersshare\office\setup.exe /configure \\installersshare\office\config.xml

Do you have the access control plugin installed?

@Sebastian-Roth

I can safely assume my devices are all running the latest version so I created a group policy to replace the settings.json with a fixed copy on a network share. Which is fine for what I need and I will just update my base images to reflect the correct setting.

Thanks for the help

@Sebastian-Roth

Is there a way to report on the client version that my currently deployed machines are running? I can push a new settings.json with group policy but I don’t want to have incorrect settings within it and I can’t guarantee that all my users have the same version.

Recently moved to using HTTPS and now clients with both existing and newly installed fogclient are not communicating with the server. If I install the client on a new machine it does not show up as a pending host in fog server. Running 1.5.6.4 dev build.

Do I need to specify HTTPS in the fog URL in the installer?

@george1421

I’m calling it spam. Especially with that oddly spaced URL at the bottom. Flagged for your consideration.

@Sebastian-Roth

Full rebuild on dev-branch works.

Thanks for looking into this so deeply!

@Sebastian-Roth

Still getting errors on iPXE with the new build

(note to anyone with this issue, I only did a buildipxe.sh on dev-branch and that didnt work, a full reinstall on dev-branch fixed it)

@Sebastian-Roth

Gotta go pick up my kids. I’ll take another swing at this tomorrow.

https://isimagingdead.com/

If you are managing Macs I would highly recommend moving away from Imaging as that is NOT the workflow going forward. Invest in DEP+MDM and netinstalls / internet recovery + Caching.

@Sebastian-Roth

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.6 LTS
Release:	16.04
Codename:	xenial```

@Sebastian-Roth said in PXE boot failed 1.5.6:

echo $SHELL && lsb_release

/bin/bash
No LSB modules are available.

@Sebastian-Roth Install 156 error log.log

@Sebastian-Roth said in PXE boot failed 1.5.6:

ls -al ~/trunk/bin/error_logs/

root@fogimaging:~/trunk# ls -al ~/trunk/bin/error_logs/
total 516
drwxr-xr-x 2 root root 4096 May 3 20:20 .
drwxr-xr-x 5 root root 4096 May 3 20:12 …
-rw-r–r-- 1 root root 45530 Mar 1 2018 fog_error_1.5.0.log
-rw-r–r-- 1 root root 37941 Nov 13 2017 fog_error_1.5.0-RC-10.log
-rw-r–r-- 1 root root 41473 Jan 26 2018 fog_error_1.5.0-RC-11.log
-rw-r–r-- 1 root root 58 Feb 15 2018 fog_error_1.5.0-RC-12.log
-rw-r–r-- 1 root root 39477 Feb 15 2018 fog_error_1.5.0-RC-13.log
-rw-r–r-- 1 root root 41019 Apr 25 2018 fog_error_1.5.2.11.log
-rw-r–r-- 1 root root 42209 Apr 11 2018 fog_error_1.5.2.log
-rw-r–r-- 1 root root 41937 May 30 2018 fog_error_1.5.3.log
-rw-r–r-- 1 root root 43541 Aug 13 2018 fog_error_1.5.4.log
-rw-r–r-- 1 root root 45401 Nov 20 2018 fog_error_1.5.5.log
-rw-r–r-- 1 root root 64951 Jun 19 08:40 fog_error_1.5.6.log
-rw-r–r-- 1 root root 15208 Jun 19 08:32 foginstall.log
root@fogimaging:~/trunk#

@Sebastian-Roth

Its odd because I’ve re-run the 1.5.6 installer recently too which from what I understand also runs the build.