• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. adukes40
    3. Topics
    • Profile
    • Following 2
    • Followers 1
    • Topics 38
    • Posts 331
    • Groups 1

    Topics

    • adukes40A

      Optiplex 390 with Realtek NIC

      Watching Ignoring Scheduled Pinned Locked Moved Hardware Compatibility
      16
      0 Votes
      16 Posts
      4k Views
      adukes40A

      Just as an FYI, we had to remove the DHCP relays on the AP’s. As the switches were apparently handling the relays anyway, the ones on the AP’s were not needed.

    • adukes40A

      Upgrade from 1.3.0 to 1.4.2

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      3
      0 Votes
      3 Posts
      1k Views
      adukes40A

      Said it couldn’t resolve the URL’s. We recently dropped our DC it was pointing to. So I edited the interfaces file to an updatde DNS IP. So basically, it was DNS, mixed with a DUH moment on my side. Thanks for pointing to the log file to shine my stupidity 🙂 (-‸ლ)

    • adukes40A

      Hostname in GUI

      Watching Ignoring Scheduled Pinned Locked Moved General
      4
      0 Votes
      4 Posts
      2k Views
      Wayne WorkmanW

      @adukes40 I don’t know how you guys do it where you are but… I’ll elaborate on my experiences with imaging 2k boxes in a summer for over a dozen locations…

      The shipment of systems came in all to one building. We inventoried all of the systems at this building & then reboxed them - and created separated stacks for which ones go to what building.

      The stacks were then transported to their pre-determined building. Once there, they were unboxed fully - and smaller stacks were made for what rooms they went into.

      These stacks of computers were registered with “Full Host Registration” and given their correct name (part of the name included the building, the room they were in, part of the asset tag, the type of system it was, etc) and imaged.

      Once the imaging process was started; keyboard mouse & monitor were removed and plugged into the next. We monitored progress in the fog web interface, in Task Management & intervened if there were problems. Systems fully imaged, joined to the domain 100%. When all was done, we’d connect monitor, keyboard, and mouse to shutdown the system (because we set the power button to do nothing because kids are brats).

      It was quite graceful a process. Systems queued up and waited for imaging - one centralized fog server was orchestrating everything from a central location - all locations were using their local storage nodes & we were using the location plugin.

    • adukes40A

      FOG and PDQ

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      1k Views
      adukes40A

      Oh, nice. Sorry didn’t see that. I just started watching the video, as I plan on moving to PDQ within the coming year.

      Glad they did this.

    • adukes40A

      Config setting clarification

      Watching Ignoring Scheduled Pinned Locked Moved General
      5
      0 Votes
      5 Posts
      2k Views
      adukes40A

      Thanks, that what I was wondering.

    • adukes40A

      WOL

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      36
      0 Votes
      36 Posts
      21k Views
      Tom ElliottT

      @Wayne-Workman He already did, it’s how I know it was already pushed and is working.

    • adukes40A

      Full Registration, causing rogue snapins to apply

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      20
      0 Votes
      20 Posts
      5k Views
      adukes40A

      @Tom-Elliott All nodes at RC-11, It back to assigning recently used snapin associations from recent image deployments

      0_1475507131758_upload-32d5e685-9979-44a5-844e-e07b3c6cd59b

      Nothing has changed here. Just going about day-to-day operation. Tried with same host name, and never before used host name, same result.

    • adukes40A

      More Snapin Oddities

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      6
      0 Votes
      6 Posts
      2k Views
      adukes40A

      Goes hand-in-hand with

      https://forums.fogproject.org/topic/8638/full-registration-causing-rogue-snapins-to-apply/

    • adukes40A

      High CPU usage/Slow GUI

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Linux Problems
      2
      0 Votes
      2 Posts
      1k Views
      Wayne WorkmanW

      Your load average is 126, and all I see are apache2 processes in top. We need to dig in deep and figure out what’s happening, I can help via Join.Me when you have time.

      For starters - you can restart apache with service apache2 restart

    • adukes40A

      Attemping to send Inventory

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      15
      0 Votes
      15 Posts
      4k Views
      Wayne WorkmanW

      @adukes40 Ok. That means your DB connection from nodes to main is good. I think it’s just a bug on the version you’re on, you’ll have to wait for tom to look at it - sorry.

    • adukes40A

      Snapins removed from Previously registered hosts

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      10
      0 Votes
      10 Posts
      2k Views
      adukes40A

      @Wayne-Workman I was able to get it rolled back. It is looking like the snapins are back now. thanks for the help

    • adukes40A

      RC10 Broken Items on upgrade

      Watching Ignoring Scheduled Pinned Locked Moved Solved Bug Reports
      146
      0 Votes
      146 Posts
      149k Views
      J

      https://forums.fogproject.org/topic/8645/fog-client-auto-updating-hotfix

    • adukes40A

      Registration Script

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      5
      1 Votes
      5 Posts
      2k Views
      george1421G

      @Wayne-Workman The other option is for the OP to extract the inits make the change to fog registration script and then recompress the inits and then exchange the “fixed” inits on his fog server with the official ones.

    • adukes40A

      Fog Management in PXE Menu

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      5
      0 Votes
      5 Posts
      2k Views
      adukes40A

      @Tom-Elliott O ok. Well I will wake up from my dream then lol.

    • adukes40A

      No space left on device

      Watching Ignoring Scheduled Pinned Locked Moved General
      24
      0 Votes
      24 Posts
      13k Views
      Wayne WorkmanW

      @cerebron That is a great tip! Thank you for posting!

      #wiki worthy

    • adukes40A

      Image Throttling

      Watching Ignoring Scheduled Pinned Locked Moved General
      4
      0 Votes
      4 Posts
      2k Views
      Wayne WorkmanW

      @adukes40 You can only limit the number going at once for unicast as @Quazz said, not the bandwidth. The bit rate is a throttle for multicast. The replication rate is a throttle for replication.

      Multicast only works from master nodes. Enable broadcast forwarding on your router and it’ll start working at other sites. You have to enable the same thing for WOL to work at other sites I believe, there’s a plugin to assist with WOL.

    • adukes40A

      Remote Control

      Watching Ignoring Scheduled Pinned Locked Moved General
      6
      0 Votes
      6 Posts
      2k Views
      Wayne WorkmanW

      @adukes40 You may like DameWare. It’s just my personal opinion. I think the software works for X number of days as a trial without license.

    • adukes40A

      New NIC solely for MGMT

      Watching Ignoring Scheduled Pinned Locked Moved General
      3
      0 Votes
      3 Posts
      1k Views
      S

      In Storage Management and possibly FOG Configuration as well Tom means I suppose.

    • adukes40A

      M.2 Sata

      Watching Ignoring Scheduled Pinned Locked Moved Solved General
      6
      0 Votes
      6 Posts
      2k Views
      adukes40A

      @george1421 Just got the new master pushed up, and the M.2’s are now working great.

    • adukes40A

      Snappy Driver FYI

      Watching Ignoring Scheduled Pinned Locked Moved General
      7
      0 Votes
      7 Posts
      3k Views
      P

      @Joe-Schmitt Yeah you’re probably right. Maybe my view on this is a little naive but it hurts to see such great project possibly die.
      But because you mention it I will donate to fog project.

    • 1
    • 2
    • 1 / 2