Configuring sysprep is beyond the scope of the FOG Project, so its not specifically a FOG concern. But I can give you some guidance on your next steps.
You need to configure the unattend.xml script to fit your company’s environment there isn’t a one size fits all solution here. There is a few sizes that fit most approach you can take. There are a few online sources that will let you dynamically create your unattend.xml file with the settings specific for your site. One place to start is here: http://windowsafg.no-ip.org/ Construct your unattend.xml file with your required settings (or generic /anonymous info and then hand edit it with a text editor later) and download that to your target computer. Place that updated file in c:\windows\panther or c:\windows\sysprep. When you invoke the sysprep command be sure to reference the full path to your unattend.xml file. There is nothing specific you need in your unattend.xml file related to FOG.
You WILL need to create a setupcomplete.cmd file to reenable the fog client once OOBE is done. Don’t forget to install the FOG client in your golden image but disable the service. We do it this way so that the fog client doesn’t start doing its thing too early in the OOBE process before OOBE finishes.
Now let talk about your key management. If you have a KMS environment available, you should USE IT. MAK keys are use once. Once you burn through all of your MAK keys you will have to call the MS Licensing center and request more keys to be added to your account. With KMS you are in charge of your keys. When you retire computers your KMS keys are returned to your key pool. With KMS you can revoke or send out platform upgrade keys. You can also use KMS for MS Office and other components too. Its a great tool if you have more than just a handful of computers.
