lunedì 31 marzo 2014

SharePoint 2010 - Configurare e abilitare Windows WorkSpace

fonte di questo articolo Jeff Widmer's Blog


Configuring SharePoint Foundation 2010 for SharePoint Workspace 2010

SharePoint Workspace 2010 is the new version of Groove that will give you an offline copy of a SharePoint website and also allow you to work with a SharePoint site outside of a browser.  SharePoint Workspace 2010 is especially nice for editing documents in a SharePoint Document library.  SharePoint Workspace makes the SharePoint Document Library work just like a folder on your computer and will handle the synchronization of the documents back to the SharePoint server for you.
If you try connecting SharePoint Workspace 2010 to a default SharePoint Foundation 2010 installation you may get an error like this one:
--------------------------- 
Sync to SharePoint Workspace 
--------------------------- 
SharePoint Workspace was unable to interpret the SharePoint location. Please check and ensure the location contains no typing errors. 
--------------------------- 
OK Help 
---------------------------
This is because the default configuration of SharePoint Foundation 2010 requires two configuration changes to allow SharePoint Workspace 2010 to work.
The first is to enable the Remote Differential Compression feature on the server that is hosting SharePoint.  This is used by SharePoint Workspace 2010 to send and receive the files for synchronization.
To enable Remote Differential Compression go to the Server Manager > Features and choose Add Features.
image
Check the box for the Remote Differential Compression feature and then click Install to enable this feature.
image

The second configuration change to allow SharePoint Workspace 2010 to work with your SharePoint Foundation 2010 server is to add an Alternate Access Mapping of the public facing DNS name (or IP address) to SharePoint using the SharePoint Central Admin.  If you are connecting to your SharePoint site using the machine name then this is not necessary, but if you are connecting over the Internet through either an IP address or DNS name then you will need to add this alternate access mapping.
The reason is that when SharePoint is first installed, the only way it thinks users are connecting to the server is through the machine name: http://machine_name (as if on a local intranet).  Since most likely SharePoint Workspace 2010 users will be connecting through a public facing DNS name (or IP address), you will need to add this DNS name (or IP address) as an alternate access mapping (indicating that this DNS name is the same as the machine_name and should map to the SharePoint site).
To add an Alternate Access Mapping to SharePoint Foundation 2010, visit the SharePoint Central Administration on the SharePoint Foundation 2010 server:
image
Once in the SharePoint Central Administration website, click on the Application Management link
image
Then under the Web Applications heading choose Configure alternate access mappings
image
Choose Edit Public URLs
image
And then select the public facing SharePoint website that you want to add an access mapping to.  You do this by changing the Alternate Access Mapping Collection (clicking on the “No selection” drop down button) to the website that is running on Port 80.
image 
The  default name of the public facing SharePoint site is “SharePoint – 80” but you may have changed that when you configured your SharePoint site.
image
Once you have switched the Alternate Access Mapping Collection to the public SharePoint website (SharePoint – 80) then you can specify the Public URL by adding the publically accessible IP Address or DNS name to the Internet field:
image
image
Click Save to apply the alternate access mapping and now you should be able to connect to your SharePoint Foundation 2010 site with SharePoint Workspace 2010:
image
clip_image001

SharePoint Foundation 2010 is the free version of SharePoint that installs on top of Windows Server 2008.  With SharePoint Workspace 2010 you can get an offline copy of your SharePoint team site allowing you to add/edit your documents in any SharePoint document library easily and allow SharePoint Workspace 2010 to handle the file synchronization for you. 
You can take a look at SharePoint Foundation 2010 quickly and easily by starting apreconfigured SharePoint Foundation 2010 Virtual Machine at Vaasnet.com.  Vaasnet.com is a new Internet startup that provides preconfigured virtual machines (such as a virtual machine with SharePoint Foundation 2010 already installed) that are ready for you to start and begin using right away.  Vaasnet.com takes the hassle out of downloading and installing the Windows Server 2008 operating system and SharePoint Foundation 2010 so that you can quickly log in and begin trying out the new features of SharePoint Foundation 2010.

venerdì 28 marzo 2014

SharePoint 2010 - Personalizzare SPAlerts

fonte di questo articolo Bernd's blog

Custom SPAlerts

You can modify the SharePoint standard alerts by modifying an existing alert definition in the alerttemplates.xml. The following steps are useful:
  1. Create your copy template file in  \templates\xml.
  2. Register the new alerttemplates file using STSADM.
  3. Customize the alert template.
  4. Add the SPAlert objects in your application.
Step 1. Create your copy template file in  \templates\xml. It is a good idea to leave the alerttemplates.xml untouched. To implement your own template simply take a copy of the file and remove all but one alert template. Remember to rename the alert template.
Step 2. Register the new alerttemplates file using STSADM.
Before you can use the new template you need to register the newly created template file with the following command:
STSADM -o updatealerttemplates -url [SITECOLLECTIONURL] -filename "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML\alerttemplates_custom.xml"

Step 3. Customize the alert template. Refer to the following articles for an overview of the alert template.
These articles are not very specific. Therefore I will dive into the details here.
Basically there are three alert types in SharePoint: Immediate, Daily and Weekly. The alert template has only two elements: Immediate and Digest. Use the Digest section for both daily and weekly alert. You can use the following to implement daily or weekly functionality:

     
         
   
      
        <!– Daily –>
   
      
        <!– Weekly –>
   

     
         
   
      
        <!– Daily –>
   
      
        <!– Weekly –>
   

   
   

In general, the fields or rowFields section are the core of the template. All content type fields that you did not explicitly exclude (ImmediateNotificationExcludedFields or DigestNotificationExcludedFields) will have the mark-up specified here applied. Think of it as a foreach loop that iterates over all content type fields. If you want to make the rendering dependent on the field name you can use the following xml:
            <!– Title –> 
             
                 
                     
               
                  
                    <![CDATA[Title]]> 
               
                  
                    <!– Do something useful here. –> 
               
            
               
           
The above example renders only for the ‘Title’ field. I use this method to render a link to the created page for the title and normal text for the other fields.
Step 4. Add the SPAlert objects in your application. To add an alert programmically you can use the following code:
guid = channelWeb.Alerts.Add(list, SPEventType.Modify | SPEventType.Add, SPAlertFrequency.Immediate);
SPAlertTemplate alertTemplate = new SPAlertTemplate();
alertTemplate.Name = SP_ALERT_TEMPLATE_NAME;
channelWeb.Alerts[guid].AlertTemplate = alertTemplate;
channelWeb.Alerts[guid].Title = "Title";
channelWeb.Alerts[guid].EventTypeBitmask = 3;
channelWeb.Alerts[guid].Filter = "… some CAML query …";
channelWeb.Alerts[guid].Update();
I figured that it is quite important to do exatly as the example shows. You do not have to update the SPWeb or SPList object. Set both the EventType and EventTypeBitmask. If you are not sure of the correct value for the EventTypeBitmask create some standard SharePoint alerts and check the values with SharePoint Manager.
If you want to read back the alerts that were created use the SPWeb.Alerts property. You will have to run your code with ElevatedPriviliges to avoid an UnauthorizedException when the AlertCollection has alerts from ohter users as well. Use the SPAlert.User.Id to filter the alerts for the current user.
If you want to delete alerts from SPWeb.Alerts collection you also need to use ElevetatedPriviliges and set SPWeb.AllowUnsafeUpdates to true.
Setting the SPAlert.Filter property to a valid CAML query that was produced with U2U CAML Builder resulted consequently in this error:
SPAlert.Query = "";
Message:
Exception: Microsoft.SharePoint.SPException: Cannot complete this action.
Please try again. —> System.Runtime.InteropServices.COMException (0×80004005): Cannot complete this action.
This means in SharePoint language that you must not use the element in filter CAML queries. The following query works as expected:
SPAlert.Query = "";
It is important to set the SPAlert.EventTypeBitmask according to the SPAlert.EventType.

http://rickenberg.dk/blog/?p=44

giovedì 27 marzo 2014

SharePoint - Segnalazione operazione lunga

Nel caso avete un'operazione custom che impiega qualche istante ad essere eseguita e si vuole fare in modo che l'utente capisca che il sistema ha preso in carico la vostra richiesta (es. click su un bottone), utilizzate questo codice per segnalare all'utente l'operazione che sta eseguendo il sistema e che ci vorrà qualche istante...

using (SPLongOperation provision = new SPLongOperation(this.Page))
{
    provision.LeadingHTML = "Operation description";
    provision.TrailingHTML = "Please wait...";
    provision.Begin();
    ...YOUR..CODE....
}
 

mercoledì 26 marzo 2014

lunedì 17 marzo 2014

Windows - Installazione certificato in "Autorità di certificazione radice attentibili" / "Trusted root certification authorities"

Se per caso cercate di installare un certificato all'interno dell'archivio "Autorità di certificazione radice attentibili" (Trusted root certification authorities) e ricevete questo messaggio di errore:

ITA: Importazione non riuscita per uno dei seguenti motivi: l'archivio era di sola lettura o pieno oppure si è verificato un errore in apertura dell'archivio

ENG: The import failed because the store was read-only, the store was full, or the store did not open correctly.

Provate ad importare il certificato in questo altro modo:


  1. Scaricare e salvare il certificato
  2. Aprire il Gestore dei certificati
  3. Aprire dal menu start "Esegui comando" (WindowsButton+R) e scrivete "certmgr.msc" (senza apostrofi).
  4. Avete aperto il gestore dei certificati
  5. Fate tasto destro su "Trusted Publishers" presente nella lista dei folder a sinistra, e selezionare la voce "All Tasks" >> "Import"
  6. Premsere sul bottone "Next" 
  7. Premere sul bottone "Browse" 
  8. Selezionare il certificato che avete scaricato precedentemente, e premete su "Open"
  9. Premere "Next"
  10. Selezionare "Place all certificates in the following store"
  11. Premere su "Browse" 
  12. Selezionare il check "Show physical stores"
  13. Espandere il folder "Trusted Publishers" 
  14. Selezionare "Local Computer"
  15. Selezionare il bottone "OK" 
  16. Selezionare il bottone "Next" 
  17. Selezionare il bottone "Finish" 
  18. Riceverete il messaggio "The import was successful".

giovedì 27 febbraio 2014

Microsoft SQL Server Management Studio - "Saving changes is not permitted"

Se dopo aver modificato qualcosa sullo schema di una tabella, ricevi questo messaggio 

"Saving changes is not permitted. The changes you have made reguire the following tables to be dropped and re-created. You have either made changes to a table that can't be re-created or enabled the options Prevent saving changes that require the table to be re-created."


Modificare questo settaggio nel proprio Microsoft SQL Server Management Studio:

  1. aprire Tools presente nella barra dei menu in alto
  2. cliccare su Options
  3. espandere Designers e cliccare su Table and Database Designers
  4. togliere il flag dalla voce Prevent saving changes that require the table to be re-created 
  5. premere OK per salvare il cambiamento
  6. riprovate a salvare la modifica sulla tabella



martedì 25 febbraio 2014

MSSQL - Script Versione SQL Server

Come vedere la versione di SQL Server che state utilizzando?
Basta eseguire questo script sul server in questione e cercate il product version nella tabella sottostante

SELECT
SERVERPROPERTY('productversion') as productversion
,SERVERPROPERTY ('productlevel') as productlevel
,SERVERPROPERTY ('edition') as edition

Numeri di build e Service Pack comuni di SQL Server

Nota Queste tabelle utilizzano il seguente formato e sono ordinate per numero della build.
Numero di build o versioneDescrizione della versione (numero KB per l'aggiornamento), data di rilascio

SQL Server 2012

Build number or versionVersion description, (KB numberfor that update), release date
11.0.3393.00SP1 CU #7 (2894115) November 18, 2013
11.0.3381.00SP1 CU #6 (2874879) September 16, 2013
11.0.3373.00SP1 CU #5 (2861107) July 15, 2013
11.0.3368.00SP1 CU #4 (2833645) May 30, 2013
11.0.3349.00SP1 CU #3 (2812412) March 18, 2013
11.0.3339.00SP1 CU #2 (2790947) January 21, 2013
11.0.3321.00SP1 CU #1 (2765331) November 20, 2012
11.0.3000.00SP1 RTW/PCU 1(2674319), November 07, 2012
11.0.2420.00RTM CU #10 (2891666) October 21, 2013
11.0.2419.00RTM CU #9 (2867319) August 20, 2013
11.0.2410.00RTM CU #8 (2844205) June 17, 2013
11.0.2405.00RTM CU #7 (2823247) April 15, 2013
11.0.2401.00RTM CU #6 (2728897) February 18, 2013
11.0.2395.00RTM CU #5 (2777772) Dec 17, 2012
11.0.2383.00RTM CU #4 (2758687) October 15, 2012
11.0.2332.00RTM CU #3 (2723749) August 31, 2012
11.0.2325.00RTM CU #2 (2703275) June 18, 2012
11.0.2316.00RTM CU #1 (2679368) April 12, 2012
11.0.2100.60RTM – March 6, 2012

SQL Server 2008 R2

Build number or versionVersion description, (KB numberfor that update), release date
10.50.4295.00SP2 CU #9 (2887606) October 28, 2013
10.50.4290.00SP2 CU #8 (2871401) August 22, 2013
10.50.4285.00SP2 CU #7 (2844090) June 17, 2013
10.50.4279.00SP2 CU #6 (2830140) April 15, 2013
10.50.4276.00SP2 CU #5 (2797460) February 18, 2013
10.50.4270.00SP2 CU #4 (2777358) Dec 17, 2012
10.50.4266.00SP2 CU #3 (2754552) October 15, 2012
10.50.4263.00SP2 CU #2 (2740411) August 31, 2012
10.50.4260.00SP2 CU #1 (2720425) July 24, 2012
10.50.4000.0SP2 RTW/PCU 2(2630458), July 26, 2012
10.50.2881.00SP1 CU #14 (2868244) August 8, 2013
10.50.2876.00SP1 CU #13 (2855792) June 17, 2013
10.50.2874.00SP1 CU #12 (2828727) April 15, 2013
10.50.2869.00SP1 CU #11 (2812683) February 18, 2013
10.50.2868.00SP1 CU #10 (2783135) Dec 17, 2012
10.50.2866.00SP1 CU #9 (2756574) October 15, 2012
10.50.2822.00SP1 CU #8 (2723743) August 31, 2012
10.50.2817.00SP1 CU #7 (2703282) June 18, 2012
10.50.2811.00SP1 CU #6 (2679367) Apr 16, 2012
10.50.2806.00SP1 CU #5 (2659694) Feb 22, 2012
10.50.2796.00SP1 CU #4 (2633146) Dec 19, 2011
10.50.2789.00SP1 CU #3 (2591748) Oct 17, 2011
10.50.2772.00SP1 CU #2 (2567714) Aug 15, 2011
10.50.2769.00SP1 CU #1 (2544793) Jul 18, 2011
10.50.2500.0SP1 RTW/PCU 1(2528583), July 12, 2011
10.50.1815.00RTM CU #13 (2679366) Apr 16, 2012
10.50.1810.00RTM CU #12 (2659692) Feb 21, 2012
10.50.1809.00RTM CU #11 (2633145) Dec 19, 2011
10.50.1807.00RTM CU #10 (2591746) Oct 17, 2011
10.50.1804.00RTM CU #9 (2567713) Aug 15, 2011
10.50.1797.00RTM CU #8 (2534352) June 20, 2011
10.50.1777.00RTM CU #7 (2507770) Apr 18, 2011
10.50.1765.00RTM CU #6 (2489376) Feb 21, 2011
10.50.1753.00RTM CU #5 (2438347) Dec 20, 2010
10.50.1746.00RTM CU #4 (2345451) Oct 18, 2010
10.50.1734.00RTM CU #3 (2261464) Aug 16, 2010
10.50.1720.00RTM CU #2 (2072493) Jun 21, 2010
10.50.1702.00RTM CU #1 (981355) May 18, 2010
10.50.1617.00GDR Security Update (2494088), June 21, 2011
10.50.1600.1RTM – May 10, 2010

SQL Server 2008

Build number or versionVersion description, (KB numberfor that update), release date
10.00.5848.00SP3 CU #14 (2893410) November 18, 2013
10.00.5846.00SP3 CU #13 (2880350) September 16, 2013
10.00.5844.00SP3 CU #12 (2863205) July 15, 2013
10.00.5840.00SP3 CU #11 (2834048) May 20, 2013
10.00.5835.00SP3 CU #10 (2814783) March 18, 2013
10.00.5829.00SP3 CU #9 (2799883) January 21, 2013
10.00.5828.00SP3 CU #8 (2771833) November 19, 2012
10.00.5794.00SP3 CU #7 (2738350) September 17, 2012
10.00.5788.00SP3 CU #6 (2715953) July 16, 2012
10.00.5785.00SP3 CU #5 (2696626) May 21, 2012
10.00.5775.00SP3 CU #4 (2673383) Mar 19, 2012
10.00.5770.00SP3 CU #3 (2648098) Jan 16, 2012
10.00.5768.00SP3 CU #2 (2633143) Nov 21, 2011
10.00.5766.00SP3 CU #1 (2617146) Oct 17, 2011
10.00.5500.00SP3 RTW / PCU 3 (2546951) Oct 6, 2011
10.00.4333.00SP2 CU #11 (2715951) July 16, 2012
10.00.4332.00SP2 CU #10 (2696625) May 21, 2012
10.00.4330.00SP2 CU #9 (2673382) Mar 19, 2012
10.00.4326.00SP2 CU #8 (2648096) Jan 16, 2012
10.00.4323.00SP2 CU #7 (2617148) Nov 21, 2011
10.00.4321.00SP2 CU #6 (2582285) Sep 19, 2011
10.00.4316.00SP2 CU #5 (2555408) Jul 18, 2011
10.00.4285.00SP2 CU #4 (2527180) May 16, 2011
10.00.4279.00SP2 CU #3 (2498535) Mar 17, 2011
10.00.4272.00SP2 CU #2 (2467239) Jan 17, 2011
10.00.4266.00SP2 CU #1 ( 2289254) Nov 15, 2010
10.00.4064.00GDR Security Update (2494089), June 14, 2011
10.00.4000.00SP2 RTW / PCU 2 (2285068) Sep 29, 2010
10.00.2850.0SP1 CU #16 (2582282) Sep 19, 2011
10.00.2847.0SP1 CU #15 (2555406) Jul 18, 2011
10.00.2821.00SP1 CU #14 (2527187) May 16, 2011
10.00.2816.00SP1 CU #13 (2497673) Mar 17, 2011
10.00.2808.00SP1 CU #12 (2467236) Jan 17, 2011
10.00.2804.00SP1 CU #11 (2413738) Nov 15, 2010
10.00.2799.00SP1 CU #10 (2279604) Sep 20, 2010
10.00.2789.00SP1 CU #9 (2083921) July 19, 2010
10.00.2775.00SP1 CU #8 (981702) May 17, 2010
10.00.2766.00SP1 CU #7 (979065) Mar 26, 2010
10.00.2757.00SP1 CU #6 (977443) Jan 18, 2010
10.00.2746.00SP1 CU #5 (975977) Nov 16, 2009
10.00.2734.00SP1 CU #4 (973602) Sep 21, 2009
10.00.2723.00SP1 CU #3 (971491) Jul 20, 2009
10.00.2714.00SP1 CU #2 (970315) May 18, 2009
10.00.2710.00SP1 CU #1 (969099) Apr 16, 2009
10.00.2573.00GDR Security update (2494096), June 14, 2011
10.00.2531.00SP1 RTW / PCU 1 April, 2009
10.00.1835.00RTM CU #10 (979064) Mar 15, 2010
10.00.1828.00RTM CU #9 (977444) Jan 18, 2010
10.00.1823.00RTM CU #8 (975976) Nov 16, 2009
10.00.1818.00RTM CU #7 (973601) Sep 21, 2009
10.00.1812.00RTM CU #6 (971490) Jul 20, 2009
10.00.1806.00RTM CU #5 (969531) May 18, 2009 SP1
10.00.1798.00RTM CU #4 (963036) Mar 16, 2009
10.00.1787.00RTM CU #3 (960484) Jan 19, 2009
10.00.1779.00RTM CU #2 (958186) Nov 19, 2008
10.00.1763.00RTM CU #1 (956717) Sept 22, 2008
10.00.1600.22RTM – Aug 6, 2008

SQL Server 2005

Build number or versionVersion description, (KB numberfor that update), release date
9.00.5266SP4 CU #3 (2507769) Mar 22, 2011
9.00.5259SP4 CU #2 (2489409) Feb 21, 2010
9.00.5254SP4 CU #1 (2464079) Dec 23, 2010
9.00.5000SP4 RTW (PCU4) Dec 16, 2010
9.00.4325SP3 CU #15 (2507766) Mar 22 , 2011
9.00.4317SP3 CU #14 (2489375) Feb 21, 2011
9.00.4315SP3 CU #13 (2438344) Dec 20, 2010
9.00.4311SP3 CU #12 (2345449) Oct 18, 2010SP3
9.00.4309SP3 CU #11 (2258854) Aug 16, 2010
9.00.4305SP3 CU #10 (983329) Jun 21, 2010
9.00.4294SP3 CU #9 (980176) Apr 19, 2010
9.00.4285SP3 CU #8 (978915) Feb 16, 2010
9.00.4273SP3 CU #7 (976951) Dec 21, 2009
9.00.4266SP3 CU #6 (974648) Oct 19, 2009
9.00.4230SP3 CU #5 (972511) Aug 17, 2009
9.00.4226SP3 CU #4 (970279) June 15, 2009
9.00.4220SP3 CU #3 (967909) Apr 20, 2009
9.00.4211SP3 CU #2 (961930) Feb 16, 2009
9.00.4207SP3 CU #1 (959195) Dec 19, 2008
9.00.4053Security update (970892) Oct 12, 2009
9.00.4035SP3 RTW (955706) Dec 15, 2008
9.00.3356SP2 CU #17 (976952) Dec 21, 2009
9.00.3355SP2 CU #16 (974647) Oct 19, 2009
9.00.3330SP2 CU #15 (972510) Aug 17, 2009
9.00.3328SP2 CU #14 (970278) June 15, 2009
9.00.3325SP2 CU #13 (967908) Apr 20, 2009
9.00.3315SP2 CU #12 (960485) Feb 16, 2009
9.00.3301SP2 CU #11 (958735) Dec 15, 2008
9.00.3294SP2 CU #10 (956854) Oct 21, 2008
9.00.3282SP2 CU #9 (953752) Aug 18, 2008
9.00.3257SP2 CU #8 (951217) Jun 16, 2008
9.00.3239SP2 CU #7 (949095) Apr 14, 2008
9.00.3228SP2 CU #6 (946608) Feb 18, 2008
9.00.3215SP2 CU #5 (943656) Dec 17, 2007
9.00.3200SP2 CU #4 (941450) Oct 15, 2007
9.00.3186SP2 CU #3 (939537) Aug 20, 2007
9.00.3175SP2 CU #2 (936305) June 18, 2007
9.00.3161SP2 CU #1 (935356) April 16, 2007
9.00.3152SP2 Rollup (933097) May 15, 2007
9.00.3068Security update (948109) Jul 8, 2008
9.00.3042SP2 (937137)
9.00.2047SP1
9.00.1399RTM

SQL Server 2000

Build number or versionVersion description, (KB numberfor that update), release date
8.00.2283Post-SP4 hotfix for MS09-004 (971524)
8.00.2282MS09-004: KB959420 October 29,2008
8.00.2273MS08-040 - KB 948111 July 8, 2008
8.00.2040Post-SP4 AWE fix (899761)
8.00.2039SQL Server 2000 SP4
8.00.1007Update.exe Hotfix Installer Baseline 2 (891640)
8.00.977Update.exe Hotfix Installer Baseline 1 (884856)
8.00.818(821277)
8.00.765Post SP3 hotfix rollup
8.00.760SQL Server 2000 SP3 or SP3a (8.00.766 ssnetlib.dll)
8.00.701Hotfix Installer v.1 released
8.00.534SQL Server 2000 SP2
8.00.384SQL Server 2000 SP1
8.00.194SQL Server 2000 RTM or MSDE 2.0

Vedi [qui] la fonte della tabella