Posts made by jpaul

Thank you for clarifying this. I strictly use fog for imaging and joining multiple lab computers to the domain. Kudos to all that make this possible.

Thanks James…

When we deploy an image in fog sometimes we have them auto join the domain. That part works. When I said a seperate issue with dns I meant we were having an issue outside of the fog senerio. This was a windows 10 machine that has fog service put we were dealing with our own network problems as a whole with dns not dns associated with fog. My initial problem is with host staying in the host list. I think it is because each machine has fog service running on them. older fog versions didn’t matter … I was able to delete the hosts and they would stay deleted.

Sorry about the question … “Little vague”. I am running fog version 1.5.4. client version is 0.11.16. the Problem is I used to be able to delete the host’s out of the list of hosts after they have been imaged as a new machine on the old version of fog.-. Once deleted they stay deleted. Now it looks like once these machines are used in the district and get logged into our network they reappear in the host list. It is not that big of deal but it gets really long after going through a hundred or so host when doing individual imaging… and finding the host your want to deploy an image to… Most of these host are windows 10 machines.

I also have a second question. We had a dns issue with one of our machines yesterday and I made sure it was out of the host list. We tried to join it to a domain and it failed but it reappeared in the host list. Maybe this question is related to the first but thought I would ask. Does the fog service have to be stopped to solve these issues with the host list?

Your thoughts would be appreciated. Thanks James

HI. I have been trying to keep all the hosts in the list deleted. I delete them but after a while they come back or some come in that have been imaged this last summer … Is there a switch I can use so there are not so many in the host list. Thanks in advance

Here is the image of error message right before i deploy …

Hi. I am currently running fog 1.5 and am experiencing something odd. When I create an image and then try to deploy that image onto another computer I get an error and it wants to reboot just right before it is ready to deploy it. Then I go back to the image on the fog server and it now has a size of 0.00 gig and I am unable to use the image. Everytime I do this it bricks the image I want to use and says that the image size is 0.00 gig. What could be causing this. Thanks in advance James

Working on a new image for fog… testing the image process because we are rolling out a 100 laptops. Been imaging with fog sense school got out and successfully imaged all lab computers and 2 of the 3 new computers. This last set of pcs are giving me problems. I install fog service and ran sysprep. Got the computer to pxe boot but it fails to inventory to capture the image. Says on the last line that " no configuration method succeded. DHCP failed. than it just reboots and repeats. Any ideas as to what to try.

@joe-schmitt That fixed it. Thank you… Sometimes the most obvious gets overlooked.

James P…

@joe-schmitt I was wandering about that. The ou was blank when I started the conversion to a new fog but I added it thinking I needed like the old version of fog.

I will give you the results. when I try it again with the ou blank.

@joe-schmitt ran it again because I found the reset data encryption. This is the test it generated. The user name and password is correct.

[mod note: removed log]

@joe-schmitt I went through the steps and there was no place to press reset Encryption Data. Ran the debugger and the text file only gave me this. Obviously it was encryted…

0_1523550041181_FOGCycle.txt

@joe-schmitt No the image was not joined to active directory ever… It was a clean image.

@joe-schmitt The last line in the log under name changer section says the parameter is incorrect , code =87

0_1523548195625_fog.log

I use the new fog 1.5.0. Got the imaging issues solved but I can not get the machines to auto join AD. Using the new client install I used the first line in fog settings / active directory settings/ and did not encrypt the password … also try to encrypt the password even tried the lagacy option using the encrypted password. None of these work. Is there another place to input this info besides fog settings/ active directory settings. Thanks

@tom-elliott . I do not sysprep my images. Never have done this. Used fog for 8 plus years and have never ran into any problems with sid’s and such. Used fogprep in previous instances especially with win 7 to image and had great success. Looks like I will have to learn the sysprep process. Do you have any great tutorials on how to start this process with moving forward. Thanks in advance.

I did not include activation key in host management page. Where is that located? I think we use KMS for the kind of key implemented.

I am wanting fog to activate it. And yes I installed the client on the computer before I captured it.

Just upgraded fog to 1.5.0 . Created my first image and deployed that image to a test machine. Running windows 10 pro education… noticed after the deployment that the on the test machine windows was not activated. Learn that fog prep was not needed for windows 10. Any thoughts??

We are fast approaching implementing some machines to windows 10 … Is there any issues that I might run into that will prohibit me from imaging windows 10 machines. I am using version 1.2.0. of fog… I have had no issues so far with my fog setup.

Thanks James

I started using fog 1.2.0 and all is well … Image computers and everything works. But when I add them to the domain. name them and put them in the correct group printers will not populate even after all the forced group policy updates per machine . Has anyone found the the problem might be with fog imagining or is it just something wrong with our group policies,

If this at all sounds familiar let me know thanks James