ADSI Does Not Accept Specific Passwords This topic contains 3 replies, has 4 voices, and was last updated by Ron 10 months, 4 weeks ago. Author Posts January 19, 2017 at 7:39 pm #62167 Jason ColotarioParticipant Problem is: Example #1 password is treated as two literals being that I have the double quote smack dab in the middle of the password. Problem is: Example #2 password is treated as a variable starting at the dollar sign character. EXAMPLE #1: [ADSI]$Admin4="WinNT://$env:COMPUTERNAME/dsmith" $Admin4.SetPassword("dds"ex6722!") EXAMPLE #2: [ADSI]$Admin5="WinNT://$env:COMPUTERNAME/gjohnson" $Admin5.SetPassword("p88$Top60") How can I fix this syntactical issue so that ADSI accepts these types of passwords via POSH. Is it possible to resolve this? Many thanks! January 19, 2017 at 8:10 pm #62175 random commandlineParticipant Use single quotes not double. ('dds"ex6722!') ('p88$Top60') January 20, 2017 at 8:08 am #62208 Mark PriorParticipant as you say you can you single quotes, however I would hazard a guess that the password generator (i assume your using one?) may spit out those also. i would go along the lines of excluding the single quotes in the password generation then all will be fine, i came accross something similar, using MS Orchestrator. January 20, 2017 at 1:56 pm #62235 RonParticipant You can double up the single quotes and still make it work, but means you have to remember to do that. Assuming you're running these commands interactively and either typing or pasting in the passwords, use a prompt to avoid having to escape any characters. $Admin5.SetPassword((read-host "Enter password")) If you are writing a one off script, you can use here-strings to avoid escaping characters. $h=@' abd'"$b23 '@ $Admin5.SetPassword($h) Author Posts You must be logged in to reply to this topic.