Best posts made by ITSolutions

@Connie You need to re-upload the picture. It must not have worked correctly

When you unplug the network cable to move it over to the new network you will need to restart the DHCP service
sudo service isc-dhcp-server restart

Or just restart the machine, when you get it moved off the “live” network to it’s segregated network location.

@CDown Did you perform an upgrade to 14.04 and install FOG 1.2 over .32 or did you do a complete wipe of the old 12.04/FOG .32 and start fresh?

@CDown That maybe your problem there. As both Ubuntu and FOG have changed so much between the versions in question it is hard to start tot troubleshoot. Especially if this is a new install with no data to worry about I would recommend wiping and starting fresh.

While you are at it I would also recommend installing the trunk of FOG as it is very stable and is better supported now and in the future. I have been using trunk for nearly a year now and I know many others have been for at least as long. It will also be more compatible with newer hardware as it is released. Not to mention the great new features that have been added to trunk.

This sounds to me like it is a self-extracting exe and that it kicks off an MSI after the exe finishes extracting. So the script waits, but when the exe is done it continues. The problem is that the MSI, the actual driver install is still running. You maybe able to use 7zip and extract the exe and then find the MSI installer and run it silently instead. I have had to do that for many driver installs.

@michael_f gave a good suggestion if you don’t need anything more than the drive itself, but if you need the Nvidia software also then my suggestion maybe a better option. I know some video cards are picky if they don’t have their entire package installed.

@Wayne-Workman I am not in the business to hack FOG either. But as I work in healthcare and we are a small shop one of my many hats is security, with PHI concerns I think about all possible attack surfaces. We have regular audits of our security and have to justify any thing that is of questionable nature. Right now I am working on closing up a few other areas, and I have been thinking of ways to harden software deployment through snapins. Currently we have a separate vlan for FOG and only deploy snapins at time of imaging, then remove the log and use the client just for user tracking and rebooting basically. I will push small single file snapins, if I need to, but nothing that needs to connect to a share due to not having a good way to do so. I love FOG and it works great, just like to include my thoughts on things to help further FOG and keep it as secure as possible along the way.

FOG 2.0 will be a huge advancement again I am sure. Just like 1.3 is truly leaps and bounds better than .3x was. I thought .3x was great, but the issues were definitely addressed. With all software there is always compromises to maintain backwards compatibility for longer than any @Developers would really want to do. In my opinion 1.3 is not just a decimal increment to 1.2, it is much closer to a 2.0 version. But with the true 2.0 they can finally drop support for the legacy client, partimage, and it sounds like move away from PHP. It will definitely be a more robust and modern system.

@Sebastian-Roth I am not saying that you cannot upgrade from 1.2 to trunk. I just have seen it break things, mostly on Ubuntu, which is not surprising due to them changing everything in each major revision. That is who your thinking about changing the web root in 14.04. In this case the OP is using Ubuntu. In my opinion it is rather painless to back up the DB and images(granted that is if you have a location to hold them all) and then do a ground up rebuild of trunk. I also usually advise using a separate drive/partition for the images, so that would mostly rule out the need for baking up the images. I guess it all depends on what your preference is or what is possible in your environment.

@phil_guy We need you to upload the actual file, so that it can be examined and find why the partition is not expanding.

I just migrated to a new FOG server and am having issues with snapins. It could be something I missed but I can’t seem to figure out what I missed.

I am running Ubuntu 14.04 fully updated
FOG Trunk 7945, which is up to data as of this writing
Win 7 with 0.10.6 client

I used the .fogsettings from my old server (which was also on 7945)to install FOG. I moved my /opt folder and my /images to the new server.

The client will image and join to AD, user tracker seems to work also. When it goes to run snapins I get the following log

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 5/31/2016 4:44 PM Client-Info Client Version: 0.10.6
 5/31/2016 4:44 PM Client-Info Client OS:      Windows
 5/31/2016 4:44 PM Client-Info Server Version: 7945
 5/31/2016 4:44 PM Middleware::Response Success
 5/31/2016 4:44 PM SnapinClient Snapin Found:
 5/31/2016 4:44 PM SnapinClient     ID: -1
 5/31/2016 4:44 PM SnapinClient     RunWith: 
 5/31/2016 4:44 PM SnapinClient     RunWithArgs: 
 5/31/2016 4:44 PM SnapinClient     Name: 
 5/31/2016 4:44 PM SnapinClient     File: 
 5/31/2016 4:44 PM SnapinClient     Created: -1
 5/31/2016 4:44 PM SnapinClient     Args: 
 5/31/2016 4:44 PM SnapinClient     Action: 
 5/31/2016 4:44 PM SnapinClient ERROR: Snapin hash does not exist
------------------------------------------------------------------------------

When I check 10.1.90.2/fog/status/getsnapinhash.php?filepath=/opt/fog/snapins/win7rollup.msu
it returns:
cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e|0

So it appears that it can find the file and hash it, but doesn’t find the hash where ever the client is looking for it.

I find it odd that the ID is reporting -1 in the log.

Anyone have any suggestions?

What OS are you going to the login page from and what browser? What kind of server are you using for DNS? If you ping fog-server does it return the correct IP?

This isn’t a FOG problem, it is definitely a DNS issue.

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

Windows 10 Pro with Google Chrome. I’ve already attempted to clear my browser history, cookies, etc. to no avail.
The server is Windows 2008 R2.
I do get the correct IP when I ping Fog-server.

Another thing to note is that when I go to the ‘wrong’ login page, I can’t login using any of my credentials. It keeps saying username/password is incorrect.

Can you try with IE or Firefox? I have had issues with Chrome using some hidden DNS stuff or something. Not sure how chrome handles DNS, but I had a case that in a school I worked at DNS was having an issue and user couldn’t get to a testing site, but in chrome they had no issue.

@RobTitian16 said in DNS Name Goes to Old FOG Installation:

@ITSolutions Ubuntu 14.04… Perhaps it’s time to upgrade?

No definitely don’t upgrade Ubuntu broke a lot of things in 16.04, so 14.04 is a better choice for now. Ubuntu moved the default location for web pages in 14.04 from /var/www to /var/www/html. FOG is designed to do a symlink back to /var/www, but maybe something broke in that. Can you check to see if there is a /var/www/fog folder and a symlink /var/www/html/fog?

@jhuesser I noticed that you said that you re-installed the client then re-sysprepped, re-uploaded and redeployed. Can you try to just re-install the client on this one machine. Don’t sysprep it or upload it, just uninstall the client and re-install it to see if it will rename correctly. Trying to rule out that the sysprep process or something else could be causing this. Lets make sure it works before complicating it with sysprep.

@phil_guy said in "TFTP open timeout" Error when trying to PXE boot.:

@Quazz To my knowledge, there is no other dhcp server.

Can you try unplugging your FOG server from the network and checking a client machine to ensure there are no other DHCP servers on the network?

@phil_guy said in "TFTP open timeout" Error when trying to PXE boot.:

@ITSolutions I unplugged my fog server from the network and on my client machine it shows the DHCP server to be the fog server.

But did you do an IPCONFIG /refresh or reboot the machine to ensure that it isn’t getting an ip with the FOG server unplugged?
Also it sounds like you have 2 nics in the server, are you sure that everything in FOG, DHCP and TFTP are configured tot he correct NIC?