Where are you seeing things running as unicast and as sending an image?
On your task list it looks like you have all multi-cast tasks and some of them just didn’t start.

Can you try to explain the problem you’re having again because I’m having trouble following.

Also, you’re on 1.2? Time to upgrade to trunk

@Wayne-Workman I would love to
However I would wait until I have finished my current project of using fog to upgrade all clients to windows 10 so that this method is more thoroughly tested first.
It’s tested, but not thorough and I will likely make some changes to my image prep script along the way. Then making it a wiki article will pretty much be copy paste from my documentation on the work project. Should be done by the end of next month, hopefully sooner, but I’m anticipating more troubles.

Confirmed working. the CA ssl folders can now be separated from the snap-ins folder

@MRCUR There is also a separate version of Windows 10 you can get with your volume licensing. The LTSB version takes out all the
“modern” apps plus the ability to just add the ones you want and don’t want I believe. I haven’t tried that as of yet

I also am a loather of sysprep.
Looking through this forum post might help a little, maybe not a lot
https://forums.fogproject.org/topic/6431/cortana-windows-search-breaks-in-default-profile/18

I use one image for multiple hardwares without sysprep
I just had to figure out what sysprep was doing that was so important.

The biggest thing is uninstalling drivers.
But doing that manually in the device manager is time consuming and if you uninstall the wrong thing, you can lose your mouse.
What you need is devcon from the windows WDK. http://go.microsoft.com/fwlink/p/?LinkId=526733
Then copy devcon.exe from the install folder of the wdk to C:\Windows\System32 on your image

Then
devcon -r remove * Will uninstall all devices in the device manager like sysprep does and then it restarts, which would be your last step before imaging.

The downisde is that it ends up removing some devices used for remote desktop and they don’t auto reinstall.
But that’s fixed with this magic script FixRemoteDesktop.bat after imaging.

@ECHO off
	REM Script for fixing remote desktop after uninstalling all devices

	call :main
	exit

:main
	call :funcHead "Welcome to the remote desktop fix!"
	call :setVars
	call :addDriver "NDIS Virtual Network Adapter Enumerator" "%drivers%\ndisvirtualbus.inf_amd64_c420021ea374b6f3\ndisvirtualbus.inf" ROOT\NdisVirtualBus
	call :addDriver "UMBus Root Bus Enumerator" "%drivers%\umbus.inf_amd64_b5911c04e2dae8d2\umbus.inf" root\umbus.inf
	call :addDriverAndRestart "Remote Desktop Device Redirector Bus" "%drivers%\rdpbus.inf_amd64_e1a9f2699d349149\rdpbus.inf" ROOT\RDPBUS

	EXIT /B

:setVars
	set drivers=C:\Windows\System32\DriverStore\FileRepository

	EXIT /B

:addDriver
	echo. installing %~1...	
	Devcon install %~2 %~3
	echo. done!
	EXIT /B

:addDriverAndRestart
	echo. installing %~1 and restarting computer...	
	Devcon -r install %~2 %~3
	echo. done!
	REM just in case -r doesn't reboot...
	Devcon reboot & exit
	EXIT /B

:dots
	REM just echoing dots in a Function instead of copy pasting them so that it's consistent
	echo ......................................................................
	EXIT /B

:funcHead
	REM A simple function for displaying a consistent header at the start of functions
	call :dots
	echo. %~1
	call :dots
	EXIT /B

Then you don’t have to deal with slow buggy sysprep.
There are some other things that you had to do in the registry for windows 7 and 8 to reset the security id, but from what I can tell windows 10 does all that automagically when it finds itself on a new computer. But that might just be me being in an ignorant bliss.
But in the time I’ve been using this method I have had 0 residual driver issues on client computers.
So I recommend ditching sysprep and making your own imageprep

@Wayne-Workman I wonder if I got compression part from that post a year ago. Some of that is what I remember from my college Networking class.

@plegrand Looks like the problem shouldn’t be the server power, and I was wrong about that part anyway.
Considering the speed difference you already are seeing, why not just use unicast? I’m just curious if there’s a specific requirement for multicast?

@plegrand A couple questions
What are the specs (cpu(s) model and speed, Ram speed and size, virtual/physical) of your FOG server?
What are the specs of the workstations (specifically the slowest one)?
What is the compression rating on the image you’re pushing?

Something to understand about multicast (and someone should correct me if I’m wrong) is that is does all the decompression on the server and then sends the packets out following multicast protocol. The idea of multicast is to do more on the server side and less on the client and get a constant speed. It also is meant to prevent using a file or part of a file that is in use to make a fail safe against corrupting files and such. The downside is that if you’re using an image with a compression level of 9 and your server isn’t all that powerful, multi-cast is going to slow down a lot compared to unicast where decompression is done on the client.

My point is if your server has less power or less optimization for decompressing then your clients, multicast will just be slower. Considering your speed difference of multicast and unicast, my guess would be this is the case.

Also, a side note in favor of just using unicast, I have used fog to deploy to a lab of 40 computers (10 at a time, which can be changed with the Max clients setting in the storage configuration, just fyi) with the same image on unicast and had no problems with corruption and the speed was glorious.

Another limiting factor is client and server port speeds. If your server is on a 10/100Mb port, you should upgrade that because it will make your life painful. But if your server is on a Gigabit switch then 10 clients on 100Mb switches will all run at around 1.7 GB/min (estimated mathematically and based on experience) If everything is on gigabit switches/ports then you might see a decrease in client speed as you add more simultaneous clients , but will still be around 2 or 3 times faster for 10 clients. Just to give you a little reference off the top of my head.

It would probably be a good idea to start recording average speeds for common configurations and post them in the forum somewhere so people have a reference of how fast to configuration ought to be performing.

@Tom-Elliott Also confirmed, it is working now. The sort is still by Captial and the lowercase alphabetic but that’s a minor issue

Just noticed another issue whilst mass updating some snapins.

If you try to only edit the title, description, arguments, or checkbox options you get that same error message.
At the moment, unless you are uploading a new file, you can’t save or update the snapin in the gui.

Another thing I just noticed is that the sort of the existing snapins is sorted case sensitively.
As in it lists everything that starts with a Capital letter alphabetically followed by lowercase alphabetic.

i.e.

A-script
Z-script
b-script
z-script

choosing from present list of snapins doesn’t work
“A file to use for the snapine must be either uploaded or chosen from the already present list” (that typo is in the error message)

I also tried clicking upload and emptying that field then updating. Still no good.

@onepotato NVME works on trunk for all partition types. I tested it myself
you can read more about the adventure to getting it working here…
https://forums.fogproject.org/topic/6315/hp-z640-nvme-pci-e-drive

Or you can just trust me, it will work and follow the following instructions to upgrade your fog version
https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

@Arrowhead-IT I ran

rpm -Uvh  http://rpms.remirepo.net/enterprise/remi-release-7.rpm
yum-config-manager --enable remi-php70
yum -y update

Then updated to the latest trunk

I didn’t see it do anything different with php packages in the FOG install, certainly did in yum -y update though.
Not sure how to tell which version of php that fog is using. I’m sure there’s a way but I don’t know it off the top of my head.
I know that php 7 is indeed installed though

php -v

PHP 7.0.3 (cli) (built: Feb  3 2016 11:30:45) ( NTS )
Copyright (c) 1997-2016 The PHP Group
Zend Engine v3.0.0, Copyright (c) 1998-2016 Zend Technologies

The dashboard certainly did load noticeably faster too.
So I think that the above method did the trick.
You may not even need to add the rpm, just enable remi-php70 with yum config mngr. It told me I already had the repo when I added it.

Hope this helps someone else update too.

I just saw this post and decided “I Want!”
Hopefully I don’t break anything…
I have centos7 and I was about to follow these guides
https://webtatic.com/packages/php70/
http://tecadmin.net/install-php-7-on-centos/#

But first I’m trying the centos version of @Tom-Elliott’s fedora instructions
being

rpm -Uvh  http://rpms.remirepo.net/enterprise/remi-release-7.rpm
yum-config-manager --enable remi-php70
yum -y update

Will report back

@mecsr said:

I updated FOG two days ago, so I think I should be good in that respect.

Just fyi, there’s typically at least a few if not a bunch or very many updates to the fog trunk version any given day containing many bug fixes and optimizations. It’s a program that just keeps getting better and you get the benefits of instantly.

The current version is 6303 and you’re on 6271. So I would suggest considering updating

@mecsr Have you run test disk on the vm your uploading that image from that gave you that message?

Still unsure why uploading an image would cause a cpu halt

Also for reference, since that server is one I set up when I worked there I know some things.

It’s on Ubuntu server 15.04 64 bit
As I recall it has a sandy bridge quad core intel i5
16 GB RAM
And it’s a HP 6300 Pro workstation being used as a server.
It has 2 4TB drives that are synced together nightly, so unless @mecsr turned off the cronjobs it is backed up database and all if an os reinstall is needed, but hopefully that can be avoided.

@mecsr What happens when you try to click install/upgrade?
That process won’t delete anything or anything of that sort, but that part of the install is now automated.

Also you should update to the latest trunk to get the latest kernel, that could help.

Hopefully some of the smarter people on here like @Tom-Elliott @Sebastian-Roth @Wayne-Workman @george1421 will have some idea on the cpu stall business

@BasavarajC You should certainly update to trunk for the better support for multiboot images.
But to answer your question.
When I’ve done multi-boot images I typically use the linux Grub boot loader and therefore call it a Linux image in Fog.
If you use the Windows boot manager to select the OS at boot then I would try calling it Windows 7. Though personally I would reccomend using Linux as the image type and GRUB as the bootloader as there is a lot more documentation and support and overall reliability and control for the GRUB method in my experience.

Thanks,
-JJ

@Tom-Elliott This is true, it is indeed fixed because Tom is the best