Yes,  you have a task sequence that handles the build and capture of your image.

For your patches you can do a couple of things.  First, if you are already 
using WSUS to patch your systems you can configure MDT to look to it for all of 
the patches.  The other option would be to import the patches directly into MDT 
each month.

You fire up a VM and run your build & capture task sequence.  MDT takes care of 
the rest.  In the end you have a new image with all of your patches.

You could automate the entire process.  Fire off a script at the end of the day 
and when you come in the next morning you have your updated images waiting for 
you.

As for your MAK, don't touch that until you're deploying machines in the final 
build process.

Mike


From: [email protected] [mailto:[email protected]] On 
Behalf Of Stuart Watret
Sent: Wednesday, September 16, 2015 12:33 PM
To: [email protected]
Subject: [mssms] Re: man seeks clarity - MDT and MAK keys


so i prep a build with all the software i want, patch it and capture it.



i don't supply a mak key in the image, instead make it part of the final build 
process yes?



are you saying this clean wim needs patching from scratch every month?



Stuart Watret

Offshore - IT Ltd

________________________________
From: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>> on 
behalf of Marable, Mike <[email protected]<mailto:[email protected]>>
Sent: 16 September 2015 17:27
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: man seeks clarity - MDT and MAK keys


Exactly.  Reusing your images and re-syspreping just leads to problems.



Always start clean.  MDT makes the process easy, it's best to take advantage of 
it.



Mike







From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of LEROY Mathieu
Sent: Wednesday, September 16, 2015 12:24 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: man seeks clarity - MDT and MAK keys



You should not supply any activation key when building your image, and you 
should not reuse your previous build and re sysprep them



Always re build with clean wim files and automate everything with MDT



Mathieu



De : [email protected]<mailto:[email protected]> 
[mailto:[email protected]] De la part de Stuart Watret
Envoyé : mercredi 16 septembre 2015 17:55
À : [email protected]<mailto:[email protected]>
Objet : [mssms] man seeks clarity - MDT and MAK keys



I auto patch my reference images every month, all my domain joined images use 
KMS and there are no issues.



I'm doing something wrong with my workgroup images, after a couple of months 
they won't sysprep once patched.  If I try to build from the image it tells me 
the max number of activations are reached.



On stuff that's built I can slmgr /upk and recover by adding the MAK key again.



My workflow for this is obviously wrong [:(] .



How is best to supply the MAK in this situation where I'm rebuilding and 
patching the same image every month?



Ta



Stuart Watret

Offshore - IT Ltd





**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues


**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues 



Reply via email to