Three smaller issues with my image

[YellowOnline]

Hello,

I only use NTLITE once per year for a new deployment. I have a problem I didn't have in the past using 1.5.0.5955 x64 with a Professional license. I guess it's a problem on my end though.

Somehow, it always asks for a key on setup. Specialize/Shell options/Product key (Activation) is empty and Windows PE (Setup options)/Windows setup options/User settings/Product key/Product key (Setup) is set to [Key]. Or is this because in my VM, where I do my testing, the BIOS does not contain a key?

My second issue is that partitioning doesn't work. Basically I just want the installer to wipe the whole disk and create a single partition for this install. I configured it like this:

But when I deploy the image:

Or would this be VMware Workstation related? I didn't try it on my ESX and on a physical machine I can only do it tomorrow.

Finally, I seem to miss an option to mark the password of the user accounts created during setup as "does not expire". I solve it by a command post-install, but I'm surprised it's not possible through the GUI.

Thanks for your time.

 

[Kasual]

Are you working with 7 or 10?

Seems like you are working with 7, i can't tell about disk partitioning as i don't use it, only delete partition and click on next, Windows setup create partitions automatically.

Take a look to the screenshots:

Disable pass expiration:

​

Enter key on setup:

​

 

[YellowOnline]

Are you working with 7 or 10?

Seems like you are working with 7, i can't tell about disk partitioning as i don't use it, only delete partition and click on next, Windows setup create partitions automatically.

Take a look to the screenshots:

Disable pass expiration:

View attachment 356​

Enter key on setup:

View attachment 357​

Hi,

Thanks for your reply. I am on w10.

The password expiry is just a command template similar to what I do. That's alright.
For the key however: this value is set to [KEY]. I'm guessing it doesn't work if the BIOS does not contain a key. I will try to add a default key and see how that works with activation.

 

[nuhi]

@YellowOnline,

Hi,

#1, correct, unless you edit the VM bios and add the key table, better to use one of the generic keys for Setup instead.

#2, you can use Disk Template wizard for that instead of the Individual partition for easier setup. Just set to 0MB those partitions you don't need.
However, be careful which disk/bios type you are deploying to and select that in the Type field.
Meaning you can't deploy the GPT/UEFI settings to the MBR/BIOS machine.
Make sure the VM, or any machine that would boot on, is set accordingly (in VMWare it's under VM-Settings-Options-Advanced-Firmware type).
Otherwise you will get similar errors on boot.
Let me know if you get stuck on that one. Attach your preset if the disk partitioning refuses to work, let me know which boot type and I'll debug it further.

#3 I think that option was skipped as its burried in the Windows user registry, per user, however that general expiration setting might be global.
Added to todo, I'll check it and add the option in Settings if securely and reliably possible.

 

[YellowOnline]

@nuhi
Hello and thanks. With a KMS key it functions indeed. I do hope it will read out the real one from BIOS still at activation time.
As for the partitioning: you're right. I switched the VM to BIOS instead of UEFI and it works right away. I never had this issue with physical machines. Do you know if I need to pay attention to this? I though UEFI always existed next to an old-fashioned BIOS.

 

[Kasual]

I do hope it will read out the real one from BIOS still at activation time.

It does if you use the right version, Home edition most of the times.

I never had this issue with physical machines. Do you know if I need to pay attention to this? I though UEFI always existed next to an old-fashioned BIOS.

You have to pay attention to this, WinSetupFromUSB (and maybe other tools too), build the USB ready for BIOS-MBR and UEFI-GPT. but if you are going to automate the partitioning, it matters.