Posts made by BPSTravis

Lepretre, did you update from .32 to .33?

We are advising to do a fresh install to make that jump. A lot of file locations changed between .32 and .33, actually, almost the entire file structure changed.

I believe this is the error description you are seeing:
[B]ERROR_SESSION_CREDENTIAL_CONFLICT[/B]
1219 (0x4C3)
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
[LEFT] [/LEFT]
Not saying it’s very helpful but maybe it can get you pointed in the right direction. I could also be off on a tangent but figured it would be worth mentioning.
[LEFT] [/LEFT]

check the actual config file and make sure your tftp/ftp username and password are set correctly in /var/www/fog/commons/config.php

Then try resetting the password for the unix user fog:
sudo passwd fog

then enter your password twice as it shows in the config file.

through the server for Tom’s custom kernel.

There are lots of defaults that can be done through the GUI but Tom’s requires you to add it without the GUI unless you go to FOG 33b.

You will need to copy the kernel to the server and place it in /tftpboot/fog/kernel

Then set the kernel for either that individual host or all hosts(fog settings page).

You will need to copy it over to the server and then set that kernel for that one host or all hosts(default kernel).

It goes in the directory /tftpboot/fog/kernel.

This sounds like an issue with this particular machine being able to do LAN booting as it will not even talk to your DHCP server until it is actually running the OS.

Lenovo has really good support, have you tried contacting them yet? Maybe they can shed some light on this.

If you boot the machine into the image currently on(load into windows) it can it receive an IP address from your DHCP server right?

Nothing else at this point would be due to FOG. DHCP is DHCP.

The IP address is required before the PC even knows the FOG server exists.

This should go without question but you are using an ethernet cable right? And you’ve tried a spare Ethernet cable just in case the original went bad.

Ok, so this machine can’t even get an IP from your DHCP server? Have you tried enabling legacy boot mode?

[quote=“Boygenius, post: 23844, member: 22716”]Any update/work around on this? I have 125 laptops ready to deploy… :([/quote]

Have you gave the latest 33b release a try? It uses part clone which will work with 4k drives. Also you could use raw image in .32 but it’s very slow.

[quote=“Rick Cooper, post: 23930, member: 22803”]First of all client in question is a windows xp box 80 gb hard drive with about 60gb used
I performed an image upload of the single disk, the first attempt I tried single resizable and fog failed to image the drive. Second attempt I tried multiple (thinking about the the recovery partition) not resizable. This mode appeared to work fine Great until the client attempted to reboot.

Totally hosed up, even goback could not repair the issue. Did a console recovery chkdis /p and it found all kinds of unhappy stuff and still not booting so I am going to try a recovery install.

In the mean time I pulled another (these are lab boxes so I have a few of the same) HD and thought well let’s see if I can deploy the image I just created and maybe the image is alright. No joy here either. When I attempt to deploy fog gets to a line stating it could not mount sr0 and was mounting it read only (/dev/sda was imaged) and after the mounting read only it sets for a few seconds and then pronounces the task done! only it did nothing at all. Now just to make sure the drive was ok I booted to windows with the second drive just fine. Tried again same thing

So ssh to the fog server and check for images. When I pulled the image it did three passes the first pass being 67gb the image was (supposedly) 16gb, second was about 2gb and I don’t recall the third. I see nothing at all about images in the web interface under the /images/DFNSA directory I see

-rwxrwxrwx 1 root root 512 Mar 10 18:31 d1.mbr
-rwxrwxrwx 1 root root 7.4G Mar 10 18:45 d1p1.img
-rwxrwxrwx 1 root root 2.2G Mar 10 18:49 d1p5.img

Obviously none of them is 16gb (compressed?) but why is fog not even attempting to deploy them and what on earth did it do during the upload process that crushed my HD’s file system? One would think the imaging process would be done in read-only mount? I have absolutely no idea as to where to go here but I am very hesitant to allow fog to touch a machine I really care about at this point.[/quote]

When the client failed to resize did you manually reboot the computer? If the partitions were not restored to where they were previously THAT is where the boot error came from.

In order to fix it you’ll need to resize the partitions yourself. If all of your lab machines are the same I would recommend using one of those to get what the partition sizes should be.

Use the recovery console. This guide should have all the info you need to get started.
[url]http://www.bleepingcomputer.com/tutorials/windows-7-recovery-environment-command-prompt/[/url]

You could also upload an image from a third lab pc using multiple partition image and then deploy to the first two.

.32 doesn’t like to back fill information, if you made the host BEFORE you entered the AD information under fog settings you will need to copy paste it into the hosts. Any hosts you create going forward will have this information filled in.

You could also delete the hosts and rejoin them to FOG.

Make sure if you do this to select “y” for “Would you like to join this host to AD using default info?”

Have you tried running a quick inventory on the 9 hosts that did not show up? Running a quick inventory or doing a “Full host integration” will load the host into inventory. Quick joins will not.

PXE-E7B is a cannot find boot server error. Are you using FOG for DHCP? What version of FOG is this, and what is the host’s OS?