No, OOBE is for making the machine into a Like new Out Of Box Experience. Audit Mode is a tool to use during an Image setup process, that requires the finalization of the OS so it can (if you supply an unattend.xml) make your Installation autonomous.

The Audit mode is where you get to windows BEFORE the OOBE process happens. You are suppose to install all your software at this point then sysprep and upload, On first deploy the installation will answer the installation questions with your provided unattend.xml and complete the OOBE process (generalizing the installation so that new drivers can be applied to the system, cleaning some registry values and other secretive windows type things).

Really, there isn’t much difference in if you just install the software as a user and push your image, except the generalization processes which allows the machine that you are imaging to have their own hardware identifiers and unique strings which will be required for activation. This is only really important if you activate to a KMS server or if you join to an active directory environment (speculation have not tested I am not AD).

Try it, tell us what does and does not work if you don’t sysprep, that’s really the only thing I can recommend.

Personally, I read many tutorials before I began pushing windows 7. each one mentioned using Audit Mode to install my software and drivers before completing the generalization process, and I have had marginal success in doing so.

Hope this helps!

You technically could but why would you want to eat up server space to keep your “server” back up on it? We already have SSH servers I merely utilized what was already there, but in theory yes, you can use fog, to image fog servers

[quote=“RLane, post: 35127, member: 23505”]Regarding the first part of your e-mail, there is a much more efficient way of doing this that doesn’t involve imaging. Look into Deep Freeze. It resets any changes made every reboot or logoff.[/quote]

Please note that Deep Freeze relies very heavily on WOL, you need to configure your settings properly, you can even set a schedule to have your labs shut off at a certain time, accept windows updates, even run batch files.

Personally, I would use a separate SSH box and clonezilla. I have used this method to set up a replacement server when I have caused problems on a working environment server.

FOG version 1.2+ supports imaging of linux partitions. I do not know of any documentation tailored towards this yet, but I do know that the linux partitions are supported. You will want to use ext4 partitions, but version 1.2.0 fully supports this

Try using the ip address instead of the ds.feb.br, what happens?

just a heads up in windows you will want to use the following command
[code]
tftp x.x.x.x get undionly.kpxe[/code]

the -v and -c should not be required.

Have you also disabled the windows firewall?

What serves your DHCP?

what kind of network equipment exists between FOG and the windows machines?

[quote=“Leandro Silva, post: 35095, member: 24513”]Hello

i’m trying to make the install but i’m having a lot of troble with the tftp, if i’m in the fog server i can test the transference successful with this command:
tftp -v ds.feb.br -c get undionly.kpxe

but when i try to do the same from a host i get a time out i already tried two tftp clients for windows and get time out from both, i can connect to the fog and ping it but not use tftp.

I already tried to disable ufw and i get the same error.

I’m using Ubuntu server 10.04.4[/quote]

Open a thread in the correct section, this thread is suppose to be the instructions to set up only, not a discussion on the issues and how to solve them.

Have you tried using the undionly.kkpxe file instead?

just make a post in the feature request section

If you have other ideas on how we can make the GUI a little more friendly, please let us know!

You can always try a test bed, pull the fog server from the network, supply DHCP and use a hub to make sure that you can pxe boot the machines, if FOG works that way, you can step back through the hoops and put the FOG server back into the network and begin troubleshooting network settings, equipment, and possibly set up a service to help circumvent the issue.

Let us know how your tests go and if all else fails we need to set up a test network and verify that the server is functioning properly before we send you on a goose chase hunting network settings.

Because FOG is meant to CLONE to multiple machines. Typically you won’t have to mess with the partitions unless it is in fact a new or blank disk. To be expected. In the olden days you had to create a partition before you could install an OS. Same base here. FOG doesn’t take it upon it’s self to start writing partitions free willy nilly. Imagine if your deployment failed a few times and then you checked the machine to find 40 partitions, sure it’s not that big of a deal, but it’s daunting and scary, and your data would be gone, so Imagine accidentally clicking the Deploy button instead of Upload on your golden image, and it starts down the path and the first thing it wants to do is make partitions, and now all your work is gone…

I have made the suggestion to include a step that will write a blank partition to a disk (if you check the box during deployment) but NOT an always on (default) selection.

so [B]FIRST[/B]

Yes, it does suck to have to touch the machine to create a partition, but it isn’t something that needs to be done on each deployment, if you add a partition and register to fog, you can continue to image that machine indefinitely until something destroys or removes the partitions again.

I am not sure why it is required, ( I bet Tom does).

Again I have made the suggestion to include the option as part of the “deployment” option, but we are actively working to solve real issues rather than ones that can be worked around, and not that often to occur.

[B]SECOND[/B]

I agree with you on the FLAG we should at least get a proper response when imaging and it fails due to a lack of partitions, a warning or an error log where I can check the actual reason would be nice. A check before it completes the job would be nice too! And it has been suggested already

You hit the nail on the head with the last comment (of section 2) there “Of cause, now adays, almost every (Windows) PC is delivered with a partition. i Assume that’s the reason why the board is not full of reports like this.” you are absolutely correct. Many of us are using a mass production model of PC and it comes with an OEM OS on it (so it has partitions) so we can just nuke the information and carry on dancing. The only time this is an issue is if you receive a hard drive replacement from the manufacturer, or you replace the drive with a brand new one, then you need a partition for FOG to store information to.

I don’t have anything to say about the VM machines. you are correct, using this “work around” with a virtual machine could be cumbersome.

I have no expertise on the [B]third[/B] set of questions

This isn’t a bug this is a feature request -.-

The SVN is bleeding edge, it is not recommended for production environments as we are actively working on bugs and fixes.

It will ALWAYS appear as the “not the current version” in the GUI because you are on a subversion that does not match the current SUPPORTED version. This won’t cause problems and is merely cosmetic, however it is the test bed where we actively work to find solutions to issues user post. It is not WRONG to use the SVN, but if you plan for a production environment, it would probably be better to at least start with the supported version and if you have issues we will tell you to install the latest release in the SVN.

The sourceforge link is the current supported version.

I would start by installing a recommended OS, Ubuntu 14 is NOT a recommended OS.

If you like Ubuntu, try Debian 7.4 or 7.5

You should be fine using VMWare but be warned, it will be slow.

That I why I created a guide on how to use the Debug system of FOG to create a partition. You need to have A partition on a hard drive if you plan to use it with fog.

[url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]

It’s called Quick Format to NTFS but this is misleading as the partition that is actually written isn’t NTFS, but it does create a partition and imaging can be completed.

You can use the following commands, you may want to back up your old kernel, I have included the steps to do so as well.

[code]
cd /tftpboot/fog/kernel
sudo mv bzImage bzImage.OLD
sudo wget --no-check-certificate http://mastacontrola.com/fogboot/kernel/bzImage32
sudo mv bzImage32 bzImage
[/code]

Is this an upload or a download job?

Personally, I wouldn’t. I would scrap Ubuntu and install on Debian. The only reason I say this is because in 14.04 Ubuntu made changes to a number of services that have deviated from the original Debian base and this has caused issues.

I believe that updating the kernel could solve your upgrade issue, but I’m not sure that it wouldn’t break services.

That being said, I haven’t really delved into Ubuntu since 13.04 other than for a test install here or there to troubleshoot. I have started using Debian and it works just as well as the Ubuntu install, (if not better now that Ubuntu is changing things).

Let us know if you decide to update the kernel and if you have an issues!

I had the best success letting linksys do the DHCP when I used DNSMasq as well.

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

[quote=“Phantox Jada, post: 34379, member: 25158”]I didn’t put in my DHCP server IP. I put in the actual fog server IP. I do not know if that was the correct thing to do, but everything is running now.[/quote]

That is the correct thing to do, that is what the documentation tells you to do!