graymadder

Have you added the images through the WDS console? Open up WDS expand server, expand images, expand install images, select your group and then right click and select add image. Browse to your image. I don't have the console right now, but the steps should be pretty close.

I ran into a similar problem, except for it was after the 3rd sysprep. The reason is that when you run sysprep it automatically uses the -rearm. You can only -rearm a pc 3 times. The workaround is either have an active KMS environment or add skiprearm to your unattend. when doing iterative builds during development, you can continue to sysprep an image multiple times when using SKIPREARM and the only limitation will be the 30-day grace period for activation. Once you have an image that you are ready to actually deploy, the last sysprep should be done without the SKIPREARM parameter.

gangsterhenk posted a similar question and i think both answers are the same. Here is my section for the disk config under WDSCLIENTUNATTEND.xml - <DiskConfiguration> - <Disk wcm:action="add"> - <ModifyPartitions> - <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Local Disk</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> - <CreatePartitions> - <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration>

Here is my DiskConfig on my WDSClientUnattend.xml. It will partition the enitre disk and format it NTFS - <DiskConfiguration> - <Disk wcm:action="add"> - <ModifyPartitions> - <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Local Disk</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> - <CreatePartitions> - <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration>

VLK Cutomers can request more MAK's. My org started out with 250. Once we burn through those we can request more, even before we use all of them we can get more. MAK's are one key that can be activated x number of times. Once they have all been activated that key becomes dead and you will get a new one. This is MS way of dealing with piracy. The VLK keys were good for infinite amount of uses so if someone got a hold of VLK they had all the benefits, now the MAK's will expire after x number of uses. MAK is one of the two ways of activation in VLK 2.0. KMS is the other method.

I think you are confusing KMS with MAK. Once you have activated a pc with a MAK you don't have to reactivate it. KMS is different. You have (only tested with Ent Edition) a 30 day grace period which can be reset 3 times giving you a total of 120 day grace period. slmgr.vbs handles this, I believe the command is slmgr.vbs -rearm which is ran from the sys32 dir. I think what cluberti may be talking about is taking an image of the pc through backup and restore centerand this would be on a per maching basis. But if you use WDS to take the image then you must run sysprep in order to properly image the pc and then you would have to reactivate the machine using up another MAK. At least this is my understanding.

From my understanding of the VLK 2.0 is what you are calling VLK's is actually MAK's (multiple activation key) and I believe everytime you use them it counts towards your total count. I think VLK customers can request more MAK's. Check with your VLS agreement it should give you that information.