Please see the fog wiki for a quick list of the most commonly used software pushed using snapins. Also feel free to edit and build on this current list. :)
Posts made by ssx4life
Fog Wiki: Supported Command Line Switches for Snapin's
How-to: Create a universal windows XP image using mysysprep.exe and VM Ware
I decided to throw together a really quick video walk through of how to create a universal windows xp image using fog.
In this demo walk through I’m using Windows XP Professional OEM + SP3 slipstreamed. I HIGHLY… [B]HIGHLY[/B] suggest that you use a vanilla OEM disk and NOT a stamped disk such as a dell / hp oem disk. These oem disks come with the hologram typically.
It’s also important to note that you can actually sysprep an OEM vanilla image. I’m using an OEM SLP key found here - [url]http://technet.microsoft.com/en-us/library/bb457078.aspx[/url] , and runing oemscan.exe after the machine is imaged to fully activate it on oem hardware.
To simplify things I’ve also included a copy of my sysprep folder (see below). This folder is ~50MB due to it including 2 driverpacks (mass storage / lan) for NT5 x86. It already has a pre-built sysprep.inf file you can edit and use for your own =)
- Create a Virtual Machine using Virtual Box or VM Ware.
- Make sure that the VM you create has an [B]IDE hard drive[/B] option selected (not SCSI) and a SINGLE PROCESSOR with [B]TWO CORES[/B]. Also make sure the lan is BRIDGED
- Install Windows XP Pro (OEM if you don’t have a VLK), or VLK if you have that license agreement and key
- Run all updates on the computer, install any software, configure the OS the way you want / etc.
- Capture a snapshot of the OS using the software (VM Ware has this built in, as does virtualbox)
- Simply download sysprep.zip and unzip the file and move it to C:\sysprep (if you are using windows xp pro vlk you will need to modify the supplied key)
- Run spdrvscn.exe and hit box #1, #2, #5 (save) and close the application
- Run sysprep.exe from a command prompt as follows “sysprep.exe -bmsd” This will run sysprep and pull all the mass storage drivers and lan drivers down into the sysprep.inf file
- Make any last changes you want to your image (if you are using a VM I suggest that you snapshot as you go along)
- Install the Fog client service
- Manually register the host by MAC address on the fog server. You can find this by running ipconfig /all
- Once registered assign it to a new computer image in fog, and select “upload”
- On the virtual machine run setupmgr.exe and modify the sysprep.inf to your liking (change the password / name / etc.)
- Once saved run mysysprep.exe and tick the box that says “run mini setup” as and then “reseal”
- Wait about 15-20 min’s for sysprep to run and shut down the VM
- Turn the VM on and smash F12 on your keyboard to PXE boot the OS.
- FOG will now boot and capture the image. =) You are set! This image will now work on any model hardware you throw it at (well just about)
The above steps are pretty cut and dry. If you have ever run sysprep.exe before on Windows XP most of this should be fairly familar to you. All that was added in this guide was we have added drivers using the sysprep driver scanner, and chanloaded mysysprep.exe instead of the standard sysprep.exe (giving us the ability to inject HAL’s into the install).
- sysprep.zip - [URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVZnhQUjRSaWFoNHM’][B]https://docs.google.com/open?id=0B6xOimbg2JqVZnhQUjRSaWFoNHM[/B][/URL]
- oemscan.exe (only needed on oem builds of Pro. Run the .exe as a snapin or manually + reboot. It will then be activated if run on a supported oem system (dell hp / compaq / etc.) with a supported OEM SLP key - [URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVS2R6bXFad1Rka28’][B]https://docs.google.com/open?id=0B6xOimbg2JqVS2R6bXFad1Rka28[/B][/URL]
If you have any questions let me know.
Thank you Boon for re-hosting / uploading these files while I was out of the states on work.
How-to: Modify your snapinclient.dll file to check in more quickly on a reboot
Just wanted to take the time to post a copy of a modified .dll file I obtained from MoellerAero over on the edugeek.net forums - [url]http://www.edugeek.net/forums/o-s-deployment/92417-how-modify-snapin-client-sleep-timer.html[/url]
By replacing this modified .dll it will auto check in for any snapin’s that need to be pushed to the client after 20 seconds of the fog service starting, not 5 minutes (which cuts down on the delay for software installs / reboots / etc.)
Simply navigate to c:/Program Files/Fog/ (or program files (x86) on a 64bit os) and replace the snapinclient.dll file with the one found attached below. Restart your fog service and you are all set.
I’ve tested this modified .dll and it works great. The only change to the file is the check in / sleep time. :)
I have gone ahead and updated my core base computer images around this modified .dll and had no issues at all. Please feel free to give it a whirl, and give MoellerAero a big thank you for editing the source and compiling the new file.
How-to: Remote control a computer using UltraVNC SC and the Snapin software
I just wanted to post a really quick and simple guide to creating a snapin for Ultravnc SC (single click) that will allow you to push a snapin to a pc, and then remotely control it.
This software works with Windows 2000 / XP / Vista / 7 (32bit / 64bit)
- A working Fog server (obviously)
- A client computer with the fog service installed and running
- A support computer that runs UltraVNC Viewer in Listen Mode (I’ve found that version 1.02 of the software works best) - [url]http://www.uvnc.com/downloads/ultravnc/81-ultravnc-downloads.html[/url]
- A copy of UltraVNC SC 2011 - [url]http://www.securetech.com.au/view-details/miscellaneous-files/uvnc-sc-2011-small-update-packager.html[/url]
To create a working snapin for UltraVNC SC all you need to do is download the file above and edit your helpdesk.txt file accordingly. If you have only a single [host] in the .txt file the executable will open and auto run, connecting you to the IP / host name you specify.
This software simply runs the sc client software and connects to the support computer that is listening on port 5500 (default).
Once you have a working tested version of this sc client software, simply upload a copy of it to the fog server as a snapin, link it to a host computer, and you can instantly push the software and connect to the pc.
This is really basic when it comes to steps and using the software, so I’m not going to dive into this too far ;) So far this is a great solution for our day to day tasks in the office.
More instructions can be found here if needed - [url]http://variableghz.com/2011/06/how-to-make-use-of-ultravnc-sc-single-click/[/url]
Also here is a full list of the available syntax for the helpdesk.txt file - [url]http://www.mail.uvnc.com/docs/uvnc-sc.html[/url]
How to: Modify the PXE boot menu to allow the booting of .iso files
There have been some really basic guides on the fog user guide, and some quick videos on youtube that show how to append the default file under the tftpboot folder in Linux so you can pxe boot your own .iso applications.
I just wanted to take the time and break down the instructions into a friendlier video that might help people a bit more.
To use this guide I’m assuming the following 6 things
- You have a working version of Fog (obvious)
- You have modified your TFTP password under the fog UI - [url]http://fogproject.org/wiki/index.php?title=Unable_to_connect_to_TFTP#For_Versions_.24_.2B[/url]
- You have a copy of the .iso you wish to boot (example: Dell Diagnostics)
- You have a copy of memdisk from kernel.org - [url]http://www.kernel.org/pub/linux/utils/boot/syslinux/[/url]
- You have an FTP program such as filezilla that will allow you to copy / paste / and append files on your fog server
- You can copy and paste + edit the following text below to meet your needs
[CODE]LABEL Dell Diagnostics
MENU MASTER PASSWD password
append iso initrd=fog/dell/delldiags.iso raw
MENU LABEL Dell Diagnostics
Dell™ Diagnostic software
Ok! ;) Now watch the video for a quick overview on how to create a folder under tftpboot/fog, copy over your .iso and memdisk file to the new folder, append the default file with a text editor under tftpboot/default.cfg
I just wanted to point out that the video also includes 720p so you can put it on high res and zoom in to see the detail, text if needed.
If you guys have any questions let me know.
RE: Deploying Storage Craft's Shadow Protect from PXE
To answer your question… “yes” but also possibly “no”
It all really depends on what you are attempting to use fog for in conjunction with WDS and how your network is segmented.
Long story short, in plain terms you can have only one DHCP server that controls or “points” to PXE that must be either FOG or WDS, not both.
You could use WDS for imaging and the fog client for software management, inventory, etc.
Or the reverse could be true and have WDS (if there is a client for it) do the management and image with fog.
Hope this answers your questions for you.
RE: Deploying Storage Craft's Shadow Protect from PXE
9 times out of 10 the limitation is on the client side if you load it via PXE into memory.
If your .iso exceeds the size of the client pc you run into issues with it not booting properly.
Hope this helps.
RE: Force Logoff
[quote=“ZeroSkillz, post: 10951, member: 3464”]Can you post how that was done? Thanks[/quote]
I don’t have a system in front of me to build a guide, but a quick and simple process is th efollowing.
- Go to the CLIENT computer and log in as admin
- Go go the c:\Program files\fog folder (I think it’s the fog folder)
- Locate the .ini file that allows you to make changes to the client software (fog client)
- Open the file in notepad
- Locate the line of code that mentions forced task reboot (or something simlar to that).
- By adjusting the code from a 0 to a 1 (or vice versa) it enables or disables the code for this.
- Save the file in notepad + reboot the fog service (services.msc) fogclient - restart service.
- Safe the file in notepad + reboot the pc.
I should note that if you have the fog client as an image you would need to make this change PRIOR to capturing and deploying it. Otherwise you would need to go to every client and make the adjustment.