Hi George!

Thank you for your quick repsonse. I get what you are saying. I agree that I would prefere not to mess with the windows registry externally if there is another way to do things.
We don’t sysprep the systems, seems less hassle in our situation. But, the bread crumbs you mention can be picked up by any system I suppose, not just OOBE, but a snapin script for example…

But, which bread crumbs are your refering to? and how would you go about leaving that trail?

@junkhacker While we removed the settable feature from FOG, the database still relies on it I believe.

If anything there is still a hook that could be tied into to “authorize” against.

USER_TYPE_HOOK and USER_TYPE_VALID are the events to go against. This was part the reason why I went ahead with it, because there are ways around it anyway.

USER_TYPE_HOOK is typically used for just checking and changing the type, as in the case of LDAP users vs. normal fog gui users.

USER_TYPE_VALID is the simplest one with would allow you to hook against whether the user is valid for that particular are or not.

@wayne-workman

Thanks for the suggestions! I have tried adjusting settings and not sitting on the dashboard, but still our nodes are sending data to the master server and bringing everything else to a crawl. I setup a new storage node at another location and during storage replication it copied data over a 1Mbps as I had set. That is good, everything running as I expected. Once that is complete it starts acting like the others with random bursts which nearly brings some of the networks down. I tried adjusting sleep settings in FOG Configuration but that made no difference. It’s sending the same amount of data back to the main server as the others were, I’m just not sure what. In the last 2 hours it has sent 3.3GB to the master node with no one logged in to the web GUI or even in the office.

This would be OK every few hours, but I am not sure what other settings to change or services to schedule.

0_1519395373497_Error_LIB.PNG

@ray-f Have you tried? It should be as simple as creating an image and using “Multiple Partition Image - All Disks - Not Resizable”

I also recommend Zstd compression at about level 10, should really speed up deployments in general.

0_1519355538979_All disks.png

@tom-elliott Yes the image is deploy . For the computer , options host registration and host renamer is ok .
But the stain remains active after deployment .

@turcotter Here is 3 different ways you could do this with powershell and a fog snapin. Reply #2 is interesting since it embeds the csv file right into the powershell script.

We can only offer ideas based on how the snapin system works since we have not / do not assign static IP addresses this way to hosts. I’m not saying its wrong, only we don’t have the experience doing this.

@joe-schmitt Yes! I just tested most of the skins and it seems to work perfectly. Thanks for the update and the hard work!

Enterprise and Education versions natively support it.

@jpaul You’ll most likely have lots of problems using 1.2. I recommend you update to 1.4.4 - instructions are here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

@FantasyGamer @rwakc It’s back up now, thanks for letting us know.

@joe-schmitt hostnamechanger a power operation is pending, abording module. the post resumes several times without change name name and without integration. I do not have the possibility to post the whole logs I’m not at work. Tomorrow … Thank you for your help

@flipwalker More or less, yes. Of course this must mean the /dev/sda is ALWAYS the 500gb SSD, and /dev/sdb is ALWAYS the 1TB disk.

@imagingmaster21 Then follow George’s guide.

http://bobhenderson.org/pdq-deploy-fog-imaging-happiness-take-2/

Create that in inventory, and after the machines join the domain from the Fog Client, it’ll find em in the collection and deploy! It’s that easy!

@redbob said in Task taking too long time to begin after FOG Menu:

r8169

120 seconds sounds like a timeout (wait) for the initialization of the card.

Would anyone happen to have any info on the open source software “Jane” that Wayne Workman mentioned? Any help would greatly be appreciated.

FYI, while deploying / capturing you are forced to disable secure boot because the kernels are not signed, after deployment / capturing you can enable secure boot if you like (uefi only).

Regards X23

@stucraster You can ignore it or make changes to it. I don’t know if sysprep will disable the admin account or not. But the unattend.xml and setupcomplete.cmd files are the way to tweak the final OS to have the features you need. These files would be dropped into place just before you run sysprep. Actually when I build my reference image, I have a batch script that copies the files into the right location and then calls sysprep to ensure everything is in the right spot each time I rebuild the reference image.

@wayne-workman

Everything now works perfectly. As always you are the best.