Posts made by chad-bisd

Did you see the thread about Ubuntu 14.04 and the changes to the apache2 documents directory changing from /var/www to /var/www/html

You can use the copyprofile command if you want to setup a bunch of stuff and save it as the default profile. It works, mostly. But I ran into the case of most things I wanted to be part of the default profile were not included in the copyprofile specifications. Also, copyprofile has issues if you have more than one user profile on the base image, which you shouldn’t if you are using sysprep to create local accounts and audit mode to run everything as built-in\administrator. Remember that sysprep copies the profile and then deletes it and disabled the built-in\administrator account before going into OOBE.

If you are getting the FOG menu on PXE booting, then you do not have the correct 01-[mac-address] file in your tftpboot folder maybe?

I have 2 images for each hardware platform I use (I don’t use driverpacks or golden images). One is audit mode before I run sysprep or rearm anything, the other is after I have run my rearm scripts and sysprep and shutdown. I use the audit image to update the base image, and the sysprepped image (in oobe) to deploy to hosts.

With that being said, all of my reading has led me to believe that in order for each office install to be unique, it must be rearmed before being deployed (cloned). I do this because I have windows 7 clients that must use KMS to activate in addition to the Windows 8/Server2012 clients that can use ADBA. I cover my bases. And with the rearm as part of the oobe image and not the audit image, I never run out of rearms because the base image never gets rearmed (only the image that becomes the oobe image for deployment).

Please start your own thread and link back to this one if it contains pertinent information.

Can we call it 0.33rc1 instead of 0.33b, and can you tag the svn at the revision number we should be testing against? Thank you.

which version of Ubuntu, and did you make sure to update the system before you run the FOG installer? (sudo apt-get update, sudo apt-get upgrade)

I do not currently have any Windows 8.1x64 clients that I deploy. All of our tablets that run Windows 8 are 2GB RAM, so no need for 64bit.

The main differences will be in the unattend.xml file, which is specific to 32 or 64bit. The sections and answers are almost the same, but have different paths (32/86 changes to 64). If you installed DISM and made an answer file, just look at the 32 bit one and answer the same questions with the same answers, just in the 64bit paths.

The setupcomplete script will remain almost untouched as will the CopyFiles-RunSysprep.bat, with changes made for filenames that changed.

Try this wiki article: [url]http://fogproject.org/wiki/index.php/Active_Directory_-_FOG_Setting[/url]

Let me know if any particular section is confusing or lacking information.

I think the Linux community is abandoning UpStart altogether and instead going to use Systemd. I know Ubuntu had hesitation, believing Upstart was a better system, but this problem goes to show you it had its flaws

You’ll need something on the windows side that can imitate wget for querying the fog server for image and os info, and can submit the results in POST format back to the fog server. The inventory part, I’m not sure, it might just be easier to avoid that during registration and call a hardware inventory task later.

If you look at the main bing/fog script in the init file, look for the code that handles the mode=manreg, I believe it calls fog.man.reg script. In that script, you can follow it along as it prompts for options and then submits those to the web server for registration, then calls doInventory, then submits the inventory info to the server. Somewhere in there, the option to image now is given and the result is either passed along, or used to call a web script that sets up the imaging task.

What you’re trying to do might be possible if you can get the hostname, mac, imageID, OS ID, and answer to “image now?” question. You just need to collect this information and then send it to the proper web scripts, imitating what the FOG scripts do from within the init.gz.

Registering a host is basically passing info to a web page, processing the result, and moving to the next step to setup the image task. If you look at how the scripts in the init.gz do it, then you can “fake it” as long as you can collect and submit the data to the same URL from your batch file.

Did you sysprep or FOGprep before taking the image? If you didn’t, and don’t want to, just run the Windows 7 repair disk and let it fix it.

Have you checked out this thread yet? [url]http://fogproject.org/forum/threads/how-to-setup-a-fog-storage-node-without-installing-fog.4294/[/url]

from you FOG server command line, see if you can ftp into your NAS using the username “fog” and the password from the setting. Then see if you can issue a mv command on a file, create a file, and delete a file.

Depending on the systems manufacturer, there may be a utility that you can run on the machines to change the BIOS boot settings from within windows.

When you select an option from the PXE menu, such as Full Host Registration and Inventory, FOG always uses the default bzImage. After a host is registered, you can specify which kernel to use for all tasks created and scheduled through the FOG web UI. If you have to manage multiple bzImage files for compatibility reasons, use the “Host kernel” setting for each host to specify the kernel that works best for that system. You can also group hosts, and update all host kernel settings for particular group of hosts. Just remember that groups in FOG 0.32 are a bit unusual. They are used for changing settings on all hosts in the group, but will not show your existing group settings.

if you get past the point of downloading the init.gz and have a problem, it’s driver related and you probably just need a kernel with compatible drivers compiled in, such as Tom’s. Make a backup of your /tftpboot/fog/kernel/bzImage file and then copy the new file your downloaded to the same folder and rename it to bzImage

Then try to register the host again.

[SIZE=3][FONT=arial]you need to create a user account on the windows server named “fog” with the password from the fog user (Other Information -> FOG Settings -> TFTP Server -> [COLOR=#333333]FOG_TFTP_FTP_PASSWORD). Give this user FTP access to the directories you are storing your images. At the end of the image upload process, FOG uses ftp to move the image from the images/dev/[mac-address] folder to the /images/[imagename] folder or file, depending on image type.[/COLOR][/FONT][/SIZE]

[SIZE=3][FONT=arial][COLOR=#333333]It does this using “fog” as the username, and the password value from the setting mentioned in the above paragraph. The password is not encrypted, just create it as-is. It’s complex because it’s only ever used by the FOG system or an admin testing/debugging. [/COLOR][/FONT][/SIZE]