Jump to content

Recommended Posts

Posted
I have an MDT deployment share that I have used for previous imaging deployments - Windows 7 a few years ago (successful), Windows 10 Education for offices and admins (few days ago I completed), so I created a new WIM for my classrooms/lab. I basically copied the TS from the office WIM which deployed, joined the domain, then silently installed Office 2016 successfully to install my new academic WIM. The image itself deploys normally, and it logs in with administrator account like it wants to continue, but doesn't join the domain or install my app, much less give me an on-screen error. Doesn't seem to be driver related, there's make/model crossover between the 2 different deployments. I even took the working TS and changed the OS to the classroom WIM. I can't seem to find any info of other people having an issue like this. Any ideas?
Posted
As much as I wanted to resolve the issue, time is of the essence here, it's not a large image, so I decided to re-create it from scratch. It captured and is now deploying successfully.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...