@Tom-Elliott Oh cool - thanks! I might test this out at some point soon

@Tom-Elliott Ah, many thanks. Indeed, I think it’s simpler just to answer the questions if users are imaging the systems themselves.
On another note, is it possible to view the description of the snapins whilst registering a host? It would be somewhat helpful as then they can see exactly what the snapin does and whether they want it or not. If not, I suppose I’ll create a Word document detailing what each one does and they can review that if necessary.

@Tom-Elliott said in FOG Snapin Not Working in Group:

update the particular group to enable that host’s “sync” with the group it’s in.

Ahh that makes more sense now. Many thanks for your explanation and help.
So I suppose when users are imaging the computers themselves, it would be better for them to say ‘yes’ to the question: ‘Do you want to join this computer to the domain using default settings?’ and letting them choose the snapins themselves, rather than expecting the group settings to replicate to the hosts?
Or, is there a way to “sync” the group settings with the hosts automatically?

Server

• FOG Version: 1.3.0-RC-14
• OS: Ubuntu 14.04

Client

• Service Version: 0.11.5
• OS: Windows 10

Description

Hi all,
I seem to be having an issue with snap-ins and groups at the moment. When I image a PC, I first perform the full host registration and inventory. I assign the PC to a group, which has snap-ins assigned to it. When the PC is then imaged, I check the FOG log and can see that it says: ‘No Snapins’. I’m expecting it to run a script that changes the default Administrator account name and password.
It’s odd though as it joins the domain perfectly fine (which is a group setting - I say no when it asks if I want to join the PC to a domain using the default settings when performing the full host registration and inventory).
So the question is: how can I get the PC to run the snap-ins assigned to the group it’s a member of?

Any help with this would be greatly appreciated.

Hi all,
I’m trying to run a PowerShell script that renames the local administrator account after a PC has been imaged through the FOG snapin. However, I run into the issue of it not running because the execution policy isn’t set to remote signed. How would I go about ensuring it can run when the FOG service starts?
Any help with this would be appreciated.

Hi all,

What do you think is the best way to install software post-image? I currently have Oracle Client 12cR1 as well as Office 2013 on a few images, but I often have the problems of:
a) The Oracle Client has to be uninstalled and reinstalled after the hostname has been changed (otherwise it won’t work properly), and
b) Office 2013 has to be uninstalled to make way for Office 2016 (or vice-versa if we don’t have licenses for Office 2016).

I was looking at potentially running WPKG, but I also read on here that I can set-up a snap-in to install Office (I’m not sure if this is possible with Oracle, but I assume it must be somehow through scripts).

Would the snap-in only run after being imaged, or could I run it at any time? (i.e. if I forget to add the snap-in during the full host registration and inventory, could I add it through the web-gui and then run it?)

Any help with this would be greatly appreciated.

@Wayne-Workman Yep, I already learnt that one the hard way
Thanks!

@Wayne-Workman Doh, many thanks for your help!

@Wayne-Workman No, it’s not there. I haven’t done anything with the FOG client on the images, so I suppose that’s the reason this is failing? I had a thought I was missing a vital step somewhere…
On another note, going to: http://[serverip]/fog/client/ doesn’t actually let me download the FOG client.

@Wayne-Workman
Ah, I don’t have that. Is this configured on the web gui somewhere?

@Tom-Elliott Where would I normally find this? I saw on another forum post it’s meant to be on the client machine, but I can’t see it anywhere.

@Tom-Elliott Yep, I can see the AD settings are there.
It shouldn’t make a difference if the username is “domain\user”, right?

@Tom-Elliott Updating hasn’t helped this issue, unfortunately.

Server

• FOG Version: 5962
• OS: Ubuntu 14.04

Client

• Service Version:
• OS:

Description

Hi all,
I’m currently having an issue where FOG won’t join a newly imaged system to the domain. I’ve gone into FOG Configuration - FOG Settings - Active Directory Defaults and have entered the correct credentials, etc. I then set-up a VM, performed a full host registration and inventory, and then imaged it (whilst selecting ‘yes’ to the question of joining it to the domain with the default settings). Upon logging in to the VM, I can see it’s still part of a workgroup.
The image was taken when a previous VM was set-up and was never joined to the domain. It was my understanding that FOG would join the system to the domain automatically using the default settings, regardless if the image was set-up as being on the domain or not.
Have I missed a set-up step somewhere?

@Wayne-Workman Thanks for the assistance with this - it’s much appreciated!
It might be an idea to put this on the wiki once all is done as it would be quite helpful to others, I’m sure

@Wayne-Workman It seemed to work without double quoting the variables - I just had to put spaces, like:

if [[ $snmysqlhost != “” ]] then

@Tom-Elliott BAM - that seems to have worked! Thanks!

@Wayne-Workman Thanks, although that’s actually a result of me blocking out the password. I can confirm there are double quotes on all 3 lines. I copied and pasted the code below, so it’s all the same as far as I can tell.
I can also confirm there is a space between the [[ and ]] brackets and the inner line between them, as suggested.

@Wayne-Workman

@Wayne-Workman Indeed, I set those as root and “password” with the host being “localhost”. It gave me those errors in the previous screenshot.