@plegrand
No worries!

@Joe-Schmitt

Makes sense, and I had suspected as much.

Thanks!

PS snapin if anyone needs it.

Start-Transcript -path c:\SnapinLogs\CleanupUpdaterLog.log $strFileName="c:\program" If (Test-Path $strFileName){ Remove-Item $strFileName } Stop-Transcript

This is because 1.2.0 had no support for windows 10 as it didn’t exist during 1.2.0’s release. The only way, that I’m aware of, to get Windows 10 to image is to use Multipart Non-resizable. That said, Trunk versions of fog will run without much issue.

@RobTitian16 Just seems to have been a slow network day I guess as it’s running through fine now at 3GB/min 🙂

@Tom-Elliott

Ok, so I changed the storage group for my snapins from my QNAP to default and now it worked.
Thanks for the help!

@jide Sounds like you’re using dnsmasq? In such case, you can turn off DHCP on the fog server (if you want), and turn it back on for the ISP box (if you want) and just roll with dnsmasq.

Glad you got it working.

@mmethe Image size on the server is determined with FTP.

If you’re referring to image size on the client, this is updated each time you capture or deploy an image and is merely an informational piece in the DB that will not affect deployment.

Confirm that it works in GIT 8259.

@foggee There are mixed thoughts about the best version of Ubuntu. IMO, I’d go with 16. There are special steps that need included (search the forums for “Ubuntu 16”), but after that it’s good to go. Ubuntu 14 will work without modification.

You do not need to install 1.2.0. You can go straight to trunk.

@Sebastian-Roth
I’m off until Monday. Unfortunately, I had to deploy that laptop without imaging. I’ll have more to do though. I may be able to grab it later and continue testing. Thanks for the help!!

Cheers,

Joe Gill

@Joe-Schmitt said in Trunk 5735 PC doesnt restart after joining the domain.:

This issue has been addressed in v0.11.2. Please test when you get a chance.

The Update worked for me Joe, Thanks!

@Tom-Elliott

This resolved our issues. Thank you for the great support. I now have a working FOG server again; now on trunk. I hope this makes our upgrades to Windows 10 Edu easier over summer break.

Thanks, again!

@bmaster001 said:

So you guys have plenty of time to think about this weird piece of hardware, and I’ll get back to this thread when we have more devices to play with!

I don’t think we are able to push this anywhere without having the hardware around or someone like you who are willing to test things out.

@phil_guy The partition table looks interesting to me:

unit: sectors /dev/sda1 : start= 2048, size= 70193152, type=7 /dev/sda2 : start= 70195200, size= 27035648, type=7 /dev/sda3 : start= 97230848, size= 19998720, type=83, bootable

First two partitions are NTFS (type 7) but the last one is marked to have a linux filesystem (type 83) and bootable. I don’t think windows is happy with that.

[moderator note] Moving to Technical / FOG Problems. This was in Tutorials

@Wayne-Workman

I did find out that the slow speed was likely from an old switch in that room. The other admin said we still have a 10/100 switch on that lab… So theirs part of the issue!

@GFm Tom fixed it for me. found the mac to be attached to another host and deleted it

Thanks fixed it.

Moved to FOG Problems.

Just tested WOL on current trunk and all is working perfectly fine.