• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 7 subscribers
  • Views 810 views
  • Users 0 members are here
Options
Related

Intune Cutover - Borked Machines

steve elliott
3 months ago

Hi - I'm running some test migrations of Intune managed, EntraID Joined PCs - but it's failing on the last task - "BT-EntraIDCutover"  I'm seeing an error of "Result code: 0 Invoke-InstallProvisioningPackage error '', hexadecimal value 0x05, is an invalid character."

The provisioning package is deployed as C:\Quest\BulkEnrollmentPackage.ppkg, I've checked that the name of the file is correct in the Profile section of the Quest tool, and that the path for the bulk enrolment package under Configurations > Repositories is set to C:\Quest (I have tried this with and without the trailing \ at the end of the path) and I get the same result.

I've tried this on a few different machines to make sure it's not anything odd on the machine and get the exact same result.

The result of this the machine is stuck between neither tenant, meaning you can only login if you have prepared a local Administrator account in advance to deal with this type of situation.

Any thoughts are welcome.

Thanks

Steve

Parents
  • 0 2 months ago

    Validate package: Open the .ppkg file with a text editor like Notepad++ and ensure the XML is valid and well-formed. Look for any special characters or unexpected encoding causing the 0x05 issue.

    Permissions: Verify the user running the Intune migration has sufficient permissions to access the package location (C:\Quest or C:\Quest\BulkEnrollmentPackage.ppkg).

    Double-check backslashes: Ensure the path in the Quest tool profile and repositories matches the package location exactly, including trailing backslashes. Try both options with and without the trailing slash.

    Additional Checks:

    Event logs: Check Intune and local machine event logs for any additional details related to the "BT-EntraIDCutover" task failure and the 0x05 error.

    Quest support: Consider reaching out to Quest support for their expertise on the Bulk Enrollment tool and potential compatibility issues with EntraID joining.

    Hopefully, these suggestions help you identify the root cause koows and get your migrations back on track. Keep us posted on your progress, Steve!

Reply
  • 0 2 months ago

    Validate package: Open the .ppkg file with a text editor like Notepad++ and ensure the XML is valid and well-formed. Look for any special characters or unexpected encoding causing the 0x05 issue.

    Permissions: Verify the user running the Intune migration has sufficient permissions to access the package location (C:\Quest or C:\Quest\BulkEnrollmentPackage.ppkg).

    Double-check backslashes: Ensure the path in the Quest tool profile and repositories matches the package location exactly, including trailing backslashes. Try both options with and without the trailing slash.

    Additional Checks:

    Event logs: Check Intune and local machine event logs for any additional details related to the "BT-EntraIDCutover" task failure and the 0x05 error.

    Quest support: Consider reaching out to Quest support for their expertise on the Bulk Enrollment tool and potential compatibility issues with EntraID joining.

    Hopefully, these suggestions help you identify the root cause koows and get your migrations back on track. Keep us posted on your progress, Steve!

Children
No Data