Best posts made by Joe Schmitt

@anthony-delarosa the log indicates that Join Domain after image task is not checked for the host. You can find this setting under Active Directory on the host / group.

Git clone should only be run once, on initial setup. Afterwards you cd into the directory and run git pull

For the client not to remove a printer, only the name has to match whats on the server. So if you have some printer installed, (e.g. cutepdf), just make a printer on fog with the same name.

@dylan123 said in Adding Machine to Domain using Active Directory:

So I’ve attempted to deploy an image onto the domain

Images should never be pre-joined to the domain, Active Directory is fundamentally incompatible with handling that scenario. Either use setupcomplete.cmd in sysprep to join the domain, or the FOG Client.

@x23piracy issue confirmed. I’ll patch it when I get some spare time later this week.

https://github.com/FOGProject/fog-client/blob/master/Modules/HostnameChanger/Windows/WindowsHostName.cs#L80

The registry is changed.

@kwisher in addition to what @Tom-Elliott asked, did you follow the sysprep instructions for the client? https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

Also per the log 4/10/2017 9:34 AM HostnameChanger ERROR: Required domain information is missing, if you’re trying to manage the machine’s domain binding you need to fix in all the required fields.

@cajos001 from a FOG perspective it doesn’t make sense to manage USB printers. If that printer is connected locally, its up to that computer to add it which could be done via Snapins but is still something FOG will not manage. If its connected to a server, its up to share it via some kind of system (CUPS, TCP/IP, Network …), which is definitely outside the realm of what FOG does.

https://github.com/FOGProject/fog-client/blob/master/Modules/HostnameChanger/Windows/WindowsHostName.cs#L32

Native Windows API is used (https://msdn.microsoft.com/en-us/library/windows/desktop/aa370675(v=vs.85).aspx). Netdom is not required.

Linking with https://forums.fogproject.org/topic/11305/fogclient-0-11-12-windows-10-1709-reboot-fails-after-joining-domain as @TrialAndError has the same issue. It seems to be specific to 1709.

@Joe-Gill the second one is caused by a bad security token (a reset encryption would fix it). Your first one is somehow unpinned, that is, something removed the servers certificate from the machines keystore. The only way to fix that is a complete reinstallation followed by a reset encryption.

@Tom-Elliott there appears to be some scenario where the server’s copy of the security token is becoming out of sync with the client evident by the numerous users having to reset encryption.

https://github.com/FOGProject/fog-client/blob/master/Modules/HostnameChanger/HostnameChanger.cs#L55

• Activate Computer
• Leave Domain (reboot if needed)
• Rename Computer (reboot if needed)
• Join Domain (reboot if needed)

It is possible to do the process in just one reboot on Windows, but that would be for another minor release of the client (v0.x.x)

@dclark v0.11.13 of the client (in the newest RC) patches the win1709 issues, thank you for your help debugging this!

@Greg-Plamondon re-run the installer with ./installfog.sh -K . That will regenerate your certificates using your old server’s private CA key, assuming it was transferred over properly.

@LibraryMark It is the Make changes even when users are logged on? setting. It is per-host / group. You can find it by selecting your host/group, and going to Active Directory.

@whereiswaldo7 thanks for reporting, I can confirm the version number issue. I’ll post back on this thread as soon as I have a build for you to test!

I remoted in with @blkeller and helped fix the issue. It was with the ssl cert being assigned to the IP instead of the FQDN. There is another bug we discovered with tunnel macs, but I will post an update about that later.

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options

@zefanja , it would seem I was near completion of 0.10.0 when I stopped a couple months back.

I just need to look over the auto updating code and verify it works, and then it seems like its about release ready.

@tesparza you’ll need to exclude the fog client’s installation directory from the snapshot. These types of software usually have a whitelist/exemption list I believe.