Site Recovery
199
Total Pages
64
Linux-Friendly Pages
135
Pages with Bias
67.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
864 issues found
Showing 551-575 of 864 flagged pages
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-plan-capacity-vmware.md
...es/site-recovery/site-recovery-plan-capacity-vmware.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: all registry and bandwidth control examples are Windows-specific (registry keys, MMC snap-in, PowerShell cmdlets), and there are no equivalent Linux instructions or examples for controlling bandwidth or configuring process/master target servers. Windows tools and patterns (MMC, registry, PowerShell) are mentioned exclusively or before Linux alternatives. Linux is only mentioned in the context of needing a separate master target server, with a link out to another article, but no Linux-specific operational guidance is provided in this document.
Recommendations
- Provide Linux-specific instructions and examples for controlling bandwidth, such as using tc, wondershaper, or other Linux-native tools.
- Include Linux equivalents for registry-based configuration (e.g., relevant configuration files or environment variables).
- Offer CLI-based or cross-platform methods (e.g., REST API, Azure CLI) for tasks currently described with Windows GUI tools (MMC snap-in) or PowerShell.
- Ensure that Linux operational guidance (e.g., installing and configuring process/master target servers, bandwidth throttling) is included inline, not just as a link.
- When listing steps or tools, present both Windows and Linux options together, or clearly indicate platform applicability.
Create Pull Request
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-sql.md
.../blob/main/articles/site-recovery/site-recovery-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a clear Windows bias. All technical examples, references, and screenshots assume a Windows environment. Features such as Task Manager, Windows Server Failover Clustering, and PowerShell scripts are mentioned or linked without Linux equivalents. There is no discussion of Linux-based SQL Server deployments, nor are there instructions or examples for Linux tools or commands. The documentation implicitly assumes SQL Server is running on Windows, omitting guidance for Linux users.
Recommendations
- Add explicit guidance and examples for SQL Server running on Linux, including supported BCDR technologies and any Azure Site Recovery limitations or differences.
- Include Linux-specific instructions for monitoring (e.g., using iotop, sar, or other Linux tools instead of Task Manager).
- Provide sample scripts or automation guidance using Bash or other Linux-native tools, not just PowerShell.
- Clarify in each section whether the instructions apply to both Windows and Linux, or note any platform-specific requirements.
- Add screenshots and walkthroughs for Linux environments where relevant.
- Reference documentation for SQL Server on Linux, including high availability and disaster recovery options.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-workload.md
.../main/articles/site-recovery/site-recovery-workload.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing and detailing Windows-centric workloads and tools (e.g., Active Directory, SQL Server, Exchange, SharePoint, IIS, Remote Desktop Services) before Linux equivalents. While Linux is mentioned as supported, there is a lack of Linux-specific examples, guidance, or parity in workload descriptions. Windows tools and technologies are referenced extensively, with little to no mention of Linux-native alternatives or application scenarios.
Recommendations
- Add explicit Linux workload examples (e.g., Apache, NGINX, MySQL, PostgreSQL, Samba, OpenLDAP) and describe their disaster recovery scenarios using Azure Site Recovery.
- Include Linux-specific guidance and best practices for replication, failover, and failback, such as handling Linux filesystems, bootloaders, and network configurations.
- Provide parity in documentation structure: for each Windows-centric section (e.g., Protect SQL Server), add a corresponding Linux section (e.g., Protect MySQL/PostgreSQL).
- Reference Linux-native tools and patterns (e.g., systemd, cron, rsync, LVM snapshots) where relevant, and provide example scripts or automation for Linux environments.
- Ensure that tables and workload summaries list Linux applications and scenarios with equal prominence and detail as Windows workloads.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-vmware-deployment-planner-run.md
...ecovery/site-recovery-vmware-deployment-planner-run.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. All command-line examples use Windows-style paths and syntax, and the only scripting example provided is with VMware vSphere PowerCLI (a Windows/PowerShell tool). The tool itself (ASRDeploymentPlanner.exe) is a Windows executable, and report generation requires Microsoft Excel on Windows. There are no Linux or cross-platform alternatives or examples, and Linux users are not addressed or given guidance.
Recommendations
- Provide explicit information about platform support for ASRDeploymentPlanner.exe (e.g., is it Windows-only? If so, state this clearly at the top).
- If the tool is Windows-only, suggest workarounds for Linux/Mac users (such as using a Windows VM or container, or remote desktop to a Windows machine).
- Offer alternative methods for generating the VM list using Linux tools (e.g., using govc, pyVmomi, or VMware CLI tools available on Linux) and provide equivalent bash or shell script examples.
- Clarify whether the output report (Excel XLSM) can be viewed or processed on non-Windows platforms, and suggest alternatives if possible (e.g., using LibreOffice, or exporting to CSV).
- Where possible, use platform-neutral language and avoid assuming the user is on Windows (e.g., avoid references to Notepad, Control Panel, or Windows-specific file paths unless necessary, and provide Linux/Mac equivalents where relevant).
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/site-recovery-manage-registration-and-protection.md
...ry/site-recovery-manage-registration-and-protection.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows environments, specifically System Center VMM, Hyper-V, and PowerShell scripts. All provided command-line examples are in PowerShell, and all procedures reference Windows-specific tools and registry paths. There are no Linux or cross-platform examples, and Linux-based recovery scenarios are not discussed. VMware and physical server sections only mention manual uninstallation of the mobility service, with no Linux-specific guidance or scripts.
Recommendations
- Add equivalent instructions and scripts for Linux-based servers, especially for unregistering, disabling protection, and cleaning up agents.
- Include Bash or shell script examples for common tasks where possible, or explicitly state if a task is not relevant/applicable to Linux.
- Clearly separate procedures for Windows and Linux environments, ensuring Linux administrators have parity in guidance.
- Reference Linux tools and patterns (e.g., systemd, Linux file paths, package managers) where appropriate.
- If certain features are Windows-only, explicitly state this and provide alternative guidance or links for Linux users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/transport-layer-security.md
...ain/articles/site-recovery/transport-layer-security.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively addresses enabling and configuring TLS 1.2 on Windows systems, with all examples, instructions, and references tailored to Windows (registry edits, Windows KB articles, .NET Framework on Windows, SChannel). There is no mention of Linux systems, nor are there instructions or examples for enabling or verifying TLS 1.2 on Linux-based Azure Site Recovery components, if supported.
Recommendations
- Add a section describing how to verify and enable TLS 1.2 on Linux machines, if Azure Site Recovery supports Linux workloads.
- Provide Linux-specific examples, such as configuration file changes (e.g., OpenSSL, GnuTLS, or relevant agent settings) and command-line instructions to check TLS support.
- Include references to Linux documentation or tools for managing TLS protocols.
- Clarify in the introduction or prerequisites if Azure Site Recovery only supports Windows, or explicitly state the scope of the documentation.
- Ensure parity in troubleshooting steps and error messages for both Windows and Linux platforms.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/upgrade-2012R2-to-2016.md
.../main/articles/site-recovery/upgrade-2012R2-to-2016.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is exclusively focused on Windows Server and System Center VMM environments, with all instructions, tools, and examples tailored to Windows. There are no references to Linux hosts, Linux-based management tools, or cross-platform considerations. Windows-specific tools (such as Control Panel, VMM console, registry paths, and PowerShell commands) are used throughout, and no Linux equivalents or alternatives are mentioned.
Recommendations
- Add a section or note clarifying whether Linux hosts or mixed-OS environments are supported or not, and provide guidance for such scenarios if applicable.
- If Azure Site Recovery or VMM supports Linux hosts, include parallel upgrade instructions and examples for Linux environments (e.g., using SSH, Linux package managers, or relevant Linux tools).
- Where PowerShell or Windows GUI tools are referenced, provide equivalent CLI or script examples for Linux (if supported).
- Explicitly state any limitations or lack of support for Linux to avoid confusion for cross-platform administrators.
- Consider referencing Azure Site Recovery documentation for Linux or heterogeneous environments, if available, to improve discoverability for non-Windows users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/upgrade-mobility-service-modernized.md
...s/site-recovery/upgrade-mobility-service-modernized.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: Windows-specific tools and patterns (such as Registry Editor, .msi installers, and command prompt usage) are mentioned and detailed extensively, often before or instead of Linux equivalents. Manual update procedures for appliance components are exclusively Windows-focused, with no Linux instructions for updating appliance components. Linux command-line instructions are provided for the mobility agent, but only after Windows instructions, and with less detail/context. There is no mention of Linux equivalents for actions like registry edits or .msi package handling.
Recommendations
- Provide Linux-specific instructions for updating appliance components, including equivalent commands and file locations.
- Ensure that Linux examples are presented alongside Windows examples, not only after or as an afterthought.
- Include Linux-native tools and patterns (such as editing configuration files or using systemd/services) where Registry Editor or Windows-specific tools are referenced.
- Clarify which steps are Windows-only and which are cross-platform; if a feature is not available on Linux, state this explicitly.
- Balance screenshots and UI references to reflect both Windows and Linux environments where applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-upgrade-failures.md
...recovery/vmware-azure-troubleshoot-upgrade-failures.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides troubleshooting steps and examples for Windows environments, referencing Windows command prompt, Registry Editor (regedit.exe), Windows-style paths (C:\), and Task Manager. There are no examples or instructions for Linux environments, nor are Linux tools or file paths mentioned. This indicates a strong Windows bias and lack of cross-platform parity.
Recommendations
- Add equivalent troubleshooting steps for Linux-based Azure Site Recovery deployments, if supported.
- Include Linux shell commands (e.g., tar, unzip) for extracting setup files, and reference Linux file paths.
- Mention Linux equivalents for tools like Registry Editor (e.g., editing configuration files or using Linux registry emulation if applicable).
- Clarify in the introduction if the product or troubleshooting steps are only applicable to Windows, or explicitly state platform limitations.
- Provide parallel examples and instructions for both Windows and Linux wherever possible to ensure parity.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-tutorial-prepare-on-premises.md
...-recovery/vmware-azure-tutorial-prepare-on-premises.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas: instructions for preparing accounts and connectivity after failover are presented for Windows before Linux, with more detailed steps and troubleshooting for Windows. Windows-specific tools and settings (such as Windows Firewall, registry edits, and SAN policy) are mentioned, while Linux instructions are less detailed and lack equivalent troubleshooting guidance. There are no command-line examples for Linux (e.g., SSH service management), and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
- Present Linux and Windows instructions in parallel, or alternate which comes first, to avoid the impression of Windows being the default.
- Provide equivalent detail and troubleshooting steps for Linux VMs, such as how to check SSH service status, configure firewall rules (e.g., using ufw or firewalld), and handle common SSH connectivity issues.
- Include Linux command-line examples for tasks such as enabling SSH, checking firewall status, and verifying network connectivity.
- Mention Linux-specific tools or configuration files where relevant, similar to how Windows registry and firewall settings are discussed.
- Ensure that all steps required for Linux VMs are as explicit and discoverable as those for Windows VMs, including any post-failover checks or diagnostics.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/unregister-vmm-server-script.md
...articles/site-recovery/unregister-vmm-server-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. The only example provided is a PowerShell script that relies on Windows-specific tools, registry paths, and services (e.g., SCVMM, Windows Cluster service, HKLM registry, net stop, Get-Service, etc.). There is no mention of Linux or cross-platform alternatives, nor are there any Linux shell or script examples. All instructions and context assume a Windows Server environment.
Recommendations
- Clearly state in the introduction that the script and instructions are intended for Windows environments only, if Linux is not supported.
- If Linux-based VMM or management is supported, provide equivalent Bash or Python scripts and instructions for Linux environments.
- Where possible, abstract platform-specific steps and provide guidance for both Windows and Linux (e.g., database cleanup commands, service management).
- Mention any limitations or lack of support for non-Windows platforms explicitly to set user expectations.
- Consider providing a table or section comparing Windows and Linux procedures, if both are supported.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-exclude-disk.md
...in/articles/site-recovery/vmware-azure-exclude-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by mentioning Windows-specific failback behavior before Linux, referencing Windows disks and their failback limitations, and not providing Linux-specific examples or tools. The failback section details Windows behavior first, with more explanation, and only briefly covers Linux. There are no Linux command-line examples or parity in tooling guidance.
Recommendations
- Present Linux and Windows failback behaviors in parallel, with equal detail and prominence.
- Include Linux-specific examples or scenarios, such as common Linux disk layouts or use cases.
- If mentioning Windows tools or behaviors, provide Linux equivalents or clarify differences.
- Add command-line or scripting examples for both Windows (PowerShell) and Linux (Bash) where relevant.
- Ensure that screenshots and UI instructions are not Windows-centric, or provide Linux context where applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-enable-replication.md
...icles/site-recovery/vmware-azure-enable-replication.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary or sole automation method, mentioning Windows-specific features (such as Azure Hybrid Benefit for Windows Server), and omitting Linux-specific guidance or examples. Windows tools and patterns are mentioned first or exclusively, and there are no Linux command-line or automation examples provided.
Recommendations
- Provide equivalent CLI (az CLI) and/or Bash examples alongside PowerShell for all automation steps.
- Explicitly mention support for Linux VMs and provide any Linux-specific prerequisites or caveats (e.g., Mobility Service installation on Linux, supported distributions).
- Include Linux-focused troubleshooting steps and examples, especially for common issues (e.g., agent installation, disk types, UEFI/BIOS boot differences).
- Balance references to Windows-specific features (like Azure Hybrid Benefit) with Linux equivalents, or clarify when features are Windows-only.
- Add links to Linux documentation or guides where appropriate, such as for managing Linux VMs in Azure or using Linux tools for monitoring and management.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-troubleshoot-appliance-health-issue.md
...recovery/vmware-troubleshoot-appliance-health-issue.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides troubleshooting steps that exclusively reference Windows tools and PowerShell scripts, with no mention of Linux equivalents or guidance for non-Windows environments. All example commands and file paths are Windows-specific, and there is no indication that the replication appliance or its management tools can be operated from or on Linux systems.
Recommendations
- Include troubleshooting steps for Linux-based environments if the replication appliance supports Linux.
- Provide equivalent shell (bash) commands and file paths for Linux users alongside PowerShell examples.
- Clarify whether the appliance and its management tools are Windows-only, or explicitly state platform limitations.
- If Linux is not supported, add a note to inform users; if it is, ensure parity in instructions and examples.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-failback.md
...b/main/articles/site-recovery/vmware-azure-failback.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by specifically mentioning the handling of VMware tools for Windows VMs during failover and failback, without any mention of Linux VMs or their equivalent considerations. There are no examples, notes, or instructions tailored for Linux VMs, and the only OS-specific guidance is for Windows. This suggests an assumption that users are primarily working with Windows workloads.
Recommendations
- Add explicit guidance for Linux VMs, including any differences in failback behavior, such as handling of open-vm-tools or other Linux-specific agents.
- Include notes or troubleshooting steps relevant to Linux VMs, such as common issues with agent registration or post-failback configuration.
- Ensure that any OS-specific instructions (e.g., regarding VMware tools) are paired with equivalent Linux information, or state clearly if there are no differences.
- Where possible, provide parity in examples and notes for both Windows and Linux environments to ensure inclusivity for all users.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-common-questions.md
...rticles/site-recovery/vmware-azure-common-questions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Windows paths, tools, and PowerShell are mentioned first or exclusively in several places. For example, installation paths and manual steps reference Windows directories (e.g., C:\Program Files), and PowerShell is given as the main scripting example. Linux equivalents are sometimes included but often as an afterthought or with less detail. Some instructions (e.g., MySQL installation, Mobility service installer location) only mention Windows paths, omitting Linux alternatives.
Recommendations
- Provide Linux/Unix paths and instructions alongside Windows ones wherever file locations or commands are referenced (e.g., Mobility service installer location, MySQL installation).
- When mentioning scripting or automation, include Bash/CLI and REST API examples, not just PowerShell.
- List Linux and Windows instructions/examples in parallel, or alternate the order to avoid always putting Windows first.
- Where GUI steps are described, clarify any differences for Linux users or note if steps are OS-agnostic.
- Ensure that all tools and deployment methods mentioned (e.g., Configuration Manager) have Linux equivalents or alternatives documented, or explicitly state if not supported.
- Add more Linux-specific troubleshooting and operational guidance where relevant.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-manage-process-server.md
...es/site-recovery/vmware-azure-manage-process-server.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias. All command-line examples use Windows-specific tools (cmd.exe, PowerShell), Windows environment variables (e.g., %PROGRAMDATA%), and Windows file paths (C:\...). There are no Linux or cross-platform equivalents provided, even though VMware and physical servers may run Linux. Anti-virus exclusions and process server management instructions are exclusively Windows-centric.
Recommendations
- Provide equivalent Linux command-line instructions for all management tasks, including process server registration, proxy configuration, and service management.
- Document Linux file paths and environment variables alongside Windows ones (e.g., /var/opt/microsoft/ASR/Agent).
- Include anti-virus exclusion paths for Linux (e.g., /opt/microsoft/ASR/Agent).
- Clarify OS support for process server components and explicitly state if certain features are Windows-only.
- When showing commands, present both Windows and Linux examples side by side.
- Avoid assuming the administrator is using Windows by default; acknowledge mixed-OS environments.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-install-mobility-service.md
...site-recovery/vmware-azure-install-mobility-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by presenting Windows instructions before Linux, providing detailed Windows-specific tooling (e.g., registry edits, Group Policy, Windows Firewall), and referencing Windows ports and anti-virus paths without Linux equivalents. Some steps (such as anti-virus exclusions and firewall configuration) are only described for Windows, with no Linux-specific guidance or examples provided.
Recommendations
- Alternate the order of Windows and Linux sections, or provide a parallel structure to avoid always presenting Windows first.
- Include Linux-specific examples for firewall configuration (e.g., using ufw, firewalld, or iptables) and anti-virus exclusions (e.g., for ClamAV or other common Linux AV solutions).
- When referencing ports (e.g., SMB, WMI), clarify which are relevant for Windows, Linux, or both, and provide Linux context (e.g., SSH, SFTP ports).
- Provide Linux command-line examples (e.g., for editing sshd_config, restarting sshd, or verifying package installation) similar to the detailed Windows registry and firewall steps.
- Mention Linux equivalents for tools like Group Policy (e.g., configuration management tools such as Ansible, Puppet, or manual config file edits).
- Ensure screenshots and illustrations are balanced between Windows and Linux environments.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-manage-vcenter.md
.../articles/site-recovery/vmware-azure-manage-vcenter.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing the use of a Windows-based configuration server tool (_cspsconfigtool.exe_) and instructing users to access it via a Desktop shortcut, which is a Windows UI pattern. There are no instructions or examples for performing these tasks on Linux-based configuration servers, nor is there mention of command-line alternatives or cross-platform tools. The documentation assumes the configuration server environment is Windows, omitting Linux parity.
Recommendations
- Provide equivalent instructions for Linux-based configuration servers, including how to access and use the configuration server tool on Linux (if supported).
- Mention whether the configuration server tool (_cspsconfigtool.exe_) is available or supported on Linux, and if not, clarify this limitation.
- If only Windows is supported, explicitly state this early in the prerequisites section to set expectations.
- Offer command-line alternatives (e.g., PowerShell, Bash, or CLI commands) for all major actions, ensuring cross-platform usability.
- Avoid UI patterns that are exclusive to Windows (such as 'Desktop shortcut') or provide Linux equivalents (e.g., application menu, terminal launch).
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-manage-configuration-server.md
...e-recovery/vmware-azure-manage-configuration-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. Most command-line instructions, tooling references, and examples are Windows-centric, including frequent use of PowerShell, Windows command prompts, Windows file paths, and Windows-specific tools (e.g., DISM, reg.exe, net.exe). There are no Linux-specific instructions or examples, even though the configuration server can be used for protecting both Windows and Linux physical servers. Linux equivalents for tasks such as certificate renewal, credential management, and server registration are missing.
Recommendations
- Provide Linux-specific instructions and examples for all management tasks, including certificate renewal, credential management, and server registration.
- Include Linux shell (bash) command equivalents alongside PowerShell/Windows command prompt examples.
- Reference Linux tools and file paths where appropriate (e.g., /var, /etc) in addition to Windows paths.
- Clarify which steps are Windows-only and which are applicable to Linux, and provide parity in guidance for both platforms.
- If certain tools (e.g., CSPSConfigtool.exe, genpassphrase.exe) are Windows-only, document Linux alternatives or explicitly state limitations.
- Add examples for managing the configuration server from Linux environments, especially for physical Linux servers.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-process-server-scale.md
...e-recovery/vmware-azure-set-up-process-server-scale.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively describes installation and usage of the process server using Windows-centric tools and patterns (e.g., .exe installers, Windows file paths, and command-line syntax). There are no examples or instructions for Linux-based deployments, nor is there mention of Linux support or alternatives. All examples use Windows conventions and terminology.
Recommendations
- Explicitly state whether Linux-based process servers are supported or not. If supported, provide equivalent installation and configuration instructions for Linux environments.
- Include Linux command-line examples (e.g., using shell scripts, .sh installers, or relevant package managers) alongside Windows examples.
- Use platform-neutral language where possible, or clearly separate instructions for Windows and Linux users.
- Mention Linux prerequisites, file paths, and environment variables where relevant.
- If only Windows is supported, clarify this early in the documentation to set user expectations.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-prepare-failback.md
...rticles/site-recovery/vmware-azure-prepare-failback.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias in several areas. Windows is mentioned before Linux when describing master target server creation, and the default master target server is described as Windows. There are more detailed instructions and default values given for Windows (e.g., default retention volume 'R'), while Linux equivalents are only briefly mentioned. Some steps, such as adding a retention drive, provide more detail for Windows than Linux. There are also references to Windows-specific tools and patterns, with less emphasis or explanation for Linux scenarios.
Recommendations
- Present Linux and Windows options in parallel, rather than listing Windows first or as the default.
- Provide equally detailed steps and examples for Linux, including explicit instructions for adding and formatting retention drives on Linux.
- Clarify Linux-specific requirements and defaults (e.g., file system types, default retention paths) with the same level of detail as Windows.
- Avoid language that implies Windows is the default or preferred platform; instead, state that either OS can be used depending on the VM workload.
- Include Linux command-line examples (e.g., for mounting and formatting disks) alongside any Windows/Powershell instructions.
- Ensure that any references to tools (e.g., VMware Tools vs open-vm-tools) are given equal prominence for both platforms.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-set-up-source.md
...n/articles/site-recovery/vmware-azure-set-up-source.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows file paths and tools, listing Windows-specific antivirus exclusions first and in greater detail, and only providing a Linux example as an afterthought. There are no Linux command-line or configuration examples, and Windows registry keys are mentioned even in the Linux section, which may confuse readers. The documentation assumes the configuration server will run Windows, and Linux parity is not addressed in setup or troubleshooting steps.
Recommendations
- Provide Linux-specific setup instructions and examples alongside Windows instructions, especially for configuration server deployment and antivirus exclusions.
- List Linux and Windows examples in parallel sections or tables, rather than Windows first and Linux as an afterthought.
- Clarify which steps or exclusions apply only to Windows or only to Linux, and avoid including Windows registry keys in Linux-specific sections.
- Include Linux command-line examples (e.g., for excluding directories in common antivirus solutions) where appropriate.
- Explicitly state OS requirements and support for each component (e.g., configuration server, process server) and provide guidance for both Windows and Linux environments.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-replication.md
...site-recovery/vmware-azure-troubleshoot-replication.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only Windows file paths, log locations, and troubleshooting commands (e.g., C:\ paths, cmd commands, VSS-specific instructions) throughout the troubleshooting steps. Linux-specific troubleshooting guidance is almost entirely absent, except for a brief mention of custom scripts for app-consistency. There are no Linux log file locations, service names, or command-line examples provided, and Windows tools and patterns (such as VSS, .cmd scripts, and Windows service management) are referenced exclusively.
Recommendations
- Add equivalent Linux troubleshooting steps for each error, including Linux log file locations (e.g., /var/log/...), relevant service names, and command-line examples (e.g., systemctl, journalctl).
- Where Windows-specific tools (like VSS) are discussed, provide Linux alternatives or clarify the Linux behavior (e.g., how app-consistency is achieved on Linux, what to check if it fails).
- Include Linux file path examples and permissions troubleshooting (e.g., using chmod/chown) alongside Windows examples.
- When referencing commands (such as restarting services or registering agents), provide both Windows (cmd/PowerShell) and Linux (bash/shell) equivalents.
- Ensure that all troubleshooting sections explicitly state if a step is Windows-only, and provide parallel Linux instructions where applicable.
Site Recovery
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/site-recovery/vmware-azure-troubleshoot-vcenter-discovery-failures.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows tools (PsExec, Internet Explorer, command prompt), providing only Windows-based procedures and commands, and omitting any Linux or cross-platform alternatives for proxy configuration or troubleshooting. All example commands and instructions are tailored to Windows environments, with no mention of how to perform equivalent tasks on Linux-based configuration servers.
Recommendations
- Provide equivalent instructions for Linux-based configuration servers, including how to check and modify proxy settings using Linux tools (e.g., environment variables, systemd service overrides, or editing /etc/environment).
- List both Windows and Linux procedures in parallel, or clarify OS-specific steps with headings such as 'On Windows' and 'On Linux'.
- Replace or supplement Windows-only tools (like PsExec and Internet Explorer) with cross-platform or Linux-native alternatives (e.g., using sudo, curl, or editing configuration files directly).
- Ensure that all command-line examples have Linux equivalents, and mention any differences in service management (e.g., using systemctl instead of Windows Services).
- Explicitly state OS prerequisites or limitations if certain features or tools are only available on Windows.