Posts made by foglegs

started using FOG 0.32 to get me thru my Windows7/Office2k10 deployments for 215 workstations, and was successful with FOG deployments, there was a slight learning curve but if you need something deployed quickly and not have to read tons of microsoft literature and tutorials then FOG is your answer. I have not yet tried 1.00 but sounds pretty cool especially now being able to read GUID partition tables this issue got me hung a few times.

how about created a new clean vm of fog as test and see where it gets hung up on.

Farm Town USA. (Fresno, California, USA)

Ok heres my update as to why I had terrible speeds trying to deploy a multicast to 8 workstations. It was because my mobile fog server was plugged into a 8-port 1Gb port switch…which eventually was uplinked to a VOIP phone (100mb) which in return the voip phone was the uplink to the rest of the network…so my fog deployments were severely bottleneck because my fog server was eventually squeezing thru 100mb pipe…by temporarily bypassing the voip uplink and plugging in the 8-port switch to the real network im happily able to say i successfully deployed 8 Windows 7 workstations thru muliticast at 590mb/min which took 52 minutes tops! then i had to image one 6200 and that took 6 mins at 3.39Gb/min.

ok I did try it on my lab fog server and no go…i also tried to build my own kernel with added scsi drivers and no go…well i guess i will stick to x32 for now on my home lab…ok back to my ssd issue

This is my issue with SSD and HP DC8300
A.) WD Black SATA3 320GB - inventories/uploads/downloads perfectly on the exact same HDD
B.) EXACT SAME DRIVE AS STATED ABOVE - WD Black SATA3 320GB - NO GO, I have 10 exact models dc8300 and HDDs WD Black SATA3 that are identical.

• Partition Information
• Error: /dev/sda: unrecognized disk label
  Disk…[Fail]
  C.) EDGE BoostPRO SSD
• Partition Information
• Error: /dev/sda: unrecognized disk label
  Disk…[Fail]

Im lost on why I could get one SATA to work perfectly then I pop in another exact HDD in original box and deploy and FOG doesnt recognize HDD, not to mention the original issue of not detecting my SSD, Tom I havent tried your new kernel you sent me for my Fog server at work I will try now…

well i know its off topic with this VM business i brought up, but I have VMWare Workstation 7 and I have a lab fog server vm and I can grab images from x32 Windows 7 but not x64 and I have read to change your HDD bus type but you can do that in workstation even if you create a new vm and install with advanced settings…its always scsi.

hey tom would this new bzImage also help with trying to get fog to see x64 Windows7 VM hdd’s? for some reason even on latest kernel running fog 0.32 with 3.3.8 I cant get my lab fog server at home to detect a Windows7 x64 when trying to inventory I always get the “failed with drive issue” but if i use x32 Windows7 works perfect.

i will try tom, regarding the format are you talking ntfs vs ext3? im just trying to get a ssd to register with the fog server then deploy/upload just the same as my other test workstations with sata and Windows 7 x64 but these dc8300s use UEFI

im thinking i need a newer kernel that supports ssd or UEFI enabled workstations…its truly the only difference between my current HP boxes…

well i do use the lastest kernel which 3.8.8 and of course it works perfectly with my HP dc5800, dc6000, dc6200 with Sata 3 drives and even my dc8300 works with sata but i cant get ssd. is there a reason why your not using latest kernel?

I have a HP DC8300 Elite that had a SATA drive which i could upload as image just fine, but im tryin to deploy that same image to a SSD on same host and I get these errors when trying to inventory with the HP DC8300

3.) Partition Information
Error: /dev/sda: unrecognized disk label
4.) Disk…[Fail]

Is there a newer kernel then the latest you can grab from the “Other Information Section>Kernel Updates” or do I need to be looking at FOG 0.33 beta

just cruising by since yesterday…what speeds where you getting before you updated to Toms latest bzImage for this exact deploy image? Are you at least 1Gb all the way around from the workstation to the network switch to the fog server? Also what are your specs for the fog server? is it a direct install with linux or you using a VM?

hey tom would your bzImage help wiht a HP DC8300 SFF/Micro with SSD. I having a hell of a time trying to get fog to register my DC8300 with a SSD but if i put a SATA it works perfect. Fog 0.32 Kernel 3.8.8

thanks for info you guys, thats one thing I didnt bother to try was doing a unicast of 8 seperate deploy tasks…I deployed one image which took 20 mins so i went full boar and tried 8 in a multicast and got stuck with 9 hours to deploy…so when i go back to site im going to have a 8-port 1Gb switch and plug the stations into that directly and try the unicast method to see how the times change.

and unicast is kicking off a task for one deploy one after another so i have 8 different deploys? or task one deploy one image then once thats complete perform another?

ok question here regarding one upload/download of a image. I have tested one image that is 35gbs of space used on a 60gb hdd and to upload this one image takes 15mins and compresses to 24gbs in the fog /images directory, to download or deploy the same image back to the workstation takes 10 mins flat. so based on the images’ times of upload/download if i had 8 identical workstations to deploy wouldnt that mean it would take 1 Hour and 20 mins to deploy one at a time back to back…what about all in a multicast, would that take longer or shorter then 1hour and 20 mins?

Well 35Gb downloaded as a deployment in 5 mins for one workstation? that sounds insane. I just tested my upload and download for one workstation using 1Gb nic on host and my fog server also using 1gb on a enterasys switch and my uploading of image took 20mins to copy 35gbs of space at 1.85GB/min , and to download the same file as a deploy it takes 11mins at 3.0Gib/min. Again this is not where I originally did a mutlticast of 8 hosts, so I will be taking a small 8 port 1 gb switch next time to make sure im at least getting 1gb speeds.

Fog Server:
HP DC8300, Intel Core i5 @ 290Ghz, 16Gb Ram, Intel 82579M Gigabit Network Card, WD 320Gb SataIII (HOST)
Ubuntu Desktop 12.04 VM 8Gb Ram 160GB HDD space, Virtual 1000 Mb/s Nic>Fog Server

My Fog server is considered mobile to me so I have no SSD or Fibre or 10Gbe as a data transfer methods

Im going to be switching out the SATA HDD on the host pc used as FOG Server and use SSD for data trasnsfer from HDD and also having the 1Gb nics should help will test and report back

ok i shrunk down the whole partition to 60GB total with 35gbs being used as OS with software installs, and I also did clean out all areas you mentions TR, which was actually kbs and mbs in space to begin with so no real change in full size of Windows7 OS, plus Office 2k10, Adobe Reader, Flash, and Java. my speeds look like this still 1.82GiB/min which avg out to 20 mins to upload the 60GB partition with 35GB of space actually being copied up to the fog server/images directory and then its compressed down to 25Gb. So it doesnt matter what my inital full HDD size of 100Gb or 60gb is, because whats never changed is the 35Gb of OS information that needs to get uploaded. So maybe I wasnt running full 1Gb speeds on the day i was testing at a remote site…next time I will plug my mobile fog server directly into a port on the switch instead of using a network cable plugged into a port out on the floor…and maybe I will just buy a small 10-port 1Gb switch and plug the workstations into that switch along with my mobile fog server because at that point i know for sure all my ports from workstation to fog server to switch will all be 1Gb…unfortunately I dont have any info on when i was downloading the image for one pc when i was at the remote site, all I have is the mutlicast speeds which was 65MiB/min for 8 hosts that had 35GBs to deploy which took 9 hours…maybe some one can figure out which this info if i was running 100mb or 1Gb…because if im currently getting 1.82GiB and that takes 20 mins to upload 35gbs then for 8 workstations that would take 2 hours and 40 mins…not 9 hours!!!

ya sysprep has been burned in my head as the very last thing you do to seal a box for image deployment since the days of Windows 2000, and no KMS here just VL on Windows 7 Pro/Enterprise…I will gave my speed transfer updates soon.

ya it definately sounds pretty close to my issue, fyi im going to reimage upload/download the huge hdd as a for sure test with speeds , then repartition it from 100gb to 60gb total and see where i sit with transfer times, also sysprep vs fogprep…should i run both or one over the other?