PowerShell Script for ACTT on Windows
Uploaded by
paola.margaritaguevaraPowerShell Script for ACTT on Windows
Uploaded by
paola.margaritaguevaraCommon questions
Powered by AIIf the PowerShell ExecutionPolicy is not set to RemoteSigned, the script may not execute due to default security settings in PowerShell that prevent running scripts downloaded from the internet. This could impede the data extraction process, as the policy is crucial for ensuring that scripts executed have a trusted digital signature. The requirement to set ExecutionPolicy to RemoteSigned ensures that remotely sourced scripts are verified before execution .
Insufficient storage space on the server during the execution of the ACTT script could significantly impact the script's ability to operate as designed. The script requires around 2 GB of free space, a critical need for accommodating output files post-data extraction. Lack of adequate space may lead to script failure, incomplete file generation, or even disrupt server operations if existing services need that space to run effectively .
The instruction document ensures that no server modifications occur during the script execution by specifically noting the script contains only 'read-only' commands. It emphasizes that the script does not alter server configurations, reassuring users that data extraction is done safely without affecting server operations .
To successfully execute the ACTT PowerShell script on a Windows Server, the following prerequisites must be met: an "ACTT_WINDOWS_Script.ps1" file, administrator privileges pertinent to the server type (Domain Admins for Domain Controllers and Local Administrator for Non-Domain Controllers/Local Servers), PowerShell version 4.0 or above installed, and the PowerShell Execution policy set to RemoteSigned specifically for the session .
The ACTT PowerShell script is compatible only with PowerShell versions 4.0 and above. It is not compatible with PowerShell version 3.0 or lower. This limitation is likely due to the script's dependence on features and cmdlets available only in the more recent PowerShell versions, thus requiring users to update their PowerShell environment if necessary to run the script .
The directory where the ACTT script file needs to reside serves as the execution environment for the script. By placing the script in an empty folder with sufficient storage space (around 2 GB), it ensures that there is an organized location for the output files to be stored post-execution. This setup prevents data overwrite or loss by isolating the execution process and its outputs .
After the ACTT script execution and data extraction, users will find a new folder created with the extracted files in the directory where the script was executed. The next step is to zip the folder containing the extracted files and share it with the Deloitte contact as part of the data analysis audit process .
Having Domain Admin or Local Admin rights is crucial because the script needs the appropriate permissions to access and extract detailed system and Active Directory information. Without the necessary administrative rights, the script may fail to execute or result in incomplete data extraction, leading to insufficient data for audit purposes .
The ACTT PowerShell script auto-detects the environment in which it is executed. If the script is run on a Domain Controller (DC), it extracts Active Directory information, whereas if it is run on a Local Server, it extracts the local server configuration. This functionality allows it to tailor the data extraction process based on the server type .
The potential risks associated with the ACTT script include the lack of warranty and disclaimers of liability for any damages resulting from the use of the script, as stated in the instructions. Users are also obliged to follow their company's regular change management policies when using the script. This indicates that while the script is provided 'as is,' responsibility for any negative outcomes or damages rests with the user or their organization, not the Deloitte Network .