Hyper-V OS Deployment

Discussion in 'Virtualization' started by razer86, Sep 12, 2013.

  1. razer86

    razer86 MDL Novice

    Jun 21, 2013
    2
    0
    0
    We perform computer repairs and services, and have currently built a Win8 pc with Hyper-V that we have been using to create sysprep 'base images'.

    Essentially, perform the Windows install on a VM, enter audit mode, install OEM info, drivers, Windows Updates etc. Snapshot the VM, sysprep /generalise /oobe, create the install wim from the VM that will be deployed on to the customer machine via DISM and then revert the VM to the snapshot state so the rearm count doesn't get used until the client machine boots up and enters OOBE.

    The problem we are having now, the VM's have been installed longer than the grace period and as such, will not perform Windows updates. Is there anyway this system could be made to continue use without haveing to rebuild the VM's every couple of months due to rearm counter?

    I know the of MDT, but that is built for use with Vol/KMS/MAK keys if I'm not mistaken. The method we are currently using allows us to have an up to date image for any os (currently only using 7/8) that can be quickly deployed to a customer computer with their existing Installation Key.
     
  2. rrohela

    rrohela MDL Expert

    Sep 1, 2009
    1,612
    1,405
    60
    If i remember correctly then windows 8 can't be syspreped more than 8 times.... Use snapshots to return to previous point but this will also increase your time required to install updates again & again...