Posts made by Andrew Aitken

@Tom-Elliott Thanks
Updated the file as instructed.

I’ve just updated our FOG server to SVN 6120 this morning and some existing clients (Windows 10) are now throwing this error?

Uninstall/reinstall of the client fixes it but clearly this is not something we can do every time we update the server.

Any advice welcomed.

Thanks

@ITSolutions
Installed .net4 and client installed fine.
Thanks again for your guidance

@Arrowhead-IT
I followed your advice RE: using diskpart and managed to get both my Dell 5450 latptop and HP 800-G1 desktops to boot legacy/MBR, install Windows 10 and can now successfully capture/deploy using single-disk resizable FOG image.

I’m pretty sure I had default GPT/UEFI Windows 10 multi-partition image capturing and deploying previously but maybe I imagined it?

Thanks for your help.

@Wayne-Workman
.net is not installed. Is there a requirement for it?

@Tom-Elliott
Pretty sure I did the last time but I ran it again to be sure and still got the same error?

@Tom-Elliott
No just executing the .msi or with msiexec from the command line. Both produce the same result

@ITSolutions As suggested I re-ran the MSI install with logging but unable to determine what the issue is?
0_1453808764504_fog-install.log

Any help in deciphering the log would be appreciated.

@Wayne-Workman said:
As for the issue with the source host being bootable after a resizable image is taken, I believe you’re experiencing the same issues as described here: https://forums.fogproject.org/topic/6536/windows-10-after-upload-partition-erased So for that specific issue, could you post to that thread?

You are absolutely right. Will post any further comments to that thread

Minor update
It installs fine on Windows 10 64-bit but not Windows 7 64-bit

Why would that be the case?

Tried capturing a fresh Windows 10 image, this time using (non-resizable Windows 10) option and at least the source machine is able to boot back into Windows after the capture task completes.

However, restoring this image failed with the following error “No disk passed (runPartprobe)” ?

Thanks for responding so quickly.

Currently running v6090 but struggling to get Windows 10 to capture and/or deploy?

Tried capturing (single-disk-resizable) but when capturing I see this, which clearly shows the destination C:\ much smaller than it should be (465GB)

After capture the source device no longer boots with this error

Image folder contents on the server

Deploying resizable image results in this error on the destination machine?

@Tom-Elliott
I don’t think it gets that far, as neither c:\fog.log or c:\program files (x86)\fog folder is ever created?
The only thing I can find is a series of 5 events in the Windows Application log culminating with “Installation success or error status: 1603”

Sorry seem to be having problems pasting images into posts.

I’m having exactly the same problem getting the agent to install interactively on our base image (Windows 7 64-bit and FOG 6090 running on Ubuntu 14.04)

The client install used to work fine previously but have been updating our base images recently and cant get this to work?

HELP!

I have been trying to get some Dell 5450 laptops to image with Windows 10 but FOG seems completely broken at the moment (SVN 6090)

Last week when attempting the capture the image, it would capture OK (WIndows 10/Single disk resizable) but then the machine the image was taken from had it’s C:\ drive reduced from the total disk size of 256GB to just above the amount of data consumed by the OS (~12GB)? The image would deploy OK but disk in the same shrunken state

I have been updating the install every day, hoping that this is fixed but things are now worse?
I updated to SVN6090 this morning and re-captured a freshly installed Windows 10 image and now the source machine wont even boot!
I then attempted to deploy the gathered image to another device and get this error on the destination 

Any advice of feedback would be appreciated?

Thanks

Comparing the old (WIN7basic) and new(win7-test) image folder contents, there is a clear difference. Can you not upgrade the old images to the new format?

We started with 1.2.0 so some of the images could be that old? I didn’t keep a record for each image, so couldn’t say for sure.
Was starting to think that I might have to spin up a 1.2.0 server, mount the old images and then deploy/regather with latest server to get good images?

We have been using for over a year with no problems but a week or so ago we updated to revision 5927 and since then we have been unable to deploy existing images?
Since then we have tried on numerous occasions to update to the latest SVN hoping there was a bug in the current rev but no luck.
We are now running SVN 5968 and old images now deploy but get stuck at the end of the imaging process “Clearing NTFS Flag” and never proceed beyond that point?

Any advice would be welcomed.

Thanks