Exam AZ-104 topic 1 question 21 discussion

Ans: A After Windows is installed but before the logon screen appears, Windows Setup searches for the SetupComplete.cmd file in the %WINDIR%\Setup\Scripts\ directory

GPOs aren't a thing in Azure AD. Just putting a Script inside the VHD doesn't make it run on boot. Configuring a "SetupComplete.cmd" in the "%windir%\setup\scripts" directory is the correct approach:

Rationale: The SetupComplete.cmd file is executed immediately after the operating system setup is complete, ensuring that the scripts are run on the new virtual machines as part of their initial configuration. This solution is both direct and efficient for automating the configuration of freshly created VMs. Why not the others? B: Logon scripts via GPO: These run only when a user logs in. For automating initial configurations on new VMs, this is neither timely nor appropriate. C: Startup scripts via GPO: While they run during the computer's startup, GPOs require the machine to already be part of the Active Directory domain, which is not guaranteed for new VMs during initial setup. D: Scripts in a new VHD: While theoretically possible, this approach is cumbersome and lacks the streamlined execution of the SetupComplete.cmd method.

Given the options, the best solution to ensure your PowerShell scripts run on the newly created VMs is: C. Configure a Group Policy Object (GPO) to run the scripts as startup scripts. Here's why: Startup Scripts: Configuring the scripts as startup scripts ensures they run when the VM boots up, before any user logs in. This is ideal for initial configuration tasks that need to be completed before the VM is fully operational. Group Policy: Using GPOs allows you to centrally manage and enforce the execution of these scripts across all new VMs in your domain, ensuring consistency and reducing manual effort.

If any script is running in the startup, it slows down the booting time. Startup script should contain only those tems which cannot stay in static state.

Configure a SetupComplete.cmd batch file in the %windir%\setup\scripts directory is another valid solution, but it is typically used for very specific scenarios during the initial setup phase of Windows deployment.

This is the best approach: Start-up scripts are run when the computer starts, before any user logs on. This ensures that the scripts are run on the newly created VM as soon as it boots, making it ideal for VM configuration automation. You can configure a GPO to run these scripts on all the VMs in your environment.

The SetupComplete.cmd batch file in the %windir%\setup\scripts directory can be used only for Windows. It does not work for other operating systems like Linux.

**Correct Answer: C. Configure a Group Policy Object (GPO) to run the scripts as startup scripts.** ### **Why This Is Correct:** - **Startup scripts** run **before user login**, making them ideal for system-level configurations. - Using a **GPO** ensures automatic execution across multiple VMs without manual intervention. ### **Why Others Are Incorrect:** - **A. SetupComplete.cmd:** Runs only **once** after Windows installation, not suitable for recurring tasks. - **B. Logon Scripts:** Run **after user login**, not suitable for system-level tasks. - **D. VHD:** Only stores scripts; does not **automatically execute** them. **Conclusion:** **Option C** ensures **automatic execution** on every VM startup, making it the best choice.

Because of coexistence with the on-premises Active Directory domain group, policies can be used

ans: C https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn789196(v=ws.11)

the best solution is to configure a Group Policy Object (GPO) to run the scripts as startup scripts (Option C). This ensures that the PowerShell scripts are executed when the VMs start up, which is ideal for automating the configuration of newly created VMs in a consistent manner

As the question specifies "The on-premise virtual environment consists of virtual machines (VMs) running on Windows Server 2012 R2 Hyper-V host servers." the correct answer is C. IF the VMs were running in Azure then the answer would be A

should be the C

C. Configure a Group Policy Object (GPO) to run the scripts as startup scripts. By configuring a Group Policy Object (GPO) to run the scripts as startup scripts, you can automate the execution of the PowerShell scripts on the new VMs when they start up. This ensures that the scripts are executed consistently and reliably on each VM during the startup process. Option A, configuring a SetupComplete.cmd batch file in the %windir%\setup\scripts directory, is not the best solution in this scenario as it applies only to the initial installation of Windows and would not cover the configuration of newly created VMs. Option B, configuring the scripts as logon scripts through Group Policy, may not be ideal in this case as logon scripts are executed when a user logs in, whereas the requirement is to run the scripts on the VMs themselves, regardless of user logins. Option D, placing the scripts in a new virtual hard disk (VHD), would require additional configuration steps and might not be necessary or the most efficient solution for executing PowerShell scripts on the new VMs.

The best solution to ensure that your PowerShell scripts are run on the new VMs is to configure a Group Policy Object (GPO) to run the scripts as startup scripts (Option C). This approach ensures that the scripts are executed when the VM starts up, which is ideal for initial configuration tasks.

The correct answer is C. This is not an Azure-specific question but a general Microsoft enterprise-managed question.