Solved Using FOG across 2 domains

[CoxM]

Hi All,

For the next 3 weeks or so we are going to be in the process of swapping from an old domain that we no longer have over to a new domain. Currently I have 3 offices with 2 on the new domain and 1 on the original domain.

I haven’t yet had to fog a machine in the 2 offices that are on the new domain but now I am.

How can I ensure that machines running fog images and fog client on the old domain (of which there are many) stay on that domain but that this single machine is on the new domain and doesn’t try to get auto switched back by fog?
Hope that makes sense.

Thanks,
Matt

[Wayne Workman]

@coxm said in Using FOG across 2 domains:

How can I stop the default FogSettings Active Directory settings impacting a specific host. Will the AD settings on the host be overwritten by FogSettings config?

How can I ensure that machines running fog images and fog client on the old domain (of which there are many) stay on that domain but that this single machine is on the new domain and doesn’t try to get auto switched back by fog?

We should first clarify - there are default AD settings that you can set in FOG, but the AD settings any particular host gets is defined on that individual host. What I’d recommend is putting in your new domain settings as the default so that new hosts get those values. Then as you are able, slowly change all the existing hosts to the new settings via groups.

If you don’t change a host’s domain settings, then it won’t get changed. Meaning imaging hosts with the old domain set on them will still use that info.

Also, you need to be extremely careful when using fog with hosts in multiple domains. Do not carelessly hit the save button when working with groups - validate the config before clicking save. Because if you save the incorrect domain settings onto hosts - fog will do what you told it to do - and there really won’t be any time to stop it.

[dsloan.ethra]

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.

[Wayne Workman]

@coxm said in Using FOG across 2 domains:

How can I stop the default FogSettings Active Directory settings impacting a specific host. Will the AD settings on the host be overwritten by FogSettings config?

How can I ensure that machines running fog images and fog client on the old domain (of which there are many) stay on that domain but that this single machine is on the new domain and doesn’t try to get auto switched back by fog?

We should first clarify - there are default AD settings that you can set in FOG, but the AD settings any particular host gets is defined on that individual host. What I’d recommend is putting in your new domain settings as the default so that new hosts get those values. Then as you are able, slowly change all the existing hosts to the new settings via groups.

If you don’t change a host’s domain settings, then it won’t get changed. Meaning imaging hosts with the old domain set on them will still use that info.

Also, you need to be extremely careful when using fog with hosts in multiple domains. Do not carelessly hit the save button when working with groups - validate the config before clicking save. Because if you save the incorrect domain settings onto hosts - fog will do what you told it to do - and there really won’t be any time to stop it.

[CoxM]

Perhaps a more simple way of asking the question would be - How can I stop the default FogSettings Active Directory settings impacting a specific host. Will the AD settings on the host be overwritten by FogSettings config?