Any ideas? I've tried deploying on a VM as well as physical hardware, so that should eliminate driver issues. I'm just not sure that there's not something else going on here. We also had problems with this image joining the domain, but I added a "join workgroup/domain" step in the TS and that fixed the problem. And it doesn't match the name of the reference image, so that confirms that I "generalized" the image during sysprep. it's been different every time I run through a test deployment. For example, if I add the machine into SCCM with a name of "VCI-TEST-1809-L1", it ends up with a default name of something like "DESKTOP-C4FG59" or something like that. I've copied our existing task sequence, modified it to use the new test image, but it is not renaming the computer properly during OSD. I've built a reference image on a Hyper-V VM. I'm still using an 1803 boot image, since our server is not yet up to 1810 and I am unable to manage an 1809 boot image (can't add drivers, etc until we upgrade our site version).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |