• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. lebrun78
    3. Posts
    L
    • Profile
    • Following 1
    • Followers 1
    • Topics 54
    • Posts 315
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Is it possible to remove the FOG Quick image password?

      I would like, for a group of machine which the name is beginning by i207, not have to insert login/password to deploy image directly from pxe menu.
      But for all the other machines I would have to keep the login/password

      posted in FOG Problems
      L
      lebrun78
    • RE: Is it possible to remove the FOG Quick image password?

      indeed, I’m a drag

      posted in FOG Problems
      L
      lebrun78
    • RE: Is it possible to remove the FOG Quick image password?

      this one :

      @Joseph-Hales said in Is it possible to remove the FOG Quick image password?:

      [SIZE=4][B][FONT=sans-serif][COLOR=#000000]From [url]http://fogproject.org/wiki/index.php/Modifying_the_Init_Image[/url][/COLOR][/FONT][/B][/SIZE]

      [SIZE=4][B][FONT=sans-serif][COLOR=#000000] [/COLOR][/FONT][/B][/SIZE]

      [SIZE=4][B][FONT=sans-serif][COLOR=#000000]Remove Authentication from Quick Image[/COLOR][/FONT][/B][/SIZE]

      [FONT=sans-serif][COLOR=#000000]This example will show how to automatically authenticate users when they select Quick Image. If you are happy to allow anybody to deploy an image to a hardrive this is for you.[/COLOR][/FONT]
      [COLOR=#000000][FONT=monospace]cd /tftpboot/fog/images
      gunzip init.gz
      mkdir initmountdir
      mount -o loop init initmountdir
      cd /tftpboot/fog/images/initmountdir/bin/[/FONT][/COLOR]
      [FONT=sans-serif][COLOR=#000000]Edit fog.quickimage
      Comment out the followig lines by putting a # in front[/COLOR][/FONT]
      [COLOR=#000000][FONT=monospace] #echo " Enter a valid FOG username and password.";
      #echo “”;
      #echo -n " Username: ";
      #read username;
      #echo “”
      #echo -n " Password: ";
      #stty -echo
      #read password;
      #stty echo;
      #echo “”;
      #echo “”[/FONT][/COLOR]
      [FONT=sans-serif][COLOR=#000000]Replace with:[/COLOR][/FONT]
      [COLOR=#000000][FONT=monospace] username=“a valid username”
      password=“a valid password”;[/FONT][/COLOR]
      [FONT=sans-serif][COLOR=#000000]Save the modification[/COLOR][/FONT]
      [COLOR=#000000][FONT=monospace]cd …/…
      umount initmountdir/
      rmdir initmountdir
      gzip init[/FONT][/COLOR]
      [FONT=sans-serif][COLOR=#000000]You are done and now users can image without the need for a username and a password.[/COLOR][/FONT]

      posted in FOG Problems
      L
      lebrun78
    • RE: Is it possible to remove the FOG Quick image password?

      @Tom-Elliott
      Is the procedure described above?

      the file fog.quickimage doesn’t exist on base 1.3.3.
      Should I add it ?

      posted in FOG Problems
      L
      lebrun78
    • RE: Is it possible to remove the FOG Quick image password?

      is it always available on 1.3.3 version ?

      posted in FOG Problems
      L
      lebrun78
    • RE: Host Product changer

      This morning, I checked a new time, reboot the machine, and I got the same error in the log.

      Remark, when I change the status of the “Reboot host on hostname changes and AD changes even if users are logged in?” check box, the Host Product Key is blanked.

      posted in FOG Problems
      L
      lebrun78
    • RE: Host Product changer

      If the label of the check box is “Reboot host on hostname changes and AD changes even if users are logged in?”
      It is already checked

      posted in FOG Problems
      L
      lebrun78
    • Host Product changer
      Server
      • FOG Version: 1.3.3
      • OS: centos 6.8
      Client
      • Service Version:
      • OS: win10
      Description

      Hello,
      I would like fog client change Host Product Key with my windows 10 client.
      So I associate a product key for each machine on the web console.
      Change hostname changer is enable.

      Here what I get in the fog client logs:

      ------------------------------------------------------------------------------
      --------------------------------HostnameChanger-------------------------------
      ------------------------------------------------------------------------------
       26/01/2017 14:12 Client-Info Client Version: 0.11.8
       26/01/2017 14:12 Client-Info Client OS:      Windows
       26/01/2017 14:12 Client-Info Server Version: 1.3.3
       26/01/2017 14:12 Middleware::Response Success
       26/01/2017 14:12 HostnameChanger Checking Product Key Activation
       26/01/2017 14:12 HostnameChanger Windows has correct key but is not licensed
       26/01/2017 14:12 WinActivation Installing Product key
       26/01/2017 14:12 HostnameChanger Users still logged in and enforce is disabled, delaying any further actions
      ------------------------------------------------------------------------------
      
      

      I don’t have any domain or AD.
      So actually I don’t use sysprep, should I ? Is there a tutorial to use sysprep within AD ?
      Should the previous key be activated previously ?

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      @Tom-Elliott said in Boot menu configuration document:

      @lebrun78 I don’t understand your question.

      fog.quickimage is a login option. You can change it right in the GUI to whatever you’re wanting though.

      I didn’t find it, where is it ?

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      I agree with you, I could install it on a virtual machine.
      But I would like not to have to manage a new server, and I have storage issue for big files.

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      I’m not yet ready to add a new server.
      I read the old code.
      My predecessor had found a subterfuge, he had modified the file fog.quickimage (on a 0.32), so, if a machine had its name that started with e207, then the login and the foo password were sent.
      This login/password foo had the right to deploy machines on all the network.
      Could I do that again ?

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      where could I found explanation of it ?

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      On 0.32 the file /tftpboot/fog/images/fog.quickimage was modified to get this functionality, this file is not present on 1.3.3 version. Which file replaced it ?

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      I invstigate why there was specificty for this class room.
      It’s a room to tech network and system. So students reset machines deployng the image.
      So there is a special comportment for this room.
      There is an account that is only available for this room.

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      Which account can pass login password on ipxe.
      fog local server accout?
      fog web console account ?

      other ?

      since update I get invalid password
      And I can’t find anything in logs

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      But we want to limit this operation to only one particularly room

      posted in FOG Problems
      L
      lebrun78
    • RE: iPXE New Menu Entry with authentication

      Ok thank you

      posted in FOG Problems
      L
      lebrun78
    • iPXE New Menu Entry with authentication
      Server
      • FOG Version: 1.3.3
      • OS: centos 6.8
        Hello

      I would like to add menus to deploy by mdt via pxe new machine to create a master image.
      I add a new entry, it’s ok but how could I limit access to this new entry by a login/password ?

      I Tried

      login
      params
      param username ${username}
      param password ${password}
      param advLog1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      cpuid --ext 29 && set arch x64 || set arch x86
      kernel http://${next-server}/wimboot
      initrd http://${next-server}/mdtboot/${arch}/media/Boot/BCD BCD
      initrd http://${next-server}/mdtboot/${arch}/media/Boot/boot.sdi boot.sdi
      initrd -n boot.wim http://${next-server}/mdtboot/${arch}/LiteTouchPE_${arch}.wim boot.wim
      boot
      

      Login and password are requeded but login and password are not checked, so it doesn’t work.

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      For my first question, I use this good tutorial https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog
      But I just like to add an authentication

      posted in FOG Problems
      L
      lebrun78
    • RE: Boot menu configuration document

      So I have two problems,

      First,
      I have this code set in the Fog Configuration> Fog Settings > Fog Boot Setting > FOG_PXE_ADVANCED

      I’ m asking if it is in the right place for it ?

      I want that a login-password asked to access this menu ?

      Second,
      On 0.32 fog version we have edited the fog.quickimage to let a teacher deploy the machine for his room. So machine called a24* did not required a authentication to deploy an image.
      How should I process in 1.3.3 ?

      posted in FOG Problems
      L
      lebrun78
    • 1 / 1