Topics created by CoxM

@tom-elliott Excellent, thanks for your time.

Would you share a screen shot of the error you see on the Dells?
Also what model of Dells do you have issues with and lastly what version of FOG are you using?

@CoxM Before we actually dive into the pending MAC stuff I want to take one step back and see if what you describe is really caused by pending MACs at all.

First, can you reproduce the issue?`Please take a screenshot of the host settings of the two systems running into the problem where we see the MACs and post here.

@george1421 Perfect, thanks.

@CoxM https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

@CoxM said in Fog Language/location client auto setup:

set the location and keyboard language on a client post image deployment

Is it possible yes with a post install script that updates your unattend.xml file.

For the most complete tutorial on post install scripts look here how to set them up: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

Specifically to your question, there is an older tutorial that give you an exact example:
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/6

With a few more hints in the post above:
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/7

Thanks @Sebastian-Roth

@Sebastian-Roth It had reset the user to ‘root’ and the password blank. I have run the ALTER USER commands previously so perhaps that did it.

Once I had manually entered the correct username “fogstorage” and the password, which I still had from the working node, I was up and running.

Thanks,

Matt.

@Hanz Amazing, thank you! worked a treat.

Our master server and one storage node is on 1.4.4
the two newer storage nodes, both having the same problem as described, are on 1.5.2

We have had issues in the past upgrading hence the mixed versions.

Thanks.

@coxm said in Dashboard Bandwidth graph not showing traffic:

For reference POR (Master) and ATL (Storage Node) are on 1.4.4
PHX (Storage Node) is on 1.5.2

Though I am not an expert on the inter FOG node communication I’d advise you to run the same version of FOG on all your nodes and see if that helps.

I have found the problem, it was the type of speech mark round the password.
Thanks to those that viewed.

Can one of the @developers or @moderators or @testers check to see if this bug exists in 1.5.2 please? I’m not able to do it at the moment.

A pending host is a host with the FOG Client installed that is not registered in your FOG Server.
That FOG Client is calling home to your FOG Server and is added as a pending host - because it is unknown and therefore untrusted until you (the admin) claim it. Claiming is basically saying ‘Yes, that’s one of ours, trust it’

@coxm Two questions:

What version of fog is this? Is your master node on the same version as the storage nodes?

@coxm Now that you have a working solution, I’ll tell you a bit easier way to go about this.

If you know ahead of time you will keep the OS on a thin image and have the /images on a separate disk then before you install fog create the /images directory and mount your image storage disk over /images and finally install FOG. There will be nothing to change post installation. If you see you need to add the disk after fog is install there are a few more steps involved but that’s basically it.

https://forums.fogproject.org/topic/11048/moving-fog-s-images-files-off-the-root-partition-2017-edition

Perfect! That worked a treat.

In the interest of housekeeping, can I now delete that group? If so do I need to remove hosts first?

Thanks,
Matt

@sebastian-roth @Tom-Elliott
Thank you both so much, through a combination of things I have it working. you guys ROCK!

Thanks again!

Just throwing my 2 cents worth in because we also have 2 domains, but segmented networks with the exception of FOG talking over both networks. But that shouldn’t matter for this.

I have set up my primary domain information in FOG as a default. I then created Locations (Using the Location plugin) and host groups for each remote location. I then placed the machines into each of their respective host groups and applying the specifics there.

Once you have the machines you want on one domain placed into the host group for your Old domain, you can apply the AD information to that group allowing the Host that needs to remain on your Old domain to re-join it. You can do the same for the New domain as well.

Simply put: Create 2 Host Groups. “Old_Domain” and “New_Domain”. Place the hosts you want to keep on the old domain in the “Old_Domain” group and apply the AD information to that group. Then Place the hosts you want to be on the New Domain in the “New_Domain” group and apply the AD information to that group. Your hosts will stay on the domain you specified to each group.

@coxm said in Image Replication Across Storage Groups:

should i image a pc in that remote site which is made part of that remote site storage group it will pull the image from that node, not the master Fog server on my local site.

Not necessarily. Without the location plugin, fog just picks whatever server that has empty slots.

You should look at the location plugin (link posted earlier), I think that’s what you need. The location plugin allows you to assign storage groups and storage nodes a physical location, and allows you to set physical location on hosts. If host A is assigned location A, and a storage node is assigned location A, then all imaging on host A would only use node A.