I get this error when i try to deploy snapins to a group.
[I]Failed to create deployment tasks for the following Hosts[/I]
[I]xx: Snapins Are already deployed to[/I]
I checked under active task and active snapins task and there is nothing there.
I get this error when i try to deploy snapins to a group.
[I]Failed to create deployment tasks for the following Hosts[/I]
[I]xx: Snapins Are already deployed to[/I]
I checked under active task and active snapins task and there is nothing there.
I solved it with kind of a workaround. I ended up recreating image to be PartClone as this was old image from 0.32 fog and it was PartImage.
I will try your suggestion if I get the same error with the image which can’t be recreated. Thank you.
No, MultiCast starts just fine but after it finishes the image wont boot (bootmgr is mising press ctrl+alt+del.). The same image works just fine if i send it with UniCast.
If i deploy two machines seperatly with unicast everything Works fine. But if I use multicast on the same two machines the deployment finishes normaly but after computers restart, they wont boot. They show bootmgr is mising press ctrl+alt+del.
What is the cause of this problem? I am using 1.2 and trying multicast for the first time after upgrade from 0.32>1.1.1>1.1.2>1.2
Update: After fast wipe it wont even deploy (unicast or multicast) just restarts.
After upgrade my size numbers are little messed up in firefox. How do I correct them back.
…ok i guess the problem is bigger. When i click submenus under host such as Groups, Basic Tasks, AD… nothing happens.
Also in chrome the information is just loading.
[url=“/_imported_xf_attachments/1/1162_fogsize.jpg?:”]fogsize.jpg[/url][url=“/_imported_xf_attachments/1/1163_fogsize2.jpg?:”]fogsize2.jpg[/url]
Just to update with the solution. I downloaded 1.1.2 files again and than I ran 1.1.2 setup again; nothing more and now it works, thank you for pointing me in the right direction.
It was for sure i also tried another image, same result. As i said in Image Management under Image Manager it is set as PartImage. What else can i do.
This is first deployment that i tried after upgrade. Maybe something went wrong when upgrading. Evertyhing went well other than updating database from 1.1.1 to 1.1.2 i had to use [URL=‘http://fogproject.org/forum/threads/fog-upgrade-1-1-1-1-1-2-database-error.10956/#post-31683’]this [/URL]soulution.
At [url]http://<fog-server>/fog/service/ipxe/boot.php?mac=XX:XX:XX:XX:XX:XX[/url] i see:
[code]#!ipxe
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=“MYDNS” keymap= web=“FOGIP”/fog/ consoleblank=0 loglevel=4 mac=xx:xx:xx:xx:xx:xx ftp=“FOGIP” storage=“FOGIP”:/images/ storageip=“FOGIP” web=“FOGIP”/fog/ osid=5 loglevel=4 consoleblank=0 irqpoll chkdsk=0 img=win7master imgType=mpa imgid=1 imgLegacy= PIGZ_COMP=-9 hostname=hptst type=down
imgfetch init_32.xz
boot[/code]
Yes i am downloading and i have recreated the job multiple times.
I see, but when deploying it still goes to same error (partclone), despite being partimage in image type.
Ok i checked the box for FOG_FORMAT_FLAG_IN_GUI i did not find the FOG_LEGACY_FLAG_IN_GUI. Image type was already Partimage i changed it back and forth to be sure but it still somehow goes to Partclone.
Is there any way to implement this into new (1.1.2) version.
[url]http://fogproject.org/wiki/index.php?title=Bypass_Host_Registration[/url]
This is really useful, when deploying small image for testing purposes on different machines few times a day.
I have updated fog from 0.32 to 1.1.1 and than to 1.1.2. All the images on the server were created with 0.32. Now when trying to deploy with 1.1.2 i get this error (Partclone>This is not partclone image.).
I get it that because image was created with older version of fog now it can’t deploy. How can i solve this, besides from obvious uploading all the images with new version of fog. Thank you.
SOLVED
I mean this is crazy. The problem was the image. I did some more tweaking not sure what fixed it but really only think that could fix it was the fogprep.exe that I run this time (I did not run it the first time since I’ve read somewhere that it is no longer necessary). Or maybe that I changed partition size in image for ( ) from 190gb to 140gb and ( ) from 100gb to 20gb (I expand this via unattend.xml after deployment)
@Tom Elliott, thank you for the tips i managed to get it down to 90gb especially WindowsUpdateCleanup was huge. Just finished deployment in 19min. And that is all on production server not the test one from yesterday.
I don’t really understand how that caused the problem to fog while deploying but the important thing is that it works now.
Ok, i just did test install of fresh fog 0.32 on ubuntu 10.04 with no extra settings, so i could eliminate any nfs, centos issues.
And the problem is still there. After it goes over 50gb in deployment it starts to drop. Instead of 20min with speed 5,5gb it drops to 1,3(something) and it takes 1h30min to complete. So the problem is with fog or maybe with the image i will try another image with similar size over 50gb, but i doubt that is going to make any difference.
Did anybody successfully (in speed) deploy image over 50gb. I mean win7 is around 30gb add MsVisualStudio both Basic and Express and that is little over 10gb, there is MsOffice and few others. So you are easily over 50gb. In my case almost 100gb there is no other way around it. Compressed size of the image is 38gb.
@Tribble, We have to have that kind of size, because we need all the programs there is no other way around it.
@Tom Elliott, I agree with you. Where could i look for those NFS settings. My /etc/exports looks like this:
[CODE]/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
[/CODE]
Fog is on Cenots 6.4
0.32
I noticed that this happens when deployment reaches around 50% and than it starts to go down. Image is 100gb big so it could be that problem is the size and not 50% progress, but than again upload of the same images goes without a problem.
Speed is 5.5gb/min at the beginning all the way up to around 50% and when it starts dropping down it drops 0.01 every second so by the end of deployment speed is around 1.17gb/min.