Tag Info

New answers tagged

0

Authentication provider should be Windows Ntlm . AD groups should be part of your domain. Then adding groups is like adding normal users. It should resolve itself


0

You don't need to create separate SP Group if you have already created AD Group. All you need to do is add that AD Group as how you add a normal user. For e.g. If you got a AD group called DOMAIN\Marketing-SharePoint, all you need to do is add that add that add group by going to Site Actions > site permission > grant permission and add that group.


0

Active directory groups should be of type "Security Group" to be added to SP.


1

There are password change solutions from other companies too: Harepoint, Virtosoftware


1

Without knowing more from your post, my guess is that these inactive users in AD still have profiles in Office 365 and assigned licenses. So you need to delete these users, free their licenses (happens upon deletion), and await the 30 day grace period. Within those 30 days, you can fully restore these deleted users and their content. So these inactive users ...


0

If the user has been logged in before, their AD group memberships will be cached (by default for 12 hours) as part of the Claims. You should therefor allow 12 hours to pass and see if the users gain the access.


0

Previously, an employee's name was entered into a people picker, which populated an employee ID field. The Employee ID field had a rule which set the query value from that, queried a data connection and was done. The Employee name field's default value was set to as the value of name = PreferredName, email field default value as name = WorkEmail, etc, up a ...


0

Why not using AD groups directly in SharePoint? They are a lot easier to manage, and you can assign permissions to them, the same way as you were using SharePoint groups.


0

It depends on, which version of AD you have. For example, in Azure AD you can use REST methods, like this one. In Windows 2008 R2 there is a web service interface for AD, that other components (like the AD PowerShell CmdLets) use as well. If you don't have (or don't like) these ones, you can create your own wrapper web / WCF services, or even extend the ...


0

I discovered that this is behavior based on on custom rendering of the control in our solution. It's not a general SharePoint issue after all. I needed to fix the code behind in C#. Names are added using a comma delimited string in the code behind which is triggering the behavior.


0

With Steve Lineberry's answer pointing to reflection I've found an internal property CanCreatePresonalSite of the Microsoft.Office.Server.UserProfiles.UserProfile class which I'm now using this way: internal static bool CheckPersonalSiteCreation(UserProfile up) { Type type = up.GetType(); PropertyInfo pi = type.GetProperty( "CanCreatePersonalSite", ...


1

I'm not sure the value will be 14 unless the person has actually created a mysite. Here is how SharePoint is doing it but it involves some internal methods: SPServiceContext context = SPServiceContext.GetContext(SiteInfo.CurrentWeb().Site); UserProfileApplicationProxy proxy = UserProfileApplicationProxy.GetProxy(context); if (proxy.CheckUserAccess(context, ...


0

this command, shown here https://technet.microsoft.com/en-us/library/ff607729%28v=office.15%29.aspx Move-SPUser -Identity "DomainA\JaneDoe" -NewAlias "DomainB\JaneDoe" didn't quite work, so I used $t = get-spuser "OldDom\User.Name" -web MyWeb Move-SPUser -Identity $t -NewAlias "NewDom\User.Name"


0

You can use a sub-string type of formula. Though sub-string itself is only available in forms and workflows (not calculated columns) you can write one of your own (use LEFT, RIGHT, FIND, LEN). See example



Top 50 recent answers are included