@george1421 The Host OS is Unbuntu 16.04.06.

When I log into the system it shows the following:

Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-66-generic x86_64)

• Documentation: https://help.ubuntu.com
• Management: https://landscape.canonical.com
• Support: https://ubuntu.com/advantage

144 packages can be updated.
36 updates are security updates.

New release ‘18.04.2 LTS’ available.
Run ‘do-release-upgrade’ to upgrade to it.

Last login: Mon Sep 23 09:26:54 2019 from 10.2.0.39

Again I am a novice to Linux so I am not sure - will this upgrade me to the latest release of Ubuntu? When I typed in sudo find / -name dnsmasq* it displayed the following:

mike@fog-server:~$ sudo find / -name dnsmasq*
[sudo] password for mike:
find: paths must precede expression: dnsmasq-2.76.tar.gz
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec|time] [path…] [expression]
mike@fog-server:~$

Thanks in advance,

Michael

@Sebastian-Roth Sorry to bother again, I am stepping though the instructions to Compile dnsmasq2.76 but am stalled out on step 6.

It instructs me to “Find this section”
/* #define HAVE_LUASCRIPT /
/ #define HAVE_DBUS /
/ #define HAVE_IDN /
/ #define HAVE_CONNTRACK /
/ #define HAVE_DNSSEC */

When I was initially stepping through this I found it, but did a keyboard combo of sorts and now cannot find it. I got called away to the administration office and when I returned the Putty session expired. I logged back in, started again at step 5 by entering in sudo vi src/config.h and this is what I have:

Last login: Mon Sep 23 07:29:15 2019 from 10.2.0.39
mike@fog-server:~$ sudo vi src/config.h
[sudo] password for mike:

~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
“src/config.h” [New DIRECTORY] 0,0-1 All

I will admit I am a Linux novice - hopefully I didn’t screw this up. I can do a full VM restore if necessary, just looking for advise from this point. I really wish I could negotiate a service contract with FOG whereas I would pay an annual maintenance fee for updates, troubleshooting, etc so I don’t have to bother you fine folks that help the ignorant

Thanks again in advance!

Michael

@Sebastian-Roth

And just like that - the simple change of Option 67 to ipxe.efi, the Fujitsu T939 is imaging!

My version of Linux is Ubuntu 16.04.6.

I was unable to boot my old Fujitsu T938s with this change to the DHCP setting, when I switch it back to undionly.pxe then of course it works. So thank you thus far, now my question is what should I do next keeping in mind I will be upgrading my Domain Controllers in December.

Thanks again!!!

Mike

@Sebastian-Roth As mentioned earlier I am currently running my DNS/DHCP services on a Windows 2008 r2 server. I am upgrading this server during our Christmas break prior to Microsoft’s End Of Life for this OS. So, if I am reading the instructions correctly - they only pertain to Server 2012 r1 and newer. I know it talks about 2008, but regardless I don’t want to bang my head on my desk getting this to work on a DC that will be retired in 3 months.

I don’t want to make a lot of unnecessary changes if waiting for my new DHCP/DNS Domain Controllers are the better option. Currently this is only affecting one machine but always looking ahead as this will be a problem for anyone refreshing their computers who haven’t already modified their environment to support dual boot situations.

@george1421

@george1421

@george1421 When I turn the laptop on and press F12 for boot options, I select Option 1: NETWORK: IPv4. Then I get a black screen that says >Start PXE over IPv4. Press [ESC] to exit…_ then a Warning Boot Failure error comes up with the only option listed is continue which puts me in an infinite loop.

Thank you for the prompt reply. I am currently running my DNS/DHCP services on a Windows 2008 r2 server. I am planning on upgrading this server during our Christmas break prior to Microsoft’s End Of Life for this OS. So, if I am reading the instructions correctly - they only pertain to Server 2012 r1 and newer. I know it talks about 2008, but regardless I don’t want to bang my head on my desk getting this to work on a DC that will be retired in 3 months. Advise from here? Shall I wait until after my upgrade then follow the instructions provided?

Thanks again,

Mike

OK let me start with a bit of history. I have 122 Fujitsu T938 Tablet computers that work fine with Fog (1.5.7.2) after making the following changes to the BIOS:

1. Under Advanced – Boot Configurations – DISABLE FAST BOOT
2. Under Security – Secure Boot Configurations - SECURE BOOT OPTION DISABLED
3. Under Advanced – Boot Configurations – CSM ENABLE

These tablets are no longer available and had to buy a replacement for one that was stolen. Fujitsu sent me a T939 for the replacement. When I go to make the changes in the BIOS I can:

1. Under Advanced – Boot Configurations – DISABLE FAST BOOT
2. Under Security – Secure Boot Configurations - SECURE BOOT OPTION DISABLED

I CANNOT make the change to enable CSM (option not there). I reached out to Fujitsu and they told me they only troubleshoot hardware problems not software. I explained the BIOS is not software specific and that I am trying to network boot this machine to capture an image. The technician on the phone couldn’t grasp the idea that the BIOS is NOT software and refuse to provide help other than “enable PXE boot”. After realizing I was trying to go up river without a paddle I read forum after forum, networked with colleagues in my state (work in education), and nobody has an answer primarily because I am the only one in South Dakota running FOG and the UEFI boot options are so embedded on the newer computers there are few examples currently to work with.

I am looking for any help as I anticipate my next major purchase will see the same challenges I am currently experiencing.

Thanks,

Mike

5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 5/1/2019 12:56 PM Middleware::Response Success
 5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/management/index.php?sub=requestClientInfo&mac=A0:66:10:07:73:ED|7C:76:35:28:66:D0|7C:76:35:28:66:D1|7E:76:35:28:66:D0|7C:76:35:28:66:D4&newService&json
 5/1/2019 12:56 PM Middleware::Response Success
 5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/service/getversion.php?clientver&newService&json
 5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/service/getversion.php?newService&json

 5/1/2019 12:56 PM Service Creating user agent cache
 5/1/2019 12:56 PM Middleware::Response Invalid time
 5/1/2019 12:56 PM Middleware::Response No Printers
 5/1/2019 12:56 PM Middleware::Response Module is disabled globally on the FOG server

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16
 5/1/2019 12:56 PM Client-Info Client OS:      Windows
 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3
 5/1/2019 12:56 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16
 5/1/2019 12:56 PM Client-Info Client OS:      Windows
 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3
 5/1/2019 12:56 PM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16
 5/1/2019 12:56 PM Client-Info Client OS:      Windows
 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3
 5/1/2019 12:56 PM Middleware::Response Success
 5/1/2019 12:56 PM HostnameChanger Checking Hostname
 5/1/2019 12:56 PM HostnameChanger Hostname is correct
 5/1/2019 12:56 PM HostnameChanger Attempting to join domain
 5/1/2019 12:56 PM HostnameChanger Logon failure: unknown username or bad password, code =  1326
------------------------------------------------------------------------------


------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16
 5/1/2019 12:56 PM Client-Info Client OS:      Windows
 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3
 5/1/2019 12:56 PM Middleware::Response No snapins
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16
 5/1/2019 12:56 PM Client-Info Client OS:      Windows
 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3
 5/1/2019 12:56 PM Middleware::Response No Printers
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16
 5/1/2019 12:56 PM Client-Info Client OS:      Windows
 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3
 5/1/2019 12:56 PM Middleware::Response Success
 5/1/2019 12:56 PM PowerManagement Calculating tasks to unschedule
 5/1/2019 12:56 PM PowerManagement Calculating tasks to schedule
------------------------------------------------------------------------------

This year we are using the Smartinstaller instead of the Legacy Client. After imaging the computer will not automatically join the domain. We have used the legacy client in the past and had to copy our config file into Programs Files (x86)\FOG\etc in order to get this to work. This is the first image ever we are attempting to use the new version of the client so I am sure it is something simple I am missing. I also verified that the FOG services are set to delayed automatic start to no avail. Does anyone have ideas or thoughts on what I am missing?

Thanks,

Michael

So we were able to get the Smartinstaller installed without the CA error, but the computer will not automatically join the domain. We have used the legacy client in the past and had to copy our config file into Programs Files (x86)\FOG\etc in order to get this to work. This is the first image ever we are attempting to use the new version of the client so I am sure it is something simple I am missing. I also verified that the FOG services are set to delayed automatic start to no avail. Does anyone have ideas or thoughts on what I am missing?

Thanks,

Michael

@michaeloberg So we were able to get the Smartinstaller installed without the CA error, but the computer will not automatically join the domain. We have used the legacy client in the past and had to copy our config file into Programs Files (x86)\FOG\etc in order to get this to work. This is the first image ever we are attempting to use the new version of the client so I am sure it is something simple I am missing. I also verified that the FOG services are set to delayed automatic start to no avail. Does anyone have ideas or thoughts on what I am missing?

Thanks,

Michael

Alright, got it figured out. When installing the client we have to enter the IP address and leave the webroot as /fog and do NOT enter anything prior to the forward slash.

I am creating my new images and was going to use the SmartInstaller for the FOG client instead of the legacy version this year and after I run the installation wizard on the image it comes up with an error “Unable to install CA Certificate”.

I will be the first to admit I am a novice with FOG so any help would be appreciated. I am running version 1.5.5.3 on an Ubuntu Server.

Thanks in advance!

Michael

@Tom-Elliott Thanks again, I am by no means a Linux expert, I wouldn’t even be considered a novice.

Michael

One other question, sorry So in the GUI I can see several Kernel updates. We won’t be purchasing new computers for 2 more years so is it worthwhile to do these or wait until new product arrives to see if it will PXE? What is best practice for Kernel updates?

Thanks in advance!

Michael

@Tom-Elliott You’re the man! Thanks TOM!

Michael

Good Morning,

Today I checked my fog server in the GUI interface and it stated that I was running version 1.5.4

So I did my normal process of upgrading my server by running the following commands:

sudo apt-get update && apt-get install git
git clone https://github.com/FOGProject/fogproject.git /root/fogproject
cd /root/fogproject
git checkout dev-branch
git pull
cd bin
./installfog.sh

After the installation, it said to navigate to http://IPADDRESS/fog/managment to update my database schema, well I logged into the GUI and didn’t really see any options to update the schema, so I clicked on the wrench to check what version I am on now. I get the follow, first line in Red:

You are not running the most current version of FOG!
You are currently running version: 1.5.5.3
Latest stable version is 1.5.5
Latest svn version is 6078
Latest git version is 1.5.5

So with all of that said is this a bug with the latest version whereas even though I am current the GUI reports the contrary?

Also on a side note, when I tried to type the command “git clone https://github.com/FOGProject/fogproject.git /root/fogproject” i got a error “fatal: destination path ‘/root/fogproject’ already exists and is not an empty directory” to rectify this I had to rm -rf fogproject I don’t recall ever having to do that in the past but seemed to work.

I just tested the server and was able to pull images down without issue, should this be something to worry about as I only store about 2 weeks of backups?

Thanks,

Michael

Thanks everyone, I upgraded to the newest version of Fog, and had to do the following and now it works:

Windows 8.0, 8.1, and 10 (and most likely future Windows versions) have a feature called “Fast Startup”. This feature basically sets windows so that a hibernation occurs whenever the system is shutting down. This enables Windows to startup much faster than in past Windows versions. Because this feature is on by default, the windows OS partition has a hibernation file which prevents mounting and imaging via FOG, and also marks the OS partition’s “Dirty Bit” to ON. Even when hibernation and fast startup is disabled, the hibernation file remains and the “Dirty Bit” remains ON and these things causes problems. There are a few ways to fix/get around this.

Way 1 (clean method)
Disable: “Turn on fast startup”, located here: Control Panel (Classic View) -> Power Options -> Choose what the power button does -> Change Settings that are currently unavailable -> “Turn On Fast Startup & Hibernate”

Both of those settings should be turned off for use with FOG. They may be turned on at a later time via GPO or snapins.

Shutdown and then boot the system.

Then run this command from an elevated command prompt to disable hibernation and remove the hibernation file:

powercfg.exe /H off

Now you can shut down and reboot once or twice, and then capture your image via FOG.