Not 100% sure, but I am assuming AVAST was the culprit. If I get some more time I will retry to upload an image with AVAST installed prior to upload and then deploy to be certain, but for now that is my assumption.
Latest posts made by ridern
-
RE: Hostname CHanger not working since moving to 1.0.1
-
RE: Hostname CHanger not working since moving to 1.0.1
Old Image: I joined the domain added some domain applications, took off the domain and then uploaded my image. This did not allow me to have FOG automatically join the domain.
New Image: I rebuilt the image never putting it on the domain, and leaving off Avast and other domain controlled applications, and now the image deploys perfect, changes the host name and connects to the domain automatically.
Thank you for the updates in 1.01!
We are off and running and making some images for the summer. -
RE: Hostname CHanger not working since moving to 1.0.1
Good thought but no I do not have a custom compiled HostnameChange.dll.
I’m thinking it has something to do with the way the image was made. I had it on the domain, installed the fog client, took it off the domain and then uploaded it, so I may have caused the issue. I am going to build a fresh 64bit windows 8 image and see if this solves the issue.
-
RE: Hostname CHanger not working since moving to 1.0.1
Welp, I FOG’d a second image, Windows 8 32bit and deployed it without changing any settings and it automatically joined the domain. So I am going to delete the 64bit host from FOG, perform full host inventory it and redeploy and see what happens. I will keep you posted. There may be something going on with that particular Windows 8 x64bit image.
-
RE: Hostname CHanger not working since moving to 1.0.1
Yes. That screen shot was from the actual host settings in FOG. It is also the default in the FOG active directory section as well.
-
RE: Hostname CHanger not working since moving to 1.0.1
Yeah, I am really hoping that it might be a Monday detail, but I do think I have both of those correct. Thank you though, it might be that simple with something else I missed.
[LEFT] [/LEFT]
[LEFT]Here is the UI config.[/LEFT]
[LEFT] [/LEFT]
[CENTER][IMG]http://vanlueschool.org/pictures/snip.png[/IMG][/CENTER]
[CENTER][IMG]http://vanlueschool.org/pictures/snip2.png[/IMG][/CENTER] -
RE: Hostname CHanger not working since moving to 1.0.1
Thanks, sorry about the lack of info. I’ve been using FOG for about 5 years now, but installing, building images and deploying images is about all I have experience with.
I put generic info in my post to protect the innocent and didn’t literally put that info in
I have used FogCrypt from the client portal to create the encrypted password for my unique local AD Admin Account and then placed that info in the FOG Active Directory Section of the UI, (following the wiki and forum instructions). I have scoured to see if similar issues have occurred and this is the closest thread I have found.
My Environment:
I recently did a clean install of 1.01 to a Ubuntu 14.04 box.Everything seems to be working great except the HostnameChanger Joining to the Domain. I’m hoping it’s something dumb that I missed.
Thank you for continuing this project and all of your help!
-
RE: Hostname CHanger not working since moving to 1.0.1
I am having similar issues. Clients will not join the domain on 1.0.1.
The Fog Log on the client says: HostnameChanger Domain Error! (‘Unknown Error’ Code: 2725)
(My Setup)
[I][SIZE=12px]FOG_AD_DEFAULT_DOMAINNAME : mydomain.local[/SIZE][/I]
[I][SIZE=12px]FOG_AD_DEFAULT_USER : myuserad[/SIZE][/I]
[I][SIZE=12px]FOG_AD_DEFAULT_PASSWORD : b711a695df5558b61be85cc70caf0860[/SIZE][/I]Any info would be greatly appreciated.