@scottalanmiller said in Add Active Directory User to Group using PowerShell:

When we work strictly from Windows Server Core installations we need to be able to do everything from the command line, even user management. Let's add a user that already exists into a group that already exists in Active Directory using only PowerShell.

To do this we have the handy Add-ADGroupMember PowerShell commandlet. This is very easy to use in its basic form, all we need is the name of the group and of the user that we want to add. In this case, I want to add user jane to the group "Domain Admins".

Add-ADGroupMember "Domain Admins" jane

That's it, jane is added automatically. This process, like most, is silent on success. To verify that all is as we want it to be, we can use the Get-ADGroupMember command to look up the members of a group.

Get-ADGroupMember "Domain Admins"

Can also do
Add-ADGroupMember -identity "Domain Admins" -members "jane" -WhatIf
to see if it gets added before actually running the command.

@IRJ said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@thwr said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@coliver said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@thwr said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@IRJ said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

Good article. There is ZERO reason to have a GUI on a Domain Controller. Everything can be done through Server Manager on Windows 10/8

You mean RSAT 😉

Both? You can do a lot of directory management through Server Manager as well.

Ok, agree. Just don't like the Server Manager this much, ugly interface. I want to be sure WHICH drive on WHICH host I'm going to format for example. But that is just my personal opinion and I'm more or less a console fetishist 😉

But when it comes to ADSIedit or AD sites, you really want to have RSAT.

huh?

0_1469044083616_2016-07-20_15-47-37.png

Those options are generally only there is RSAT is installed.

Sweet. Thanks for getting this for us @adam-ierymenko

@scottalanmiller said in Renaming a Windows Computer from the Command Line:

@IRJ said in Renaming a Windows Computer from the Command Line:

@scottalanmiller said in Renaming a Windows Computer from the Command Line:

@IRJ said in Renaming a Windows Computer from the Command Line:

I learned something new today. I have been using the shutdown command for years. I never realized you could rename a PC with it.

shutdown doesn't do the renaming, you just have to reboot after you rename.

I use "m" instead of c for computer name

/c is the comment for the logs to tell them that you just "Renamed Machine", it doesn't rename it, it literally puts "Renamed Machine" into the reboot logs.

Ok. Got ya.

It does work really well, especially for form building. It's a trial thing, so it'll expire after a period of time. Porbably worth it if you're doing a lot of PowerShell work, tho'.

@Kelly said:

You're not alone. You have to hack the functionality in, but it can be done: http://blog.danskingdom.com/powershell-ise-multiline-comment-and-uncomment-done-right-and-other-ise-gui-must-haves/.

Hell's yeah!

Works wonderfully.

@Minion-Queen -- Yes, this code is available for anyone to test. It needs to be run from the Connection Broker, for now.

If folks find it useful enough, I may change that.

Thanks! That's helpful.

thanks @dafyre looks good, but I have been doing a bit of reading online and I think I will change the output to make it output the data as rows with each user named with what member they are part of next to there name. two columns. in other words the output would be "Transpose" and then I would use a pivot table to do the rest.

still working on it, but if anyone knows of an easy way please do share 🙂

again thank @dafyre

Team,

I have made some head way, but what I need to know is how do I call the function "MyADGroups" in my script. not sure if the below script is correct, but what it needs to do is check who has access to the parent folder and all the children folders only, if its inherited I do not want to know, which the script does :). but if it is a Group it needs to expand the group and show me the users only.

I have done a function but I am not sure if it is correct and it will output the data I need.

$exclude = @( 'CREATOR OWNER' 'NT AUTHORITY\SYSTEM' 'BUILTIN\Administrators' 'HTBPLC\Domain Admins' ) Function Get-MYADGroups($GroupsAD){ Return Get-ADGroupMember -Identity $GroupsAD -Recursive | Where {objectClass -eq "User"} } # Get-ADGroupMember -Identity -Recursive | Get-ADUser -Property DisplayName | Select Name,ObjectClass,DisplayName? $credentials = Get-Credential Get-ADUser -Credential $credentials -Filter * -Properties DisplayName,EmailAddress,memberof,DistinguishedName,Enabled | % { $RootPath = "\\XYZ.net\users\GP\DEPT\IT\" $folders = [array](Get-Item -Path $RootPath) $folders += Get-ChildItem -Path $RootPath -Recurse -Directory $acls = foreach ($Folder in $Folders){ get-acl $Folder.fullname | Select-Object -ExpandProperty Access | Where-Object { -not $_.IsInherited -and $exclude -notcontains $_.IdentityReference } | Select-Object -Property *,@{ 'Name' = 'Folder' 'Expression' = { $Folder.FullName }} }} $acls | Export-Csv -NoTypeInformation -Path C:\NTFS\DEPARTMENTS1.csv

@DustinB3403 @dafyre can you maybe help me out on this one, should be a quick fix, just need to know if I am on the right tracks.

Thanks

I found an even easier way.

$guid.id

Since the $guid is a Powershell custom object you can call individual elements of it. This is the first time I've really dug into Powershell but this is a good thing to know.

Hmm thats actually pretty cool

Thanks

Should look into using Send-MailMessage for email. It's a lot easier to work with.