[SOLVED] tis-windows11-upgrade

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
smandel
Messages: 111
Registration: May 5, 2022 - 11:30

June 1, 2022 - 4:03 PM

Hello,

I'm having a problem with the Windows 11 migration package from Windows 10.
I successfully built the package using a Windows 11 ISO and uploaded it to the WAPT server.
The `def_install` file contains an installation command with a `/noreboot` option.
The problem is that the logs show the installation failing because of this `/noreboot`.
So, I modified the package and removed the `/noreboot` option. The Windows 11 installation completes, but it shows an "ERROR" error in the console.
Is there a specific reason why the `/noreboot` option is failing, or is there a solution to prevent the package from showing an error?

Thank you!
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

June 1, 2022 - 4:44 PM

Hello,
I'll try again on my end. Could you please send me the WAPT installation logs (from the console) and any logs found in C:\WindowsUpgradeLogs if you find a relevant error message?

Regards,
Jimmy
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

June 1, 2022 - 5:36 PM

I also invite you to install the package https://store.wapt.fr/store/tis-windows11-requirements to ensure that the PC is compatible with Windows 11.
smandel
Messages: 111
Registration: May 5, 2022 - 11:30

June 2, 2022 - 10:14

Good morning,

The script confirms that the workstation is capable:

Code: Select all

Auditing dsirum-windows11-requirements
Auditing: dsirum-windows11-requirements
{
    "returnCode": 0,
    "returnReason": "",
    "logging": "Storage: OSDiskSize=238GB. PASS; Memory: System_Memory=8GB. PASS; TPM: TPMVersion=2.0, 0, 1.38. PASS; Processor: {AddressWidth=64; MaxClockSpeed=2112; NumberOfLogicalCores=8; Manufacturer=GenuineIntel; Caption=Intel64 Family 6 Model 142 Stepping 12; }. PASS; SecureBoot: Capable. PASS; ",
    "returnResult": "CAPABLE"
}
Auditing 4C4C4544-0043-5A10-8033-B6C04F4A3333
OK: No setup.py
Pas de résultat d'audit pour dsirum-windows11-requirements(=2021.11.30-4): OK
4C4C4544-0043-5A10-8033-B6C04F4A3333(=1): OK
Moreover, deployment via WADS in Windows 11 is functional.
smandel
Messages: 111
Registration: May 5, 2022 - 11:30

June 2, 2022 - 10:54

And so here are the WAPT console logs:

Code: Select all

Auditing dsirum-windows11-upgrade
ERROR: Windows 11 upgrade failed
Auditing 4C4C4544-0043-5A10-8033-B6C04F4A3333
OK: No setup.py
Pas de résultat d'audit pour dsirum-windows11-upgrade(=10.0.22000-93): ERROR
4C4C4544-0043-5A10-8033-B6C04F4A3333(=2): OK
And here are the last lines of the "setupact.log" log file:

Code: Select all

2022-06-02 10:40:41, Info                  MOUPG  Finalize: Leaving Execute Method
2022-06-02 10:40:41, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2022-06-02 10:40:41, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2003]
2022-06-02 10:40:41, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2001]
2022-06-02 10:40:41, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [5].
2022-06-02 10:40:41, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x5, 0x64 / 0x64, 0x64
2022-06-02 10:40:41, Info                  MOUPG  ProgressHandlerAction: Sending final progress message for action [5].
2022-06-02 10:40:41, Info                  MOUPG  ProgressHandlerAction FinalUpdate: 0x5, 0x64 / 0x64, 0x64
2022-06-02 10:40:41, Info                  MOUPG  Signalling actions thread to shut down.
2022-06-02 10:40:41, Info                  MOUPG  Waiting for actions thread to exit.
2022-06-02 10:40:41, Info                  MOUPG  Actions thread has exited.
2022-06-02 10:40:41, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2004]
2022-06-02 10:40:41, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x2000]
2022-06-02 10:40:41, Warning               MOUPG  CSetupDiagnostics::ReportData - Not reporting WINDLP data point [0x3000]
2022-06-02 10:40:41, Info                  MOUPG  DlpTask: Leaving Execute Method
2022-06-02 10:40:41, Info                  MOUPG  Setup phase change: [SetupPhaseInstall] -> [SetupPhasePostFinalize]
2022-06-02 10:40:41, Info                  MOUPG  SetupHost: Reporting pending reboot event
2022-06-02 10:40:41, Warning               MOUPG  SetupNotify::ReportEvent - Report ID or Event Reporter not available.
2022-06-02 10:40:41, Info                  MOUPG  SetupManager: Rebooting system... prevented by command line override.
smandel
Messages: 111
Registration: May 5, 2022 - 11:30

June 2, 2022 - 11:25

Okay, never mind, the migration is working fine.
After rebooting, Windows 11 installs successfully and the "ERROR" status disappears after a package audit. 👍
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

June 2, 2022 - 3:00 PM

Hello,
Perfect, yes, I should implement a WARNING message that prompts a reboot rather than an ERROR message. I'll submit an internal ticket.
I was going to reply that NOREBOOT seemed correct.

Regards,
Jimmy
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

June 9, 2022 - 3:36 PM

Hi @smandel,

Just so you know, the package has been redesigned. You can see the changes here:
https://wapt.tranquil.it/store/fr/tis-w ... e-template

Regards,
Jimmy
smandel
Messages: 111
Registration: May 5, 2022 - 11:30

October 5, 2022 - 11:36

Hello,

thank you! 👍
Everything seems to be working fine!
Locked