Skip to content

English and Brazilian Customizations tweaks

Jump to bottom
LUIZ HAMILTON ROBERTO DA SILVA edited this page Oct 9, 2024 · 1 revision

🌎 English and Brazilian Customizations Tweaks

Welcome to the PowerShell-codes-for-Windows-Server-Administrators wiki! This page provides detailed information on customizing the PowerShell ToolSet and VBScript Repository for English and Brazilian (Portuguese) environments. Whether you're configuring scripts for English-speaking regions or adapting them for Brazilian settings, you'll find the necessary guidelines and tips here.

🛠️ Table of Contents

  1. 🇺🇸 English Customizations
  2. 🇧🇷 Brazilian Customizations
  3. 🌐 Regional Settings
  4. 📂 Locale-specific Scripts
  5. 📥 Installation Instructions
  6. 🔧 Troubleshooting
  7. ❓ Frequently Asked Questions
  8. 📚 Additional Resources

🇺🇸 English Customizations

Customize your toolset for English-speaking environments to ensure seamless integration and functionality.

📝 Language Settings

  • PowerShell Language: Ensure PowerShell is set to English to maintain consistency in script outputs and error messages.

    Set-WinSystemLocale en-US
Set-WinUserLanguageList en-US -Force

  • Scripts Documentation: All documentation and comments within scripts should be written in English for universal understanding.

📅 Date and Time Formats

  • Standard Format: Use the MM/dd/yyyy date format and hh:mm:ss for time to align with common English-speaking region standards.

    $date = Get-Date -Format "MM/dd/yyyy"
$time = Get-Date -Format "hh:mm:ss"

🌐 Network Configuration

  • DNS Settings: Configure DNS settings appropriate for English-speaking regions, ensuring proper domain resolution.

    Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("8.8.8.8","8.8.4.4")

🇧🇷 Brazilian Customizations

Adapt your toolset for Brazilian environments, accommodating Portuguese language settings and regional formats.

📝 Configurações de Idioma

  • Idioma do PowerShell: Configure o PowerShell para Português do Brasil para garantir consistência nas saídas dos scripts e mensagens de erro.

    Set-WinSystemLocale pt-BR
Set-WinUserLanguageList pt-BR -Force

  • Documentação dos Scripts: Toda a documentação e comentários dentro dos scripts devem ser escritos em Português para melhor compreensão local.

📅 Formatos de Data e Hora

  • Formato Padrão: Utilize o formato de data dd/MM/yyyy e HH:mm:ss para hora, alinhando-se aos padrões regionais brasileiros.

    $data = Get-Date -Format "dd/MM/yyyy"
$hora = Get-Date -Format "HH:mm:ss"

🌐 Configuração de Rede

  • Configurações de DNS: Configure as configurações de DNS apropriadas para regiões brasileiras, garantindo a resolução correta de domínios.

    Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses ("200.160.0.8","200.160.0.9")

🌐 Regional Settings

Ensure that regional settings are appropriately configured to match the target environment's standards.

🗺️ Locale Settings

  • English Locale:

    Set-WinSystemLocale en-US
Set-WinUserLanguageList en-US -Force

  • Brazilian Locale:

    Set-WinSystemLocale pt-BR
Set-WinUserLanguageList pt-BR -Force

🕰️ Time Zone Configuration

  • English-speaking Regions:

    Set-TimeZone -Id "Pacific Standard Time"

  • Brazilian Regions:

    Set-TimeZone -Id "E. South America Standard Time"

📂 Locale-specific Scripts

Customize specific scripts within the toolset to cater to different locales.

🔒 ADAdmin-Tools Customizations

  • English:

    • User Management: Scripts for creating and managing users should use English prompts and logging.

      New-ADUser -Name "John Doe" -GivenName "John" -Surname "Doe" -SamAccountName "jdoe"

  • Brazilian:

    • Gestão de Usuários: Scripts para criação e gestão de usuários devem usar prompts e logs em Português.

      New-ADUser -Name "João Silva" -GivenName "João" -Surname "Silva" -SamAccountName "jsilva"

🔒 BlueTeam-Tools Customizations

  • English:

    • Incident Response: Ensure incident response scripts log information in English.

      Write-Host "Incident detected: Unauthorized access attempt."

  • Brazilian:

    • Resposta a Incidentes: Garantir que os scripts de resposta a incidentes registrem informações em Português.

      Write-Host "Incidente detectado: Tentativa de acesso não autorizado."

📥 Installation Instructions

Follow these steps to install and configure the toolset for your specific locale.

🇺🇸 English Setup

  1. Download the ToolSet:

    Invoke-WebRequest -Uri "https://github.com/brazilianscriptguy/PowerShell-codes-for-Windows-Server-Administrators/releases/latest/download/SysAdminToolSet.zip" -OutFile "SysAdminToolSet.zip"

  2. Extract the Files:

    Expand-Archive -Path "SysAdminToolSet.zip" -DestinationPath "C:\SysAdminToolSet"

  3. Configure Locale Settings:

    Set-WinSystemLocale en-US
Set-WinUserLanguageList en-US -Force
Set-TimeZone -Id "Pacific Standard Time"

  4. Run Initialization Script:

    .\C:\SysAdminToolSet\Initialize.ps1

🇧🇷 Brazilian Setup

  1. Baixar o ToolSet:

    Invoke-WebRequest -Uri "https://github.com/brazilianscriptguy/PowerShell-codes-for-Windows-Server-Administrators/releases/latest/download/SysAdminToolSet.zip" -OutFile "SysAdminToolSet.zip"

  2. Extrair os Arquivos:

    Expand-Archive -Path "SysAdminToolSet.zip" -DestinationPath "C:\SysAdminToolSet"

  3. Configurar as Configurações de Locale:

    Set-WinSystemLocale pt-BR
Set-WinUserLanguageList pt-BR -Force
Set-TimeZone -Id "E. South America Standard Time"

  4. Executar o Script de Inicialização:

    .\C:\SysAdminToolSet\Initialize.ps1

🔧 Troubleshooting

Resolve common issues that may arise during installation or usage.

❓ Common Issues

  • Issue: Scripts not executing with proper permissions.

    Solution: Run PowerShell as an administrator and ensure execution policies are set correctly.

    Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

  • Issue: Locale settings not applying correctly.

    Solution: Verify the locale codes and ensure scripts are run with appropriate permissions.

🛠️ Tools and Logs

  • Log Files: Check log files located in C:\SysAdminToolSet\Logs for detailed error messages.

    Get-Content -Path "C:\SysAdminToolSet\Logs\error.log" -Tail 50

  • Diagnostic Scripts: Use diagnostic scripts to verify configurations.

    .\C:\SysAdminToolSet\Diagnostics\Check-Environment.ps1

❓ Frequently Asked Questions

Q1: Can I use the toolset for other locales besides English and Brazilian?

A1: Currently, the toolset is optimized for English and Brazilian environments. However, you can customize scripts further to support additional locales by following the guidelines in this Wiki.

Q2: How do I update the toolset to the latest version?

A2: Follow the steps in the Upgrading Your ToolSet section to download and install the latest version.

Q3: Who can I contact for support?

A3: For support or to report issues, please refer to the Reporting a Vulnerability section or contact us at [email protected].

📚 Additional Resources

🗂️ Version History

Versão Data Mudanças Realizadas Autor
1.0 2023-01-01 Criação inicial Luiz Hamilton Silva
1.1 2023-06-15 Adicionadas customizações para Core-ScriptLibrary e ITSM-Templates Luiz Hamilton Silva
1.2 2024-04-27 Atualização das tabelas de versões suportadas e links Luiz Hamilton Silva
1.3 2024-10-05 Melhorias na formatação e adição de ícones Luiz Hamilton Silva

🗣️ Feedback

We value your feedback! If you have suggestions for improving this Security Policy or encounter any issues, please contact us at [email protected].

📣 Final Thoughts

This Wiki page serves as a comprehensive guide for customizing the PowerShell ToolSet and VBScript Repository for both English and Brazilian environments. By following the guidelines and utilizing the provided resources, you can ensure that your administrative tasks are streamlined and tailored to your specific regional needs.

Feel free to explore other sections of the Wiki for more detailed information on various aspects of the toolset. If you have any further questions or need assistance, don't hesitate to reach out!

Clone this wiki locally