Just ran into this too. Giving it a poke.

EDIT:
The drive had Windows 10 on it before, and it worked. After running a fast wipe through FOG, I could no longer get any tasks to work (same error as above). More fiddling inbound.

Glad to see it worked. I re-wrote most of the files in v0.7.3 and ended up breaking everything…

Win 7

Heh! You’re going to love this.

Twelve servers later, I check my source document.

I copy and paste my commands into the CLI … I had accidentally highlighted the CR+LF after the last command. So it’s piped into the CLI to appear, invisibly mind you, after the prompt. But it doesn’t actually enter itself at that prompt. So that when I enter “y” then <enter>, it has actually received CR+LF Y <enter> and fails out.

Doh!

Yeap thanks

Ok updated to SVN 3348 still seeing the resize issue it is still intermittent and may or may not affect the same machine twice in a row. I ran a debug task on one that failed and manually ran the resize command as you can see in the pic attached the command not so much fails as sees the partition as already ok even though its still at the deployed size.

[url=“/_imported_xf_attachments/1/1956_2015-05-04 08.24.04.jpg?:”]2015-05-04 08.24.04.jpg[/url]

If you’ve been following FOG for a little bit of time, you all may remember a week or so ago where we had the “random” mac deletions occurring?

Well, last night, or two nights ago (i don’t remember which exactly) i found the culprit and corrected it.

What this means:

FOG is actually working as intended. You’re missing the MAC that once existed because the hostMAC field for that host either one or both are set at id of 0 (which is invalid).

I don’t have a nice means to fix this, so if you’ve got phpmyadmin or are knowledgeable about database entries you can correct it on the fly.

The simplest method I can think if, for now, would be to delete the host (or hosts as the case may be) that’s causing a problem and attempt re-registering them.

Duplicate thread. Follow the thread here: [url]http://fogproject.org/forum/threads/pxe-menu-absent-svn-build-3325.12843/[/url]

[QUOTE]This isn’t highly documented as it’s relatively new. In an attempt to allow legacy and new client’s to operate with a single version of FOG, I created a Field for the New Client (FOG_AD_DEFAULT_PASSWORD) and the legacy client (FOG_AD_DEFAULT_PASSWORD_LEGACY).[/QUOTE]

Perfect explanation - I ran into this issue today, wasn’t aware of the new legacy field. All is working fine now.

Wearing my idiot hat this morning just used to seeing it all on one screen like in the add snapin screen. Off to get more caffeine.

r3254 fixed it.

Thank you for being awesome, Tom.

Hello
i noticed that some isatap adapter (IPV6 protocol) appear with the same mac address in the result of ipconfig/all

i tried to unchek ipv6 and the error message change :

CommunicationHandler Response : Error multiple hosts returned for list of mac addresses

Thank’s !!!

The update solved it !

Regards,
Ch3i.

[quote=“Wayne Workman, post: 45339, member: 28155”]So the moral of the story is to use ext4 ?[/quote]
Well, there are a lot of other nice filesystems out there too! ext4 is working for us right now and I am sure it will for others having an issue with deleting hugh files on ext3. But I am not saying that ext4 is the only fs that can do this…

r3232 fixed this.

Thank you, Tom.

The issue is resolved. The above post fixed it.

Same here, although this isn’t critical because things are working.

Just reporting the bug is still here. FOG r3218

[quote=“Wayne Workman, post: 45160, member: 28155”]This may or may not be related, but, I’m sitting in a lab watching it image right now.

Things are going smooth, but the “Tasks” tab in the FOG web GUI is reporting some hosts speeds correctly, while others are sitting at zero… FOG version r3218[/quote]

[url]http://fogproject.org/forum/threads/svn-2806-task-management.12134/#post-40095[/url]

This isn’t really a feature request. It’s a bug. I’ve since corrected for this. The only thing you can’t do is set multiples for the same time, but you can set how ever many of any kind. It was only allowing one greenFog entry at all and this was incorrect.