Latest FOG 1.0.0
-
[quote=“Tom Elliott, post: 26876, member: 7271”]Just make the guess, that because you’re scheduling tasks on the Server side, that the information is from the client’s point of view. If you’re “downloading” an image, it’s being “Downloaded” from the server and being placed on the client. If you’re “uploading” an image, it’s being “Uploaded” from the client and being placed on the server.[/quote]
Yes but it’s not logical for me… sorry.[quote=“Tom Elliott, post: 26876, member: 7271”]If your HD Size is 320 GB, but the HD you’re trying to download the image onto is 80GB, you simply would need to use the Imaging Type you’ve already determined. Single Partition (NTFS Only, Resizable) will resize the image before uploaded to the smallest possible size + 5% of the size on the free space on the drive. If you want to be able to put the image on an 80GB drive, you would need to ensure the data size on the “to be uploaded” drive uses less than 80GB. If you’re using this imaging type on Windows 7, before you can upload a resizable image, you also need to sysprep/generalize the system as well.
All that said, you still don’t get to tell the system, directly, what size you “WANT” it to be because it’s all based on the used disk space. If your image is 140GB of actually used data, you can’t tell the system, only image the first 70GB. Imaging just doesn’t work that way.[/quote]
No, it’s the inverse problem :- source HD = 15 Gio
- client HD = 320 Gio
I would want to deploy the image on the client with a size of 80 Gio and not 320-5%.
-
[quote=“aruhuno, post: 26880, member: 105”]Yes but it’s not logical for me… sorry.[/quote]
That’s okay, I don’t know how else to change it though.When you “download” an image, you’re placing it on the client from the server.
When you “upload” an image, you’re placing it on the server from the client.
[quote=“aruhuno, post: 26880, member: 105”]
No, it’s the inverse problem :- source HD = 15 Gio
- client HD = 320 Gio
I would want to deploy the image on the client with a size of 80 Gio and not 320-5%.[/quote]
So you’re trying to limit the size of a larger disk to be that of only 80GB?
FOG wouldn’t be able to perform this trick for you, but if you still do the Sysprep information I recommended to you before, then you can specify the ExtendPartition to be that of the size you want for that particular system.
-
[quote=“Tom Elliott, post: 26882, member: 7271”]So you’re trying to limit the size of a larger disk to be that of only 80GB?
FOG wouldn’t be able to perform this trick for you, but if you still do the Sysprep information I recommended to you before, then you can specify the ExtendPartition to be that of the size you want for that particular system.[/quote]
Perfect, thanks ! -
Hey tom hows has everything been I see i missed alot where up to 1.0.0 now. I am rebuilding my labs as we speak and should be ready to help test again soon.
-
Everything goes pretty good Troye, hope everything is well.
Everybody:
r1667 released,Hopefully fixes many of the issues found with undionly.kpxe giving sporadic timeout issues.
-
Hello!
It’s me, again ^^
Could we explain me how to add sysrecueCD please? -
[quote=“aruhuno, post: 26946, member: 105”]Hello!
It’s me, again ^^
Could we explain me how to add sysrecueCD please?[/quote]you mean adding an ISO to the Boot menu?
-
[quote=“falko, post: 26949, member: 48”]you mean adding an ISO to the Boot menu?[/quote]
I would be interested in knowing how to do that as well
-
[quote=“Tom Elliott, post: 26866, member: 7271”]Fog does clean the drives first. But only on the download task. Creating the initial image is completely up to you. I wouldn’t have the “FOGGIEST” of idea’s on what it is you’re planning to do to actually have FOG create the image for you. I hope this makes sense.
If you’re trying to make an MBR style OS on a disk that originally in GPT format, you have to make sure all is well.
Converting from GPT to MBR has some quirks. Converting from MBR to GPT is fairly easy with some minor modifications. FOG wouldn’t have any interaction in this process.
The reason why this is all important to know is because, if GPT is “present” on the Disk, FOG 1.0.0 will create a backup of the GPT partitioning table. GPT is present in many cases if you don’t properly wipe the drive and partitioning tables prior, especially if your OS came preinstalled with UEFI enabled on the system.[/quote]
I redid the test in a virtual machine. Still not working. The same result. Please check the pictures. I can’t figure what am I doing wrong…
[url=“/_imported_xf_attachments/0/754_vm.png?:”]vm.png[/url][url=“/_imported_xf_attachments/0/755_vm1.png?:”]vm1.png[/url]
-
[quote=“falko, post: 26949, member: 48”]you mean adding an ISO to the Boot menu?[/quote]
Yes, because I don’t understand how to do that with the new PXE -
Thanks!!!
-
this is a good place to start for your options with the Advanced Boot menu options
[url]http://fogproject.org/forum/threads/fog-0-33b-edit-pxe-menu.10403/#post-26419[/url] -
did the install to 1.0.0 now when I try to install/update the database schema, i got you my web gui url and it just says unable to connect to database.
-
did you update your password in fog/commons/config.php after the install?
-
I did not…am I suppose to update it to the username and password it gave me as default user or as my password?
-
nevermind, I got it. My password was missing from database_password. Thanks for letting me know where to look though. Still learning as I go…
-
So… are we still using svn for udpates?
-
you can, if you want to be on “the bleeding” edge. Right now it’s the exact same as the release.
-
Ok. I like the bleeding edge!
I was just unsure if the “fog_0.33b” folder in subversion was going to change.
-
there was never a fog_0.33b folder. You create the name.
[code]svn co https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_0.33b[/code]If you want the name changed you would just mv the folder to the new name.
or recheckout and change the folder name:
[code]svn co https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_1.0.0[/code]
