Ahh right, if it resets the OU settings its best kept as it is, as each classroom has its own OU to manage programs that we push to specialised classrooms.

If there was an option to just refresh the username and password details to all hosts without modifying the OU’s that would be great.

Only reason I asked for the feature was because I had to change the settings as I updated to v1.2.0 and got caught out by the hosts storing credentials, maybe the hosts should just store the OU by default but if a different account needs to be used to join the machine to the domain then the option remains and could be activated per host via an option box…

Maybe if the username & password per host is left blank then it would use the settings from the configuration area, but i was trying to shorten my task of updating the host’s stored credentials by asking about a tick box that could enable the already specified username & password to be used.

Just a minor ask but in my opinion it would enhance FOG by making the management of it easier if the main domain adding account needed the password resetting or the account changes altogether.

Cheers

I have them grouped by which classroom they are in, if you can have more groups under a main group then I will do that.

I wasn’t aware you could make a tree like the below in FOG?

--------> Computers
----> Group1
----> Group2
----> Group3

I’ll take a look at this tomorrow if its possible to do

Thanks for your speedy response, if it works then thats great!

Hi,

Just a suggestion for a future version regarding system usability. I think it would benefit most users to have a tickbox that allows all hosts to have their AD settings reflect the current credential values in the configuration area on each host, this means that you can still use different credentials for different hosts in the same way you can now but on a more optional basis per host.

The majority of people probably use one account designated for FOG to add all hosts to the domain upon deployment so I think that this would make FOG more manageable.

It’s probably more difficult to implement than it seems but would mean that if the user account that adds the computers to your domain was compromised or has it’s password reset then you can easily update all hosts at once and will not need to do this for each individual group as I’m currently having to do.

This would probably make the system easier to manage in the event of a password or entire account change as mentioned above.

Many Thanks.
KOA-IT

Hi,

You might want to check my post out here: [url]http://fogproject.org/forum/threads/domain-join-not-working-since-moving-to-v1-2-0-error-87.11642/[/url]

If you change the settings in the configuration area the change does not update in the individual/group hosts so you need to check your settings in the config area match up and then go and replicate your change on either the one host you want to fog… the easier way of doing it is to replicate the configuration change for the groups you have the hosts in, if you’ve grouped them.

Hope this helps you out

Hi,

Sorry to bother you guys again…

I would like to know if this is a Kernel issue regarding the use of SSD’s or would you know if there is anything else I can do to get the NUC’s working?

Thanks for your help in solving these niggly issues so far, you’ve been very helpful

Think I may have solved this, I didn’t realize that FOG saved the AD settings “inside” each host instead of using the settings specified in the configuration area. Will see if I’ve fixed it now. - Will update this post with result in case anyone else hits the same barrier.

That was the solution…
For people suffering with difficulties make sure the actual host has got the correct credentials as it didn’t apply globally when I changed it in the configuration area. See image below for the secondary configuration I needed to do.

[ATTACH]1363[/ATTACH]

Thank you for your help with this issue, I hope this helps others as well.

[url=“/_imported_xf_attachments/1/1363_fixed.png?:”]fixed.png[/url]

I just got that solution as well whilst looking at other threads for similar issues Thanks for letting me know personally.

I’ve just changed it but it looks like it’s still sending the data with the KINGSFIELD/ part - is there a way to force the setting to change? I have rebooted the server but it seems the same.

[ATTACH]1362[/ATTACH]

[SIZE=4][FONT=Times New Roman][COLOR=#000000]#!ok=CLASSROOMTEST #AD=1 #ADDom=kingsfield.int #ADOU=OU=Unassigned,OU=Computers,OU=Kingsfield,DC=kingsfield,DC=int #ADUser=kingsfield.int\KINGSFIELD\AD_USER [/COLOR][/FONT][/SIZE][SIZE=4][FONT=Times New Roman][COLOR=#000000]#ADPass=USER_PASS[/COLOR][/FONT][/SIZE]

[url=“/_imported_xf_attachments/1/1362_settings.png?:”]settings.png[/url]

I just saw another post asking to see the data sent to the client, as it may help to provide that to you as well here it is with the confidential data removed.

#!ok=CLASSROOMTEST #AD=1 #ADDom=kingsfield.int #ADOU=OU=Unassigned,OU=Computers,OU=Kingsfield,DC=kingsfield,DC=int #ADUser=kingsfield.int\KINGSFIELD\AD_USER #ADPass=USER_AUTH_PASSWORD

Hi there,

I am having trouble getting machines to join our domain since moving to version 1.2.0 whilst trying to get our Intel NUC’s working with FOG. The service is able to rename the computer but is unable to add it to the domain and the FOG log shows an unknown error 87. I have also seen the occasional report in the FOG Log of unknown error 2692 the first time it tries to join the domain.

We have made sure the encrypted password for the AD account matches what is in the fog web interface and have left the passkey as it’s default value to avoid re-compiling the DLL file in the testing stage.

I have tried using a modified hostnamechange.dll file supplied: [url]https://github.com/mastacontrola/fogproject/blob/dev-branch/FOGService/src/FOG_HostNameChanger/MOD_HostNameChanger.cs[/url]

Which then errored and then wouldn’t change the name of the PC so have reverted back to default. I can upload fine from the computer and deploy to the computer but cannot get the domain join working in this new version.

I have rebuilt the image to make sure that it is not already attached to a domain and used sysprep to make it join a temporary workgroup on build through an automated mini-setup answer file. The client is the standard client since removing the modified hostnamechange.dll which is now able to rename the machine but still seems unable to join the domain.

Any help with this and my other post regarding the NUC not looking like it’s compatible with FOG is appreciated.

Thank you for your time helping us out.

Yep it is a Crucial 120GB SSD in the mSATA slot which is what I think was causing the issues regarding communicating to it, but wanted to know if there was a fix. I did mention it in previous posts but it may have been overlooked… Sorry for not making the hardware setup clearer.

I appreciate your very timely responses with the issues I’m experiencing, and hope we can come to a resolution so we can roll out some NUC’s to our Library as the testing ground. =]