In Quebec, MID Server Powershell probes/jobs using Credentials with Username in UPN format will fail ("userName@testexample.com" vs. "testexample\userName")DescriptionPowershell Activities and windows credential tests stop working after upgrading to Quebec if the windows credential username is in UPN format, i.e. userName@testexample.com. Starting in Quebec, a credential in UPN format will be converted to domain\name format before being used. The credential will fail if the domain in the UPN format is not a valid domain (e.g. testexample.com is not a valid domain). Symptoms will be see in any feature that uses Powershell probes via a MID Server, including Discovery, Service Mapping, Orchestration, IntegrationHub/Spokes, Client Software Distribution, Password Reset, etc.Steps to Reproduce Powershell activity Create a powershell activity via workflow editor in Paris and QuebecCreate user in format userName@testexample.comTest the activity successfully in ParisTest the activity in Quebec and see errorAlso, log into MID server and test the credential via Powershell ISE with following script (populated needed variables): $computer = ""$user = ""$password = ""$passwordSecure = convertto-securestring -string $password -asplaintext -force$cred = new-object -typename System.Management.Automation.PSCredential -argumentlist "$user" , $passwordSecuregwmi win32_operatingsystem -computer $computer -credential $cred -impersonation 3 -authentication 6 -EA "Stop" Windows credential test Navigate to discovery_credentialsSelect the credentialClick on "Test Credential"Fill out necessary valuesClick on "Ok"Compare results pre Quebec (e.g. Paris) and on Quebec Note: On the test above, try both formats "userName@testexample.com" and "Domain\userName"WorkaroundThis problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix. Until you can upgrade, please use one of the two options below for the workaround: ============= Option 1: Update the credential user name: Run the script below to determine impacted discovery_credentials(function() { var ga = new GlideAggregate('discovery_credentials'); ga.addQuery('active','true'); ga.addQuery('type', 'windows'); ga.query(); var likeEmails = []; while (ga.next()) { var username = ga.getValue('user_name'); if (/\S+@\S+\.\S+/.test(username)) { likeEmails.push({ username: username }); } } var results = { 'eMailLikeUserNames': likeEmails, 'total': likeEmails.length, 'reason': 'PRB1484975' }; gs.print(JSON.stringify(results));}());Navigate to table discovery_credentialsDetermine the correct domain nameChange user name from userName@testexample.com to Domain\userName from the script results returned in step #1Test workaround Option 2: Update scripts: Navigate to sys_script tableSearch for business rule with name = "Prevent Duplicate,Spaces & Colon in name"Set active = "false", else this BR will prevent the scripts from updatingNavigate to table ecc_agent_script_fileOpen records with sys_ids 3f234355376001006b882d465abe5de8 and e0343456372331000e4d03488e41f149Find functions getCredential (script 3f234355376001006b882d465abe5de8) and getCred (script e0343456372331000e4d03488e41f149)Remove following line from above functions $user = formatUser -user $user; Save recordRevert business rule "Prevent Duplicate,Spaces & Colon in name" back to OOBTest workaroundRevert modified scripts to OOB once upgrade is complete to a version where the fix is providedRelated Problem: PRB1484975