by Ayoub Umoru | Feb 25, 2014 | SharePoint 2013 |
Good news for everyone planning to build a farm with Windows Server 2012 R2.
The Server Pack 1 for SharePoint Server 2013 has just been released and is now supporting Windows Server 2012 R2 !!!
Download the Server Pack
List of adressed issues. (Excel)
Summary
- Added support for Windows Server 2012 R2
- Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and security.
- All the monthly security updates that were released through January 2014, and all the Cumulative Updates that were released through December 2013.
Like this:
Like Loading...
by Ayoub Umoru | Nov 25, 2013 | Migration |
The new Version of the PowerShell Content Deployment codeplex project has been released.
This solution is the only way to implement incremental content deployment, without having to transfer the whole site collection!
It also supports content deployment across two different SharePoint versions. (SharePoint2010 / SharePoint 2013)
Check out the latest Version.
I have created a tool for Content Deployment between two SharePoint Farms.
By using the switch OverrideSchemaVersion it is also possible to deploy content from SharePoint 2010 to SharePoint 2013.
Its made of PowerShell Scripts and XML.
Of course there are other tools already on the market, but with this Solution you are able to “Copy” only the list, without being forced to Copy the whole SiteCollection.
It is also possible to establish a content deployment scenario with having different Farm Versions/Patch Levels and Feature sets in the Source VS. Destination.
This tool makes it possible to implement an incremental content deployment szenario for SharePoint Lists between two distinct Farms
Features
- SharePoint2010->SharePoint2013 migration
- Full migration
- Incremental migration
- Transfering original metadata : Created,CreatedBy,Modified,ModifiedBy
- Lookup column support
- Support for disconnected scenarios (2 different Farms Intern vs Extern)
- Transfering UserInformation from external Users, even if they do not exists in the destination Farm (e.g. FBA and internal Intranet)
Installation
- Each Farm needs a own copy of the scripts.
- Both Farms share the same storage and export/import history file
Like this:
Like Loading...
by Ayoub Umoru | Oct 28, 2013 | SharePoint 2013 |
Get-UserProfiles – Get your own user profile report
Ever wanted to check your profile store in terms of usage or correct data for a specific property in all profiles?
Download this tiny script to accomplish your mission.
.\Get-UserProfiles.ps1 -PropertyConstant [PropertyConstant]
[Download]
Like this:
Like Loading...
by Ayoub Umoru | Jun 20, 2013 | Migration |
Sharepoint Content Deployment with PowerShell
I have created a Tool for Content Deployment between two SharePoint Farms.
Here is the Link to the Tool.
Its made of PowerShell Scripts and XML.
Of course there are other tools already on the market, but with this Solution you are able to “Copy” only the list, without being forced to Copy the whole SiteCollection.
It is also possible to establish a content deployment scenario with having different Farm Versions/Patch Levels and Feature sets in the Source VS. Destination.
This tool makes it possible to implement an incremental content deployment szenario for SharePoint Lists between two distinct Farms.
Features
- Full migration
- Incremental migration
- Transfering original metadata : Created,CreatedBy,Modified,ModifiedBy
- LookupColumn Support
- Support for disconnected scenarios (2 different Farms Intern vs Extern)
- Transfering UserInformation from external Users, even if they do not exists in the destination Farm (e.g. FBA and internal Intranet)
Installation
- Each Farm needs a own copy of the scripts.
- Both Farms share the same storage and export/import history file
Like this:
Like Loading...
by Ayoub Umoru | Jan 11, 2013 | SharePoint 2013 |
I wrote a script for all those who want an easy and safe way to change the quota of a site.
[Download]
.\AdjustSiteQuota.ps1 -Identity [$url] -Percentage [1-1000]
Its very simple… just suppy the url and the percentage how the new values for StorageWarningLevel and StorageMaximumLevel should be adjusted.
Iagine if you want to decrease the quota of a site by 50%, jsut supply 50 as parameter, let me give some examples.
I want to increase the site quota for a (mysite http://mysite/personal/themysite) by 20%
Command: .\AdjustSiteQuota.ps1 -Identity "http://mysite/personal/themysite" -Percentage 120
I want to decrease the site quota for a (mysite http://mysite/personal/themysite) by 50%
Command: .\AdjustSiteQuota.ps1 -Identity "http://mysite/personal/themysite" -Percentage 50
See the script in action…
Enjoy and comment if you have an idea or found an bug.
Like this:
Like Loading...
SharePoint Guru