@Sebastian-Roth I believe there is a configuration where you can (ICH9 chipset + virtio-net network adapter)

@merrittw

What tools are you using to manage your linux infrastructure.

I know Ubuntu is the bane of FOG devs but we use it in our environment because i can push updates regularly to all our hosts with Landscape.

@Sebastian-Roth https://github.com/FOGProject/fogproject/commit/d3a70dd417eb1d08b48a637e26ec8776f4409d29

652b6f04-876c-4c27-89b0-d3bc6b01513e-image.png

I commented out the “style” info you put, and moved it to push info out to the left instead of the right so that the form field is still accessible when reading the information.

@Lugga said in Installed Snapins shown as not installed:

BUT: In the FOG Webinterface it is shown as not installed.

As Tom said, FOG only tracks the return code but not the status of a software installation. Do you mean the return code? What happens if you run your silent office installer from the command line and check the return code? Be aware that fog-client runs as a service and uses the SYSTEM account therefore. So testing things with a user account might give you a different return code. If you want to try it as SYSTEM you need to look into using PsExec. Search the forums for that.

Hey George,

No worries on the delays. Work’s been busy for me too, but today is slow finally.

I realize I messed up how I explained things. I was creating a template host with the same exact name as the group. After not being able to get it working, I tried your example name of TemplHost01 for both a new group and new host. I set the details on the host, added it to the group, and still nothing.

So I just tried again today, and the functionality is working as expected. Curious … I wonder it just needed a little more time. I’ll play with it a bit more and see if everything seems to be good.

Yeah, it definitely seems to be working better now, including with groups/host-templates that I name. I’m not sure what was happening the other day.

One thing which seems like a bug: if I’m in a group and I navigate to Membership to then search for and add additional hosts, it only adds one at a time even if I click the checkbox for multiple.

@george1421 @Sebastian-Roth @Quazz

Thanks George, I tried to use your unattend file, but it kept bluescreening on the host once imaged, so I tried creating a new one today and it worked fine. I probably didn’t change enough things in it, and missed something important, but I got around it now.

I greatly appreciate all the help you kind folks have provided. It is very much appreciated. I couldn’t have gotten to this point without it,

Dave

@ayy_nelson said in Another Domain Join Issue:

Is there a way to join domain AND change the name?

Yes there is. In my case I don’t use the FOG Client at all for regulatory reasons. So I do everything in the unattend.xml file. My unattend.xml file connect the computer to AD as well as sets its host name. I do this using a FOG Post install script that connects to the windows 😄 drive just after the image is copied, updates the unattend.xml file with deploy time data, and finally disconnects from the 😄 drive before FOG finishes its deploy sequence.

The post install script how to is covered here: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

You are probably most interested in the “fog.updateunattend” script. I know the sed scripts will melt your brain, but that’s where all of the action is. They search for the key word(s) then replace the key words with the keywords + the proper values.

Here is a sanatized version of my unattend.xml script. I’m using the same one for Win10 1903 as I used for Win7. https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7 The point is if its in a text file and can be searched by sed the value(s) can be replaced by sed

@Trev-lchs uploaded image with no issue, I love Fog. I have been using it since 2006 not an expect by any means and i have no knowledge of Linux, but the online info is great and makes it possible for a Windows man to make it work.

@Trev-lchs oh and sorry this was on Unbuntu 16.04 with Fog 1.3.0

The issue ended up being a configuration problem with the dhcp server. Once that was straightened out the target system pxe booted like expected.

@george1421

thank you george, the current switch is unmanaged, it’s a simple switch. There is not much in the specification of the switch, so I bet that switch is the problem.
All PCs are the same and support WOL and on the old switch they all turn on, but I will check it, maybe one of the students has changed something in the BIOS

Hi @chaddarnold @Quazz

1º.- As @Quazz said, use the Reset Encryption Data Button for the host/group in UI.
2º.- Delete the token.dat file on the Fog Client folder directory if it exists.
3º.- If you install Fog Client on the image be sure to image the computer with that file deleted, better if you automate the client installation on the first boot.

Make your install script with this recommended commands:

msiexec /i "C:\NewClientInstaller" /quiet USETRAY="0" HTTPS="0" WEBADDRESS="YourFOGAddress" WEBROOT="/fog" ROOTLOG="1" sc.exe config FOGService start=delayed-auto sc.exe failure FOGService actions= restart/60000/restart/60000/restart/ reset= 120 net start FOGService

@Tom-Elliott

I guess I just see this as a UI quirk. I’ve found typically with radio buttons that are linked its one or the other and not removeable, and for a situation like this would just have a none option rather than be removed.

@Sebastian-Roth

Of course I go back to take a picture to share and it works 100% right away no error… Not sure what happened.

Got it to happen again. And after this I couldn’t even see the nic in the PXE menu. Starting to think this is a machine / usb adapter issue not a FOG issue. Here’s the screenshot anyway:

IMG_3907.jpg

I rebuilt my master and slave from scratch. Everything worked as expected, this topic can be resolved.

Just close it. Maybe I’ll put together a Galera tutorial one of these days for FOG.

@ConJon @jmason As we haven’t heard from other users this being a problem I suspect pretty much all current UEFI firmwares are able to find Windows bootloaders by themselves and I don’t see why we should mess with this if there is no need for 99% of users. I’ll put this to the archive unless I hear otherwise from someone.

If you still see this issue talk to your mainboard manufacturer first to provide an updated UEFI firmware.

@processor I still have not found the time to look into this. Can you check if this is still the case or if replication picked it up?

@Dan_Ansel No problem, there’s so much to think about, it can be hard to figure out what’s going wrong!

@0juke You are more than welcome to help us improve this part of FOG. I don’t think we will find the time to add your suggestions in the near future. Just too many other things on the list.