@Olduser What the image sysprep’d? Did you include the 9020 drivers into your golden image? But the likelyhood if you sysprep’d the image then the native win10 drivers will probably work on the 9020. Other issues, is the 7760 in uefi or bios mode? The same goes for the 9020? You can only capture and deploy uefi based images to uefi base target computers. You can’t mix bios hardware with uefi captured images.

Sebastian,

I was able to Register Windows10 Host and it is working. What a fantastic jobs, all of you people are doing.

Thank you for all your hard work.

Olduser.

@Wayne-Workman There’s already reports for this. Login History, and Hosts and users.

This would not present the info on the host management page.

A hook can/should be used to perform this if you really feel it necessary though.

Tom & JJ,

Thank you for your help. I will make changes to batch script and add full path to networkdrive and modify my script as you both suggested. On last Friday before going home. I un-installed the FOG client on PC , re-installed it and my batch script was there. I waited for about 1/2 hours to see if this file gets deleted from C:\Program Files\FOG\temp folder but it was still there. I will follow your suggestions and let to you know.

Thanks,
Olduser

@Olduser said in Snapin not working properly:

(1) Do I have to select ‘Reset Encryption Data’ on host because once I reset encryption data, the snapin works quickly.

That only seldom needs done, it’s for when the encryption between the server and host gets screwed up. The intention is for the encryption to not auto-heal thus putting the admin in charge. Because if it auto-healed this would be a vulnerability that could be exploited.

As a rule of thumb though, before I do anything concerning a single host or large groups in fog, I reset the encryption on that host/group prior to deploying my work. This seems to make things go a lot more smoothly but it might not be best practice. Maybe the @Senior-Developers can weigh in on why we need to reset encryption so often.

(2) Can I combine ‘/i and /c’ for Snapin Run With Argument? I am using Normal Snapin.

Try it first. At the bottom of the snapin area, you’ll see the sanpin command. If you take your snapin file and put it in a directory on your computer, and then cd from an elevated command prompt to that directory, and then run this snapin command, it will run just as the FOG Client would run it, minus running as the SYSTEM user.

(3) What arguments should be for ‘Snapin Arguments’? I put /qn. Is this correct? I could not find these arguments value.

Whatever you need them to be. For instance, with Smartboard Drivers and SmartNotebook you can pass the license key as an argument. For Faronics Insight you can pass the channel number. For an old typing program called MicroType you can pass the server address. You are not limited in what you can pass or how many things. Fog will use what you put in there, but if it’ll work or not with the file your pushing is entirely dependent on the exact thing your pushing. Read about deployment strategies on the vendor’s site and look for examples. Also, any error codes in the C:\fog.log file after a snapin runs is not an error from FOG or the FOG Client, the error code is from the program you ran with snapins.

Does this make sense? Feel free to ask more questions.

@Olduser are you creating a pack or a normal snapins?

@Olduser Normally this is an FTP issue (as ftp is used to move the image from the /images/dev to /images folder).

Please run through:

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@Olduser said in Windows 7 64 bits image:

Again I like to thank all of you for doing wonderful work.

so true 😉