It makes no sense to measure WDS virtually, because the virtual machines got ready at different times. That’s because multicast process deploys and the installation takes part “offline” so it is not like fog, that all machines get ready at the same time with multicast. Tomorrow i can test multicast performance but only with an 100 MBit switch.
For sure it can be said fog is quicker with 1 Gbit both in backup and deployment.

yeah or just make it a yearly thing that I update 3 times then re do them staggered ??? not so bad I suppose

Also you could try to specify some settings in your unattend.xml sysprep answer file:

<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>

fini 🙂

I think you can install windows 7 and customize the partition to be about 80gb, which is hopefully the smallest drive you’ll need to support. Do your customizations and sysprep it with an unattend option to resize the partition to fill the drive. Shutdown and take the image as single disk, multiple partition (it just works better).

When you deploy, depending on your sysprep options, it should fit onto any drive 80GB and over and auto expand the partition to fill the disk.

It’s more complex than this because of all the sysprep steps and making the unattend file, but I think this is the route you’ll want to take I think.

I do NOT use single partition resizable with Windows 7 because it may not work, and if it dies in the middle of resizing the partition, it makes it unusable.

I solved it by disabling the Stealth mode in with a registry tweak vi AD GPO: [URL=‘http://www.fogproject.org/wiki/index.php/Troubleshooting_Host_Management_Showing_Hosts_as_Down#Windows_Vista.2F7_.28Windows_Firewall_with_Advanced_Security.29’]A[/URL]rticle [URL=‘http://www.fogproject.org/wiki/index.php/Troubleshooting_Host_Management_Showing_Hosts_as_Down#Windows_Vista.2F7_.28Windows_Firewall_with_Advanced_Security.29’]HERE[/URL]

I went mad enabling / disabling firewall, logging packets, changing rules … That made it work. If you are not in an Active Directory, add the registry key, changing DomainProfile for PublicProfile, StandardProfile or PrivateProfile, depending of your needs.

I am wanting to deploy XP or Win 7 via Fog, but I would like the machine to pull the drivers from the server

What is the best option and is there any chance you can assist me on this

I can deploy images and join to the server but im kind of stuck with the driver side / updates

thanks

Lee

you do not need to specify the Reseal in your xml file as that’s what the switches do - by having this in your unattend file it conflicts with the switches you pass to sysprep. just remove this section all together from your unattend file and it should stop the issue.

Cloud windows 8 is more functional than a disk management software like partition magic: [url]http://www.partition-magic.org/[/url]

[quote=“danuel, post: 9573, member: 628”][url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url][/quote]

danuel, that guide is where I got some of the information but it is an incomplete guide. Also There is the SAD2 part which bloats the install to way to big a size for storing and transferring over a WAN or even a LAN at some points. That is why I wrote this one.

Something perhaps to do with fixed lease addresses and corresponding DNS entries on the windows side perhaps? Just a thought.

After restarting FOG service, it worked…
No more information in the log… I don’t know why it needed a restart of the service while it did not work this night.

That is a ridiculously simple and awesome solution, thanks!

the default username is set under WindowsNT/Winlogon in the registry, for more info just google display last user registry (make sure your GPO doesn’t disable this)

OK…thanks…everything appears to be clean and working as expected!

A backup recovery software can help solve more questions, so you need to have one like: [url]http://www.partition-magic.org[/url]

I too am having trouble to deploy images wit UEFI images. Each time I deploy the computer boots into recovery.

If the machine was in the domain before you reimaged, then you’ll need to reset the computer account or delete the computer account before you can add it back as the same name.

If you have computers in specific OU’s, then you can just reset the computer accounts and the domain adds should work.