Applying Room Changes with PowerShell is a practical project for learners who already know basic PowerShell. Help a workshop organizer move only approved sessions to suitable rooms. Build a complete change plan, preview it, and use one confirmation for the whole plan before saving a new schedule.
Two Guided Labs first establish the exact session-to-room relationships, then make native preview and confirmation control the real write. One independent Challenge changes the IDs, approvals and capacities while using the same mechanisms. Every lab starts with its own schedule and plan; files do not carry over between environments.
What You Will Learn
After completing this course, you will be able to:
- join sessions and rooms by exact IDs, even when their displayed names are identical;
- validate every requested session, approval and room capacity before applying any change;
- describe the whole plan with its old and new room assignments;
- use
SupportsShouldProcess,ShouldProcess,-WhatIfand-Confirmfor one overall authorization; - make preview and a No response leave originals untouched and create no output or temporary files;
- save and reopen a complete new JSON schedule while preserving sessions outside the change plan, nested metadata, original inputs and notes.
Who This Course Is For
This course is for PowerShell learners who want to make a controlled data change with an honest preview and a clear approval boundary.
Prerequisites: Complete PowerShell for Beginners or have equivalent experience with objects, JSON, filtering, function parameters and error handling. The Guided Labs explain the approval, capacity and native confirmation mechanisms used here. The two Bash projects are not prerequisites.
Learning environment: LabEx provides a browser-based Linux environment with PowerShell and synthetic event data prepared for you. Read and edit your scripts in WebIDE; use PowerShell in Terminal to run them, answer confirmations and read the saved result. No local installation, Windows administration or real meeting-service account is required. Terminal labels and command output remain in English.
Frequently Asked Questions
What makes a requested room change valid?
The exact session must exist and be approved, the target room must exist, and its capacity must accommodate the attendees. Capacity exactly equal to attendance is valid. Every request is checked before writing. Target time slots are already free; you do not build a calendar-conflict solver.
What happens during preview or when I decline?
-WhatIf and No at the native confirmation prompt leave course files unchanged and create no output or temporary files. Yes authorizes the whole validated plan once. Existing output targets are refused; you save to a new JSON file under an existing parent directory. One overall confirmation does not promise recovery from crashes or concurrent writers.
Will saving discard information the script does not recognize?
You work with supplied, well-formed UTF-8 JSON in a documented shape and preserve its other values, including nested metadata, array order, Boolean values and date-looking strings with their original offsets. Property order and whitespace may change. The result is a complete schedule with only the authorized room assignments changed.
