[RESOLVED] Windows 10 WAPT Deployment

[sfonteneau]

Hello,

we recently encountered this problem

. The x86 UEFI mode does not work

, the x86 legacy mode works
, and the x64 UEFI mode works.
The x64 legacy mode works.

It appears to be an IPXE/Wimboot issue; we are looking into a possible solution.

Could you try using x64?

[chris2b]

Good morning,
Thank you, so trying the x64 version did improve things, but now it's stuck on the deployment:

Screenshot 2022-05-12 134802.png (17 KB) Viewed 9171 times

[sfonteneau]

Error 1355: The specified domain either does not exist or could not be contacted.

The command displayed is the command that actually runs on your computer, so you can test it.

Is your machine with the console in the borgopeda.local domain?

Note that you selected the domain root as your OU. This is not an OU; you must select an OU.

[chris2b]

Hello, indeed the console wasn't in the correct domain.
I've changed that, and it's better, but now I'm getting error code 1326, which apparently corresponds to a user/password problem. However, in the XML file, I can't find how to enter the password correctly because our password starts with characters like @!$.

[sfonteneau]

You can try opening the console directly with the account in question; this will avoid being asked for the username and password.

The password is not passed to the XML file during the join process; that's the whole point.

[chris2b]

Thank you, it works correctly

[smandel]

Hello florian777,

WAPT version? OS/server version?

This is a problem that has been reported to us and occurs when the network takes too long to connect in WinPE. There was a fix in the latest version, wapt-2.2.1.11899-2d82654e.
Note: you must run postconf.sh after installation (nginx configuration as well).

Regards,

Denis

Good morning,

I confirm that the problem is still present in the latest version 2.2.1.11932
It works 1 out of 10 times.
The rest of the time you need to copy the command "start x:\dlls\..."

THANKS !

[sfonteneau]

We've just added another rather useless fix, but oh well,

at startup we'll wait 10 seconds anyway for the network to become available with a ping of 127.0.0.1

[smandel]

I don't have the problem on a VM running on ESX, but we're not talking about the same processing power...

[smandel]

However, there's a small deployment problem...
I customized the response file with UEFI partition formatting:

Code: Select all

<DiskConfiguration>
                <Disk wcm:action="add">
                    <CreatePartitions>
                        <CreatePartition wcm:action="add">
                            <Order>2</Order>
                            <Size>100</Size>
                            <Type>EFI</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>1</Order>
                            <Size>500</Size>
                            <Type>Primary</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>3</Order>
                            <Size>16</Size>
                            <Type>MSR</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>4</Order>
                            <Extend>true</Extend>
                            <Type>Primary</Type>
                        </CreatePartition>
                    </CreatePartitions>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">
                            <Order>1</Order>
                            <Label>WinRE</Label>
                            <Format>NTFS</Format>
                            <TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID>
                            <PartitionID>1</PartitionID>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <PartitionID>2</PartitionID>
                            <Order>2</Order>
                            <Format>FAT32</Format>
                            <Label>System</Label>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Order>3</Order>
                            <PartitionID>3</PartitionID>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Format>NTFS</Format>
                            <Label>Windows</Label>
                            <Order>4</Order>
                            <PartitionID>4</PartitionID>
                        </ModifyPartition>
                    </ModifyPartitions>
                    <WillWipeDisk>true</WillWipeDisk>
                    <DiskID>0</DiskID>
                </Disk>
                <WillShowUI>OnError</WillShowUI>
            </DiskConfiguration>
                        <ImageInstall>
				<OSImage>
					<InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>4</PartitionID>
                    </InstallTo>

But during the deployment he told me:

The partition selected for installation (disk 0 partition4) does not meet the required conditions (...)

So I don't understand because when I boot directly with the Win10 ISO, the installation assistant sees the partitions created by the deployment and when I select partition 4, it starts the installation correctly.

Do you have any idea...?

THANKS