Posts made by Scott Adams

It sounds to me like this might be new UEFI type of BIOS. If that is the case, you would need to make sure that you have a .efi listed as your bootfile option 67 in your DHCP. When dealing with UEFI devices, I currently use ipxe.efi and it seems to work pretty well.

@george1421 Thanks for the response. This is a Dell Latitude 3550. We have imaged several of these particular laptops since our upgrade to 6124.

I should also say that I am running Ubuntu 14.04.4, SVN 6124

I currently am having to swap the boot file that my DCHP is assigned when imaging Surfaces and legacy computers. I know that is not the issue as I have made sure theat file has been swapped back.

Up until Feb. 12th, imaging/registering devices was working fine. We had recently updated to SVN 6124 in order to get imaging working with Surface Pro 3s.

However, starting Friday 19th, this issue occurred. It doesn’t matter the device (Surface or existing computer), but get the following screen when trying to do a quick image:

@Wayne-Workman

I did. Created a backup user to avoid this in the future. Thanks everyone for your help! I am up and running again.

Thanks @Quazz! I did reset using recovery mode and can now log in.

I’m going to do another SVN update to try to resolve the No Disk Passed error. What should the new version be after the upgrade?

Well, I’m the only one that can make changes to fog. I updated to the 6110 on Monday, 1/25.

I have not made any password changes to the account. I have rebooted the server, hoping that would restart any service, but it still does not. I am unable to log into the fog server.

@Sebastian-Roth

I’m pretty sure you have to enable root, which I didn’t do. As I just use the Sudo command to do root level stuff, and I always use the password for my fog account.

@Sebastian-Roth

Don’t know of a root password. Don’t remember using one/setting one up when I installed fog server almost a year ago. The fog user account has always been the account we use to access the putty session and it just no longer works after the update.

@Wayne-Workman

Don’t have another user. Should I add one using the web console and see if I can log in using that?

@Wayne-Workman

I am using the Fog account. This has always been the account I use. I can log in using the same credentials as always to the web interface, just not putty.

I can log into web console using my only username/password, but I cannot log into the server using putty with the same credentials.

I too am getting the “No Disk Passed” error after upgrading to 6110, and was thinking that another SVN update was needed, but I cannot get into the command line to do so.

Please help!

Can FOG do bare metal imaging? That way I don’t have to have a plethora of dated images on my server. Looking to do some streamlining if possible.

Using the FQDN seems to be working. We were able to join a computer to the domain from a different subnet.

Thanks Wayne for your help! Not sure why FOG client is not using our DNS entries, but it worked.

I will give that a try and then reply back when complete. Thanks Wayne! I’m crossing my fingers.

Thanks Wayne.

In the FOG AD settings, we use the sloppy domain name. In our DHCP scopes, we point to the FQDN.

At the remote sites, imaging works great, but no domain join. On FOG server local subnet, imaging works great AND domain join works.

FOG IP address is set correctly on the client for imaging. Like I said, everything works great local subnet, but just doesn’t join domain when away from server subnet.

All settings on the client, AD settings, FOG Configuration, everything is set right.

It’s something about the remote sites. Just not sure what. DHCP has the correct settings (66 and 67). set exactly the way as the local server subnet.

To clarify, we are using the FOG client that got installed with 1.2.0. I just read that a new fog client has started to be distributed for testing. We are not using that client.

We are on Fog 1.2.0., using the new FOG client.

As far as domain, we just use the first part of the domain name, we do not use the .local at the end.

We have created several images, and they download fine. Hostnamechanger does reboot system and rename the computer to the appropriate name. However, joining the domain is a different issue. Let me go into a little more detail.

We have multiple sites that are subnetted out. Each scope has the 66 and 67 options set. That is not the issue. At all of our remote sites, the computer will not join the domain. The fog.log gives the error 1355 when it tries to join. However, if we use the same image on the same local subnet as the FOG server, computers join the domain fine. Same options are set here, there is no difference in the DHCP setup. At the remote sites, we can manually join the domain, we can even use the netdom command no problem.

Any thoughts?

Yes sir. On Upload. We are able to upload other images (we just did an Optiplex 360 yesterday). But, we have been unable to upload one for our new Latitude 3440s.