EtherAssist
  • Administration
  • Agent mode
  • Integrations
  • Getting Started
  • Models and AI
  • Partner portal
  • Security & Compliance
  • Settings
  • Support
  • Supported topics
  • Tools
  • Using EtherAssist
  • Windows 11 readiness
  • PowerShell
  • Release Notes

Windows 11 readiness scripts

EtherAssist can draft PowerShell scripts that collect or transform readiness data for Windows 11 planning. Review every generated script before running it in production.

Before you begin

  • Sign in with an account that has access to this area.
  • Confirm the organisation, tenant, or source material you need to work with.
  • Keep customer data, secrets, and screenshots within your organisation's handling policy.

Prerequisites

  • Permission to collect device inventory or readiness data.
  • A target collection method: manual/USB, Active Directory, Configuration Manager, or CSV transformation.
  • A test device or pilot group for validation.

Generate a hardware readiness script

  1. Open the Windows 11 Readiness Wizard from the main page or search bar.
Windows 11 Readiness Wizard option on main menu
  1. Select Hardware Readiness Scripts.
Hardware readiness scripts option
  1. Choose a collection method: manual/USB drive, Active Directory, or SCCM collection.
  2. Review the generated script and confirm it is read-only before testing.
Hardware readiness script generated

Generate an application inventory script

  1. Open the Windows 11 Readiness Wizard.
  2. Select Application Inventory Script.
  3. Review the generated script before running it.
  4. Export inventory output for planning and application risk review.
Application inventory script generated

Safe script workflow

  1. Ask for a read-only script first.
  2. Define the input and output format.
  3. Request comments and assumptions.
  4. Review the script with an engineer.
  5. Test in a lab or limited pilot before wider use.

Prompt example

Create a PowerShell 7 read-only script that imports a CSV of devices and outputs Windows 11 readiness categories. Do not make tenant changes. Include comments and error handling.

Review checklist

  • No destructive commands.
  • Clear authentication assumptions.
  • Safe error handling.
  • No hard-coded secrets.
  • Output suitable for review or export.

Expected result

You have a reviewed script and a repeatable output format that can feed readiness reports, migration plans, or remediation groups.

Tips

  • Keep names, prompts, and configuration values specific to the task you are performing.
  • Check role, subscription, region, and tenant policy when a feature is not visible.

Troubleshooting

IssueWhat to do
The script includes changes to devicesAsk for a read-only version and remove modification commands before testing.
The output format is hard to importRequest CSV output with stable column names.
The script assumes the wrong management toolSpecify Intune, Active Directory, Configuration Manager, or manual collection explicitly.

Next steps