Yes, that's why you do a build and capture, not a reference image, which it sounds like you are doing.
I can kickoff a B&C and its done in about 6 hours for us, but it takes me about 10 minutes of attended work. Daniel Ratliff 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
