[Enhancement] Enhance CloudWatch Agent Startup on Windows AMIs via Dependency Updates

[okankoAMZ]

Description of the Issue

The CloudWatch Agent service on Windows fails to start automatically on certain custom AMIs created using Windows sysprep. This issue occurs due to a race condition between the agent's startup and the initialization of network drivers during system boot.

Description of Changes

This PR modifies the CloudWatch Agent's service configuration to improve its startup reliability:

1. Removed the dependency on the "LanmanServer" service.
2. Added new service dependencies: "Tcpip" and "Dnscache".
3. Implemented more detailed failure action settings in the service configuration.
4. Added Start='install' to the ServiceControl element.

Rationale:

• Removed "LanmanServer" dependency: Eliminates a non-critical wait during startup, reducing potential delays.
• Added "Tcpip" and "Dnscache" dependencies: Ensures that the network stack is fully initialized before the CloudWatch Agent starts, addressing the race condition with network drivers.
• Failure action settings: Provides specific instructions for Windows to handle potential startup failures, improving service recovery.
• Start='install' addition: Ensures proper service management during installation, streamlining the setup process.

License

By submitting this pull request, I confirm that you are permitted to use, modify, copy, and redistribute this contribution under the terms of your choice.

Tests

Testing was performed on a Windows 2016 instance using the latest AMI in US-East-1:

• Installed MSI and used the default configuration for the .json file.
• Verified that when pushing the JSON config via parameter, the agent service started immediately after the AmazonCloudWatch-ManageAgent document completed.
• Confirmed that CloudWatch metrics were successfully streamed from the Agent to the service.
• Created an image from the working instance and launched it.
• Launched an initial instance and 10 additional instances for testing.
• Used SSM Run Command to execute the following PowerShell script on all instances:
  Get-Service -Name "Amazon CloudWatch*"
• All executions returned success, confirming that the CloudWatch Agent was running on instances launched from the AMI.
  

[chadpatel]

has this been tested w/impacted customer?