• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. SupEric
    3. Topics
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 27
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by SupEric

    • S

      Trust relationship broken

      FOG Problems
      • • • SupEric
      12
      0
      Votes
      12
      Posts
      4.8k
      Views

      sudburrS

      The trust relationship between the AD and the computer is based on the Computer Account Password which is saved as part of the computer object in the AD.

      By default, trust relationship and computer account passwords are negotiated every thirty days, except for computer accounts that can be disabled by the administrator.

      This password is generated, negotiated and maintained by the computer, entirely silently. A short history of passwords is supposed to be maintained by the AD for each computer object, in the case of some synchronization problems. However, this can easily be fubar’d if the computer undergoes one too many recovery sessions to restore points, is away from the domain too long to have been able to properly recognise the new password, or your AD has been restored to a previous restore point.

      If you are capturing an image that is already joined to the domain, stop doing that.

      The recommended fix from MS for a computer that no longer is trusted by the AD is:

      From the client, remove it from the domain. Delete the computer object from the AD. Join the computer to the domain.

      … Or …

      Logon as a local Administrator CMD: netdom /resetpwd /server:YourDC /userD:Your.Domain\YourADAccount /passwordD:* /SecurePasswordPrompt

      There are other scripting and powershell options as well.

      See [url]http://support.microsoft.com/kb/216393[/url] for more information.

      This problem can also be remediated by changing the default behaviour of the client by extending the lifespan of the computer account password through local Group Policy.

    • S

      Creating images

      FOG Problems
      • • • SupEric
      18
      0
      Votes
      18
      Posts
      4.4k
      Views

      Roger SaffleR

      hmmm. seemed to have worked. I moved the files over manually to /images but didnt like the image. I went and uploaded a new image. Worked then. But I had already made the dir in /images.

    • S

      Computer wont boot from hard drive after PXE from FOG

      FOG Problems
      • • • SupEric
      30
      1
      Votes
      30
      Posts
      19.9k
      Views

      O

      I know I’m gravedigging an old topic, but since this is all the Google could find for me on this topic I thought I’d post a solution for future reference.

      For my setup (FOG 1.3.5), the following allowed me to get my Dell Latitude M4800 and E7470 laptops to exit iPXE and continue booting the hard disk properly without the dreaded flashing cursor:

      FOG Configuration -> iPXE Boot Menu -> Exit to Hard Drive Type = GRUB_FIRST_HDD (default is SANBOOT, which was giving me trouble)

      Hope this helps someone.

      Jon

    • S

      Problem Upgrading from .32 to 1.1.2

      FOG Problems
      • • • SupEric
      3
      0
      Votes
      3
      Posts
      1.0k
      Views

      S

      Is there an easy way to reset the password? Is there a place to look up the password. Here is the contents of our config.php file.

      <?php

      define( “UPDSENDERPATH”, “/usr/local/sbin/udp-sender” );

      define( “MULTICASTLOGPATH”, “/opt/fog/log/multicast.log” );

      define( “MULTICASTDEVICEOUTPUT”, “/dev/tty2” );

      define( “MULTICASTSLEEPTIME”, 10 );

      define( “MULTICASTINTERFACE”, “eth0” );

      define( “UDPSENDER_MAXWAIT”, null );

      define( “MYSQL_HOST”, “” );

      define( “MYSQL_DATABASE”, “fog” );

      define( “MYSQL_USERNAME”, “” );

      define( “MYSQL_PASSWORD”, “” );

      define( “LOGMAXSIZE”, “1000000” );

      define( “REPLICATORLOGPATH”, “/opt/fog/log/fogreplicator.log” );

      define( “REPLICATORDEVICEOUTPUT”, “/dev/tty3” );

      define( “REPLICATORSLEEPTIME”, 600 );

      define( “REPLICATORIFCONFIG”, “/sbin/ifconfig” );

      define( “SCHEDULERLOGPATH”, “/opt/fog/log/fogscheduler.log” );

      define( “SCHEDULERDEVICEOUTPUT”, “/dev/tty4” );

      define( “SCHEDULERWEBROOT”, “/var/www/fog” );

      define( “SCHEDULERSLEEPTIME”, 60 );

      ?>

    • 1 / 1