Bugs in FOG 0.33
-
Hey guys. I’m running 0.32, not 0.33 but I wanted to share some insight to help the Windows 8 support for 0.33.
I set up a virtual machine running Windows 8 Enterprise with a single partition and uploaded it to FOG. I ran the fogprep exe which I had to modify because it does not support Windows 8 (I just commented where you check to make sure the machine is running Windows 7 because the registry keys being modified are exactly the same in Windows
and I ran sysprep with my unattended xml answer file. When I tried to download the image to another machine, I received an error at boot saying “Booting… Missing Operating System”. I dug into the fog source code with my boss and discovered that the issue is that there is a method that checks the os version and applies one of several mbr files that you have. Because Windows 8 is not supported and I selected Windows 7 as the host os on the fog web interface, it wrote the wrong mbr to the machine. After we copied the correct mbr from the Windows 8 master image and wrote it to the machine, it booted correctly. There still is a problem, however. The hard drive was not resized properly to the size of the new machine it was being imaged to. The new machine is showing only ~40GB which was the size of the actual fog image. Also, I the fog client is not working properly. It is not renaming the machine or joining it to the domain. -
We don’t sysprep for the pure fact that we don’t trust our users to make it through the first boot process. . it’s much easier to make an image for a certain model, setup everything just the way we want it and let FOG/Active Directory do everything Post-first boot.
-
[quote=“Jesus Jordan, post: 9263, member: 2573”]Hey guys. I’m running 0.32, not 0.33 but I wanted to share some insight to help the Windows 8 support for 0.33.
I set up a virtual machine running Windows 8 Enterprise with a single partition and uploaded it to FOG. I ran the fogprep exe which I had to modify because it does not support Windows 8 (I just commented where you check to make sure the machine is running Windows 7 because the registry keys being modified are exactly the same in Windows
and I ran sysprep with my unattended xml answer file. When I tried to download the image to another machine, I received an error at boot saying “Booting… Missing Operating System”. I dug into the fog source code with my boss and discovered that the issue is that there is a method that checks the os version and applies one of several mbr files that you have. Because Windows 8 is not supported and I selected Windows 7 as the host os on the fog web interface, it wrote the wrong mbr to the machine. After we copied the correct mbr from the Windows 8 master image and wrote it to the machine, it booted correctly. There still is a problem, however. The hard drive was not resized properly to the size of the new machine it was being imaged to. The new machine is showing only ~40GB which was the size of the actual fog image. Also, I the fog client is not working properly. It is not renaming the machine or joining it to the domain.[/quote]Hopefully this (windows 8 support) is rectified in version .33 because we are having the same problem. Curiously it does occasionally work but only on certain machines. Also fog client from memory did work, it renamed and installed snapins?
-
This post is deleted! -
Found a visual bug on the login form. If you switch languages, the names and fields would get all out-of-wack. The diff file I have attached should fix the issue (tested in the latest FF, Chrome and IE 9), just add a .diff to the end if you’re using svn.
[url=“/_imported_xf_attachments/0/216_fog.css?:”]fog.css[/url]
-
I’m going to attempt to throw .33 on a DELL PowerEdge R620 running Ubuntu 12.04 LTS.
All the systems I need cloned are EXT4 and this is my last shot. I will keep everyone informed.
The machines I will be cloning are HP Z620’s running Ubuntu 12.04 LTS- Install went smooth.
- Imaged first computer/workstation. FOG detected the partitions as EXT3FS even though they are EXT4… any work around?
-Partitioned first computer/workstation as EXT3. Booted fine.
-
Any solutions? I thought the .33beta allowed EXT4 imaging?
-
The cloning package used by default does not support ext4 and I don’t think the conversion to a newer cloning package has been finished yet. I forget if it’s partclone to partimage or vice versa, but either way it’s going to take a lot of testing to make sure it doesn’t break existing functionality and may get pushed to 0.34 depending on workload and time tables.
If you just MUST clone linux systems, they have to be ext3, or you can use a different product for now. That’s the best I can tell you.
-
Ummm… If you need clone a ext4 partitions, you can do a RAW or dd image. This way is slower than a normal way.
-
[quote=“falko, post: 9221, member: 48”]just to double check, when I set up my FOG 0.33 test vm, all I need to do is Import the Host Inventory cvs from my FOG 0.32 box? Following the format provided from the Web Interface cvs ‘Import example’ sheet?[/quote]
Feedback, though I am guessing the DEVs are aware already. using the latest svn: 898 the above import attempt does not work.error [CODE]FOG DEBUG: FOGPageManager: Class: ReportManagementPage, Method: upload, Error: Method not found in class, defaulting to index()[/CODE]
-
using SVN 898 I have also been unable to import my sql host file from my production 0.32 box, anyone able to test importing??
-
The database schema has changed between 0.32 and 0.33, so you can’t just do a export/import because the tables no longer line up. The devs were working at one point on getting a conversion script together, but I’m not sure if that’s still happening or what state it’s in.
-
okay, what is the recommended way to bring my hosts across? ie moving to a new ubuntu server as well as upgrading to 0.33.
Build the new server as 0.32, import from older 0.32 server, then upgrade the newer server to 0.33note: I am aware 0.33 is in beta, just speaking on testing terms
-
As this point I’m not really sure. I’ve only been somewhat involved in the development process, so I don’t know where they’re at with the upgrade path from 0.32 to 0.33. The code is the best (only) documentation for that at the moment, so I’d say give it a try on a test machine and let us (the community) know how it goes.
-
As a New Forum Member Im currently downloading this eval addition to see if I can offer any opinions on this new version. I also hope that there is headway made to get this new release finished soon… I know that with previous versions updates were avail. almost like clock work… and being this is a completely new version, i know and expect major delays based on GUI enhancements and Kernel Upgrades… Im very anxious for a more robust and up to date version. We are expected to roll out newer Win7 and now Win8 PC’s where we have had issues with capturing images in the past… we hope the new releases will solve some of our original headaches…
I must however commend all of the community and the Development team and coders for all the Time and Effort put into coming up with a new (FREE) cloning software solution. Godd Bless the OpenSource file community.
Thank you Very much
Bill -
I am trying to download the Tarball, how ever it gets to about 800meg and then gives me a network error. will not resume either…
- how big is this file?
- is there any other site i can get this from? Anxious to install and test as well. Im trying to download from “[url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/[/url]”
-
Around 50meg.
You want to download the latest trunk. freeghost.svn.sourceforge.net/viewvc/freeghost/trunk/ -
If there is an official tarball of 0.33 then it’s news to me. The command I use to pull down 0.33 from SVN is:
[CODE]svn co https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk /opt/freeghost[/CODE]
If you don’t add “/trunk” to the end of the URL it will pull down the entire history of FOG, which is probably over 1GB. -
-
I downloaded .33 last week to try out Win 8 support. I created my image using basically the same process I used for Win 7 and it works just fine. Obviously there are some things missing in the UI (when I tick the shutdown option when deploying something, it doesn’t work, for example), but the actual process of taking and deploying an image seems to work just fine.
I created the image in virtual box and customized it using audit mode. Then I ran sysprep (not fogprep – FP never worked for me in Win 7) and deployed it using the Microsoft unattend file. I’m running .33 beta on Ubuntu 10.04.
I’ve created/deployed 4 different images (playing around with the unattend file). FOG worked perfectly every time.
I’m not sure if adding Win 8 support is the biggest change for .33 or not. If so, then as far as I can tell, the hard part is done
