Although it rarely occurs it is sometimes necessary to work with a runas-credential that contains a space in the username (eg a web-service authentication). In pre 2012 R2 environments, spaces are apparently not allowed in the username when entering it through the SCOM console GUI.
Lukcily, the PowerShell interface does not contains such restrictions, and if upgrading to R2 is not an option, you can use the following set of commands to create and distribute a runas-account that contains spaces:
# setup variables
# create a PS credential from the user/password variables
# Connect to the SCOM environment
# Retrieve the agents, management servers or pools to distribute the account to (can be an array of a combination of these object types, use Get-SCOMAgent, Get-SCOMManagementServer or Get-SCOMResourcePool to populate)
# create a simple (or basic) runas-account using the PS credential
# distribute the account
After running these commands, you can verify (but not modify!) the changes in the GUI:
Assigning this account to a profile afterwards is perfectly doable with the GUI however!
Although this post revolves around bypassing a GUI restriction, you can use the same commands of course to administer any runas-account in the context of automation or general nerdyness
Let me know if you have further question on this topic! Jan out!