Tag Info

New answers tagged

1

First, Install Microsoft Online Services Sign-In Assistant. Then, Run this Powershell : Connect-MsolService Get-MsolAccountSku $val = Get-MsolAccountSku |ForEach-Object {;$_.AccountSkuId;} $mytnt = $val.Split(":")[0] New-MsolUser -DisplayName "John Smith" -FirstName "John" -LastName "Smith" -UserPrincipalName john@mytnt.onmicrosoft.com -Department ...


2

This is done by the PowerShell Script New-MsolUser either by adding the user without a license: New-MsolUser -UserPrincipalName JWarner@contoso.com -DisplayName "Jamie Warner" -FirstName "Jamie" -LastName "Warner" Or with a license New-MsolUser -UserPrincipalName DomTru@contoso.com -DisplayName "Dominique Trujillo" -FirstName "Dominique" ...


2

I would recommend using a query against the change log. The "Event Receiver" really isn't it's just a timer job using the same approach detailed in the article. You could even run it all external to SharePoint from PowerShell if you wanted. No need to deploy custom code to SharePoint.


1

SharePoint Password Reset from the boostsolution having a feature which i believe solve you issue. For security reasons you can force users to change their password on their next logon. This not only enforces security, but also allows users to easily remember passwords they themselves changed. SharePoint Password Reset


0

The problem stems from the list view web part itself, and the way it tries to retrieve all possible filter values for the column, which causes it to bump up against the list view threshold even when your view is able to circumvent it. One alternative is to use metadata navigation, which adds specified filtering options to the quick launch. Of course, this ...


0

In addition to approach suggested by Jeffrey, if you wish to access list exceeding threshold by code(create a web part with filtered data display), refer to link given below: Overcome list threshold


0

I've had my woes with the list view threshold being reached. Good call first off on not increasing the threshold. The best advice I have is to review the below article, which toward the bottom has tips on how to handle large lists/libraries while avoiding increasing the threshold. It explains in better detail what I'd like to tell you. Useful Link


0

Did you check SharePoint 2013 Permission Report: Check Access Rights for a Specific User. I think this report in PowerShell can help. This are the parameters: Generate-PermissionReport $Userid $WebAppURL $ReportPath You can iterate web applications to call the report. Hope it will be helpfully.


1

This happens because web has not been loaded. Load the web i.e. context.Load(currentweb);. Finally Load the RoleAssignmentCollection and then execute query before looping through them. Example: RoleAssignmentCollection roleAssignment = currentweb.RoleAssignments; context.Load(roleAssignment); context.ExecuteQuery(); for (int i = roleAssignment.Count - 1; i ...


2

The official and supported solution is to iterate through all the web applications in the farm and then through all site collections in the given web application. For example, using PowerShell: $loginName = "domain\user" Get-SPWebApplication | % { $_.Sites | % { $_.Url; $_.RootWeb.AllUsers | ? { $_.UserLogin -eq $loginName } | % { $_.Groups } | % { $_.Name ...


1

Also you can consider solution from VirtoSoftware Password Changing (30-days free).


0

JavaScript Client Object Model Code: var clientContext = new SP.ClientContext.get_current(); var web = clientContext.get_web(); var lists = clientContext.get_web().get_lists(); clientContext.load(lists); clientContext.executeQueryAsync(onListSuccess, onListFail); function onListSuccess() { var listInfo = 'Lists: \n\n';; var listEnumerator = ...



Top 50 recent answers are included