29 August 2013

Service Pack 2‏ (SP2) for Microsoft SharePoint 2010 and Office 2010

Last month came new version (Service Pack 2) for Office 2010, SharePoint 2010,  Project server 2010 and the Fast 2010.

Here are some links that will help you

Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition
http://www.microsoft.com/en-us/download/details.aspx?id=39667

Service Pack 2 for Microsoft Office 2010 (KB2687455) 64-Bit Edition
http://www.microsoft.com/en-us/download/details.aspx?id=39647

Note: In addition to the products in the Office 2010 suite, service pack 2687455 also updates Microsoft Project 2010, Microsoft Visio 2010, and Microsoft SharePoint Designer 2010

Service Pack 2‏ (SP2) for Microsoft SharePoint Server 2010 (KB2687453)
http://www.microsoft.com/he-il/download/details.aspx?id=39672

Service Pack 2‏ (SP2) for Microsoft SharePoint Foundation 2010 Language Pack (KB2687466)
http://www.microsoft.com/he-il/download/details.aspx?id=39674

Service Pack 2‏ (SP2) for Microsoft FAST Search Server 2010 for SharePoint (KB2687446)
http://www.microsoft.com/he-il/download/details.aspx?id=39670

Service Pack 2 for Microsoft Office Web Apps (KB2687470)
http://www.microsoft.com/en-us/download/details.aspx?id=39659

Service Pack 2 for Microsoft SharePoint and Project Server 2010 (KB2687452)
http://www.microsoft.com/en-us/download/details.aspx?id=39657

Service Pack 2 for Microsoft Search Server 2010 (KB2687461)
http://www.microsoft.com/he-il/download/details.aspx?id=39656

Yours,
Roi

23 August 2013

Which w3wp process belongs to which App Pool

Often you wonder which process belongs to which site (in my case usually SharePoint site)? Or maybe you just want to debug only your website on the development server .

For this we have the appcmd.

all you need is to run this command:

%windir%\system32\inetsrv\appcmd.exe list wp



Now you can see who is gobbling sites memory from is id (pid)



Yours,
Roi

04 August 2013

Speedup Powershell at SharePoint 2013

If you worked in stsadm in MOSS 2007 and even if it worked in SharePoint 2010, you saw it slow.
In 2010 we also added the powershell - who was sometimes slow.

It turns out that in sharepoint 2013 not made significant changes - is suggested

The solutions are
  1. Add crl.microsoft.com to your hosts file and point it to your local machine
    Go to Start -> Run
    Click "Drivers" (It need to open "C:\Windows\System32\drivers" - in not go to it)
    Go to folder "etc" and open "hosts" file with notepad
    and add this line
    127.0.0.1       crl.microsoft.com
    Disclosure: this solution find a lot on Google - but my no significant change
  2. Disable the CRL check by modifying the registry for all user accounts that use STSADM and all service accounts used by SharePoint.
    Go to Start -> regedit and fund this location

    [HKEY_USERS\<userid>\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing]

    Yon need to change all yours users to “State”=dword:00023e00 
    Click Modify and change it.


Yours.
Roi