• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Flyer
    3. Topics
    F
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 22
    • Groups 0

    Topics

    • F

      Which pxe file to use

      Watching Ignoring Scheduled Pinned Locked Moved General Problems
      8
      0 Votes
      8 Posts
      6k Views
      S

      @george1421 All those binaries are shipped with FOG and installed by default - see the list of ipxe binaries on github.

      It’s more or less a question on which binary we make the default when generating the dhcpd.conf - which obviously not everyone is using anyway.

    • F

      WOL Not Working After Imaging

      Watching Ignoring Scheduled Pinned Locked Moved Solved General Problems
      10
      0 Votes
      10 Posts
      2k Views
      S

      @Flyer said in WOL Not Working After Imaging:

      I guess they only way to know is to test.

      Exactly. 🙂

    • F

      Imagin Fails Every time

      Watching Ignoring Scheduled Pinned Locked Moved General Problems
      5
      0 Votes
      5 Posts
      819 Views
      F

      With the bad RAM removed the system imaged just fine with the same image. Thanks again.

    • F

      Maintaining Saved Samba Mappings

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Windows Problems samba credentials password mapped drive sysprep
      4
      0 Votes
      4 Posts
      749 Views
      george1421G

      @Flyer I create users in the setupcomplete.cmd batch file. That gets executed at the end of the WinSetup process and before the first login.

      You can also with the unattend.xml file define an auto admin login process for a specific user. You can set up a counter so the auto login process only executes X times then reverts to login required. This is configured in the unattend.xml file. There is also a first run section where you can do things to update the user’s current profile.

      So the idea would be to have the setupcomplete.cmd file create the user with a predefined secure password, then in the unattend.xml file have this user account setup to auto login once or twice depending on what you need, then have the first run section do what is needed to the user’s profile.

      One of the last steps in the unattend.xml file is to delete the setupcomplete.cmd and the unattend.xml to erase any clear text passwords that might be contained within. Finally reboot the computer.

      These are just ideas on alternate ways to go about solving this problem. I agree that accounts you create before should still exist after winsetup, but M$ typically has other ideas for us.

    • 1 / 1