MBAM 2.0 - Installation with a Powershell script.

Hi All,
Can someone suggest me how to install all of the features of MBAM 2.0 in a single server configuration with a power-shell script. I am not getting any documentation on it. And my own methods are not working.
Any help would be greatly appreciated.
Gaurav Ranjan

David, I am following the very same for the powershell commands to install MBAM features.
Manoj, there is not any reason behind this.. I am doing this for my own just for a development so that we can automate the whole process.
I am installing the MBAM features in a single server configuration. IIS, Dot.Net, ASP.NET MVC2 and SQL has been successfully installed. now it's time to install MBAM features. As it is a single server configuration I have to instal all of the features on
this server. When I am running powershell commands to run the MBAM features one by one, i am unable to do so.
With some research I found that, You can not install MBAM DB features one by one. You have to install it al together. Then in next turn, I have to install MBAM compliance and Audit report and in last MBAM web server.
Please intimate me if I am wrong.
Now after following this scenario, I tried one more shot and I have added all of the features in a single powershell command. I tried the mahnual installation and figured out the requirements needed in a single server configuration and I followed the following
powershell command:-
MbamSetup.exe /qb /l*v MaltaServerInstall.log TOPOLOGY=0
I_ACCEPT_ENDUSER_LICENSE_AGREEMENT=1 ADDLOCAL=KeyDatabase,ReportsDatabase,
Reports,AdministrationMonitoringServer,SelfServiceServer,PolicyTemplate
REPORTS_USERACCOUNT=[UserDomain]\[UserName1] REPORTS_USERACCOUNTPW=[UserPwd1]
COMPLIDB_SQLINSTANCE=%computername% RECOVERYANDHWDB_SQLINSTANCE=%computername%
SRS_INSTANCENAME=%computername% ADMINANDMON_WEBSITE_PORT=83 WEBSITE_PORT=83
I have done all the steps with different powershell like one for IIS and another for .net and another for SQL. Now I am going to combine all those scripts and will create a single script. i will let you know the result when I will be done.
Meanwhile Manoj and David, I would request you to look into the some of my unanswered post in MBAM forum. That will be a great help. Manoj, can I send you mails on your ID which I have used earlier to have a communication with you.
Gaurav Ranjan

Similar Messages

Issue with AD Powershell Script

Matt338 wrote:This returned that I had two 1st OU's.
It was what I was looking for.
cduff wrote:
it will work without manually specifying the DN property, because the OU object will implicitly cast to a DN string
As I always passed the object and never the DN, I made in my head an implicit definition of the needed type for the targetpath argument :D

So I have been working this summer getting ready for the next school year. I need to move all of my students up and I thought this would be a great job for a PowerShell script. So I did a little research and found the commands and added the -whatif tag so I could test my scripting. It worked and I was happy.Fast forward now two months and I went to run the script once yesterday and I received some errors for the first six lines the the remaining seven ran just fine.Here is my script:Powershellget-aduser -filter "description -eq 'grad27'" | move-adobject -targetpath (Get-ADOrganizationalUnit -filter "name -eq '1st'") -whatifget-aduser -filter "description -eq 'grad26'" | move-adobject -targetpath (Get-ADOrganizationalUnit -filter "name -eq '2nd'") -whatifget-aduser -filter "description -eq 'grad25'" | move-adobject -targetpath (...
This topic first appeared in the Spiceworks Community

Issue with running powershell script in pssessions

Hi Everyone,
I am trying to run powershell script from remote machine using below commands
C:\Users\user>"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
-command "$s= New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
http://Exchservername/PowerShell/ -Authentication Kerberos ; Import-PSsession $s; "C:\Failback.ps1"
and Below is the failback.ps1.
$mbxs = Get-MailboxDatabase | Sort Name
ForEach($mbx in $mbxs)
$MBdb=$mbx.Name $ServerHosting=$mbx.Server.Name
if($mbx.activationPreference.value -eq 1)
If ($ServerHosting -ne $ActivationPreference.Key.Name)
Move-ActiveMailboxDatabase $MBdb -ActivateOnServer $ActivationPreference.Key.Name -confirm:$False
Below is what i am getting.

What is your question? Are you pointing out the yellow text? This is normal, and appears every time EMS is opened.
I should also point out that Microsoft provides a script to re-balance databases, if that's what you're trying to accomplish:
You can use the RedistributeActiveDatabases.ps1 script to balance the active mailbox databases copies across a DAG. This script moves databases between their copies in an attempt to have an equal number of mounted databases on each server in DAG. If required,
the script also attempts to balance active databases across sites.
https://technet.microsoft.com/en-us/library/dd335158(v=exchg.141).aspx
Mike Crowley | MVP
My Blog --
Baseline Technologies

Login / out history extraction from 2008R2 Event Logs with a PowerShell script?

Hi folks,
I think I'm asking something similar to a few other posts, but instead of hijacking their threads, I thought I'd start my own.
As the subject suggests, I'm trying to extract from a 2008R2 server's Event logs a table of users and their respective login / out events. Not just asking AD for their last login times, but a list of login / out events.
So far, I'm using:
Get-EventLog -logname security -Newest 1000 | where {$_.eventID -eq 4624 -or 4634 }
but the list is long, and contains host authentication connections as well as users. I believe I need something like the ability to filter on "user is domain user", or "user is not a computer", or similar, and then pipe it to Export-CSV,
but the data is not a CSV file, but more like Text. ie:
Index : 87290035
EntryType : SuccessAudit
InstanceId : 5156
Message : The Windows Filtering Platform has permitted a connection.
Application Information:
Process ID: 1688
Application Name: \device\harddiskvolume2\windows\system32\dns.exe
Network Information:
Direction: %%14592
Source Address: 192.168.xx.xx
Source Port: 53
Destination Address: 192.168.xx.xx
Destination Port: 44242
Protocol: 17
Filter Information:
Filter Run-Time ID: 66055
Layer Name: %%14610
Layer Run-Time ID: 44
Category : (12810)
CategoryNumber : 12810
ReplacementStrings : {1688, \device\harddiskvolume2\windows\system32\dns.exe, %%14592, 192.168.xx.xx...}
Source : Microsoft-Windows-Security-Auditing
TimeGenerated : 28/01/2011 4:46:35 PM
TimeWritten : 28/01/2011 4:46:35 PM
UserName :
Why is that even coming up as a result?
Ideally, I would like a CSV file containing these columns:
User,timestamp,computer,logon/off
I've thought about adding a script to the Group Policy where it runs on local machines and appends details to a file on a network share, but I think I would prefer to run this locally, perhaps periodically as a script.
-- Ebor Administrator

Thanks Matthew for the links. While I was initially thinking that's looking rather complicated, and my solution was simplistic in comparison, I'm finding (with no surprises, really) that things can get rather complicated quickly. If only parsing was easier
(or if only they didn't use "Here-Strings" instead, using normal Strings... </grumble>), as it's now looking at almost ten lines (mostly for readability).
In short, I'm now looking at:
Get-ADUser -Filter * -SearchBase "OU=Users,OU=Ebor Computing,DC=Ebor,DC=Local" | Sort-Object | ForEach-Object -Process {
$UserName = $_.SamAccountName
$MsgQuery="*" + $UserName + "*"
$EventID = $_.EventID
$Events = Get-EventLog -logname security -Message $MsgQuery | where {$_.EventID -eq 4624 -or $_.EventID -eq 4634} | ForEach-Object -Process {
$SrcAddr = "Unknown"
$idx = $_.message.IndexOf("Source Network Address:")
if ($idx -gt 0) {$SrcAddr = $_.message.substring($idx+23,15).trim()}
$UserName+","+$SrcAddr+","+$EventID+","+$_.TimeGenerated | Out-File -FilePath $UserName"_login_events.csv" -Append
Eeuuw... don't know why that was parsed as it was above... Either way, this takes a very long time, but gives a separate file for each user and goes back the entire length of the Event Log's history for reporting purposes.
Noting that I had to query AD for the users thus has to run from the AD Powershell, instead of the normal PS, as I don't know the appropriate module load command to get a normal PS to work with AD. Keeping this limitation in mind, I think it works, but needs
some tweaking for formatting and output I think.
I'm tempted to create an RODC for this to run on, but what else does the DC do, really? May as well warm up the CPU for an hour or so ;-) I guess one of the improvements could be to determine if the cycles are being taken up with poor String parsing, or
with AD querying. Another would be to add some comments... ;-)
-- Ebor Administrator

Can anyone help with a powershell script using the search-adaccount cmdlet to filter out accounts that have been created in the last 90 days?

Hi,
I have the following script that is supposed to search AD for all user accounts that haven't logged into the domain in more than 90 days. I first did not have the where-object clause because I didn't realize the search-adaccount would provide results
back of users that have never logged in, but were created less than 90 days ago. So I tried to incorporate the logic to not include user accounts that were created in the last 90 days.
#requires -version 4
#This script creates a file of accounts that have not been logged into in the past 90 days, excluding accounts that have been created within the past 90 days since the -AccountInactive option does not factor for the whenCreated property of an AD object
$DateThreshold = ((Get-Date).AddDays(-90))
$ReportDate = Get-Date -Format yyyy-MM-dd
#Create a folder according to the current date to be used for storing the report
New-Item -Path ".\$ReportDate" -ItemType Directory
$InactiveUsers = Search-ADAccount -UsersOnly -AccountInactive -TimeSpan "90" -SearchBase "OU=XXXX,DC=XXXX,DC=XXXX,DC=XXXX" | Where-Object {$_.whenCreated -gt $DateThreshold} | Export-Csv ".\$ReportDate\Inactive90_$ReportDate.csv"
However, I can't ever get the whenCreated field to populate with data. What gives?

Hi,
Search-ADAccount doesn't return a whenCreated property. If you want that, you'll need to use Get-ADUser as well. Here's a basic example you can build from:
$dateThreshold = (Get-Date).AddDays(-90)
Search-ADAccount -UsersOnly -SearchBase 'OU=Users,DC=domain,DC=com' -AccountDisabled | ForEach {
$whenCreated = (Get-ADUser -Identity $_.SamAccountName -Properties whenCreated).whenCreated
If ($whenCreated -gt $dateThreshold) {
$_
Don't retire TechNet! -
(Don't give up yet - 12,950+ strong and growing)

Please help me with Powershell Script - Message Box to display after Installation

Hi Guys,
Am using package model to deploy the software. After installation on client machines i want to display a dialog box to notify the successful installation.
Currently trying VBScript to show the dialog message.
But few machines i get this dialog and few machines am not getting, in program command line am calling a batch script.
Now am planning to use a Power shell scripting to show a message box and trying to call it through a batch script.
Please assist me with the powershell script which will display a message box like above
(and let me know in script how to enable the set-execution policy Remote signed enabled)
Thanks,

You can set the execution settings from within the client settings.
For a simple message box without having to load assmemblies
$wshell = New-Object -ComObject Wscript.Shell
$wshell.Popup("Operation Completed",0,"Done",0x1)

Error with SMLets in an Orchestrator called PowerShell Scripts

Hi!
This is likely so simple I am overlooking the problem but...
I have a "Run .Net Script" activity in an Orchestrator 2012 SP1 Runbook. It calls SMLets. The issue is it runs in the PowerShell ISE on the Runbook server without issue. It runs in the Runbook Tester just fine. But if I
call the runbook with the PowerShell script, it errors out on the first call the a SMLets provide cmdlet.
A Few Detail:
We loaded the latest SMLets from CodePlex. We can use the cmdlets in both the 32-bit and 64-bit environments.
The very first line of the PowerShell script is: Import-Module SMLets
The first SM cmdlet is: $class = Get-SCSMClass System.WorkItem.Activity.ReviewActivity$
The Runbook Containing the PowerShell Script:
And lastly, the Event of the error thrown:
In trying to make this work we have tried to run the script remotely on the SCSM server (New-PSSession and Invoke-Command). Failures due to rights on the SCSM server.
My opinion is the issue is a rights issue but we cannot find the difference between any of the accounts testing/debugging and the Orchestrator Runbook Service account. I can run the PowerShell and the Runbook Tester when logged on as the
Orchestrator Runbook Service account. It works until I have to call the runbook with the PowerShell Activity. It just like my Account. We've even set the account on the security tab of the Invoke Runbook Activity.
Is there something I've overlooked? Something in the install of the SMLets, maybe? A clue? Help?
If nothing else, thank you for letting me voice my issue onto the 'Net. Maybe someone else has been down this road and can tell me where the off-ramp is. ;-)
Ray Watters,
Chicago, IL

Hi,
also make sure that your PS scriptruns with Windows PowerShell (x86) (32bit)
http://www.sc-orchestrator.eu/index.php/scoblog/64-using-64bit-powershell-cmdlets-in-the-run-net-script-activity-from-orchestrator
or with PowerShell V2
http://www.sc-orchestrator.eu/index.php/scoblog/102-running-powershell-30-with-the-run-net-script-activity
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

How to use UDL file in Powershell script?

Hello Scripting Guys,
I have a VBScript that works great for connecting to an Oracle DB using a .UDL file. Here is the important part of the script:
Set dataconnect = CreateObject("ADODB.Connection")
Path= "File name=C:\UDLs\TEST.udl"
dataconnect.ConnectionString = Path
dataconnect.open
Set oCmd = CreateObject("ADODB.Command")
oCmd.ActiveConnection = dataconnect
oCmd.CommandText = "SYSTEM.JOB.INSERT_JOB"
oCmd.CommandType = 4
set oParam = oCmd.CreateParameter("job_name_val")
oParam.type = 200
oParam.direction = 1
oParam.size = 255
oParam.value = job_name
oCmd.Parameters.Append oParam
set oParam = oCmd.CreateParameter("description")
oParam.type = 200
oParam.direction = 1
oParam.size = 4000
oParam.value = descrip
oCmd.Parameters.Append oParam
set oParam = oCmd.CreateParameter("status_val")
oParam.type = 200
oParam.direction = 1
oParam.size = 50
oParam.value = status
oCmd.Parameters.Append oParam
oCmd.Execute
As you can see, it creates "ADODB.Connection" and "ADODB.Command" objects. Everything works as intended here.
Now, I'm trying to convert this VBScript to a Powershell script.
Here's what I have so far with my PowerShell Script (non-working, but no errors):
$job_name = $args[0]
$status = $args[1]
$descrip = $args[2]
write-host "Job Name = " $job_name
write-host "Status = " $status
write-host "Description = " $descrip
#Create an object of type: ADODB class: Connection
$objConn = New-Object -com "ADODB.Connection"
#Create Connection String
$connString = "File name=C:\UDLs\TEST.udl"
#Open the connection
$objConn.open($connString)
#Command Object
$oCmd = New-Object -com "ADODB.Command"
#Assign DB connection To Command
$oCmd.ActiveConnection = $objConn
#Set Command text
$oCmd.CommandText = "SYSTEM.JOB.INSERT_JOB"
#Set Command Type
$oCmd.CommandType = 4
#Create parameter list For Command
#Job name Parameter
$oParam1 = $oCmd.CreateParameter("job_name_val")
$oParam1.type = 200
$oParam1.direction = 1
$oParam1.size = 255
$oParam1.value = $job_name
#Append parameter list
$oCmd.Parameters.Append($oParam1)
#Description Parameter
$oParam2 = $oCmd.CreateParameter("description")
$oParam2.type = 200
$oParam2.direction = 1
$oParam2.size = 4000
$oParam2.value = $descrip
#Append parameter list
$oCmd.Parameters.Append($oParam2)
#Status Parameter
$oParam3 = $oCmd.CreateParameter("status_val")
$oParam3.type = 200
$oParam3.direction = 1
$oParam3.size = 50
$oParam3.value = $status
#Append parameter list
$oCmd.Parameters.Append($oParam3)
#Command Execution
$oCmdX = $oCmd.Execute
write-host $oCmdX
#Cleanup
#Set parameters = To NULL
$oParam1 = $null
$oParam2 = $null
$oParam3 = $null
#Set Command = To NULL
$oCmd = $null
#Close DB object
$objConn.Close()
So, not too many changes with the syntax, but it doesn't actually send the ADODB Command to the Database. I have also tried hardcoding the connection string, but no luck there either. Am I not using the right syntax with the Command object? I am fairly new
to both of these languages, so I appreciate any help/suggestions you can offer!
Thank you,
Brian

Thanks JRV.
I am now getting this error (at least some feedback from Powershell now):
Exception calling "Open" with "1" argument(s): "[Microsoft][ODBC Driver Manager
] Data source name not found and no default driver specified"
At C:\temp\JobMon.ps1:21 char:14
+ $objConn.open <<<< ($connString)
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
The thing is, it shouldn't be using a Microsoft driver. It should be using the Oracle Client driver (which I have installed and tested successfully using TNSPing).
Do I need to declare some sort of "using System.Data.OracleClient namespace" like in C++? How would I do that in Powershell?
Thanks again,
Brian

Powershell Script to change the target destination on a shortcut file.

Hi All,
I am in a middle of a new file server implementation and have come across a problem where the items on the old file server has been archived and moved to another server and in place a shortcut is left at the original location. The current target of those
shortcut is going to be changed and thus I need to change the Target destination on those various shortcuts files. I am new to powershell and will really appreciate if someone can assist me with a powershell script for the below steps:
To find all shortcut files (Excel, word, powerpoint and other types) whose current target destination is \\abcserver\z\abcpath
Change the Target destination to \\xyzserver\z\abcpath on the shortcut file and apply the change.
Effectively only change shortcut files whose current target begins with "\\abcserver\" and change to "\\xyzserver\"
Search for the next shortcut and continue changing it.
Hope the above makes sense and appreciate the assistance.
Thanks!

Did you look?
https://www.google.com/?gws_rd=ssl#newwindow=1&q=powershell+change+shortcut+path
¯\_(ツ)_/¯

OSD - Task Sequence to run powershell script

Hello,
I'm building up an image with OSD and will be layering some components to meet our needs with some powershell scripts. At the moment we will not have this device add itself to the domain so it'll be in a workgroup. The scripts are on a share that everyone has
read access to. Should I add a task sequence that will map a drive letter with domain credentials and have the task sequence call the script from that drive letter?

That is possible to do, but why would you not create a package/application with the script and let it download and run locally?
Daniel Ratliff | http://www.PotentEngineer.com

Powershell script monitor with encrypted password

I have created a powershell script based monitor in my management pack and everything is ok but I can't get my credentials work inside the script. I want to open pssession to another computer with my credentials. I have triple checked that my pssession is
working because I can access it from powershell console.
This works perfectly at local server from PSconsole:
$EncryptedPassword ="01000000d08c9ddf0115d1118c7a00c04fc297eb01000000534b2....etc...etc..."
$pw = convertto-securestring -String $EncryptedPassword
$cred = new-object System.Management.Automation.PSCredential -argumentlist "MyDOMAIN\MyACCOUNT",$pw
$s = New-PSSession -ComputerName "MyServer" -Port MyPort -Credential $cred
But when I run the same lines inside my management pack the convertto-securestring
does nothing, it just wont convert the encrypted password to secure string!
I have tried this plain text method and it works
inside my management pack, but I don't want to use it because you can see the password in plain text:
ConvertTo-SecureString -String "myPlainTextPassword" -AsPlainText -Force
This is the $error variable, so it's basically says that I don't have anything in the password secure string variable because the convertion did not work for some reason:
The argument is null. Provide a valid value for the argument, and then try running the command again. Cannot process argument transformation on parameter 'Credential'. PromptForCredential Exception calling ".ctor" with "2" argument(s):
"Cannot process argument because the value of argument "password" is null. Change the value of argument "password" to a non-null value." The system cannot find the file specified. Exception calling "SecureStringToBSTR"
with "1" argument(s): "Value cannot be null. Parameter name: s" The system cannot find the file specified. Exception calling "SecureStringToBSTR" with "1" argument(s): "Value cannot be null. Parameter name: s"
The system cannot find the file specified.
So is there some known issue with SCOM Agent / management pack when you are dealing with convertto-securestring
function with encrypted passwords?
I used these methods to encrypt the password: Technet article about encryption

I got it to work!
<TypeDefinitions>
<EntityTypes>
<ClassTypes>
<ClassType ID="MyClass" Accessibility="Public" Abstract="false" Base="Windows!Microsoft.Windows.LocalApplication" Hosted="true" Singleton="false" Extension="false"
/>
</ClassTypes>
</EntityTypes>
<SecureReferences>
<SecureReference ID="MyRunAsAccountProfile" Accessibility="Public" Context="System!System.Entity" />
</SecureReferences>
<ScriptBody>param (
[string]$Username,
[string]$Password
$API = new-object -comObject "MOM.ScriptAPI"
$PropertyBag = $API.CreatePropertyBag()
$cred = New-Object System.Management.Automation.PSCredential -Argumentlist @($Username,(ConvertTo-SecureString -String $Password -AsPlainText -Force))
$s = New-PSSession -ComputerName "myserver" -Credential $cred
Invoke-Command -Session $s -ScriptBlock { $service = Get-Service -Name Spooler}
$invcom = Invoke-Command -Session $s -ScriptBlock { $service.status}
Remove-PSSession -Id $s.Id
if ($invcom.Value -ne "Running") {
$PropertyBag.AddValue("State","ERROR")
$outputLongLine = "Spooler Service is not running on target server!"
$PropertyBag.AddValue("Description", $outputLongLine)
else {
$PropertyBag.AddValue("State","OK")
$outputLongLine = "Spooler is Running on target server."
$PropertyBag.AddValue("Description", $outputLongLine)
$PropertyBag</ScriptBody>
<Parameters>
<Parameter>
<Name>Username</Name>
<Value>$RunAs[Name="MyRunAsAccountProfile"]/Domain$\$RunAs[Name="MyRunAsAccountProfile"]/UserName$</Value>
</Parameter>
<Parameter>
<Name>Password</Name>
<Value>$RunAs[Name="MyRunAsAccountProfile"]/Password$</Value>
</Parameter>

Split filename and create folders with Powershell script ( --newbie user)

I have a folder with 1000's of files. Each file varies in length; typically between 9-14 characters. Example:
C:\workpics\1238955678.1
C:\workpics\744556224.1
C:\workpics\744556224.2
C:\workpics\8445655996.1
I would like to run a script to split the filename and separate into folders. The filename would then consist of 5 characters, the foldername would be the first characters remaining.
C:\workpics\12389\55678.1
C:\workpics\7445\56224.1
C:\workpics\7445\56224.2
C:\workpics\84456\55996.1
Any assistance to create this Powershell script would be awesome. Thank you!!

I have a folder with 1000's of files. Each file varies in length; typically between 9-14 characters. Example:
C:\workpics\1238955678.1
C:\workpics\744556224.1
C:\workpics\744556224.2
C:\workpics\8445655996.1
I would like to run a script to split the filename and separate into folders. The filename would then consist of 5 characters, the foldername would be the first characters remaining.
C:\workpics\12389\55678.1
C:\workpics\7445\56224.1
C:\workpics\7445\56224.2
C:\workpics\84456\55996.1
Any assistance to create this Powershell script would be awesome. Thank you!!
Please reread your request. It makes no sense. Read each statement carefully and notice that the statements are in conflict.
Start your scrip in PowerShell. Look up things like how to list files and how to manage strings. All of the information you need is here:
http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx
¯\_(ツ)_/¯

Which is better approach to manage sharepoint online - PowerShell Script with CSOM or Console Application with CSOM?

Which is better approach to manage sharepoint online - PowerShell Script with CSOM or Console Application with CSOM?
change in sharepoint scripts not require compilation but anything else?

Yes, PowerShell is great, since you can quick change your code without compilation.
SP admin can write ps scripts without specific tools like Visual Studio.
With powershell you can use cmdlets,
which could remove a lot of code, for example restarting a service.
[custom.development]

App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results

Please Vote if you find this to be helpful!
App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results
Just posted this to the wiki:
http://social.technet.microsoft.com/wiki/contents/articles/25323.app-v-powershell-script-to-query-xenapp-servers-for-app-v-publishing-errors-and-output-an-excel-document-with-the-results.aspx

Hi petro_jemes,
Just a little claritification, you need to add the value to the variable "[string]$ou", and also change the language in the variable "$emailbody" in the function "Get-ADUserPasswordExpirationDate".
I hope this helps.

How to give readonly Permission rights to 1000 users with button using powershell script?

$site = Get-SPSite
-Identity "http://mysite/"
$user = Get-SPUser
-Identity "mydomain\myuser"
-Web $site.RootWeb
$assignment = New-Object
Microsoft.SharePoint.SPRoleAssignment($user)
$role = $site.RootWeb.RoleDefinitions[[Microsoft.SharePoint.SPRoleType]::Reader]
$assignment.RoleDefinitionBindings.Add($role);
foreach ($web in $site.AllWebs)
if ($web.HasUniquePerm)
$web.RoleAssignments.Add($assignment)
With above script I can give Readonly permission to the users...but at a time I can give permission to only one user...Actually 1000 users requires these permissionMy requirement is I will have a textbox and a button.I will enter username in textbox
and when i clicked button the required permission should be assigned to the user given in the textbox...can you please tell how can i achieve this........how make to run powershell script when button is clicked.

Hello,
Instead of applying security to user level, it'll be better to create a SharePoint group where you will add the users. and use the outof the box interface to give permissions.
and for your button, just add the direct link to add user
http://serverurl/_layouts/15/aclinv.aspx?GroupId=7&IsDlg=1
replacing the group ID by the id of your new group (you can see it in the url when your are in the group)
Best regards, Christopher.
Blog |
Mail
Please remember to click "Mark As Answer" if a post solves your problem or
"Vote As Helpful" if it was useful.
Why mark as answer?

MBAM 2.0 - Installation with a Powershell script.

Similar Messages

Maybe you are looking for