Windows powershell

I'm using windows powershell to add new users. Whenever I press enter at the end of my command it simply puts >> as if it's expecting more commands but I don't know what else it wants. I followed the MCITP lab exactly so I don't know what the issue is.

Find more posts tagged with

Comments

undomiel

Without seeing the command you're entering make sure you're closing all quotes and brackets.

rsutton

Some sort of a syntax error, posting the command would help.

method115

New-ADUser -Path "ou=User Accounts,dc=contoso,dc=com" -Name "Mary North"
-SAMAccountName "mary.north" -UserPrincipalName "mary.north@contoso.com"
-EmailAddress "mary.north@contoso.com" -GivenName "Mary" -Surname "North"
-Description "Sales Representative in Australia"
-Company "Contoso, Ltd." -Department "Sales"
-Office "Sydney" -AccountPassword (ConvertTo-SecureString
-AsPlainText "Pa$$w0rd" -Force)
-ChangePasswordAtLogon $true -Enabled $true

I went through the command twice and all quotation markets and brackets were closed.

IT Explorer

method115 wrote: »

New-ADUser -Path "ou=User Accounts,dc=contoso,dc=com" -Name "Mary North"
-SAMAccountName "mary.north" -UserPrincipalName "mary.north@contoso.com"
-EmailAddress "mary.north@contoso.com" -GivenName "Mary" -Surname "North"
-Description "Sales Representative in Australia"
-Company "Contoso, Ltd." -Department "Sales"
-Office "Sydney" -AccountPassword (ConvertTo-SecureString
-AsPlainText "Pa$$w0rd" -Force)
-ChangePasswordAtLogon $true -Enabled $true

I went through the command twice and all quotation markets and brackets were closed.

Did you use "Import-Module ActiveDirectory" at the begining ?

undomiel

In your -Path parameter change the double quote to a single quote.

rjs_essex

IT Explorer wrote: »

Did you use "Import-Module ActiveDirectory" at the begining ?

As IT Explorer said, you need to import the AD cmdlets into the environment before you can call them. Did you do this?...

Zartanasaurus

If he hadn't imported the AD mod, he'd get an error telling him the cmdlet was unrecognized. Anytime I've gotten the >> it's because of mismatched single or double quotes.

rjs_essex

Zartanasaurus wrote: »

If he hadn't imported the AD mod, he'd get an error telling him the cmdlet was unrecognized. Anytime I've gotten the >> it's because of mismatched single or double quotes.

Good point

method115

Thanks for the help guys never figured out what I did wrong. Closing and opening a new powershell fixed it though. I noticed other commands were not working with that same powershell session as soon as I opened a new one everything was working fine. I must have clicked a key or something that causes that to happen not sure.