How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
-
It would increase network traffic, but when testing this with wireshark on my network I didn’t notice too much of an increase in overall traffic.
The pro’s of having this solution is reduced image and deployment time. The con’s being a slight increase in overall network traffic (but marginal on a 450 - 500 networked system here at work.
Let me know what you find in your overall network traffic, I’m curious.
thanks.
-
Another question: I don’t have any compilers I can use to recompile the .dll file. Would the file you provided, work when I stick it into the FOG folder? Or would I need to recompile it? Thanks!
-
[quote=“variable205, post: 3357, member: 359”]Another question: I don’t have any compilers I can use to recompile the .dll file. Would the file you provided, work when I stick it into the FOG folder? Or would I need to recompile it? Thanks![/quote]
Sorry for not getting back to you sooner.
The .dll I provided goes in the client folder (C:\program files (x86)\fog) or just program files on an 32bit os.
You don’t have to re-compile it, it’s already been modified for a 20 second check in time
-
Excellent! Ty ssx, I’ll go ahead and start regulating my current bandwidth before I implement the .dll file. We got our network worked on and now we got a whole heck a lot of more bandwidth. We’ll see how it goes!
-
You may want to start small and monitor your network traffic while implementing this. I didn’t notice any large scale increase in overall network traffic by YMMV.
Remember you can switch back at any time by swapping the .dll back and restarting the fog service.
Enjoy.
-
I think I came to the conclusion that I’ll just stick the modified .dll file into my “guinea pig” computer only, when I want to test out some new snap-ins I’ve made. If I can conclude that the snap-in works, I wouldn’t have to worry about having the recipient computer waiting 5 minutes. Therefore, I feel as though there isn’t a need to put it on all of the computers on the network.
Thanks for the file though! it’ll definitely help me in the long run!
-
I have lowered the initial snapin client wait from ~5.5minutes - 8.3minutes to 30seconds - 60seconds for the 0.33 release.
I cannot see any issue in lowering the initial wait time. The client simply performs 1 HTTP request.
Your browser does at least 20 - 30 of these every site / page. -
[quote=“Blackout, post: 3607, member: 1”]I have lowered the initial snapin client wait from ~5.5minutes - 8.3minutes to 30seconds - 60seconds for the 0.33 release.
I cannot see any issue in lowering the initial wait time. The client simply performs 1 HTTP request.
Your browser does at least 20 - 30 of these every site / page.[/quote]
I see! Duly noted. I was just reporting back from my guinea pig computer and it turns out the .dll file didn’t lower down the snapinclientmanager “query.” It still remains at 5 minutes; I must be special
-
The client (including the snapin dll) has not been recompiled yet. This will be done when 0.33 is released.
-
[quote=“Blackout, post: 3723, member: 1”]The client (including the snapin dll) has not been recompiled yet. This will be done when 0.33 is released.[/quote]
Excellent
-
Hi,
iam gonna try to recompile the msi myself, if i have success i will upload the new msi for the time till 0.33 rises.
Greetz X23
-
Hi,
[quote=“Blackout, post: 3723, member: 1”]The client (including the snapin dll) has not been recompiled yet. This will be done when 0.33 is released.[/quote]
[quote=“variable205, post: 3753, member: 359”]Excellent :)[/quote]
Here we go…
i have recompiled the msi pakage for two ways,
faster snapinclient.dll & faster snapinclient.dll and no fog tray autostart entry.See attachments.
Greetz X23
[url=“/_imported_xf_attachments/0/323_FOG Service Installer_fastsnapinclient.zip?:”]FOG Service Installer_fastsnapinclient.zip[/url][url=“/_imported_xf_attachments/0/324_FOG Service Installer_fastsnapinclient_noautostart.zip?:”]FOG Service Installer_fastsnapinclient_noautostart.zip[/url]
