Categories

• Announcements

  Get the latest news on what's happening.
  167
  Topics
  702
  Posts

  S

  @astrugatch Quazz is spot on with what he says.
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1956
  Topics
  15701
  Posts

  

  @george1421 I had time to spin up two new fog servers in my test area, one for imaging and one for client interaction. The client interaction one is set to connect to the DB of the imaging one. I also imported the certs from my production machine to both. Unfortunately I ran out of time before I could actually test anything. Holding pattern until Monday I suppose.
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9315
  Topics
  91426
  Posts

  O

  @Sebastian-Roth user fog version 1.5.5
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2037
  Topics
  19356
  Posts

  

  @p4cm4n said in Associate all new hosts with Snapin: assign template host to template group, assign properties to template host. No don’t do this because it will create a loop. The names have to be exactly the same that is all. Every host added to the template group will cause the database trigger to fire copying the host template settings over to the host just added to the group. nothing that was ‘set’ is actually ‘deployed’ but rather with the sql hack/trigger, its just a property of the host Its possible that the settings are made in the database but because of database caching the FOG application may not see the changes until the cache is refreshed. So are you saying that the settings on the template host are not being copied over (like OU or some other parameter field) or is this a question about the snapins not installing?