I’ve confirmed full registration works with imaging too.

@kverkiss said in Communication ERROR: operation timed out, could not authenticate, obj error:

@Jbob Thanks for the information!

The problem has been resolved. Thanks for all help.

@andyroo54 Thanks for noting! I just added this to the wiki: https://wiki.fogproject.org/wiki/index.php?title=Installation#VMWare_ESXi

@andyroo54 I’ve added error checking for getting the $_FILES[‘blah’][‘error’]

The problem, in the case of too large a file chosen, is it completely blows away ALL $_POST/$_FILES variables as blank. This is why it’s reporting the “blank name”.

Unfortunately there’s not much I can do to fix that.

I have also added the suggested 3g limit instead of 100 megs. Of course, it won’t change this if your values have been set to other the the 8m (post_max_size) and 2m (upload_max_filesize).

@VincentJ So this kinda died.

I was so busy this week… it’s just madness at work and I’ve been spending every spare second I have trying to rebuild my win 7 SOE with a new way to manage drivers (I’m going to make a new thread for win 7 deployment, or maybe update my old one, and maybe a win 10 guide too).

Anyway I’m not really sure what the upshot of this thread was. But I will make a virtual appliance, at some stage. Honestly work is just so busy and shows no signs of slowing up… we have to replace our entire core and edge network (which is huge) plus new core server infrastructure at two main sites all this year… on top of just trying to keep everything running and setting up new businesses everywhere…

@andyroo54 You can edit it from the GUI on the “User Management” tab. There is no link between fog user on GUI and fog unix user.

@Wayne-Workman

Thanks Wayne.

For anyone who finds this thread, on Ubuntu, just cd to /etc/php5/apache2 then edit php.ini

Using nano to edit, find upload_max_filesize and post_max_size and increase both as desired. I increased mine to 3000M (3GB approx.)

@andyroo54 I still suspect the raid is failing. Do you see the same “fix now”? As it is raid, does the system raid controller see an issue with the disk?

What is the partition layout, lvm ext?

@Wayne-Workman Yeah it’s not a big deal. It was just a nice feature of .32

Like I said it’s a small price to pay to upgrade.

@Sebastian-Roth Yes Sebastian, I meant to write yesterday, fog is booting no probs now with the new trunk version. I am getting corruption of the image but that might be the OEM image I’m trying to upload. I’m going to try a win 10 soe today.

The records are stored in the imagingLog’s table, and I only recently as in 1.x.x started copying the records displayed on the home screen from this table, where prior it was pulling from the tasks table entirely.

[quote=“mlb2009, post: 15450, member: 13741”]Windows 7 support will also be good[/quote]
Windows 7 is already supported in 0.32, and as such would be supported in 0.33

[quote=“chad-bisd, post: 5103, member: 18”]Download the kernel from the sourceforge page you linked above. Backup your current kernel and then copy this one to the /tftpboot/fog/kernel directory. Rename it bzImage and chown to fog:root.

Try to boot up one of the new laptops and see how it works for you.[/quote]

Thanks for your help. Updated kernel and it’s working, using a custom kernel from fellow user.

I’m excited about Windows 8. At this time, if it works, it works; if not, we’ll probably have to wait until retail before we can troubleshoot.

@george1421 Thanks for the tutorial, i’ll try it.. .

@Bigredcherokee

Okay think I found my own fix.

The package .exe file must contain an application manifest, i.e. an XML file with special instructions. All UAC compliant applications should have a requested execution level added to the application manifest. Requested execution levels allow the system to know the specific privileges required for a package.

Sorry to bring up an old post.

enjoy! and here i just got to work …

Still having problems with this. It’s strange. I built a windows 7 pro image on a physical machine (samsung series 7 slate) and uploaded without sysprep because it was only to be deployed to the same hardware. But for whatever reason the virtual just won’t rename once it’s deployed to clients. I’ve tried installing the fog service both before/after sysprep and neither seems to work. Fog log doesn’t show any problems… I think anyway. Doesn’t show any tasks pending, but the host name in fog is totally different. Does the machine name have to be less than 15 characters when the fog service is installed maybe?

20/02/2012 9:32 PM FOG::GreenFog No actions were found.
20/02/2012 9:32 PM FOG::GreenFog No tasks found after validation!
20/02/2012 9:32 PM FOG::GUIWatcher Dispatch OK!
20/02/2012 9:32 PM FOG::printerManager Management level = 0
20/02/2012 9:32 PM FOG::printerManager This host is set to NO MANAGEMENT, we will exit now.
20/02/2012 9:32 PM FOG::printerManager Major printing operations complete, moving to tracking mode.
20/02/2012 9:32 PM FOG::printerManager New user detected: WINDOW\Administrator
20/02/2012 9:32 PM FOG::printerManager Waiting for tray to load…
20/02/2012 9:32 PM FOG::DirCleaner Starting directory cleaning process…
20/02/2012 9:32 PM FOG::DirCleaner Attempting to connect to fog server…
20/02/2012 9:32 PM FOG::DirCleaner Module is active…
20/02/2012 9:32 PM FOG::DirCleaner Determining which directories should be cleaned…
20/02/2012 9:32 PM FOG::DirCleaner No directories are configured to be cleaned.
20/02/2012 9:32 PM FOG::DirCleaner Starting directory cleaning loop…
20/02/2012 9:32 PM FOG::DirCleaner Module has finished work and will now exit.
20/02/2012 9:33 PM FOG::MODDebug Reading config settings…
20/02/2012 9:33 PM FOG::MODDebug Reading of config settings passed.
20/02/2012 9:33 PM FOG::MODDebug Starting Core processing…
20/02/2012 9:33 PM FOG::MODDebug Operating System ID: 6
20/02/2012 9:33 PM FOG::MODDebug Operating System Minor: 1
20/02/2012 9:33 PM FOG::MODDebug MAC ID 0 00:0C:29:82:CB:AC
20/02/2012 9:33 PM FOG::MODDebug MAC POST String: 00:0C:29:82:CB:AC
20/02/2012 9:33 PM FOG::MODDebug A user is currently logged in
20/02/2012 9:33 PM FOG::MODDebug Username: WINDOW\Administrator
20/02/2012 9:33 PM FOG::MODDebug Hostname: WINDOW
20/02/2012 9:33 PM FOG::MODDebug Attempting to open connect to: [url]http://fogserver/fog/service/debug.php[/url]
20/02/2012 9:33 PM FOG::MODDebug Server responded with: Hello FOG Client
20/02/2012 9:33 PM FOG::MODDebug Module has finished work and will now exit.

Just confirmed that if I:

Run sysprep, then upload and then deploy the image to another machine, (the PC name is 15 characters for some stupid reason, I can’t figure why my unattend.xml won’t specify the PC name, rather than giving it this random 15 character windows-wa532f2 name…), then rename the machine manually to a smaller name- THEN install fogservice and restart- THEN it will rename to the correct FOG name…

So basically I need to rename the PC after sysprep to a short name (can probably do this with a powershell script), THEN get FOG service to install on SECOND start up… I wonder if I can even do that… “second” log on commands?