[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
Posts made by variable205
-
RE: How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
-
RE: [SnapIns] "Interactive services dialog detection" Popup
OH!! I didn’t know it was that simple, I thought there was something else I was missing. Nevermind then
-
RE: [SnapIns] "Interactive services dialog detection" Popup
I’m having this issue when I’m deploying a printer on my Win 7 as well. (It fails to deploy, but thats aside the point). I would also like to know how to disable the fog tray
-
RE: How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
[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 -
RE: How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
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!
-
RE: How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
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!
-
RE: User self service snapins site
I agree. This would make an excellent addition to an already fantastic system! Instead of using a user name (via Active Directory, etc) to log into FOG, let the computer name that’s already registered with FOG be the means of authentication.
Therefore if the computer isn’t registered with FOG, it cannot log into FOG.
-
RE: How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
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!
-
RE: How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
Really quick (possibly stupid) question, with the amount of computers that would periodically check the FOG server for snap-in pushes every 20 seconds, would that bog down the overall network bandwidth?
-
RE: Can't connect to FOG website
Nevermind I was able to fix the issue. Basically what had happened was that somehow the connection of “auto eth0” didn’t have the correct ip configuration settings because when I typed in the “gateway” Ip address section, the IP “vanished.” I just figured out that one must hit “enter” after you type in the IP address in the gateway IP address section. How annoying.
Very noobish mistake and now I know for next time.
-
Can't connect to FOG website
Hey Guys,
My old FOG server just fried. So I went ahead and literally took out the hard drive from the server to another server (different models) and now FOG can’t be contacted via web portal from a client computer. I’m able to do a “localhost/fog” on the server just fine, AND I’m also able to boot to FOG via PxE.
There’s gotta be something I’m not seeing or not doing right. Any suggestions and ideas are welcome! Thanks in advanced.
variable
-
RE: Using FOG with older computers that can't boot via PxE
Thank you! And also thanks for pointing out the CD and floppy drive options too
-
Using FOG with older computers that can't boot via PxE
This tutorial is for those who have computers that do not have PxE and still wish to use FOG Project to upload and deploy images. The tutorial is [U]also[/U] useful for the computers that “freeze” during the DHCP sequence (I just used this today when the PxE wasn’t working properly).
First off, one must need the following three things:
-gPXE ([url]http://rom-o-matic.net/[/url])
-Win32DiskImager ([url]http://sourceforge.net/projects/win32diskimager/[/url])
-A flashdriveFirst off, go and download both gPXE and Win32DiskImager.
Select the first link ([URL=‘http://rom-o-matic.net/gpxe/gpxe-git/gpxe.git/contrib/rom-o-matic/’]gPXE git (current-top-of-git-tree) Image Generator[/URL]) within the rom-o-matic website. Then please choose the “.usb” format and download it by clicking on the “Get Image” button. Rename the “.usb” part at the tail end of the name to .img. (Example: gpxe-1.0.1±gpxe.usb to gpxe-1.0.1±gpxe.img).
Next, obtain the Win32DiskImager program. I personally chose the [B][URL=‘https://launchpad.net/win32-image-writer/0.5/0.5/+download/win32diskimager-binary.zip’]win32diskimager-binary.zip[/URL][/B] link because it works for me. Then go ahead and execute the program.
If you haven’t already; plug in the flash drive. Upon execution ofWin32DiskImager, click on the folder icon next to the textbox. Navigate to the gPXE image and select it. Your flash drive should already be selected from the drop down list (to the right of the folder icon). If not, click on the drop down box with the appropriate drive letter.
Click on “write.” There you go, you now have a working PXE boot for a non-PXE booting computer. In order for the computer to boot into PXE, choose the flash drive on the computer’s startup and gPXE will take care of the rest.
–variable205
EDIT: Win32DiskImager had a broken link: replaced it with a newer one
-
RE: Future thought
I know you may not want to see a non-fog related solution, but the “Alerter” and “Messenger” services within Windows provides this type of functionality. In command line (if of course you’re the admin) you can send something like:
net send <hostname of computer> <message>
One example is: net send labComp7 Failure to comply with the proper use of computers policy will result in automatic shutdown of this computer or something…
These alerter and messenger services are disabled by default on Windows. I know there’s a way to remotely enable them, but can’t recall how.
-
RE: Fog Printer won't deploy
[quote=“Tony, post: 1401, member: 522”]I can’t seem to get my printers to deploy from fog. The fog log says:
2/15/2012 2:35 PM FOG::printerManager Printer update was request from fog tray…
2/15/2012 2:35 PM FOG::printerManager Management level = 2
2/15/2012 2:35 PM FOG::printerManager Removing unwanted printers from host…
2/15/2012 2:35 PM FOG::printerManager Adding new printers to host…
2/15/2012 2:35 PM FOG::printerManager 1 found on server side.
2/15/2012 2:35 PM FOG::printerManager Installation requested for Innie
2/15/2012 2:35 PM FOG::printerManager Printer Installed: Innie
2/15/2012 2:35 PM FOG::printerManager Setting Default Printer…
2/15/2012 2:35 PM FOG::GUIWatcher Message found, attempting to notify GUI!
But the printer never shows up in control panel
Help[/quote]Sadly, I wasn’t able to make an install for local printers. HOWEVER, we went and set up a Windows printer server which contains both of the 64-bit and 32-bit drivers for the printers (obviously because we have 32-bit computers, and the server is 64 bit), and we just use the “network printer” option and type in \printerserver\printer_name. Of course, you have to make sure you’re sharing the printer from the server too :).
-
RE: Feedback: Snap-in system
I would absolutely love to see another application to create snapins. Because unfortunately, InstallRite seems to be a “hit-or-miss” problem. Not to mention, I’ve also used another custom build repackager called “AppDeploy” which has the same concepts as installrite, but converts it into an MSI form. (There’s other little handy features it comes with as well!). However, when running MSI’s and putting in arguements and everything needed to run the MSI snap-in; sadly it fails because the account for which it is to be installed on, does not have the permissions