Question : Your role of Systems Administrator at ABC.com includes the management of the company's virtual infrastructure. The company has virtual machines running in an on-premise virtual environment and in Microsoft Azure. The on-premise virtual environment consists of virtual machines (VMs) running on Windows server 2012 R2 Hyper-V host servers. You have created some PowerShell scripts to automate the configuration of newly created VMs. You plan to create several new VMs. You need a solution that ensures the scripts are run on the new VMs. Which of the following is the best solution?
1. Configure a SetupComplete.cmd batch file in the %windir%\setup\scripts directory.
2. Configure a Group Policy Object (GPO) to run the scripts as logon scripts.
3. Configure a Group Policy Object (GPO) to run the scripts as startup scripts.
4. Place the scripts in a new virtual hard disk (VHD).
Correct Answer : 1 Explanation: You can add custom scripts to Windows Setup that can be configured to run in different circumstances. You can run a custom script: Immediately after Windows Setup completes. If Windows Setup encounters a fatal error. Run a Custom Script after Windows Setup Completes You can make further customizations after Windows Setup completes by adding commands to the %WINDIR%\Setup\Scripts\SetupComplete.cmd file. This file enables you to install additional applications, run custom Windows scripts (cscript/wscript), or make other modifications to the system before a user logs on.
Commands in the Setupcomplete.cmd file are executed with local system privilege. After Windows is installed, but before the logon screen appears, Windows Setup searches for the SetupComplete.cmd file in the %WINDIR%\Setup\Scripts\ directory. If a SetupComplete.cmd file is found, the file is executed. Otherwise, installation continues normally. Windows Setup logs the action in the Setupact.log file.
You cannot reboot the system and resume running SetupComplete.cmd. Setup does not verify any exit codes or error levels in the script after executing SetupComplete.cmd. The functionality of Setupcomplete.cmd differs from the RunSynchronous and RunAsynchronous commands in that Setupcomplete.cmd runs after Windows Setup completes while the RunSynchronous and RunAsynchronous commands run during Windows Setup. Run a Custom Script if Windows Setup Encounters a Fatal Error If Windows Setup encounters a fatal error, you can configure Setup to automatically launch a script that contains custom commands or actions. A fatal error is an error in which Windows Setup is prevented from completing the installation. This functionality is useful when you automate the installation of many systems at the same time. By enabling this functionality, you can immediately detect when an error occurs during Windows Setup and run custom actions. If Setup encounters a fatal error and is prevented from completing the installation, Setup searches for a command script in the following directory: %WINDIR%\Setup\Scripts\ErrorHandler.cmd. One of two actions will occur, depending on whether the script is found. If the script is not found, a dialog box is displayed with the error text. A user must dismiss the dialog box before Setup exits. If the script is found, the script executes synchronously. No dialog box or error text is displayed. After the ErrorHandler.cmd script completes, Windows Setup exits. Depending on the phase of Windows Setup, the computer will return to the environment from which Setup was executed (for example, a downlevel operating system or Windows PE). There are several ways that you can add the ErrorHandler.cmd file by using the $OEM$ directory structure. Create a Sources\$OEM$\$$\Setup\Scripts folder in the Windows distribution. Copy the ErrorHandler.cmd file to this directory. For more information about using $OEM$ files, see Add Content to $OEM$ Folders.
Create a temporary folder that contains a $$\Setup\Scripts folder structure. Copy the ErrorHandler.cmd file to this directory, and then run Windows Setup with the /m:temp_folder parameter. For example, if you create C:\Temp\SetupFiles\$$\Setup\Scripts\ErrorHandler.cmd, use the following command: setup.exe /m:C:\temp\SetupFiles For more information about the setup.exe /m parameter. There may be instances when Windows Setup encounters more than one error and runs the ErrorHandler.cmd script more than once. When developing the code for ErrorHandler.cmd, ensure that you can run this script multiple times.
Question : Your role of Systems Administrator at ABC.com includes the management of the company's virtual infrastructure. The company has virtual machines running in an on-premise virtual environment and in Microsoft Azure. The on-premise virtual environment consists of virtual machines (VMs) running on Windows server 2012 Hyper-V host servers. An on-premise VM named TK-App1 runs a custom application that is used by company employees. You want to host TK-App1 in Microsoft Azure. You want to upload the virtual hard disk (VHD) of TK-App1 to your Microsoft Azure Storage account. Which of the following PowerShell cmdlets should you use?
Correct Answer : 2 Explanation: The Add-AzureVhd cmdlet allows you to upload on-premises virtual hard disks (in .vhd file format) to a blob storage account as fixed virtual hard disks. You can configure the number of uploader threads that will be used or overwrite an existing blob in the specified destination URI. Also supported is the ability to upload a patched version of an on-premises .vhd file: When a base virtual hard disk has already been uploaded, you can upload differencing disks that use the base image as the parent. Shared access signature (SAS URI) is supported as well.
Question : Your role of Systems Administrator at ABC.com includes the management of the company's virtual infrastructure. The company has virtual machines running in an on-premise virtual environment and in Microsoft Azure. The on-premise virtual environment consists of virtual machines (VMs) running on Windows server 2012 R2 Hyper-V host servers. The VMs running in the on-premise environment include the following operating system configurations and VHD formats: .Windows Server 2003 R2 on VHD disks. .Windows Server 2003 R2 on VHDX disks. .Windows Server 2008 on VHD disks. .Windows Server 2008 R2 on VHD disks. .Windows Server 2008 on VHDX disks. .Windows Server 2008 R2 on VHDX disks. You want to migrate VMs from the on-premise environment to Azure VMs. Which two of the following statements are true? (Choose two) A. Virtual hard disks must be in VHDX format to support migrating to Azure. B. Virtual hard disks must be in VHD format to support migrating to Azure. C. The VMs must be running Windows Server 2003 R2 or later to support migrating to Azure. D. The VMs must be running Windows Server 2008 or later to support migrating to Azure. E. The VMs must be running Windows Server 2008 R2 or later to support migrating to Azure.
1. Select the Install the VM Agent checkbox while provisioning a VM based on your uploaded VHD. 2. Select the Enable the VM Extensions checkbox while provisioning a VM based on your uploaded VHD. 3. Access Mostly Uused Products by 50000+ Subscribers UpdateAzureVM -Name Sname -VM $vm.VM -ServiceName $svc 4. Install the VM Agent MSI and execute the following Power Shell commands: $vm = GetAzureVM -serviceName $svc -Name $name Set-AzureVMBGInfoExtension -VM $vm.VM Set-AzureVM Access Extension -VM $vm.VM Update-AzureVM -Name Sname -VM $vm.VM -ServiceName $svc