Latest Development FOG
-
Your domain join issue looks like it’s reporting:
[code]No mapping between account names and security IDs was done.[/code]This is based on the Error code 1332 described and I found this information:
[url]http://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx[/url] -
Tom , the domain function is ok now , it is succefully changed name , and joined succesfuly on the domain.(without the product key set )
For the product key ? on fog interface should be xxxxx-xxxxx-xxxxx-xxxxx-xxxxx or xxxxxxxxxxxxxxxxxxxxxxxxx ? -
I haven’t added any checking for the input, but as it’s using the slmgr cscript function to activate I believe to work properly it needs to be xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
-
Hi,
would be nice if the webif would check that 5 signs are entered and auto add the “-” to the input field, also if key is pasted it have to check if there are 5x5 pairs separated by “-” if a key is pasted without the “-” it should auto add them if at least 25 signs are pasted.
Regards X23
-
SVN 2077 released: Please see below.
I’ve now added the ability to add “individual” password login settings to menu items
My current menu that is tested and working, although very minimal, is:
[code]isset ${userID} && goto do_me || goto MENU
:do_me
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
imgfetch init.xz && boot || goto MENU
:MENU
menu
item --gap Please Select one of the images below
item fog.local Boot from hard disk
item d101_64 D101 Base Image (64 bit load)
item return Return to main menu
choose --default fog.local target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:d101_64
chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
autoboot[/code]Notice the :d101_64 how it has the chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU ?That’s all that’s needed to have a “login” for your menu item. Notice the top where it says :do_me? This is important to note that it’s ABOVE the menu generation part of the advanced menu setup.
As I stated, this is very basic, but a method to :sort: the different functions could be:
[code]isset ${userID} && iseq ${bootnum} 1 && goto do_me ||
isset ${userID} && iseq ${bootnum} 2 && goto do_me2 ||
goto MENU
:do_me
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
imgfetch init.xz && boot || goto MENU
:do_me2
kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=blahblah ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
imgfetch init.xz && boot || goto MENU
:MENU
menu
item --gap Please Select one of the images below
item fog.local Boot from hard disk
item d101_64 D101 Base Image (64 bit load)
item return Return to main menu
choose --default fog.local target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:d101_64
set bootnum 1
chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
:d102_64
set bootnum 2
chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
autoboot[/code] -
Short of installing, is there a file in the trunk that indicates the svn?
-
[quote=“sudburr, post: 33646, member: 4706”]Short of installing, is there a file in the trunk that indicates the svn?[/quote]
The “cloud” on the FOG Web GUI page will display the SVN revision number.
-
Hi,
i also thougth that first, then i started to believe that he talks about a file (filename or content) with current svn number.
I searched for stuff like that and couldn’t find that if that was the scope.If yes you may could parse “Revision XXXX” from the source of:
[url]https://svn.code.sf.net/p/freeghost/code/[/url][IMG]http://i.imgur.com/0QOYnfU.png[/IMG]
Search for "Revision[SPACE][4NUMBERS], cut last 4.
Regards X23
-
Grabbing a version number from [url]https://svn.code.sf.net/p/freeghost/code/trunk/[/url] doesn’t help me in identifying a downloaded trunk file.
This afternoon I saw 2093 posted as [url]https://svn.code.sf.net/p/freeghost/code/trunk/[/url] , so I immediately downloaded [url]http://mastacontrola.com/fog_trunk.tar.bz2[/url] .
When the download completed I revisited [url]https://svn.code.sf.net/p/freeghost/code/trunk/[/url] and it had changed to 2094. Which version did I just download?
-
As the previous gentleman have stated, it’d stored in the “cloud” on the logo part of the page. That being said, the version number’s only change when I make a commit. There’s still Chuck and Jian who can make commits. I do my best to keep up with them but can’t guarantee that it will always the be case. I was at the hospital with my wife so I’m sorry I wasn’t able to keep up when chuck made his commits.
-
Hi,
install subversion and get the trunk the right way…
[url]http://fogproject.org/forum/threads/ad-integration-on-new-fog-1-1-2.11128/#post-33016[/url]When a SVN checkout is finished it displays the SVN Version:
[IMG]http://i.imgur.com/WWduiVV.png[/IMG]Regards X23
-
You’re assuming I’ve installed it.
-
This is all updated.
-
[quote=“x23piracy, post: 33663, member: 3982”]Hi,
install subversion and get the trunk the right way…
[url]http://fogproject.org/forum/threads/ad-integration-on-new-fog-1-1-2.11128/#post-33016[/url]When a SVN checkout is finished it displays the SVN Version:
[IMG]http://i.imgur.com/WWduiVV.png[/IMG]Regards X23[/quote]
IIRC, I believe doing a ‘cd’ to the trunk directory and then typing ‘svn info’ will also show the revision.
-
You can also CD into trunk directory and type svnversion
-
SVN 2099 released.
With this comes some hopeful aspects to support Arch Linux for FOG Installation.
-
BSD support incoming as well or would that be painful?
-
SVN 2103 released.
Should fix, more properly, the __toString() issue as reported by andyroo. It’s needed so javascript will work properly, otherwise active tasks won’t update at all, it will just be an infinite spinner.
-
SVN 2119 released.
Has updates for tftp files. Also enables services if hosts are imported now.
-
Tom,
I had a few ideas for Full Registration option, if possible:[LIST]
[]Where it asks the yes/no questions, like joining the domain, it accepts input of other characters other than y/n. Is there any way to have FOG only accept y/n and if anything else is entered, prompt again, this time entering y/n? It would avoid having to shut down and restart the registration if you accidentally enter the wrong key
[]By default, the answer to the full registration questions is ‘no’ - is there any way to add an option in the web interface to change the defaults? For example, every machine we image gets joined to the domain - I know that can be done with groups, but it would be nice to be able to just hit enter when doing the registration
[/LIST]
