Hi All,
I ran into an interesting issue last week, I have a custom .WIM file that I created for my acct dept, has some software on it that other departments don't need. Its fully patched (or was as of last week) I captured the image without incident, imported into MDT created, deployment task sequence. Etc. What is happening is the process is getting to the last part of applying my image, gets to APplying Unatended.xml file using DISM.exe and hangs there for about 5 mins. Then the computer restarts and it takes me to the login screen.
When I first tried to login (thinking it was done) it stats that the administrator account has been locked, I thought well that's odd, so I restarted in safe mode and logged in that way. Once I got to the desktop I noticed that the computer had not been imaged at all and still had the previous test image installed on said machine. Thinking it was my task sequence I created a new one but get the same results.
So I am testing another image (for acct) that was patched 2.17.14 and it works without incident. I checked the logs but see no errors or anything that jumps out at me.
Thoughts?
Alex
I ran into an interesting issue last week, I have a custom .WIM file that I created for my acct dept, has some software on it that other departments don't need. Its fully patched (or was as of last week) I captured the image without incident, imported into MDT created, deployment task sequence. Etc. What is happening is the process is getting to the last part of applying my image, gets to APplying Unatended.xml file using DISM.exe and hangs there for about 5 mins. Then the computer restarts and it takes me to the login screen.
When I first tried to login (thinking it was done) it stats that the administrator account has been locked, I thought well that's odd, so I restarted in safe mode and logged in that way. Once I got to the desktop I noticed that the computer had not been imaged at all and still had the previous test image installed on said machine. Thinking it was my task sequence I created a new one but get the same results.
So I am testing another image (for acct) that was patched 2.17.14 and it works without incident. I checked the logs but see no errors or anything that jumps out at me.
Thoughts?
Alex