• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. albion
    3. Topics
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 16
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by albion

    • A

      Windows Update problems after a re-image.

      FOG Problems
      • • • albion
      6
      0
      Votes
      6
      Posts
      1.8k
      Views

      A

      @george1421 Even though the machine “seems” to be connected to the domain after reimage, I always remove and readd the machine to the domain.

      On my current “problem” I had to use the manual complete reset method to get Windows Update working again. And I’m still not sure because it’s “Checking for Updates” on 2 years worth of updates.

      @Wayne-Workman: Fog version 1.2.0. Linux CentOS 6.7 server, Windows 7 SP1 Workstation clients.

      @MRCUR: I am using WSUS. But, points at george1421. Each Workstation image will only be restored to that Workstation with a new same model hard drive. The impression I always got was that sysprep wasn’t necessary in my case.

    • A

      Proper preparation of workstation for Fog 1.2.0 image upload.

      FOG Problems
      • • • albion
      5
      0
      Votes
      5
      Posts
      1.8k
      Views

      A

      @Wayne-Workman

      Model: Whitebox ASrock MB, Core i5 CPU
      Winodws 7 Sp1 x64
      MBR
      Image: I installed from a Microsoft SA Win7sp1x64 downloaded ISO.
      When I hit DEL BIOS starts in UEFI Setup Utility.
      The SSD was operating in AHCI mode. The new HDD is the same.

      @sudburr

      I’m not taking images for distribution. I install a machine, install the OS, and install that particular users software. I then take an image of the machine in case there’s a virus or hard drive crash. I haven’t gotten to distributions yet, although that is my next step.

    • A

      CentOS ClamAV and Fog 1.2.0.

      Linux Problems
      • • • albion
      21
      0
      Votes
      21
      Posts
      12.1k
      Views

      Tom ElliottT

      I’m currently working a different system to this.

      I have built a clamav system from source.

      Stored the source in /opt/fog/clamav.

      Gave it 777 permissions throughout.

      Added it to nfs mounts.

      Making the mount point happen at boot, along with a checkin to let the system know it’s in progress.

      Use those binaries to load the data. Freshclam can be run, and it will update the database files on the fog server as well.

      Hopefully this will help us out. If you need the files right away, you can update the freshclam from the fog server using:
      [code]/opt/fog/clamav/bin/freshclam[/code]

      This is in testing and there may be bugs to work out, but for right now I’m hoping this will help.

      It has the added benefit that the init can be that much smaller as it won’t require building the init with clamav built into it. So when clamav updates, you can update on the fog server. I’ll see about building a "zip’ to keep this updated autonomously, but that can wait. I hope this will help everybody out.

    • 1 / 1