Tag Info

New answers tagged

0

If the problem is still occurs, try this PowerShell script: Add-PSSnapin "Microsoft.SharePoint.PowerShell" $site = Get-SPWeb -Identity http://<Your site address> $listname = "Members" $list = $site.Lists[$listname] $users = Get-SPUser -Web $site -Group "<The name of the required group on $site>" -Limit all foreach ($user in $users){ ...


0

Instead of changing the STS configuration as suggested in the blog posts, I'd suggest to just clear the Logon Token Cache. Clear-SPDistributedCacheItem –ContainerType DistributedLogonTokenCache


1

This is your lucky day, since it's always been quite hard do develop using PowerShell. However, the script has already been published and is free to use. You find the script here: List all Distribution Groups and their Membership in Office 365. ...


0

To create a field like the one pictured above, you would need to go into the list settings, advanced, and turn on appending. Then you would go into InfoPath, remove the fields from your form and add them back. This is actually a really simple process that I spent a solid 72 hours trying to figure out.


0

I was working on a staff rota and came up with a sort of solution that allows the team to see what they should be doing on any particular day in a sort of Group Calendar. Basically - stop thinking of a date as a date, but think of it as a piece of text that is ordered by column number that just happens to look like a date. I created a spreadsheet of dates ...


0

Add farm account(s) to AD security group Windows Authorization Access Group. Added farm services accounts to the AD security group Windows Authorization Access Group, because in order for Check Permissions to work whatever account is running the background service needs read access to the TGGAU (tokenGroupsGlobalAndUniversal) attribute of the account being ...


0

Only Site Collection Administrator can edit memberships of all groups. Some groups may be configured to only allow the group's owner (single person or SharePoint Group) to edit the membership. By default, the Visitors, Members and Owners groups are owned by the Owners group, but the groups created later manually are owned by default by the user who created ...


1

Also, in the Group Settings (go to the group > Settings drop-down > Group Settings), make sure you or a group you are in is listed as the "Group Owner".


0

You said you are the owner of the Site Colletion, right? If you are Site collection admin / Owner then you can view the permissions or add the users. Make Sure you are Site collection administrator. As the Site Collection Admin you can change Group Settings...select the group and select Settings > Group Settings to access it.


0

While creating a group there is an option to specify who can view and who can modify the group members. I strongly believe that your account might have removed from these two places. You can contact your Site Collection Administrator and ask him to make you the owner to that particular group.


1

Not sure why it could be empty - perhaps was deleted at some point (this has happened to me before). You can set the owner by visiting _layouts/permsetup.aspx of your site collection.


0

It seems the only missing part in your example is assigning permissions to the Web site. Use SP.Web.associatedMemberGroup property to set the group of users who have been given contribute permissions to the Web site SP.Web.associatedOwnerGroup property to set the associated owner group of the Web site SP.Web.associatedVisitorGroup property to set the ...


0

You should manually create those groups and assign permission as below var groupCreationInfo = new SP.GroupCreationInformation(); groupCreationInfo.set_title(siteName + ' Members'); groupCreationInfo.set_description('Member Group'); this.oGroup = oWebsite.get_siteGroups().add(groupCreationInfo); var collRoleDefinitionBinding = ...


1

As per Microsoft maximum 10,000 groups are allowed per Site Collection. Anything beyond that will cause performance. (The performance degrade you can observe while adding users into group etc.) Hence I don't think in your use case this will have any performance impact.


1

Try this var siteUrl = '/mysite'; var clientContext = new SP.ClientContext(siteUrl); this.collGroup = clientContext.get_web().get_siteGroups(); clientContext.load(collGroup); clientContext.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed)); function onQuerySucceeded() { var ...


0

In the code, you have just loaded the web and the sitegroups which do not actually have any information. Unless the request is sent to the server, you wont be able to get the groups information that you are iterating on. You will have to execute context.executeQueryAsync(onSuccess,onFailure) in order to get the group collection information and then get ...


1

Late answer but, The User Profile is not responsible in this case. SharePoint recognizes AD security groups and attaching permissions to these groups will cause the permissions to be granted to the User. Unfortunately, due to SharePoint caching the user's memberships on login, changes made to a security group are identified only after the cache has ...



Top 50 recent answers are included