I can not capture Win7 images anymore. Admin Account get's disabled?
-
Thursday, December 27, 2012 4:38 PM
For some reason, after no changes, I'm unable to capture images successfully. After it finishes, the computer reboots to a logon screen. When I try to log on, I get the message telling me the Admin account has been disabled. Any ideas on how I can fix that?
So far, I have rebuilt the Deployment Share, and I'm getting the same results. I run the capture, it upload and creates the wim, then reboots to a log on screen preventing me from getting in, since the Administrator account is disabled. I've never had this happen. Not sure how to resolve
- Edited by The Superman Friday, December 28, 2012 2:15 PM
All Replies
-
Friday, December 28, 2012 4:55 PMwhy would you need to login on the system you just captured? isn't the image the end product you will use to deploy computers.
or do you get that error while deploying your captured image? -
Friday, December 28, 2012 5:36 PM
Usually, I after I capture an image, the machine reboots it self and continues with it's sysprep. I have never seen it get stuck at the log on screen disabling the Administrator account. If I take the newly captured wim file and setup a task, then deploy it to a machine, that machine will get stuck at the log on screen as well since the Administrator account is disabled. Does this make sense as far as what happening? This is a problem because now, I can not update my images.
- Proposed As Answer by Betty Wong Sunday, January 06, 2013 6:07 AM
- Unproposed As Answer by Betty Wong Sunday, January 06, 2013 6:07 AM
-
Sunday, January 06, 2013 6:12 AMCheck if this helps.
-
Sunday, January 06, 2013 11:18 AM
Check if this helps.
The post is interesting, and I guess I can play with that, it's just, that I've never had an issue with MDT not rearming on it's own?
-
Wednesday, January 09, 2013 9:12 AM
Hello Superman,
did you find a solution?
Same problem here.
-
Wednesday, January 09, 2013 11:42 AM
No, I never was able to fix this. I've uninstalled MDT2012 along with WDS, re installed, rebuilt the Deployment Share and still have the same issue. It's a virtual server, so my next step is to completely remove the server and start over.Hello Superman,
did you find a solution?
Same problem here.
-
Wednesday, January 09, 2013 12:08 PM
do you update your exisiting images or start from scratch with the base image from microsoft.
if you use your exisiting image it might be that the rearm limit has been reached and that it might not behave like you expect it to.
and are you doing a standard task sequence or using a sysprep and capture?
-
Wednesday, January 09, 2013 12:14 PM
Hello Stefan,
i am doing an update of an existing image.
I saw my rearm limit has been reached.
I did do : customize, sysprep (with reached rearm) and then deploy. After this the administrator-account is disabled and the deployment will not go on after step 57.
I saw there were some issues with rearm with KMS. I am using MAK. This shouldn`t be a problem?
IF the rearm-registrykey is the problem...can this be modified from central MDT like cs.ini ?
Thx
- Edited by Mvd12345 Wednesday, January 09, 2013 12:21 PM
-
Wednesday, January 09, 2013 12:32 PM
Everyone keeps saying that the Rearm is the problem, but I've never seen this happen, and I've installed and use MDT / WDS many times. If it is the problem, I see no way to fix it. When I rebuilt the deployment share I even tried a clean install on a machine, an I still was not able to capture. Being that I'm virtual, I'm going to start over, given the amount of time that I've been trouble shooting this, I could have rebuilt the server 5 times by now.Hello Stefan,
i am doing an update of an existing image.
I saw my rearm limit has been reached.
I did do : customize, sysprep (with reached rearm) and then deploy. After this the administrator-account is disabled and the deployment will not go on after step 57.
I saw there were some issues with rearm with KMS. I am using MAK. This shouldn`t be a problem?
IF the rearm-registrykey is the problem...can this be modified from central MDT like cs.ini ?
Thx
-
Wednesday, January 09, 2013 1:05 PM
the fault is not with MDT superman it is with the image you try to deploy/capture
just try for once to use a unmodified windows disk/image import that into MDT and use it in a unmodified task sequence just to see if it works and if it does work from there.
mvd even though you use mak i think for creating the image it is wise to just start with a clean image. it shouldn't be that hard to set up and once it is set up eveytime you need a new image you can make one.
-
Wednesday, January 09, 2013 1:10 PM
Hello Stefan,
which issues will the rearm generate (using MAK-keys)?
Thx
-
Wednesday, January 09, 2013 1:21 PMpossibly the problems your experiencing now? otherwise well it will give problems with sysprep since it will throw errors and possibly won't execute at all.
-
Wednesday, January 09, 2013 1:24 PM
Hello,
i did the following:
1) take the problem-image
2)Customize my settings/applications
3)changed the registry key for SkipRearm from 0 to 1
4)Capture
5)Add new captured .wim to existing Task-Sequence
6)Deploy this task-sequence
7)Completed Succesfully !
So the SkipRearm-key is working for me (with MAK-keys)
.png)
