Tag Info

New answers tagged

0

Hi you don't need to get the site context for the user profile service application manage page. For a start your users won't have access to that page/site. Just get a site context for where the application resides. If it doesn't then suggest you use the root site of your main web application. Here is an example of how to get the user profile: ...


0

You can develop the apps in the SharePoint Foundation 2013 but with Limitation. Even MSFT mentioned all the below features avaiable in foundation but limitation. They put 1 with it. 1 Means: Certain app authoring features require user profiles, which aren’t available in SharePoint Foundation 2013. Conclusion : Yes you can build the apps but not fully ...


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 ...


0

User profile service is not available in the foundation version. You need to have SharePoint Standard or SharePoint Enterprise. SharePoint Server 2013 Features – Foundation vs Standard vs Enterprise Edit I see now that Microsoft states that you can develop apps in SharePoint Foundation. However, i can't see how you can follow the article for setting up a ...


0

I found a solution to my problem, clear the configuration cache following this guide http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx The User profile service started to sync again


0

Not sure about 2013 but I had the same issue in 2010. I found this link very helpful. Basically I had to replace a couple of .dll files. TechNet Article HERE


0

In the connection setting, you should use the Fully Qualified Domain Name, and not only the domain name you're using when you're signing in to a computer in the domain. Neither should you use the forest name which looks like tmpl-dev.local in your case. Your FQDN might be tmpl-dev.company.com which differs from the forest name and the <domain ...


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() { ...


0

You can try like this: var serviceContext = SPServiceContext.GetContext(site); var userProfileManager = new UserProfileManager(serviceContext); foreach (UserProfile userProfile in userProfileManager) { // ... } You will need elevated privileges to perform this operation


0

Their is no OOTB way to setup alerts on the timer job. You can use the 3rd party tools which is best way, to montior the sharepoint farm. We are using the SCOM from MSFT. Other way is write some piece of code which parse the Server Application log and report when an event related to failure occur. Or write a powershell script and schedule it as per your ...


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 ...


0

here is what MSFT stance on this: I should say that, REST service partly work in SharePoint Online. I’d tried to confirm this question in our internal resource, and got the information as the following: With the scenario we use REST service in InfoPath, it will works when we preview forms in the client, as soon as we publish it to SharePoint ...


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 ...


0

As i said before, even you exclude the account from dirsync but after that if you login with that account, sharepoint will create a profile for that account. Now on next sync it will exclude it from the sync but again you login with that account, a new profile will e their. You should be fine in term of your worries that if account removed then that account ...


0

Sometimes there are errors on profiles not visible in the GUI. You could try the following script and do a sync again then the script has finished. Get-SPServiceApplication #Copy the ID an replace <identity> in the following line $upa = Get-SPServiceApplication <identity> Set-SPProfileServiceApplication $upa -GetNonImportedObjects $true #When ...


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 ...



Top 50 recent answers are included