Tag Info

New answers tagged

0

Had the same issue and logged a call with MS. They said there is no documentation on the setup and configuration for this. In the end we Recreated our Farm so that it was in the same domain. Some helpful links that might help you: Configure People Picker in SharePoint 2013 SharePoint 2013: “Sorry, we’re having trouble reaching the server. “


1

Its advisable to create a custom Page Layout based on your requirement. Then create a Welcome Page out of that. Once completed, you can create a PowerShell Script which goes and create this Page for existing My Sites. And also change the Welcome Page to the newly created page.


0

A few ways you can approach this (in addition to what @AmalHashim has given you above): You can re-run the configuration wizard on the affected machine, or just run the PowerShell command from SharePoint shell Initialize-SPResourceSecurity this will go thru and re-set local permission that SharePoint needs. If you want to find the specific registry key, ...


0

SharePoint gives a Correlation Id in the Error Page. Something like below To find the real issue, you can copy the Correlation ID and find in the Logs files. From the error message I believe its a permission issue with one of the Registry Key. To find which key your only option is to get more details of the error from the log files.


1

If the current user is part of the FARM ADMINISTRATORS group then the below code currentUser.get_loginName() will return Sharepoint\System. This is the expected behavior and you don't need to worry much. Try using a normal user account and you can see it returns the expected result. Alternatively you can also use currentUser.get_title()


0

Problem for my case was profile.ps1 for PowerShell. Answer is to comment all code (Admin rights, Add-PSSnapin etc.) in profile.ps1. Open Windows PowerShell ISE like always (Run as Admin) Run this if (!(test-path $profile.AllUsersAllHosts)) {new-item -type file -path $profile.AllUsersAllHosts –force} powershell_ise $profile.AllUsersAllHosts if profile.ps1 ...


0

The best practice is to Create a Visual Studio Solution. Then add your page layouts and other styling files. Create a feature receiver Use that to set the Page or create new page using the custom layout etc. For existing site, you can deploy the solution and then use PowerShell to activate it on all the sites.


3

No, you should be using the single sync connection for the entire forest. If you have a secondary forest (or more) create a sync connection per forest.


0

Maximum supported limit is 750,000 MySites (site collections) per web application. I don't think there is a limit. There is nothing on TechNet that says otherwise, but I'm sure the number you have is much less than SharePoint can handle. If users are planning on using their MySites for content, I would recommend creating multiple MySite content databases, ...


3

in this case msdn is you best friend. As i created it for the company that i work for i could answer this for you ;) mysite limmit for webapplication first you need to understand what is a mysite? a mysite is a site collection. The mysite when setup if done according to best practice should be hosted on its own web application. This web application ...


0

There is a User Profile Change log that is maintained for 14 days by default. You can query it and determine what changed and even if your property of interest changed. In PowerShell you could get a service context and then do something like: $manager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager $context Then use one of the ...


0

As per my knowledge there is no event associated with User Profiles. Hence there is no way we can define an event receiver. As you suggested you need a timer service and then loop through the profile change log. Then take a decision based on that.


0

From the TechNet article: This message can be ignored. The User Profile Synchronization Service must run as the farm account. The detailed information: http://technet.microsoft.com/en-us/library/gg750254(v=office.14).aspx#alert



Top 50 recent answers are included