SharePoint 2013 Known issues

If you are looking for known issues in SharePoint server 2013 then please appreciate Microsoft for publishing a wonderful article as mentioned below:

SharePoint 2013 Known issues:

http://office.microsoft.com/en-us/help/sharepoint-server-2013-known-issues-HA102919021.aspx

SharePoint 2013 for IT pros

http://technet.microsoft.com/en-us/sharepoint/fp142366.aspx

Install prerequisites for SharePoint 2013 from a network share

http://technet.microsoft.com/en-us/library/ff686793(v=office.15).aspx

Download Microsoft SharePoint Server 2013

http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx

Query variables in SharePoint Server 2013

http://technet.microsoft.com/en-us/library/jj683123(v=office.15).aspx

Microsoft MCSE certifications in 2013

Exam 70-331

Core Solutions of Microsoft SharePoint Server 2013

"The candidate is an IT professional who plans, implements, and maintains a multi-server deployment of SharePoint 2013. Has a working knowledge of and hands-on experience with SharePoint Online. Has broad familiarity with SharePoint workloads. Have experience with business continuity management, including data backup, restoration, and high availability. Has experience with authentication and security technologies. Has experience with Windows PowerShell."
Read more about Exam 70-331 at http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-331

Exam 70-332:
Advanced Solutions of Microsoft SharePoint Server 2013
"The candidate is an IT professional who plans, implements, and maintains a multi-server deployment of SharePoint 2013. Has a working knowledge of and hands-on experience with SharePoint Online. Has broad familiarity with SharePoint workloads. Have experience with business continuity management, including data backup, restoration, and high availability. Has experience with authentication and security technologies. Has experience with Windows PowerShell."
Read more about Exam 70-332 at http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-332

MSCE: SharePoint – Microsoft Certified Solutions Engineer SharePoint
"To earn your MCSE SharePoint certification, start with the MCSA: Windows Server 2012 certification, then pass Exams 331 and 332."

MCSE: SharePoint (SharePoint Server 2013)

Exam 70-331: Core Solutions of Microsoft SharePoint Server 2013(Release February 05, 2013)
http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-331

Exam 70-332: Advanced Solutions of Microsoft SharePoint Server 2013(Release February 05, 2013)
http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-332

This Website does not support workflows created by SharePoint Designer.

Issue: This Website does not support workflows created by SharePoint Designer.

One of my clients today came up with unique issue that he is not able to create any workflow in the designer. 

Troubleshooting: 

1.      Based on the error message, I have checked the permissions of the clients; he has Full control permissions on the site.  

2.      The website was allowed to use the Designer

3.      Check the permissions on the library where he was trying to create workflow. Correct permissions were in place for the workflow history library as well.

4.      Both of these libraries inheriting permissions from the site. No question of permissions issue on the site level.

5.      Tried to disable contributor access in the designer.

6.      Tried to change the proxy via designer. 

7.      Workaround to the problem was adding him as a site collection admin. However, this was not a permanent solution to the problem.

Little hard goggling help to resolve the issue. 

Resolution:

Exit and then start Office SharePoint Designer 2007.

The site owner should verify that the affected user has been added to the list of users who have permissions to the Workflows library. If not, add the user to the list: 

1.      In Office SharePoint Designer 2007, in the Folder List, right-click the Workflows library, and then click Properties.

2.      Click the Security tab.

3.      Click Manage permissions using the browser.

4.      In the browser, on the Permissions: Workflows page, click New, and then click Add Users.

5.      Add the user to the list.

If you have any queries/questions regarding the above mentioned information then please let me know. 

I would be more than happy to help you as well as resolves your issues, Thank you.

List Attachments over 50MB need more than an increase in Maximum Upload Size

Issue: Unable to attach a file more than 50 MB in SharePoint List. 

Troubleshooting Steps:

Checked the default size of uploading file in CA.  It was set to 100 MB. 

Tried to upload the file of the size 60 MB, successfully uploaded. However has issue attaching the file which is more than 50 MB only with SharePoint Lists. 

We all know we have a best friend of all the times GOOGLE. Thanks to Google team to create it. It saves me most of the time. 

Resolution:

I found the below article which says that every site is also binded with a run time upload size of 51200 MB. Anything attached more than this give you error message and below article save you from the this bug. 

Well explained reference.

http://blogs.msdn.combbgeoffroarchive20080319list-attachments-over-50mb-need-more-than-an-increase-in-maximum-upload-size.aspx

If you have any queries/questions regarding the above mentioned information then please let me know. 

I would be more than happy to help you as well as resolves your issues, Thank you.

Users are not deleted from SharePoint site after leaving the company

Our company's security policy is to immediately delete user accounts in AD after when an employee leaves the company. The user account still shows valid in SharePoint people picker/ all people group etc. 

Normally on full import of AD users all users are import into SharePoint from AD, then if new user requests to log into SharePoint it checks against AD and adds user, but SharePoint doe not remove users if removed from AD, so Site Admins sometimes wanting to find a script to iterate thru the current users listed in SharePoint and test against AD, if user does not exist in AD then remove from SPUsers?

Answer to the above concern would be that after the profiles have been imported. If a user  is deleted in AD then after 3 successive full profile imports there profile will be deleted also. If
deactivated their MySite will be cleaned up, but not their profile.

You also need to understand about the difference between SharePoint users used for security and Profiles. They are related, but not the same thing.

First, Profiles.

1. Moss is setup to import all the users in your AD domain as profiles into the SSP that you create. However, this action is not scheduled. Profiles will not be imported until you either do a manual import or setup the schedule for Full and incremental imports. This imparts no security rights to the user
at all.

2. After the profiles have been imported. If a user is deleted in AD then after 3 successive full profile imports there profile will be deleted also. If deactivated their MySite will be cleaned up, but not their profile.

Second, Authentication/Authorization (Assuming you are not using any kind of Forms Based Authentication)

1. SharePoint depends on Windows Authentication via IIS to establish the user's identity. (this happens completely external to SharePoint)

2. SharePoint checks the user's AD identity and group membership, as established in #1, to see what the user has the ability to do in SharePoint.

You can successfully authenticate and still not gain access to SharePoint.

3. Security Access in SharePoint is dependent on the AD identity or an AD group of which the user is a member being added as a SharePoint user. Or the user or group may be added directly to a SharePoint group. This will allow the user to gain access to SharePoint resources.

4. If the access is through group membership then the user's identity will only be added to SharePoint when the user logs in and submits something to a document library or list. This adds their identity as a user, but doesn't directly re-associate them with specific rights. The rights are still gained through group membership. But they would now show up in the People and Groups
list.

5. If the user's account is deactivated or deleted in AD their account in SharePoint is NOT deleted, but they won't be able to use it to access SharePoint  anymore because AD won't be able to authenticate them so they'll never get to Authorization. If deactivated, you will still be able to click on their name attached to documents or list items and see their profile. If deleted clicking on these items will normally lead to an error page because the profile isn't there anymore.

6. Removing SharePoint users can be done programmatic, but it is a fairly involved process requiring walking each object in the FARM and looking for the user entries. There are 3rd party products that do this, but I don't normally recommend using them since you are destroying the history of the user in the system.

My normal recommendation is to deactivate users in AD, but let them stay in SharePoint. Once deactivated they won't be able to login, but history of their usage of the system will remain intact.

The users deleted from AD certainly still exist in the SharePoint SSP user profiles. Suggested is to run a full import of user profiles. The first full import (after the users are deleted) will make them inactive. After the 3rd full import they will disappear completely.

To run a full import of users profiles go to Central Admin > Click your Shared Service Provider under Shared services administration > User profiles and properties, under user profiles and mysite section > Start full import. You must grant yourself the right to manage user profiles: Under user profiles and mysite section, click Personalization services permissions > Select manage user profiles.

If you have any queries/questions regarding the above mentioned information then please let me know. 

I would be more than happy to help you as well as resolves your issues, Thank you.