Tag Info

Hot answers tagged

2

It may happen as they are configured within an Active Directory group, instead of web.SiteUsers try using web.Users , to understand the difference you can check this link You can also get Users from User Profile Service as you said you get right result from the service var serviceContext = SPServiceContext.GetContext(site); var userProfileManager = new ...


1

Yes, you can run SharePoint 2013 apps in SharePoint Foundation 2013, but with some limitation, as Some apps may be written to leverage client side code that will only work in SharePoint Server. Those Apps won't work in Foundation. For example, an app that interacts with the User Profile Service wouldn't work in Foundation since the User Profile ...


1

So I had to go out in the twittersphere and get an answer for this. In this scenario, I can assign a secondary administrator, this person will still have access, but the notifications and reassignment will occur on the user specified as the secondary owner.


1

I found the solution. It seems that there were two User Profile Services. So what I did was this: go to CA>Application Management > Configure Service application associations and made the first UPS as default one and deselected the other one, which did not do anything and was not correct. I hope this one helps someone.


1

The following class could be introduced for that purpose that implements Enumerable Interface: class UserProfileTypedManager : UserProfileManager, IEnumerable<ProfileBase> { public UserProfileTypedManager(SPServiceContext serviceContext) : base(serviceContext) { } public new IEnumerator<ProfileBase> GetEnumerator() { ...


1

This can be solved by trying out multiple options listed below If you recently provisioned the UPS you need to reset IIS before you can create the sync connection. Have you created Managed Metadata service application? If Restart doesn't work then create Manage metadata service application and then try. Are there multiple servers in your farm? Check if it ...


1

I don't think you should focus on DirSync, as this only is a part of the issue/solution. If you have a lot of cloud-only-accounts (e.g. user@tenant.onmicrosoft.com) they would show up anyway, regardless of DirSync-settings. As far as I know there is no way of excluding your service desk agents, administrators etc that use such an account-type from the user ...


1

You can use DirSync for this purpose DirSync is simply a pre-configured Microsoft Identity Integration Server [MIIS] installation specific for Office 365 integration There are 3 ways of setting up directory sync filtering: Organizational Units based, which allows you to select which OUs are to be synced to the cloud; Domain based, allowing you to ...



Only top voted, non community-wiki answers of a minimum length are eligible