![]() I had found parts and pieces of these processes previously but this was the first answer with all the pieces. Is there a ligit (even if I have to contact Microsoft) way to reset the Rearm count (for legitamte purposes) to avoid loosing days + of work? We don't have time for the tech to redo his manual work, and our Rearm count is at 0. I did not realize the Rearm count had decremented to (0) and am now in a delima. So, in this case I did a sysprep / capture with MDT 2012, sent the image to our tech who then made several updates and sent it back to me. In this particular case the client was already using ghost images and we had a short deadline to update their image for our break/fix shop. ![]() ![]() I have built several MDT images to date, but all were built from source CD up to drivers and apps. We (I) am building a quick first MDT 2012 Windows 7 image for a new client, with the intent to bring them up to a full-blown MDT image in the near future, as they do have an SCCM 2012 and KMS server base. The initial indication I had problems was that the local administrator account was disabled after sysprep on both the source laptop, and also on any VMs or laptops I tried to image. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |