Latest Ec2Launch V2 no longer updates wallpaper when user logs in

That Start Folder link is there for both default users and my user account.

I think it’s a permissions issue with the log file?

If I run the EC2Launch wallpaper command from an administrative PowerShell window it works fine (on both images)

If I run it from a regular PowerShell window on the 2023.06.14 image it also works fine.

If I run it from a regular PowerShell window on the 2023.07.12 image it barfs with issues

panic: Failed to initialize the log files: Failed to set up log folder: Failed to create agent log file: Failed to set permissions on log file: The operation completed successfully.

goroutine 1 [running]:
golang.a2z.com/EC2InitAgent/task.(*Util).InitializeFileLogger(0x0?)
        /local/p4clients/pkgbuild-qS5b5/workspace/src/EC2InitAgent/task/util.go:100 +0x93
golang.a2z.com/EC2InitAgent/cli/internal/cmdtree/wallpaper.ConstructCommand.func1(0xc00019a000?, {0xc00018ccc0?, 0x2?, 0x2?})
        /local/p4clients/pkgbuild-qS5b5/workspace/src/EC2InitAgent/cli/internal/cmdtree/wallpaper/wallpaper.go:49 +0x65
github.com/spf13/cobra.(*Command).execute(0xc00019a000, {0xc00018cca0, 0x2, 0x2})
        /local/p4clients/pkgbuild-qS5b5/workspace/src/EC2InitAgent/build/private/bgospace/Go3p-Github-Spf13-Cobra/src/github.com/spf13/cobra/command.go:920 +0x847
github.com/spf13/cobra.(*Command).ExecuteC(0xc00011d800)
        /local/p4clients/pkgbuild-qS5b5/workspace/src/EC2InitAgent/build/private/bgospace/Go3p-Github-Spf13-Cobra/src/github.com/spf13/cobra/command.go:1044 +0x3bd
github.com/spf13/cobra.(*Command).Execute(0x1eb676f0598?)
        /local/p4clients/pkgbuild-qS5b5/workspace/src/EC2InitAgent/build/private/bgospace/Go3p-Github-Spf13-Cobra/src/github.com/spf13/cobra/command.go:968 +0x19
golang.a2z.com/EC2InitAgent/cli.ExecuteRootCmd()
        /local/p4clients/pkgbuild-qS5b5/workspace/src/EC2InitAgent/cli/executeroot.go:12 +0x91
main.main()
        /local/p4clients/pkgbuild-qS5b5/workspace/src/EC2InitAgent/main.go:20 +0x50

Can someone try and duplicate this logging in as a non administrative user?

Machines are domain joined and I am logging in over RDP as a Domain power user who has local admin rights.

Machines are up for hours (restart each day in business hours) so I'm on for more than 5 minutes.

I did not build these instances but I'm working with the team that did to clarify f they did something different with this AMI.

It is useful for me to know that it appears to be just us and not a known issue.

This is happening for me as well, and AWS Support was not able to resolve it. It seems like this may be a bug in EC2Launchv2, and it's interesting that it's only happening with a recent AMI. Also using v2.0.1521, Windows Server 2022.

Hello,

Thanks for reaching out, I am happy to help. I understand that you are experiencing issues with EC2Launch v2 no longer updating wallpaper during user logins after using an updated AMI 'ami-0fc682b2a42e57ca2'.

As you may already know, EC2Launch v2 runs as a service [1] and executes at each startup with certain tasks configured per its agent-config.yml file [2]. If you are using the provided AMI 'ami-0fc682b2a42e57ca2' without any configuration to the agent, then the wallpaper is expected to regenerate at login.

I verified that this AMI works as expected in generating this wallpaper by launching a new instance with AMI ami-0fc682b2a42e57ca2. I then logged in with the default 'Administrator' account, and the wallpaper was generated ~5 minutes afterwards. To be clear, it is common for the wallpaper generation to take a few minutes to generate.

I then stopped the instance, changed the instance type, and started it again in order to observe a change in the wallpaper. There was no issue with this and the wallpaper changed within a few minutes.

I was unable to recreate any circumstance you're describing where the wallpaper was not generated during login on this AMI. In order to understand and assist you further, I would ask that you provide step-by-step instructions that can be used to recreate the issue in my environment. Please also provide whether the users login is the 'Administrator' over Remote Desktop, or some other user and or method.

Otherwise, since I am unable to reproduce this issue at this time, we will need to wait for more information from you. If you have access to AWS Support [3], please open a ticket and we can assist you there where we can review your logs (%ProgramData%\Amazon\EC2Launch\log\agent.log) more carefully.

Thanks!

References:

1. https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2launch-v2-overview.html
2. https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2launch-v2-settings.html
3. https://aws.amazon.com/contact-us/