Windows 8 support in .33?
-
I have a similar setup as SNT. We are deploying windows 8 in mass now and have no issues. The only thing I can see is that you have to install .netfx3 Will this be changed in .33?
-
I am experimenting with Windows 8 and FOG 0.32. I set my OS type to Vista and use Multiple Partition Single Disk. I am not using FOGPrep, but going through sysprep in audit mode to setup the system, then sysprep to oobe.
My only issue is not FOG related afaik, my systems aren’t generated unique CMID’s. I do have them auto activating Windows and Office 2013 against a Server 2012 domain controller though, so it’s a partial success.
-
Have you had any luck with Windows store apps in audit mode? I seem stuck.
-
Everything I have read says do NOT install or update windows store apps in audit mode. MS says you can side load LOB apps if you need, but do not update or install any store apps before the oobe has run. It kills the sysprep run with an error about the apps not being provisioned for all users.
I think the suggested way is to use powershell scripts run at the end of oobe to install and update any apps from the store.
-
Does anyone have a sample powershell script for installs?
-
[quote=“chad-bisd, post: 12087, member: 18”]I am experimenting with Windows 8 and FOG 0.32. I set my OS type to Vista and use Multiple Partition Single Disk. I am not using FOGPrep, but going through sysprep in audit mode to setup the system, then sysprep to oobe.
My only issue is not FOG related afaik, my systems aren’t generated unique CMID’s. I do have them auto activating Windows and Office 2013 against a Server 2012 domain controller though, so it’s a partial success.[/quote]
Very interesting i’m going lab this right now because i have the setup as you
-
[quote=“chad-bisd, post: 12087, member: 18”]I am experimenting with Windows 8 and FOG 0.32. I set my OS type to Vista and use Multiple Partition Single Disk. I am not using FOGPrep, but going through sysprep in audit mode to setup the system, then sysprep to oobe.
My only issue is not FOG related afaik, my systems aren’t generated unique CMID’s. I do have them auto activating Windows and Office 2013 against a Server 2012 domain controller though, so it’s a partial success.[/quote]
When you do a upload or push what does it say for you file system type? mine says raw & it take 9 to 12 hours per computer like this
-
[quote=“The Dealman, post: 12935, member: 53”]When you do a upload or push what does it say for you file system type? mine says raw & it take 9 to 12 hours per computer like this[/quote]
When I set up a Windows 8 Virtual box, for imaging, and I am ready to upload my image, I always choose Windows 7 as the OS type, Multiple Partition, All disks (Non-Resizable) as the type, and I NEVER run fogprep, only sysprep. This will cause it to upload as yes a RAW format which takes a little longer to upload, but it shouldn’t take THAT long to upload.
So far is seems that your set up is fine.
When you said you are pushing an image are you pushing a virtual image? It’s really recommended you use Virtual Box and set your image up for deployment there. After sysprep upload to your FOG server.
Have you used the machines you are currently working with before? Have you imaged them with FOG before?
the reason I ask is because if the drivers aren’t available in the Kernel when it boots then you can get some pretty shotty speeds.I built my own custom kernel including the drivers necessary and I can upload a ~30gb image in under 20 minutes.
something else to consider, if you have jetdirect cards or any printers on the same network as the machines imaging, un plug the printer until you are done casting, I don’t know if the cards are causing a loop back or what, but I notice a SUBSTANTIAL increase in time (13+ hours) when I leave those damn printers on!
I can’t answer much about the CMID, as I didn’t even activate it was more or less a test to see if the hardware could handle the OS and if the software we were using could handle the OS. The image booted fine, and the software worked well, boss man just decided to stick with 7 this year.
-
[quote=“Jaymes Driver, post: 12936, member: 3582”]When I set up a Windows 8 Virtual box, for imaging, and I am ready to upload my image, I always choose Windows 7 as the OS type, Multiple Partition, All disks (Non-Resizable) as the type, and I NEVER run fogprep, only sysprep. This will cause it to upload as yes a RAW format which takes a little longer to upload, but it shouldn’t take THAT long to upload.
So far is seems that your set up is fine.
When you said you are pushing an image are you pushing a virtual image? It’s really recommended you use Virtual Box and set your image up for deployment there. After sysprep upload to your FOG server.
Have you used the machines you are currently working with before? Have you imaged them with FOG before?
the reason I ask is because if the drivers aren’t available in the Kernel when it boots then you can get some pretty shotty speeds.I built my own custom kernel including the drivers necessary and I can upload a ~30gb image in under 20 minutes.
something else to consider, if you have jetdirect cards or any printers on the same network as the machines imaging, un plug the printer until you are done casting, I don’t know if the cards are causing a loop back or what, but I notice a SUBSTANTIAL increase in time (13+ hours) when I leave those damn printers on!
I can’t answer much about the CMID, as I didn’t even activate it was more or less a test to see if the hardware could handle the OS and if the software we were using could handle the OS. The image booted fine, and the software worked well, boss man just decided to stick with 7 this year.[/quote]
How long does it take you to upload and push a raw image? I’m not using any virtual apps because i have physical test machines (1 of each model i have in my network). I’m test windows 8 deployment on the dell inspiron 15z right now.
-
I see, I use to image that way as well. Just make sure to sysprep before uploading to fog, you shouldn’t have any problems releasing the CMID information for a new client. Each Windows OS has a built in number of “re-arms” for imaging anyway.
I’m uploading a raw image as I type this and so far it has taken 11 min and 14 min remain. Image size 23.24 gb. uploading at ~920 mib/min.
I’d look into a custom kernel or using the “Kitchen Sink” kernel. Have you tried deploying? Does it also take just as long to deploy as upload?
-
I have tried those KitchenSinks in the past & they have been hit or miss for me. I found kernel that had the network driver in on this site under the hardware section i think. At this time i’m fighting the error
[SIZE=5][B]unable to move /images/dev/macaddress to /images/name-of-image[/B][/SIZE]I tried the steps here [url]http://www.fogproject.org/wiki/index.php/Images_Directory_Permissions[/url] but none of those worked. I had this issue before but i don’t recall what i did to resolve it
-
[quote=“Jaymes Driver, post: 12939, member: 3582”]I see, I use to image that way as well. Just make sure to sysprep before uploading to fog, you shouldn’t have any problems releasing the CMID information for a new client. Each Windows OS has a built in number of “re-arms” for imaging anyway.
I’m uploading a raw image as I type this and so far it has taken 11 min and 14 min remain. Image size 23.24 gb. uploading at ~920 mib/min.
I’d look into a custom kernel or using the “Kitchen Sink” kernel. Have you tried deploying? Does it also take just as long to deploy as upload?[/quote]
I actually may have what thought of what the issue is with what i’m doing. I started reading up on ahci for the sata mode type in the bios, in the past with my windows 7 images i used ata mode. I’m going to try and change it to that & see if it works or not. It’s been a while since i had to create a new image so i may have had a brain fart
-
Windows 7 support will also be good
-
[quote=“mlb2009, post: 15450, member: 13741”]Windows 7 support will also be good[/quote]
Windows 7 is already supported in 0.32, and as such would be supported in 0.33
