You know I was really going to write this article for my reference because it was about the few lines to add the “Sign in as a different user” again rather than searching & copying it from other posts every time I need it but I then stopped & thought…
But why the hell they removed it!!! It’s killing the developers & administrators are suffering!!
is this option uses an unsupported browser feature which is unreliable and causes other issues. Currently this option does not work in IE 10 and Safari.
Ok I didn’t write the reason, I copied it from here http://support.microsoft.com/kb/2752600 because actually after adding it, it works!
Now I am signing in as a different user, who has a contribute permission,
As below, I am checking that the user logging name changed and also more sure that this user is contribute from the menu, it’s obvious; just checking the caching problem, I don’t see it happening at all.
Check this article to add the “Sign in as a different user” https://www.nothingbutsharepoint.com/sites/itpro/Pages/Sign-in-as-a-Different-User-in-SharePoint-2013.aspx
This article covers the final step in the process of setting up SharePoint 2013 for the new workflow platform for SharePoint 2013 workflows. This is where SharePoint is connected to Workflow Manager services.
This post assumes you have already installed the Workflow Manager product and configured the Workflow Manager and Service Bus farms using either the Configuration Wizard or through PowerShell. Here, we shall go ahead and set SharePoint up to use the Workflow farm. Based on whether SharePoint is collocated with the Workflow Manager and whether communication between SharePoint and Workflow Manager over HTTP is allowed, the steps through which this configuration is performed are different and are documented here. For the configuration in this instance we are using SharePoint on the same farm as Workflow Manager and communication over HTTP is allowed.
Configuration on SharePoint is about creating a service application proxy for workflow that has…
View original post 765 more words
Sometimes I installed it smoothly and sometimes I spend a day to configure it and of course every time something is different than the previous time which is why I spend time configuring it!!!
Microsoft can’t live without making our life miserable in configuring a piece in SharePoint, you see the User Profile now working like sharp and the “Forefront Identity Manager Synchronization Service” is running J thank god with no hassle.
Now the hassle is in configuring Workflow Manager 1.0, the hassle started when I installed the update, once removed, things became cleaner.
Also I removed the Workflow Manager from the Farm using its configuration wizard, then removing Workflow Manager from “Control Panel” à “Uninstall a program” & reinstalled it again & re-configured it.
Anyway, one of the many errors I got when publishing the workflow manager is solved below;
This exception one when publishing from SharePoint Designer 2013;
” Microsoft.Workflow.Client.ScopeNotFoundException: Scope ‘/SharePoint/default/5d37625b-d6d9-46a1-805e-93bb53cd0568/cf67d4d4-3b59-4bb4-8c8a-47985deff0ad’ was not found. HTTP headers received from the server – ActivityId: d4579f0b-d88b-4026-b058-cdbbd48e4ac4. NodeId: XXXXX. Scope: /SharePoint/default/5d37625b-d6d9-46a1-805e-93bb53cd0568/cf67d4d4-3b59-4bb4-8c8a-47985deff0ad. Client ActivityId : 6d46e39b-7077-409e-5672-ef055175b994. —> System.Net.WebException: The remote server returned an error: (404) Not Found. ”
The idea is that there is a scope name “SharePoint” which I need to register the Workflow by. I used this PS
Then closed & re-opened SharePoint Designer and published & VIOLA J worked!
SharePoint 2010 was supporting the In-place upgrade, the only advantage I see from this is reducing the required number of environments ya but you still have to take backup right?
SharePoint installation is smooth yes but upgrade is not unless your environment is empty! So who would do In-place upgrade for SharePoint!! And what if it failed as always I believe, you will have to start new environment from scratch … that will be sweet times J .. I am just laughing at that.
In-place upgrade already have problems mainly and importantly is performance issues.
Microsoft realized this, oh thank god! And decided to remove it from SharePoint 2013.
In case you are reading this and don’t know what is In-place upgrade means; read below:
“An upgrade to SharePoint Server 2010 or SharePoint Foundation 2010 provides an option to install the new version over the earlier version on the same hardware. This is called an in-place upgrade. During this process, the complete installation, that includes databases and sites, is upgraded in a fixed order. Although this is a simple method, in-place upgrade presents problems in performance and control for a farm administrator. There was no way to control the order in which content is upgraded, and a failure in a particular site collection could stop the whole process.”
SharePoint 2013 does not support In-place upgrade
So the supported and recommended upgrade is the database-attach upgrade.
The database-attach upgrade method offers more flexibility, more control, and a better success rate.
To use a database attach upgrade, you will need to complete the following tasks:
- Create and configure a new farm that is separate from the old farm
- Copy the content and services databases to the new farm
- Upgrade the data and sites
You can upgrade the content databases in any order and upgrade several databases at the same time to speed up the overall process.
Trying to clear the confusion here and questions I have been asked a lot last week. Please find below the venue details.
Burjeel Hospital Auditorium
2nd Floor, Burjeel Hospital
Bani Yas Najda Street
For map view, please visit this link: