SharePoint Saturday was organized on Saturday, June 22 2013 at Sofia, Bulgaria. It is an educational, informative & lively day filled with sessions from respected SharePoint professionals & MVPs, covering a wide variety of SharePoint-orientated topics. Over 200 SharePoint architects, developers, and other professionals that work with Microsoft SharePoint technologies joined the conference.
Virtual Affairs was sponsor of the event and colleague Natalia Pavlova, Team lead Bulgaria, gave two presentations:
1) SharePoint report server ‘Develop a SharePoint Dashboard with Report Server’
2) SharePoint 2010 PowerShell ‘Make the hosting company life easier with SharePoint PowerShell’
6. Automate deployments
Solve
Error prone manual deployments
Unclear requirements
Prevent Risks of
Time consuming deployments
High risk changes to production
Human error
Messy production systems
Complicated roll-backs.
7. Deployment Good Practices
Standardise where you can
Make it simple
Make it reusable
Make it Self Aware
Automating Infrastructure Deployment
Treat configuration files as code
Test your deployments – involve QA team
8. What to deliver to Hosting Company ?
SharePoint packages
solution packages
Documentation
Manual
Release Notes
Scripts for automated deployment
SharePoint PowerShell Scripts
Scripts for integration with 3rd parties
9. SharePoint Solution Packages
What is a solution package?
What to be in?
Features
Site definitions, Master Pages
Application Pages, Custom Pages, layout pages
Templates, Images
Web Parts, User Controls
Cascading style sheets ,JavaScript, JQuery
Event Receivers, Workflow Activities, Workflow Assemblies
Global Resources (.resx files) , XML,XLST and etc.
Policies and assemblies.
10. Documentation
Release Notes
Released Items
Open items
Deployments by environment
Installation Manuals
PowerShell's Scripts settings
17. SharePoint PowerShell - Site Management
Get Site Template
Get site template globally installed
$template =Get-SPWebTemplate "SharePointTemplate"
Get site template available on the current web
$template =(Get-SPWebTemplate | Where { $_.Title –eq
$template } | Where { $_.LocaleId –eq "$lang"}).Name
$template =$web.GetAvailableTemplates(1033) | Where-
Object {$_.Name -eq "My Custom Template Name"}
$site= Get-SPSite "siteURL"
$site.GetWebTemplates(lcid)
18. SharePoint PowerShell - Site Management
Create Site
New-SPSite "siteURL" –OwnerAlias "domaincompName" –Template
$template
web = New-SPWeb” siteURL”|
$web.ApplyWebTemplate("{FeatureGUID}#MyTemplate")
$site.GetWebTemplates(1033)| Format-Table -Property * -AutoSize
Delete Site
Remove-SPSite -Identity $url
24. SQLSaturday #199 in October!
Saturday, October 26, 2013
For the second time in Bulgaria!
Free 1-day training event by/for SQL Server & BI
professionals
More info and registration at:
http://www.sqlsaturday.com/199/
25. Thanks to our Sponsors:
Diamond Sponsor:
Platinum Sponsors:
Gold Sponsor:
Swag Sponsors:
Media Partners:
Silver Sponsor:
Notas do Editor
Deployment only via ScriptsAutomating Infrastructure DeploymentIntegration with 3rd partiesContinuous Delivery and Development
Windows PowerShell commands, called cmdlets, let you manage the computers in your enterprise from the command line. The real benefit of using Windows PowerShell cmdlets is the ability to use a script to automate a series of tasks. The default policy for Windows PowerShell is Restricted , to change the policy use Set-ExecutionPolicy . The minimum required execution policy for SharePoint 2010 Products is RemoteSigned.A script is a plain text file that contains one or more Windows PowerShell commands. Windows PowerShell scripts have a .ps1 file name extension. 1.Sample Get-Date ;Get-Help Get-Date2. & ScriptPath sample & “C:\\Scripts\\HelloWordScript.ps1”3. PowerShell –NoExit & ‘C:\\My Scripts\\Scripts.ps1’More info: http://technet.microsoft.com/en-us/library/bb978526.aspxSharePoint PowerShellTo add snapin to Powershell: Add-PsSnapin Microsoft.SharePoint.PowerShell