Stuck with AWS error during validation of workspace image? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see steps followed by our Support Techs to resolve this AWS error.

 

How to resolve AWS error during validation of workspace image?

Today, let us see some of the common causes and steps followed by our Support Techs to resolve it.

There is a default limit of 5 WorkSpace images per Region.

If you have reached this limit, then new attempts to create an image fail.

Also, Image creation from an encrypted WorkSpace is not support.

 

Validation of the WorkSpace image fails

1.Firstly, deactivate or uninstall any antivirus software or security agent that might prevent a successful image creation.

2.If a WorkSpace service (services.msc) uses a Domain account, change the service logon account to one of the following per the service requirements:

Local System
Local Service
Network Service

3.Then, keep your user profile size under 10 GB. Verify that only user profile data that is required as part of the image is present on the WorkSpace.

4.Next, verify that C:\ has free space equal to at least the user profile size plus 2 GB.

For example, if the user profile size is 10 GB, C:\ must have at least 12 GB of free space.

5.The PowerShell execution policy in a WorkSpace must set to allow RemoteSigned scripts.

To verify the value, run the Get-ExecutionPolicy PowerShell command.

If it’s not set to Unrestricted or RemoteSigned, run the Set-ExecutionPolicy –ExecutionPolicy RemoteSigned command to change the value of the execution policy.

This setting allows you to run scripts on Amazon WorkSpaces, which is required to create an image.

6.Then, verify that Amazon WorkSpaces is up to date with the latest patches to prevent interruptions in the image creation process due to Windows updates.

WorkSpace image creation can fail if Windows updates are missing or if the WorkSpace isn’t updated with the latest patches.

7.The WorkSpace that you’re testing image creation with must not assign to a user within a Domain Guests group.

To verify if there are any domain accounts, run the following command:

Get-WmiObject -Class Win32_Service | Where-Object { $_.StartName -like "*$env:USERDOMAIN*" }

8.Next, confirm if there’s a pending reboot for Windows Update. The image creation process fails if a reboot is pending.

 

Copy profile fails

Please note copy profile failure troubleshooting applies only to custom images create from private Windows 7 bundles.

For Windows 10 WorkSpaces, any files from the user profile that are intend for the image must manually copy to C:\users\default.

The image creation might fail when a user profile is copy from the WorkSpace’s D:\ drive to C:\Users\Default\ntuser.dat.

During the image creation process, the existing WorkSpace user profile is copied as the default user profile.

This allows the settings of the existing user to copy to new users. An error can occur if:

• The user profile, or a file within the user profile, is lock by a process or is in use during image creation.
• Appropriate permissions aren’t present on the profile folder. Make sure to assign full privileges on the profile folder for the system and all application packages.
• The profile path for any of the folders within the user profile is longer than 261 characters.

[Need help with the procedure? We’d be glad to assist you]

Conclusion

In short, we saw how our Support Techs resolve AWS error during validation of workspace image.