Best posts made by george1421

Mod Note: Moving to bug reports.

IMO it sounds like the multicast manager is starting up before the database server is fully ready to accept connections.

@bacelo The error indicates that the tftp process could not download the file that is defined. Can we safely assume that 10.1.8.254 is the IP address of the FOG server (one might think that the .254 may be a router address in some installations)?

@John-Johnson Again, I want to restate this is not a FOG issue.

You are sysprepping it so that is fine/good.

1. Are you using an unattend.xml file? If so, that is good.
2. If you are using the unattend.xml file does it contain this line: <CopyProfile>true</CopyProfile> ??
3. And when you fixed the reference image, were you logged in as the Administrator?

If you answered no to any of the questions above, I understand how/why the fix is gone. Because when you sysprep the image all profiles are reset except the administrator’s account. When you have the copyprofile set to true then when you sysprep the image the Administrator’s account is copied to the default profile. And the default profile is the basis for all new users after imaging is complete.

@wcheung let switch this a bit.

What you do in fog is create image definitions first. (i.e. Image name Win7ENTX64, Win10ProX64 and so on.) Then you register your hosts. And then you connect your host to A single image definition.

So if you capture to host “123” and host 123 is connected to Win7ENTX64 the captured image will be saved to Win7ENTX64 imaged definition. So now if you change host “123” and connect it to image definition Win10ProX64 and recapture from host 123 the image will be saved in image definition Win10ProX64.

Now lets add host 234 to the mix. You connect it to image definition Win10ProX64. And schedule a deploy to host 234. The win10 pro image will be pushed to host 234.

This gives you a many hosts to a single image. Now lets say you want to reimage host 234 as a win7 image. Just connect it to the Win7ENTX64 image and schedule a deploy.

@skipdawg02 said in Intel NUC10i3FNK Network Adapter Intel i219-V 10/100/1000 Mbps Ethernet not detected:

George I could about kiss you. I got a new batch of Dell Precision 3551 laptops in and the regular kernels were not working for the network adapter but your bzimage5618 did the trick!! Thank You!!

Because of social distancing I think I’ll pass on the kiss, but I’m glad the updated kernel got you going. It appears the linux kernel developers (not related to the FOG Project) are no longer back porting drivers to the older 4.19.x series of linux kernels. That is why the current (latest) FOS Linux kernel doesn’t support this new hardware. I did chat with the FOG developers today and they have agreed that FOG will need to support linux kernel 5.x line of linux kernels.

@bacelo Again, what is 10.1.8.254 ?? Who owns it?

That is the device you need to set dhcp options 66 and 67 in/on. Once you do that, the pxe client should boot into the fog menu. My intuition is telling me that 10.1.8.254 is your firewall/internet router.

Once you get that working, you MUST make sure that the dhcp server in fog is not used or you will have IP address conflicts.

Does the new version of fog have that feature, no it does not. FOG can rename the computer (post OOBE) and connect it to the domain no problem. Adding domain users to local admin group is not supported (and even a bit questionable security wise IMO).

But with that said you can do what you ask in one of two ways but both require the use of a FOG post install script.

With a FOG post install script you can access device specific properties (like user name) and then interact with the target computer’s files or registry. In my company we have a post install script that alters the unattend.xml file with FOG host parameters just after the image is deployed to the client but before windows boots the first time.

You could use this concept to update the unattend.xml file to add the user to the local admin group. Just use sed with a string replace on the unattend.xml file to replace a key word with the assigned user.

If you didn’t want to touch the unattend.xml file you can use the setupcomplete.cmd file. Just use a fog post install script to append something like net localgroup administrators /add "domain\user" where domain would be static and user would come from the user field in FOG.

@wcheung That is correct the mac address is typically a unique item per machine.

I would have to ask how do you plan on using FOG in your environment? Will you use FOG for only image deployment or will you use FOG to manage the target computers (such as deploying applications post imaging)?

Your approach will be slightly different depending on if you will use fog for only imaging or system management.

If you are only doing imaging then you can use the quick image function of the iPXE menu just to push an image to the target computer. If you want to use fog to manage your clients, you will need to register them with the usb ethernet adapter, image the computer then manually update the mac address of the carbons to match the wifi mac address. That will free up the usb network adapter mac address for the next registration. Its a bit more cumbersom this route but then you can push applications post imaging (because fog uses the fog system id and not the mac address) without issue.

@george1421 I was just notified by the developers that there is the optional FOS Linux version 5.6.18 of the kernel out in the FOG repository. If you need this kernel for new hardware support you can upgrade your FOS kernel using the built in update tools.

NOTE: This kernel has not been fully tested with all versions of FOG. It has had some limted testing with FOG 1.5.8 and 1.5.9RC2 but not with every possible hardware combination. There may still be some unexpected events related to this new kernel. Use it at your own risk.

The developers are making this new 5.6.x kernel available for those that 'need' it to image the newest hardware platforms ahead of having the kernel fully approved.

FOG Configuration -> Kernel Update

Sorry for intentionally being dense here. What is device 10.1.8.254 ?

Are you still getting the same exact error message as you posted below?

@Tom-Elliott

Just so I’m clear here…

If the OP installed the FOG client on the target system first, then the client would check into the FOG server and create a “pending” host record?

If that is true, then the proposed work flow would be something like.

1. Install the FOG client on the target windows system using a similar command line:
   msiexec.exe /i FOGService.msi /quiet USETRAY="0" WEBADDRESS="<fog_server_ip>"
2. Wait for at least 2 check in times (just a guess) or about 20 minues.
3. Go into the FOG web gui and find the host record in a pending state and mark it as active.
4. Update the host record in the web gui and connect it to the proper image.
5. Setup the FOG capture/ deployment task
6. PXE boot the target computer and since it is already registered it will begin the scheduled task

@wcheung said in Host Machine and images:

I think I understand, I will play around. I’m glad I used norton to capture an image prior so my didn’t lose an data really.

Once you see how it works you will understand the concepts here. One other thing I should mention. After you upload your golden image to the FOG server, go back into image management and for that image select the protected check box. This will keep you from accidentally overwriting your golden image (if you happen to hit capture again).

@skipdawg02 said in Intel NUC10i3FNK Network Adapter Intel i219-V 10/100/1000 Mbps Ethernet not detected:

Thank you for the feedback. That’s strange because it should have worked with 5.6.18 out of the box. We’ll compare the config files to see what else is different.

@KellyM said:

For Reference, we are running FOG 1.2.0, no SVN, I believe a UEFI image, (though our machines are set to boot using legacy BIOS, so I am not sure how FOG sees it) and our OS is Ubuntu 14.04 LTS hosting FOG.

UEFI vs Bios is a state of being. You either are or are not. On the Dells you CAN have UEFI enabled with the legacy roms turned on. In this case uefi emulates bios. For me its not clear either if fog sees a uefi system or an emulated bios device. There is a way to tell if you capture the initial bootp request from the client as its asks for an IP address. It will state the arch in object 60 or 93 (I believe). It will be 00000 for bios, 00006 for uefi 32 and 00007 for uefi x64. There are a few others but that is what I can remember.

If you are using the 1.2.0 stable then you may have the same issue as the OP, hang tight.

@sourcaffeine said in Windows 7 errors post deployment:

Description

A group of 60 computers, all with nearly identical hardware, seem to have some that have issues when installing post sys-prep. Some of these computers seem to work fine, others seem to give the error of "Windows could not complete the installation. To install windows, restart the installation.”

When I’ve seen this it is because the installation has rebooted in an incorrect time. There are two common causes I’ve seen so far.

1. Before you sysprep’d the image you forgot to disable the FOG service. Whereas during the OOBE setup of the system the FOG Service kicks in too soon to rename the system and reboots the target system before OOBE setup has completed. Typically what we will do is disable the FOG service before sysprep and then enable it again in the setupcomplete.cmd file. When setup complete has been run the OOBE setup parts have finished.

2. You have a bad driver that is causing the computer to spontaneously restart when the driver is installed. There is a way when you get that “to install windows, restart the installation” message. It like shift-f3 to bring up a command window and then you need to run regedit and flip a registry value. When you reboot the system will come up so you can inspect the event logs to what really happened.

Well I was so close, and yet still wrong, its shift-F10. Look at the accepted answer here: http://answers.microsoft.com/en-us/windows/forum/all/error-message-the-computer-restarted-unexpectedly/b770f14d-e345-e011-90b6-1cc1de79d2e2

But I’m still thinking its the fog service doing this to you. Since it seems like its seeming random. The fog service only done things when it checks into the FOG server, and that is on a timer.

@x23piracy If that is the case, then the OP should setup a WSUS server then windows updates will be deployed automatically.

There is another option is to use a tool called wsus offline. http://download.wsusoffline.net/ WSUS Offline can be run from a command prompt against a network share. The OP would refresh the repository once a month and then deploy a FOG snapin that would call the wsus offline installer to update the windows updates on the target computers.

@maxcarpone My recommendation would be to not use 1.6 at the moment. I would switch back to 1.5.9 and then upgrade to the dev branch.

Then install the latest FOS Linux kernel (FOG Web ui->FOG Configuration->Kernel update) install linux kernel 5.15.x

Lastly update FOG iPXE to the latest release: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe

That will take your FOG install to what FOG 1.5.10 will be when its released. Its now looking like it will be fall before the developers will have time to release it.

@FlareImp said:

My network admin suggested that our content filter may be screwing with something in the script if it’s trying to access a site out on the web.

This makes me think you do have a transparent proxy server/content filter enabled at this site. If you could white list sourceforge.net that should allow the installer to pull the client and kernel images.

[Edit] rereading your OP you will need to enable more than just sourceforge, since the installer reaches out to your linux distribution’s archives to bring in any missing packages. It may be easier to while list the FOG server’s IP address for a short time until you have it updated. [/Edit]

Is there an issue here or are you announcing a solution.

I can say from my experience that with win10 a shutdown is an enhanced “sleep mode”. But if you use sysprep and have sysprep shutdown the system the disk will be closed properly. Or if you don’t use sysprep, reboot the computer and catch it before it restarts. A restart properly closes the disk.

@ABane OK now that I had my first cup of coffee I can see where I misunderstood.

In your case, I would use the wsus server if you have it.

If you don’t have it you can use wsus off-line and the first run section of your unattend.xml file. You will have to configure your unattend.xml file to log in as a workstation administrator ( 1 ) time to run the first run commands. But then you can connect to the remote share where wsus offline is stored and run the cmd file. Once wsus offline completes then issue a shutdown.exe -r -t 10 to reboot the computer and it will be fully updated.