Summary:<\/span><\/b> Learn how to use Windows PowerShell to create local Windows groups in this step by step Scripting Guy blog post.<\/span><\/p>\n <\/span><\/p>\n — AM<\/span><\/p>\n <\/span><\/p>\n Portions of today’s post are excerpted from Ed Wilson’s Windows PowerShell Scripting Guide<\/i>, Microsoft Press, 2008. <\/span><\/p>\n We may have to create local groups on a Windows machine to control access to local resources<\/span><\/a>, such as a shared scanner, or printer<\/span><\/a>. Local groups are also used in workgroup settings. These are still used in remote offices in many companies. There is a new group tool in the computer management toolkit. <\/span>This is seen in the following figure.<\/span><\/p>\n <\/span><\/p>\n In the CreateLocalGroup.ps1<\/b> script we first use the param<\/b> statement to define three parameters: -computer<\/i>, -group<\/i> and –help<\/i>. We set the –computer<\/i> parameter to the local machine by default. This line of code is seen here. <\/span><\/p>\n param($computer<\/span>=”localhost<\/span>“, $group<\/span>, $help<\/span>)<\/span><\/span><\/p>\n <\/span><\/p>\n Next we define the funhelp<\/b> function. The funhelp<\/b> is a giant here-string, that is stored in the $helpText<\/b> variable. Inside the here-string, we are free to ignore quoting rules, and to format the text the way that we want it to appear on the screen. We define the description of the script, the parameters, and the syntax. After we have defined these sections of the string, we then print the text of the $helpText<\/b> variable, and exit the script. The funhelp<\/b> function is seen here. <\/span><\/p>\n function funHelp()<\/span><\/span><\/p>\n {<\/span><\/span><\/p>\n $helpText<\/span>=@”<\/span><\/span><\/p>\n DESCRIPTION:<\/span><\/span><\/p>\n NAME: CreateLocalGroup.ps1 <\/span><\/span><\/p>\n Creates a local group on either a local or remote machine.<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n PARAMETERS: <\/span><\/span><\/p>\n -computer Specifies the name of the computer upon which to run the script<\/span><\/span><\/p>\n -group <\/span>Name of group to create<\/span><\/span><\/p>\n -help <\/span>prints help file<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n SYNTAX:<\/span><\/span><\/p>\n CreateLocalGroup.ps1<\/span><\/span><\/p>\n Generates an error. You must supply a group name<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n CreateLocalGroup.ps1 -computer MunichServer -group MyGroup<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n Creates a local group called MyGroup on a computer named MunichServer<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n CreateLocalGroup.ps1 -group Mygroup<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n Creates a local group called MyGroup on local computer<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n CreateLocalGroup.ps1 -help ?<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n Displays the help topic for the script<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n “@<\/span><\/span><\/p>\n $helpText<\/span><\/span><\/span><\/p>\n exit<\/span><\/span><\/p>\n }<\/span><\/span><\/p>\n <\/span><\/p>\n If the $help<\/b> variable is present then we will print the help text. This line is seen here. <\/span><\/p>\n if($help<\/span>){ “Obtaining<\/span> help<\/span> …” ; funhelp }<\/span><\/span><\/p>\n <\/span><\/p>\n We also have to make sure that a group name is supplied to the script when it is run. If the $group<\/b> variable is not present, then it was not supplied at run time. Therefore, we will generate an error by using the throw<\/span><\/a> statement. This section is seen here. <\/span><\/p>\n if(!$group<\/span>) <\/span><\/span><\/p>\n <\/span> <\/span>{<\/span><\/span><\/p>\n <\/span>$<\/span>(Throw ‘A value for $group<\/span> is required. <\/span><\/span><\/p>\n <\/span>Try this: CreateLocalGroup.ps1 -help ?’)<\/span><\/span><\/p>\n <\/span> <\/span>}<\/span><\/span><\/p>\n <\/span><\/p>\n Finally we get to the main [ADSI] section of the script. It resembles the section that creates a local user. The difference is we create a group, instead of a user. The other difference is no password is required for a group. Other than that, the syntax is almost the same. This section is seen here. <\/span><\/p>\n $objOu<\/span> = [ADSI<\/span>]”WinNT<\/span>:\/\/$computer<\/span>“<\/span><\/span><\/p>\n $objUser<\/span> = $objOU<\/span>.Create(“Group<\/span>“, $group<\/span>)<\/span><\/span><\/p>\n $objUser<\/span>.SetInfo()<\/span><\/span><\/p>\n $objUser<\/span>.description = “Test<\/span> Group<\/span>“<\/span><\/span><\/p>\n $objUser<\/span>.SetInfo()<\/span><\/span><\/p>\n <\/span><\/p>\n The completed CreateLocalGroup.ps1<\/b> script is seen here. <\/span><\/p>\n CreateLocalGroup.ps1<\/strong><\/span><\/p>\n param($computer<\/span>=”localhost<\/span>“, $group<\/span>, $help<\/span>)<\/span><\/span><\/p>\n <\/span><\/span><\/p>\n function funHelp()<\/span><\/span><\/p>\n {<\/span><\/span><\/p>\n $helpText<\/span>=@”<\/span><\/span><\/p>\n![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/q-for-powertip.jpg\" "\\"Hey,")
Hey, Scripting Guy! I have to create some local security groups on my Windows 2008 server. I want to use Windows PowerShell 1.0 because I have not upgraded Windows PowerShell 1.0 to Windows PowerShell 2.0<\/span><\/a>. In fact, I am planning on upgrading the server to Windows 2008 R2 and I know that I will get Windows PowerShell 2.0 when that upgrade takes place. What do I have to do to create local security groups on my Windows 2008 Server?<\/span><\/p>\n![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/a-for-powertip.jpg\" "\\"Hey,")
Hello AM, Microsoft Scripting Guy Ed Wilson here. To create local security groups on your Windows Server 2008 server, you use the same procedure that you would use on a Windows 2000 computer, Windows XP<\/span><\/a> workstation, Windows Server 2003<\/span><\/a> server or just about any other version of the Windows operating system. In fact, the script would probably even work on a Windows NT 4.0 or NT 3.51 computer. This is because the SAM based security groups are mature technology. I decided to take a look at the Windows PowerShell Scripting Guide<\/span><\/a> book that I wrote for Microsoft Press, and excerpt a portion of one of the chapters in that most excellent book. <\/span><\/p>\n![](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/0181.HSG-11-24-10-01.jpg\")
<\/span> <\/span><\/p>\n