PHPMyAdmin can be ran directly from your FOG server.
[code]apt-get install phpmyadmin[/code]
Then access it at
[code]http://fog/phpmyadmin/[/code]
Use your FOG MySQL Username and Password

Sounds like an MBR issue with your image.

There is no reason uploading an image would cause FOG to respond this way.

This sounds more like one your services has a problem, for what ever reason.

Since you can replicate the problem easily, i would:
[LIST=1]
[]Log into your server via SSH
[]Run top (or something to monitor process activity)
[]Replicate the problem
[]Pinpoint any processes that start consuming a lot of cpu / memory
[]Find the problem in that service
[]Fix the problem
[*]Profit
[/LIST]
[quote=“Pete Helgren, post: 224, member: 111”]the spinners for the Estimated FOG sites and Version spinners spin for a while and then…nothing. No error…no nothing.[/quote]
If the spinners turn to red crosses, this means your browser failed to connect to the FOG website.
Nothing to do with the FOG server itself.

[quote=“Pete Helgren, post: 229, member: 111”]all I see is the spinners spin and then nothing…[/quote]
Nothing as in they fail to load, or nothing as in the screen goes blank?

[quote=“Pete Helgren, post: 235, member: 111”]BUMMER! Stopped working after one image upload! Can anyone help me here? Is there any way to determine why I cannot log in but I see no errors as well?[/quote]
It’s a little slow over xmas, chill

I was using the auto login X amount of times with no issues, not sure what the issue is there.

I run a batch file during mini setup, you could probably do the same with your AutoIt script

From my AutoUnattend.xml
[code] <settings pass=“specialize”>
… other components here
<component name=“Microsoft-Windows-Deployment” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<RunSynchronous>
<RunSynchronousCommand wcm:action=“add”>
<Order>1</Order>
<Path>cmd /c c:\windows\defaults.bat</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>[/code]

This is a known bug with Schedule Group Tasks in 0.32. This issue will be fixed in 0.33.

Thank you for reporting. Please report any other bugs you find.

I need more information before i can help further.

Follow this guide to see what the messages are after it deploys.

[url]http://fogproject.org/forum/threads/wiki-troubleshooting-an-image-deploy.20/[/url]

If it deploys for a little bit, then reports it was Done, this almost always points to an image file issue.

How big is the on disk data? Normally image files are roughly 1/2 of the size, so your on disk data is around 7.4gb? Is that correct?

If you cannot think of anything else, create a basic ‘windows only’ image, prep that, upload then deploy… does it work?

Being a teacher, you should be able to troubleshoot and walk through the problems. If there are problems, always go back to the simplest thing first and work forward until it fails.

Please follow this guide on trouble shooting an image upload.

[url]http://fogproject.org/forum/threads/wiki-troubleshooting-an-image-upload.21/[/url]

The screenshot looks like it’s failing on the ‘ntfsresize’ command. This is where it will probably error or break.

Generally if the NTFS resize fails, there is some sort of file system issue that has to be fixed with chkdsk.

Any errors, or anything odd should be reported here.

I would not use RedHat… I have used it a lot in the past, the application support is sub par. I always ran into issues when installing almost everything that hasn’t been specially packaged for RedHat.

I highly recommend Debian (expert) or Ubuntu (easy - built from debian though) as it’s package manager (apt) is leaps and bounds ahead of anything else in the Linux world. They are also VERY strict when accepting new packages, so everything is always in the correct location. (see FHS: [url]http://www.pathname.com/fhs/[/url]). All of this makes both distributions extremely easy to manage.

If you are unsure, i would practice on a VM first, then move to the real thing.

Return code 0 = all ok

No idea about the state sorry.

You should get the snap-in working from the .exe file first, then upload and deploy from FOG.
Can you confirm it works directly from the exe? If not, you need to work on that.

It looks like you might already be updated, or maybe in an in between state.

The Schema updater has been updated in 0.33 allowing it to continue if it encounters an error like this.

I have hacked the 0.32 schema updater to allow it to continue even if there are errors. It will then display all errors at the end.

Please replace ‘commons/schemaupdater/index.php’ with the attached file.

[url=“/_imported_xf_attachments/0/5_index.php?:”]index.php[/url]

2.6.39.1

Yes… make sure the image type is ‘Single Disc (Resizable)’ and it will be done automatically.

Great to hear you got it all working.

100gb!! That’s massive!

It sounds like a problem with your image.

What process did you undertake when preparing the image? Did you run [B]chkdsk /x c:[/B] before syspreping to fix any file system problems?

Make sure the image has NO extended partitions.

If you cannot modify the DHCP scope variables, you will need a DHCP Proxy.

[url]http://fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]

[quote=“Adam Croft, post: 193, member: 54”]How can it be Windows related if the operating system hasn’t even loaded, Blackout?[/quote]
Because FOG has done it’s job of cloning the data successfully.
FOG doesn’t care what the data is, it will just clone the data… problems and all.

You are now at the stage of the OS booting, it then fails to boot. Thus a windows related problem.

Chuck hinted at this above by asking you to look at MBR issues.
[quote=“Adam Croft, post: 136, member: 54”]I also tried building a really basic image from scratch and then uploading it. Deploying that basic image works. Any other suggestions?[/quote]
This tells me there is something wrong with that image. With the data inside of that image.
Remember FOG does not care, verify, or even look at the data in your image.

Maybe with the MBR of that image? These types of messages normally hint at an MBR issue.

First thing i would be doing is running [B]chkdsk /x c:[/B] on the master (non syspreped) version of your image.

If that brings no joy, you need to narrow down WHY windows is failing to boot.
Can you manually fix the problem (maybe using ‘fixmbr’) and get the image working?

After it’s fixed on the Master, re-sysprep and take the image up.

Checking BIOS version differences is a good idea too. You might need to re-flash your BIOSes.

Thanks for the feedback guys.

Multiple files is a hard one as it will require a lot of work (more than i can do before 0.33)

Dependency & weighting are very possible though.

I assumed you were on the latest version. That is the first thing to do if you are having problems.

I’m running 0.32 with no problems, as are many others.

If you are still on 0.30 i would suggest upgrading.
The new Web UI is leaps and bounds ahead of the old interface, not to mention all of the other work that makes it more stable.

Don’t be one of those people who are scared to upgrade. Trust me, once you upgrade you will wonder why you havent done so sooner.

Look in /images/IMAGENAME

How big are the files?