@irishfoguser

not sysprepped

This is possibly the problem. Not everyone syspreps here, but I recommend trying it and see if that alleviates the issue.

@irishfoguser Hi, generally speaking you’re better off using Resizable image. If this for some reason doesn’t work (fails to deploy), then trying the other options is recommended.

For your situation, it sounds like Resizable Image will do the trick. So I recommend picking an image, setting it to resizable, recapture, deploy and see if it works for you.

1.3 is able to resize the correct partition for you before Windows even boots for the first time.

You have to path to the executable or include PATH in the crontab itself.

so if you ran command -v grsync it would give you the full path, you’d use this full path instead of just grsync. Or you could just stick the path at the top of the crontab file. echo $PATH and then take the output and put it into line 1 of the crontab as a variable like PATH="put the path output here"

Read through this, they may make better sense than me. Plus I’m tired. http://stackoverflow.com/questions/2388087/how-to-get-cron-to-call-in-the-correct-paths

as for the “replacing the computer name” issue check the testpc primary mac address for “Ignore client” and this should prevent changing the hostname to testpc.

@irishfoguser 2nd yep right where you are scheduling the task

@irishfoguser just wanted to say the messages you saw aren’t hurting anything whatsoever. Tom reworked the build parameters for the kernel not long ago to include better support for Surface Pros. Some of those messages are the kernel not seeing the surface pro hardware.

Turning down the log level could even be a disadvantage to you, because if you did have kernel problems, you wouldn’t know it, and you’d post here with zero errors asking for assistance - and it’ll maybe take us a while to figure out what’s going on. And - say you remember to turn the log level when you have a issue. But will the person that comes in behind you do that? Would a co-worker know that?

I’d suggest leaving the log level at default, but you can do as you wish.

@irishfoguser Not sure what we can help you. The solution you mentioned (setup a new RAID and move the images) is perfectly fine!

You can see how to fix this issue on the [url]https://github.com/FOGProject/fogproject/issues/1[/url]

Finally!!

Thanks to TOM and everyone else on here who helped me out.

I wont be touching it again for a while.

Why cant be I be in bin directory while running svn?[/quote]
because it’s only updating the files in the bin directory if you’re in the bin directory when you run the update, which is 2 files

Works perfectly Thanks Tom.

Guys, he solved his issue, this is an old topic. We are just playing Necromancy.

Thanks for all the help.

My first image is deploying on the server i built from scratch. 😄

enable fog configuration>fog settings>general settings>FOG_FORMAT_FLAG_IN_GUI
all new images created are made using partclone, deploying partimage images is included only for legacy support.
if an image is set to partimage and reuploaded, it will be converted to partclone