The easy way to get around the three time limit of sysprepping is to either a) use a virtual machine and save a snapshot before the first time you sysprep, or b) capture an image through the console of the state before sysprepping, and then deploy it when it to the same class machine when it needs updated. If you accidentally reached the three rearm limit without having to start over from scratch, here is a step by step how to get around it
!!LINK!! Easy Sysprep V3 Final
Hello, Thank you very much for your explanation !! now I understand better the big part of the problem. However, a few points still seem unclear to me: 01 - According to the Microsoft communicated link: the limit of 3 rearm is applied to versions Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2 and months I am on Win server 2016 and Win server 2019 and this explains the value Reamaining Windows rearm count = 995 after executing the slmgr.vbs / dlv command (capture attached) and what I confirm with the link below: -us/windows- hardware / manufacture / desktop / sysprep - generalize - a-windows-installation # limits-on-how-many-times-you-can-run-sysprep am I true ?? 02 - in my current case: I deployed a new VM, and the result after booting: new SSID, SkipRearm = 0, GeneralizationState = 7, CleanupState = 2, Reamaining Windows rearm count = 995 (attached captures) **** If I only change the GeneralizationState to 3 value on the same VM does not work. **** Another Sysprep on the same VM with GeneralizationState = 7 On. Thank you very much for your help and explanations Looks. Hadjer YH. ![99837-error.png][1]![99819-reamaining-windows-rearm-count.png][2]![99838-generalizationstate.png][2]![99759-skiprearm.png][3] ![99931-reamaining-windows-rearm-count.png][4] [1]: /api/attachments/99837-error.png?platform=QnA [2]: /api/attachments/99838-generalizationstate.png?platform=QnA [3]: /api/attachments/99759-skiprearm.png?platform=QnA [4]: /api/attachments/99931-reamaining-windows-rearm-count.png?platform=QnA
Hello Thank you for those Steps !i have an issue :once we are in audit mode and after finalizing the customization of windows if i run the sysprep with Generalize its giving issue later on when the users login into the pc the profile loading is very slow average of 7 min .if i run sysprep without Generalize i lose all customization but when user login its work file , so look like generalize make issue with user profiles .do you know alternative solution plz 2ff7e9595c
Kommentare