@tech49 Please make a new thread for the new issue so we can help you there. (since it’s unrelated to the thread)

@Sebastian-Roth said in Fog installation and cofiguration on ubuntu 18.04: You are welcome to open new topics for each question you have. It’s way easier for others having similar or same problems to find the right answer in a short topic instead of half a dozen questions being packed in one thread. thanks, I agree, i will start a seperate thread to update on any progress on this topic.

@processor In this case I’d ask you to update to the latest development version. There is a minor issue with 1.5.7 on Ubuntu and it’s better you use the latest version in case we still need to work on fixing the multicast issue. sudo -i apt-get update apt-get install git git clone https://github.com/FOGProject/fogproject cd fogproject git checkout dev-branch cd bin ./installfog.sh

@lperoma The grep error can be ignored.

@lperoma No I have not tried Acrobat Reader myself. Though I might give you some hints on what to try. First see if there are logging options for the EXE installer. Then you might try to run it in the same context the fog-client is running in. Search the forum for PsExec and SYSTEM account to find information on this.

@Hubi i’m pretty sure there’s references on how to do it on the forums, but here’s how i’ve done it in the advanced menu. it will take just a little modification to put this into the ipxe menu entries instead, but it should give you a pretty good idea of where to start :Win7SP1x64 kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=Win7SP1x64 ftp=${fog-ip} imgType=n imgPartitionType=all osid=5 storage=${fog-ip}:/images/ capone=1 imgfetch init.xz boot || goto MENU

@mpatel said in Windows 10 issues: “WebCacheLock.dat” … “WebCacheV01.dat” Both are related to caching and history mechanisms in IE / Edge and may be safely deleted.

@EduardoTSeoane said in Common WebUI pages takes minutes to load.: Ok, I’m ready to start the test, plz explain me how do you want the, bugs/problems report? Just report here in the forums as you did before. Or if you are keen you could also post an issue on github. Whichever suites you best.

@MHImager If you even see such an behaviour with different models I’d think about something different causing this. Maybe it’s one switch or port or cable or??!?

@Borega Try this file: https://github.com/FOGProject/fog-client/releases/download/0.11.16/Modules_SnapinPack_empty_dirs.dll Should have the fix in it as well.

@Quazz @Sebastian-Roth Thank you, you found the solution ! Here is the result of the tmpoutput.txt file Indeed, the problem came from a problem with the filesystem of my “mother” image. After several chkdsk (I had reboot only once the first time), the expand works well. Thank you guys ! The problem is so solve now.

@UWPVIOLATOR My colleague and I have a PS script that at least checks if the service is running. It exports the results into .csv file. It can at least give you an idea of how many and which ones need fixed. (I sanitized this a bit, so put in your own stuff where needed) ForEach ($Computer in (Get-ADComputer -Filter * -SearchBase "OU=XXXXXXXXXXX,DC=MYDOMAIN,DC=COM")) { $ComputerName = $Computer.Name If (Test-Connection $ComputerName -Count 1 -Quiet) { $FogService = Get-Service -Name FogService -ComputerName $ComputerName -ErrorAction SilentlyContinue If ($FogService) { Write-Output "FOG is running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append} Else {Write-Output "FOG is not running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append }} Else {Write-Output "$ComputerName is Offline" | Out-File C:\Scripts\FOG.csv -Append} } From there, I am pretty sure you can just add affected PC’s to a group in Active Directory and map a GPO to run the following batch script (Note I sanitized a bit, so insert your own stuff where needed): msiexec /q /x "PATH TO FOG CLIENT MSI" msiexec /i "PATH TO FOG CLIENT MSI" /quiet USETRAY="0" HTTPS="0" WEBADDRESS="FOGSERVERIP" WEBROOT="/fog" ROOTLOG="1" net start FOGService

@george1421 Sorry, I wiped the PC. I have a hard deadline to meet to get the old FOG server replaced. The good news is that a fresh install, starting from zero on bare metal with a Debian 10.2 net install* and a git clone of FOG worked with no FOG related problems. I have successfully collected an image from a local PC in the IT Admin Lab and deployed it across the routed network to two ‘volunteer’ PCs. So I apologize again for wasting your time. All I can suggest is that the installer checks if it is being run as a re-installation and posts a warning, and maybe points to some documentation on how to properly do a reinstall. I recognize I’ve incurred some debt here, so I’ll try and post some helpful information for other people. I very much appreciate the FOG project. Thank you for providing such a useful tool. Junior Catherd *Debian 10.2 net install grabs a DHCP address, and persuading the OS later to use a static IP was a little more convoluted than I expected. Similarly, the default install does not include sudo, which is easy enough to remedy.

Knowing that my FOG server is in place, I mounted a drive to a nas in the / etc / fstab file. it does not work … how to deport my storage without reinstalling FOG thanks

@Pablo For your FOG server to get to the internet is a web proxy server required or does the fog server have direct internet access? You can also use a windows computer and download these two files: https://fogproject.org/kernels/Kernel.TomElliott.4.9.4.64 https://fogproject.org/kernels/Kernel.TomElliott.4.9.4.32 After download rename Kernel.TomElliott.4.9.4.64 to bzImage and Kernel.TomElliott.4.9.4.32 to bzImage32 Make sure you use the exact capitalization I used. Then move these files to the FOG server into the /var/www/html/fog/service/ipxe directory.

@FredG said in How to update FOS?: Ok I thought that the development of FOS was independent of the development of the FOG server. Yes, correct. You are on the right track with what you posted so far. We just try to ask because sometimes people head down a road that costs a lot of effort and is not needed. In your case I guess it’s quite a nice idea you look into generating your custom FOS initrds to be able to play with it. Two things I’d mention: Best you use the versions we currently use as well to prevent from possible issues that might just arise when using newer ones that we have not tested yet. Find the version numbers here: https://github.com/FOGProject/fos/blob/master/Jenkinsfile#L12 Be aware there is a much easier way to modify existing FOS initrds: https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image#Version_1.0.0_and_up

@Quazz Thank you for your answer, I did not know that deployed partitions were prorated to captured partitions. It’s clear for me now

@SBrady said: Which is better for Xen VM, guided or guided with LVM? LVM is great if you know Linux well and can handle that complexity. If you don’t it might make things more prone to errors and I’d suggest installing without LVM.

@boomtown said in Interactive PXE Boot setting?: Is it possible to require a key be pressed before the PXE image will boot so that if nothing is pressed the computer will go to the next device in the boot priority? Unless I’m missing something here, this is the default. In the iPXE menu the default menu item is boot to the hard drive. If you don’t touch the keyboard during the timeout period the system will select the default menu item and boot the hard drive. You can change what the default iPXE menu item is, but as shipped from the developers, its the boot to hard drive menu. Now if your target systems are Dells (only system I have) you can use the command and configure utility (i.e. CCTK) to change firmware settings. So you can from a running windows system change the boot order by calling cctk with the proper command line parameters.