Posts made by falko

if a task is set, the task works etc.

I too am seeing this with 1.3.4-RC1 when a host is booting up, also using Debian OS 8.6

@george1421 how did the testing go?
I plan to start checking out windows 10 deployments myself and had seen you mentioned adding the sysprep part in your post download script post
Hope to test this the wknd

I use to, had no issue.
I now use turnkey LAMP distribution for fog server deployments, has webmin preinstalled. All works fine

Just set this up, thanks

@Wayne-Workman good to know thanks, guessing my rebuild and host import cleaned this up.

I too have seen this once or twice, but many revisions ago. And it was only adding the very most recently registered devices (maybe 2-4) to groups. But since then my fog server died and I have rebuilt adding a storage node and haven’t seen this happen in a while since keeping up with the revisions of the development. I actually forgot about it…

I will also check this again, although recently I registered I have registered quite a few new machines and created a few groups and not seen this happen. I’m on Debian 8, FOG 1.3.0

said in Organizations Using FOG:

Organization Name: Guru Nanak Multi Academy Trust
Web: www.gurunanaksikhacademy.co.uk
Location: UK
Approximate Number of systems: 600
How long: Implemented March 2016
Can be listed on the Wiki

@Tom-Elliott

applied the fix and the web is now displaying correctly but when exporting the reports, they come out blank?

Thanks for the quick fix, have left the office but will update and run report when I get home
Much appreciated

Server

• FOG Version: 1.3.0-RC-37
• OS: Debian 8

Description

I am able to view the imaging log from two days ago but not yesterdays.

The only difference being that we imaged about 70 machines yesterday.

We have one storage group and 2 nodes

this was the report error

@george1421 said in Replicating drivers across FOG servers:

@Wayne-Workman said in Replicating drivers across FOG servers:

Two approaches here.

Create a fake image and make its path /images/drivers and setup the fake image so it’s shared with the other servers via groups or whatever way you have the images set up.

This is the option we use. You should also be able to set this “fake image” to disable so someone won’t try to deploy it, but enable replication so the drivers will be sent to the remote fog/storage nodes.

I also use this method

@Tom-Elliott thanks Tom, updating now

Server

• FOG Version: 1.3.0-RC-30
• OS: Debian 8

Client

• Service Version: 11.6
• OS: Windows 7 x32

Description

Imaging works and it seems everything else does, however the machines do not join the domain once deployed

0_1481192533885_fog.log

Sounds similar to what I experienced a while ago when messing with servers in a test environment. Even though it displayed as zero, imaging worked fine. I’m guessing you can image ok?

Hi,

Not sure if this is even possible and if it is I also realize it is bottom of the list with the FOG 1.3.0 Release hitting RC 1.

Just curious if in the FOG Imaging Log it is possible to report on what node provided the imaging?

@Wayne-Workman thanks, I was meant to say that I had been through that article after searching the forums and finding similar posts.

I also rebooted the server and also tried again after updating, I know it doesn’t really help us in finding what went wrong but I ended up rolling back my FOG VM a few days (both master and node was able to deploy after this). I then updated the master to the latest (to match the storage node) and both are able to deploy images.

thanks again

I have a Master and a Storage node in the same group both running Version: 8595

However when imaging from the Master node the deploy fails as below. The storage node images fine

I am running Debian 8.5 on both nodes

Thanks Tom, I won’t be able to check this out until end of the day but much appreciated

Hi,

Is it possible to display the Max number of clients for each storage node in the list on the Storage Management page. As you can see below I only have two nodes myself (for now) however due to possible expansion over the next few years I can see it being useful to be able to glance at this page and see what each node is set to.

Thanks