New Machine Problems

[george1421]

@Andrew134 @Developers a little input on adjusting the image here?

[Andrew134]

@george1421 said in New Machine Problems:

@Andrew134 @Developers a little input on adjusting the image here?

Actually it seems like I got it working. Not exactly sure how but now my Elitedesk is up with the image. Lenovo not so much but I am beginning to believe the machine is the problem not fog Thank you everyone so much for your help! Cannot express how happy I am that this community is so helpful/ responsive to questions. If I come back around to thinking the image is the issue I will open a new topic but at this point I think it is the machine.

[george1421]

@Andrew134 Which ever you decide on this hardware, you will be happy with the 100s of improvements with the 1.3.0 build over 1.2.0.

I would suggest that you go through the global fog settings and then look at the storage node settings to be sure they are now consistent with what you need.

[Andrew134]

@george1421 Got a quick one for you. What do I have to put in AD settings to make it work? The machine I added is not joining the domain automatically like it use to. Again I am sure it is a minor change like when we upgraded to 1.2.0 but I have not been successful at finding an answer.

[george1421]

@Andrew134 Lets see.

I don’t use fog to connect the target to AD but use the unattend.xml file instead so, I’m going to have to make some educated guesses.

You have the FOG client installed on the target computer? If so did you remember to start the fog client service and is it running?
For the target computer are you sure you have the AD credentials set in the host properties in AD. That defined user account must have domain edit rights.
Did you properly define the OU path for the target computer?

[Andrew134]

Just so others know/ so you know. There are two different Domain password spots. One for if you have the new client installed and one for legacy clients. It had my password in the new one’s spot where the client on my machines is the old client. Used FOGCrypt to generate the Legacy password again and it worked like a champ.