Some SCSM links

Personal View  (not possible, only admin can pre-create views)

Send email when analyst comment is set (http://blogs.technet.com/b/servicemanager/archive/2013/05/13/how-to-configure-notifications-for-assignment-re-assignment-as-well-as-action-log-and-user-comment-updates-for-incidents-and-service-requests-in-scsm.aspx)

Process for Languages https://technet.microsoft.com/en-us/library/hh519587.aspx

Views vs  queues http://blog.acceleres.com/dude-where-are-my-queues-or-is-it-views/   

Number of fields shown in portal http://blogs.technet.com/b/servicemanager/archive/2011/11/08/request-offering-wizard-overview.aspx

Locales used by Microsoft https://msdn.microsoft.com/en-us/goglobal/bb964664.aspx

OPEN issue: Set Locale in AD then sync does not work in SCSM?

Create incident by email  https://technet.microsoft.com/en-us/library/hh519602  and http://scug.be/scsm/2010/01/07/configure-scsm-email-incident-support/

Update incidents by email http://www.systemcentercentral.com/forums-archive/topic/update-incidents-by-email/

SharePoint 2010 LVT

Nice and quick training video regarding Large Lists and issue of LVT limitation

https://support.office.microsoft.com/en-us/article/SharePoint-lists-V-Techniques-for-managing-large-lists-13456600-ff66-46ec-a2d2-91736d4a166e?section=2&CorrelationId=0f7b2a49-ba3d-4456-a043-3eb1f3048c89&ui=en-US&rs=en-US&ad=US

SharePoint 2013 Search issues

I find this article as very correct in the analysis of Search issues on SP13:

http://platinumdogs.me/2014/01/07/controlling-search-noderunner-memory-usage-in-sharepoint-2013/

Although it is tempting to reduce memory of node runner this will result in noderunner out of memory error.

Leave it at zero or adjust carefully as suggested above to 1 or 2 GB.

Somme errors that you might see:

Log Name:      Application
Source:        .NET Runtime
Date:          29.01.2015 11:43:59
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:    
Description:
Application: NodeRunner.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
   at System.Runtime.Fx+IOCompletionThunk.UnhandledExceptionFrame(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Log Name:      Application
Source:        Application Error
Date:          29.01.2015 11:43:59
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:    
Description:
Faulting application name: NodeRunner.exe, version: 15.0.4420.1017, time stamp: 0x506723c5
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xe0434352
Fault offset: 0x000000000000940d
Faulting process id: 0xe90
Faulting application start time: 0x01d03bb070ecf82a
Faulting application path: C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\NodeRunner.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: bae00371-a7a3-11e4-b181-00155dfe9e6f


UPDATE: the issue is back again. This article here talks about finding out which com ponent is using memory http://blogs.msdn.com/b/kristopherloranger/archive/2014/03/24/sharepoint-2013-noderunner-exe-process-information.aspx

Exchange Online Autottendant and Lync OnPrem

To integrate Exchange Online AA with Lync, we need to create a contact

https://technet.microsoft.com/en-us/library/gg412978.aspx

Then get Identity, you can run run Get-CsExUmContact

but then if you try to call AA but sip, or number you will get an error (in Snooper).

SIP/2.0 500 Server Internal Error
ms-user-logon-data: RemoteUser
...
CSeq: 1 INVITE
ms-diagnostics: 15014;reason="Hosted Voicemail Policy assigned to the user is not fully configured. Destination or Organization might be null";source="xxxx";appName="ExumRouting"
Server: ExumRouting/5.0.0.0

You will want to run another command to assign policy to this contact.

Grant-cshostedvoicemailpolicy –identity “paste-your-Identity as you see in get command above” –policyname O365

O365 is your policy as you defined in Exchange Online - refer to https://ahandyblog.wordpress.com/cloud-technologies/office-365-unified-messaging-with-lync-2013-on-premise/

SharePoint 2010 An update conflict has occurred, and you must re-try this action

In case of an error similair to this:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (7d825bde-c4d8-475c-b3f6-c52911242f33).

Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by ad\svcWSSAdmin, in the OWSTIMER (4472) process, on machine S2010.  View the tracing log for more information about the conflict.

Technical Support Details:
Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by AD\svcWSSAdmin, in the OWSTIMER (4472) process, on machine S2010.  View the tracing log for more information about the conflict.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)


Use cache cleanup procedure as described
http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance


quote:

Stop the Windows SharePoint Services Timer service (Found in Windows Services)

Navigate to the cache folder
In Windows Server 2008, the configuration cache is in the following location:
Drive:\ProgramData\Microsoft\SharePoint\Config
In Windows Server 2003, the configuration cache is in the following location:
Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
Locate the folder that has the file "Cache.ini"
(Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)

Back up the Cache.ini file.

Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.

Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.

Double-click the Cache.ini file.

On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.

Start the Windows SharePoint Services Timer service

Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.

Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

- See more at: http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance#sthash.PDz2zKwa.dpuf