Posts made by Psycholiquid

What I am trying to do is boot from USB pxe because the laptop has no NIC or UEFI is not cooperating like it should.and Wireless wont boot from network. So basically trying to make a live USB drive so I can boot to FOG on machine where there is no nic or the docking station wont show up.

@Tom Elliott Let me give that a try. I tried just loading the ipxe.efi directly form the server I get the same result. I hate these Dell XPS 12s

I am trying this and for the most part it is seeing my USB drive and starting, however once it hits the Open Source Network Boot Firmware it closes and goes into windows. Am I missing something here. It never asks me for the server IP.

Here is the script I used in the ROM-o-matic site:

#!ipxe

dhcp
set next-server 10.20.60.14
set filename ipxe.efi
chain tftp://${next-server}/${filename}

I have tested and the file is easily grabbable form all VLANs, so I am not sure what might be happening, unless the network card I am using just isn’t working. Is there anyway to tell. I am not seeing a IP being assigned.

not yet, been on the road will test when I get back on Monday

@Psycholiquid Removing and re-adding the Snapin to the host resolved the issue. Not sure why it happened though. It was happening on a few machines right after imaging.

SnapinClient ERROR: Snapin hash does not exist

is the error I am seeing in tehe FOG client LOG

Cloud version 5453

Ubuntu 14.04.3 LTS

@Jbob Sweet appreciate it.

Found the post on the silent install but I am trying to push this via GPO and don’t want the tray icon. Anyone have any ideas?

@Psycholiquid From an updated trunk I am now seeing the .msi being put in place. Tested and is updating clients also

@Tom-Elliott I’m giving it a try this morning.

@george1421 I didn’t get any errors when I did the upgrade but he is right after a fresh install it just isn’t there.

@Wayne-Workman as a workaround that worked like a champ. All I had to do was drop the file in the folder using the command provided. So until repaired others should do this or a form of this.

Location only also

@Tom-Elliott said:

@Wayne-Workman What roll back? I did not make a roll back to the system file which keeps track of the client version.

While I did revert some code, I did not do a “roll back” of any files.

Perhaps the .msi wasn’t uploaded when the commit was done. Please don’t think that I have any idea what I am talking about I am just guessing. I was always under the impression that the client files were downloaded form somewhere else and that was done in the background after the server install.

I have it but my server isn’t a fresh install. Could explain the problem I am having.

@Malos I would suggest installing over it again maybe something was locked when you updated it and caused and issue

/puts rope away. What lynch mob?

OK this is what I have so far. The uninstall / reinstall is a crap shoot.

The new server trunk is giving me version 0.9.5. I have 0.9.5 installed in my image. So I am not even sure why it is trying to update the client unless something has changed in the code of it that is above my head.

I am uninstalling it from a freshly imaged machine and everything is fine. I download the new file from the FOG server ot make sure I am using what is on that page there and when I reinstalled it says it is version 0.9.5 which is what was in there in the first place and I get the same problem of machines not changing name and adding to domain.

However to get around this I just turn off the client updater in the service and it allows everything to work as intended.

TLDR:

Leave the Client as is for now as it is still working.
Turn off Client updater service on either the whole server or the client you have just imaged and everything will continue to flow.

Hmm looking at the commit I am seeing the client is supposed to be 0.9.7 but when I download the client form ym FOG server I am only getting 0.9.5.

Perhaps wrong version in trunk or I am not getting the right one from the background downloader?

@Wayne-Workman Yeah I figured. I am uninstalling and reinstalling and that is resolving the issue for now