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

    Topics

    • F

      SSD not detectable on 0.32 with latest kernel 8.3.3

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      13
      0 Votes
      13 Posts
      5k Views
      Tom ElliottT

      It sounds like the partitioning scheme on the hdd is causing this particular issue.

      You may try an fdisk on the drive to verify what partitioning scheme is setup on it. It sounds like the first drive was initialized with the MBR tables and the other one is partitioned with GUID Tables.

      I don’t have much more information to help out with this.

    • F

      How to make deployment quicker with Windows 7 and fog

      Watching Ignoring Scheduled Pinned Locked Moved General
      24
      0 Votes
      24 Posts
      17k Views
      K

      It is a good idea to try using a “dumb” switch as a multicast test. Smart switches might see heavy multicast sessions as a storm or flood control target. Or perhaps they will throttle the heavy traffic. I needed to tweak our switches to allow multicast at a decent rate - I got 700mb/min for multicast but 4gb/min unicast - in fact I could start 5 clients unicast and still finish before 5 clients multicast. Using a dumb 1gb switch I got close to 2gb/min multicast.

      The sweetspot for me (multicast) seems to be >5

    • F

      Using Fog Server for mulitiple locations which has different subnets.

      Watching Ignoring Scheduled Pinned Locked Moved General
      12
      0 Votes
      12 Posts
      6k Views
      F

      ok we are finally getting somewhere…[B]FYI if clients are trying to use FOG as the DHCP server you need to modify this directory as well if your modifying your pre-existing FOG servers ip information for a different site location.[/B]

      /etc/dhcp/dhcp.conf - this was the culprit for me, it still had the old ip address information and I also discovered I can narrow down the dhcp address scope here as well.

    • 1 / 1