@tesparza did you run PrinterManagerHelper on a computer that has the printer already installed? It will give you all the field values, as sometimes even things such as Model aren’t what you think they should be. Did you also try using the generic printer inf the tool will point you to? It should work for the majority of printers.

@Wayne-Workman until we know more information its doubtful the powershell script will likely do anything to resolve his issue, as we do not yet fully know what it is. Based on the errors this seems to be a simple configuration issue for now.

As a note, the client log states that it has already attempted to configure the printer, not that it is installed. If a printer configuration fails to add once, there is no reason for the client to continue spamming your printer spooler every cycle unless the config has changed. If you scroll up more in the log to where the client first attempts to add the printer, you’d probably see an error message similar to what PrinterManagerHelper is giving you.

So, the mysql-fix postet by Tom Elliot helped. No need to rerun the fog installer.

@tom-elliott said in Ubuntu is FOG’s enemy:

TLDR; … or run the ALTER USER syntax shown below.

As a note, it seems this problem is specific only when the mysql account is the 'root' user AND the password is blank.

The “fix” if you must do it manually is to open a terminal and obtain root:
Super (Windows Key) + T then sudo -i (in most cases).

From there, open mysql with mysql -u root

NOTE: MySQL MUST be run with ROOT.

Run:

ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY ''; AND
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';

It’s okay if one of them fails. This is going to fix Most people’s issues.

I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

To prevent this problem from happening in the future you could run:

apt-get -y remove unattended-upgrades (AS Root again).

@fradlo ok well that rules out stp then.

I guess the next round of testing should be this

Lets get a pcap (packet capture) of the pxe booting process. Since the fog server and the target computer are still connected to the same switch I want you to follow this process (I know you are wireshark capable, but lets follow this route): https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue Lets add to the filter sting port 80 too, so we can capture http requests to the FOG server. Run the pcap all the way through registration. Upload the pcap to a google drive or drop box. You can either post the link here or DM me the link so I can take a look at it.

We need to rule out anything in your environment that could be causing this issue. It may be worth setting up isc-dhcp server on your fog server for a test. Keep that unmanaged switch between your FOG server and your target computer and unplug the unmanaged switch from your business switch. and then with isc-dhcp server running see if pxe booting behaves any differently. I have 790s in our office and they pxe boot just fine. So unless the bios is the original release on the 990s pxe booting should just work.

Error in the server config file. Thanks for the pointer, happily cloning away!

@alwos Two comments.

Please open your own thread because your problem may not be the same. If you are more happy, use your native language to explain the problem because your post is not understandable.

@trex said in Database Install blank page:

With the Ubuntu servers, Veeam Backup and Replication wouldn’t do a VeeamZIP job on the server, only on its replica (which made backups on the host with the replicas much longer than the host to the FOG servers. But the Debian servers can have a VeeamZIP job done on them,

That’s a great reason for Veeam users to install FOG on Debian.

Thank you for your reply.
I will try that 😉

@pkt said in Lenovo X1 Tablet hang on init.xz.... OK:

DHCP 067 Bootfile Name: ipxe.efi
Yes, secure boot is off in the BIOS on the tablet.

See here is where we keep seeing a conflict. You are saying BIOS and ipxe.efi in the same context.

The issue is the target computers need the proper ipxe kernel for the firmware mode.

For BIOS (legacy) configured systems you must use undionly.kpxe class images.

For UEFI configured systems you must use ipxe.efi class images.

@george1421 Hello George as you seen on the Database schema error log

"General error: 1819 Your password does not satisfy the current policy requirements Error Message: Error Code: “HY000”, Error Message: [“HY000”,1819,“Your password does not satisfy the current policy requirements”], "

because of mysql root password policy requirements I coulndt get update or install database schema to new one.

so I searched about error for mysql server then I understhand I dısableit Password validation on mysql

[https://dev.mysql.com/doc/refman/5.7/en/validate-password.html]

For what it’s worth: these are the manufacturers of the NICs: (You have two 00:09:0f, so I’m guessing this is a wireless card with Bluetooth?)

00:09:0F Fortinet Fortinet Inc. 98:E7:F4 HewlettP Hewlett Packard E4:A7:A0 IntelCor Intel Corporate

@sebastian-roth Hi ! the initial kernel bzimage after fresh install was 4.11.0. I attempted to update from web interface but it was tricky because of rights on directories. Finally, I did it (command line via putty) but the pxe boot resulted in an error. I worked again on it and I succeeded : the current version is now 4.13.4 and all is working great ! I had to copy this new kernel in two places : /var/www/html/fog/service/ipxe and /var/www/fog/service/ipxe to overcome an error during the pxe boot process. That said, we configured another fog server for redundancy purpose and the upgrade from web interface 4.11.0 to 4.13.4 worked perfectly this time …(?) Thanks to every body for the reactivity. The Fog server is our very useful weekly tool to restore our classrooms… Best regards.

@wayne-workman said in Images not replicating:

I have, it just shows online/offline. I created it for exactly the problem you described. In the past, this problem was fixed but I guess it just keeps cropping up. Anyways, the project is called MonitorFogStorageNodes and is located here: https://github.com/FOGProject/fog-community-scripts

I thought I saw a Fix for this issue in one of the the RCs for 1.5, but can’t find it now… I saw the referenced issue (https://forums.fogproject.org/topic/10503/images-not-replicating) and saw that it was “Solved”, so i was hoping for a confirmation that the replication issue was fixed in the upcoming release…

I will grab that plugin, thank you!

@dhruvin-t said in cant make the presented virtual disk as a storage node.:

get fog switched to the mounted share

What do you mean by ‘mounted share’ ? If this is an iSCSI block device you’re mounting, then this works fine. If it’s a regular network share, it’s not going to work. If it’s just a new local disk it’ll work but please say ‘local disk’ instead of ‘mounted share’.

@sourceminer Did you get this fixed? I am fairly sure George and Tom had the right pointer for you.

@wlainey Do you have more than one storage node defined in the Web UI?

From the username apache I see this could be a CentOS system. Any chance this is a SElinux issue? Please run sestatus and ls -alZ /opt/fog/snapins/ssl and post here.

I’ll mark this solved as it seems like the issue was fixed by disabling the other NICs.

@jmeyer I don’t seem to be able to explain this properly. I am not talking about disk size and start sectors although this might be an issue as well. But even if you get this right it still might not be able to boot in the VM as of difference in (virtual) hardware.

By the way, is your image UEFI or legacy MBR? Configure your VM accordingly.

@birvin Thanks for the update. Good to Herr it’s working now. Don’t think think it’s worth looking into this more as it seems to be a one time issue…

I always Sysprep. For me it removes any questions of there are any device independent licenses for software installed on the image.

@sebastian-roth yes the client is installed but I figured it out. I had to the reset the encryption data before doing the snapin deployment. Solved