Posts made by jenesis

you are wrong
this is happening when creating an image.

ok i have made a video screen capture of the error creating a single disk resizable image.
[media=youtube]QE5a5t8NXng[/media]
the pc has been deployed in the past by fog .
it says that the first partition is to small , and later on asks to do a chkdsk.
this is false alarm, the disk is fine and windows partitions are fine .

i will create another image. but truly , if the guys at Acronis can make an image and deploy it no matter the hardware , surly this team can do it too

i have uploaded an 8.1 image successfuly to fog server (default:Windows 8.1
Multiple Partition Image - Single Disk (Not Resizable)
Everything)
And now i want to download/deploy it to another computer (different hardware) , pxe works ,all the way , but when it comes to actually deploy the image it just skeeps on to the next phase and nothing is being deployed.
the task is then finished fast but nothing happens.
i have tried to to do a debug download to see if there are any error messages , pressing Enter at each stage , but i could not see anything wrong.

my guess it has to with the hard disk being different size , and that it cant deploy it because of that.

any ideas would be appreciated
J

Thanks Tom for answering, I am truly honored just by this.
Here is my humble response
1.[FONT=Times New Roman] [/FONT]I had the fog windows client installed on xp , and when I was scheduling task for immediate image making , it rebooted on its own to start the process ,on windows 8.1 that didn’t happen so I figured something was blocking the connection between fog server and the client, that’s why I thought about a visible “handshake " something to tell me if the connection is made or not.
2.[FONT=Times New Roman] [/FONT]Clarifying this matter is essential, because the first thing I did was to change the management password to my login password , because hey it’s the same username how come the password is different ?.. so I guess to continue my line of thought the username for internal fog staff (FTP/TFTP and others ) should be different from the default web user login , say “fogftp” or “lighthouse” or whatever… Just as long as it doesn’t confuse us innocent users…
3.[FONT=Times New Roman] [/FONT]”[FONT=Tahoma]How can we “automount” a non-existent folder?[/FONT]" that’s exactly my point , fog server should verify the existing of the path , and if something fails , it should [U]deny[/U] the change of it , Now I can click Update , and no verification takes place. Of course this is the responsibility of the user , but at least it should notify there is something wrong
4.[FONT=Times New Roman] [/FONT][FONT=Tahoma]“FOG already checks if the image exists in the case of download tasks. … of these things fail during task creation, the task will not be generated. Is this what you’re referring to?[/FONT]” No , I had to manually change the image folder permissions and mount it things I only found out after I got “access denied” error and mounting error later on. I expect fog to check these things for me . but then again perhaps it[FONT=Arial]'[/FONT]s just me.
5.[FONT=Times New Roman] [/FONT]This is my test machine, once I get it up and runging , I am planning to install it on another machine. So that can be more of a notification then a feature request per say
6.[FONT=Times New Roman] [/FONT] I meant to [U]fish out[/U] just the errors not all the logs , I am aware this is not easy , perhaps an easier thing would be a red flag inside the web interface showing something went wrong , and when clicking it a window will open with the error details.

Thank you very much for you referring to my note , I am sure if I was a Linux Guru
I wouldn’t write half of these things, but as u can imagine, I am not [FONT=Wingdings]J[/FONT]

May the force be with you , Always.
J.

My Fog wish list
1.[FONT=Times New Roman] [/FONT]Create color deference between a windows agent “F” icon who has successful connection with a server to [COLOR=#70ad47]Green [/COLOR]as of a disconnected service agent with [COLOR=red]Red[/COLOR].
2.[FONT=Times New Roman] [/FONT]One password to rule them all, TFTP, Fog management , fog web login and whatever can cause a permission issue
3.[FONT=Times New Roman] [/FONT]When changing image location in fog , Automatic Mounting test will take place , if it fails , it will mount the folder as needed.
4.[FONT=Times New Roman] [/FONT][U]A connection test wizard[/U] will be one of the options in the fog client menu, which of course will test mounting, permissions to read/write whatever Is necessary for a successful operation.
5.[FONT=Times New Roman] [/FONT]When setting fog server to an old machine (P4) – fog_PIG_Z_COMP will default to 2 or 3 (~ 30 minutes image windows 8.1 taking on 100 M/b ) rather then 9 ( ~ two hours)
6.[FONT=Times New Roman] [/FONT]Errors with logs anywhere connected to fog will be consolidated [FONT=Arial]/[/FONT]centralized to one easy error log file with a link to the relevant file[FONT=Arial]/[/FONT]service related to it for easy troubleshooting.

Feel free to add more of your choice,
I will probably add some more later

[U]Thanks to all the developers for making this vital project available to us all.[/U]

J.