readysteadywhoa
New Member
Hi there, I've recently started using NTLite to try and create some customized images for deployment at the company I work for but I'm wondering if I'm actually using the program for it's intended purpose.
The images install great with the features I selected, but it seems to be pulling system info from the workstation that NTLite was installed on, especially in WMI. I noticed when doing certain WMI queries, it's trying to contact the computer name of the NTLite workstation the image was created on, as if it was the local computer name. In our case the issues are with the Unified Write Filter -- doing some WMI queries against it return the actual local computer name, while others return the NTLite computer name, breaking functionality.
I then tested the deployment scripts using an OEM image (Windows 10 Ent 1909) and the problem doesn't appear, so it seems to be with how the unattended image is being created in NTLite. I also tried SysPrepping/generalizing the install after the fact but the problem persists even then. I haven't found any options in NTLite that sound like they would affect WMI (I did select to 'clear cache' but I don't believe it's related). I'm also not using the options in NTLite to populate values in the image with local machine values. I'm building off the same 1909 Ent OEM image that I tested with.
I also tried running NTLIte from a brand new 1909 VM (as recommended online), but then the computer name of the VM was then being substituted on deployed computers in the same way as it was with the original NTLite workstation.
Anyone run into these issues before? I know one of the biggest use cases of NTLite is customizing an install for the specific computer you're running it on, but is there any way to create more generalized images that are meant to be deployed to multiple computers?
Thanks!
The images install great with the features I selected, but it seems to be pulling system info from the workstation that NTLite was installed on, especially in WMI. I noticed when doing certain WMI queries, it's trying to contact the computer name of the NTLite workstation the image was created on, as if it was the local computer name. In our case the issues are with the Unified Write Filter -- doing some WMI queries against it return the actual local computer name, while others return the NTLite computer name, breaking functionality.
I then tested the deployment scripts using an OEM image (Windows 10 Ent 1909) and the problem doesn't appear, so it seems to be with how the unattended image is being created in NTLite. I also tried SysPrepping/generalizing the install after the fact but the problem persists even then. I haven't found any options in NTLite that sound like they would affect WMI (I did select to 'clear cache' but I don't believe it's related). I'm also not using the options in NTLite to populate values in the image with local machine values. I'm building off the same 1909 Ent OEM image that I tested with.
I also tried running NTLIte from a brand new 1909 VM (as recommended online), but then the computer name of the VM was then being substituted on deployed computers in the same way as it was with the original NTLite workstation.
Anyone run into these issues before? I know one of the biggest use cases of NTLite is customizing an install for the specific computer you're running it on, but is there any way to create more generalized images that are meant to be deployed to multiple computers?
Thanks!