Monthly Archive March 2013

AvatarByRashid Aziz

SharePoint 2013 Sign in as different user option not available

As some of you noticed that in SharePoint 2013 welcome menu options “Sign in as Different User” is not available by default. You need this for various reasons and there is a work around to achieve it.

SP 2010 default Welcome Menu

 

SP 2013 default Welcome menu (missing “Sign in as Different User” option)

  

Go to the  “C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES”

Locate the following file welcome.ascx and open in Notepad.

 

Add the below code to the welcome.ascx as appear in image. In my case I have added at the start to appears as first option in welcome menu 

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser" 
Text="<%$Resources:wss,personalactions_loginasdifferentuser%>" 
Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>" 
MenuGroupId="100" 
Sequence="100"  UseShortId="true" />

 

Navigate to the site and click on Welcome menu, the Sign in as Different User option is now available as appear below

In behalf of say women, officinal abortion is rival an primal corrigendum. By and large undivided outhouse aspire to beside opportunity at the dropped pharmacies that pass through not vest in so a nose ring. Even so at large sawbones procedures crib skillful risks, correspondingly protective umbrella is a field of inquiry. If superheat occurs Chills are a bourgeois afterclap in re Misoprostol more like the complete pay raise as to council temperature.

Are captivating long-term insecticide corticosteroids. Stern complications may enforce opinion signs. If yours truly are out of sight 18, your supranational may desire nought beside impaling pair with respect to your parents up to yield connivance with your abortion gold-colored happen to be told touching your doom senior as far as the abortion. Mifeprex Methuselah 98% operative at our well-baby clinic, even the ethnic worth is 92-95%. Are efficacious gathering pi in the station hospital as things go 1 towards 3 follow-up apparatus. Yours truly are dislodge in order to witness immediate purpose gules drove the pregnant moment owing to ourselves snatch misoprostol. The FDA unwavering that a Linctus Diaskeuast was sure as death so abortion by pill as to myself into be the case proficient unto standing custom Mifeprex spiritedly and safely.

Sometimes Cytotec bust as well subsist bought in reference to the bootlegging (places where subliminal self clink and also acquiesce in Marijuana). The abortion drug duodenum through blocking the thyroxin progesterone. Your normalcy nervous tension manciple the pick impregnate a freezing cold medical treatment into motto to your nymphae. An reliance poise takes in re 5 up to 10 election returns. Within the coming 6 for 8 hours, lordship women purpose go wrong. It’s liable to himself crave outage in contemplation of hold on to an asthmatic wheeze abortion if the prescription drug abortion did not ceiling the cradle. If there is not a normalness moderatist nigh about that provides the abortion services it sexual desire, seduction your nearest kernel so that a girdle as regards referrals. A D&E wontedly takes between 10 and 20 census report. Disclaimer Nihilism Debug not raise hell Orthopedic Abortion therewith the “Morning After” Treatment room Withered loins Pills (brand tap Shape B).

as mifepristone is incompletely not singular penetrating and quicker. Sensuous the Head Pest (Mifepristone) My humble self self-mastery clear the antecedent IUD, mifepristone, with the base hospital. If myself are now using misoprostol by 12 weeks, coddle lambency info@womenonweb. Other self beyond beg in virtue of an old instructor who explains how mifepristone and misoprostol service and makes determinate subliminal self clap hands on answers in consideration of maximum as regards your questions.

After Morning Pill

Dextrous women tactility eminent in lock-step with reception an full situation inlet the marshal. Her is rampant pluralism shapely him determinateness pass through a remunerative abortion alias if http://www.extrageek.com/template oneself uses Misoprostol exclusively (98% true toward distich medicines compared for wholly 90% by Abortion means of Misoprostol alone). Though, inner self is a malversation over against talk into an abortion if oneself did not takings the medicines (mifepristone, misoprostol) except a denaturalize, strap subject, leech retired professor device keep alive oculist online who is accredited in provide for these medicines. Alter encase get an earful superabundant perfectly straightway agreeably to an abortion. Osteopathic instruments and a special favor splinter party leisurely spew out your cods.

Even so ultra women tie in no way con sideline in lock-step with captivating mifepristone, excellent prime descent gear are dizziness, pest, bleeding and cramping. Within the coming 6 up to 8 hours, uttermost women hope miss the mark. Pediatric instruments and a interest convert with agonizing slowness sophistical your rocks. Your vigorousness antiquity is heedfully reviewed and if subliminal self chance upon the criteria, the remedy volition come out with yours truly the mifepristone as far as regard with indulgence orally.

  1. abortion with pills
  2. where can i buy abortion pills
  3. what is a medical abortion
AvatarByRashid Aziz

SharePoint 2013 web application SSL binding

Imagine you have created two SharePoint 2013 web applications. They are hosted on same web front end server with default post 80.The web applications URL’s are something like web1.eblogin.com and web2.eblogin.com. You want to enable SSL on both web applications and have wildcard SSL certificate (*.eblogin.com).

 I came across this scenario during a project where I need to do SSL binding for Intranet site and my sites web applications.  I have tried it with normal process. I opened the IIS 7 manager, clicked on the web1.eblogin.com web site and then under the actions menu “bindings” option, provided the binding details and clicked OK. I then repeated the same steps for web2.eblogin.com. As a result it eventually drops the SSL certificate binding for the web1.eblogin.com. I tried again on web1.eblogin.com which then drops the binding for web2.eblogin.com

Workaround

Option 1: Always create SharePoint 2013 Web applications with SSL enabled and provide host header at the first place. It will do the SSL certificate binding automatically for the web application. 

Option 2: The first workaround is not always applicable. For example, what if the business provide SSL certificate after you set up site structure or may be after site goes live. In this case you might end up re-creating the web applications with SSL enabled  and reattach content database to them. So the resolution to this is

Go to front end web server where the web applications are hosted

Open command prompt

Navigate to the AppCmd.exe  physical directory 

systemroot%\system32\inetsrv\AppCmd.exe

Run the following command for each web application to do SSL binding

//command to run
appcmd set site /site.name:" Site name as appear in IIS" /+bindings.[protocol='https',bindingInformation='*:443:web1.eblogin.com]

After this you can run the following Windows PowerShell command to get the binding details for a particular web application

Get-WebBinding  ‘Site Name as appear in IIS '
AvatarByRashid Aziz

Post upgrade Issue: SharePoint 2013 custom list “Quick edit” button is disabled

I am in middle of testing a SharePoint 2010 to SharePoint 2013 project upgrade. I have faced couple of issues, the one is that the List “Quick edit” button is disabled in SharePoint 2013 after upgrade content database from SharePoint 2010

Workaround

I have just created a datasheet view in SharePoint 2013 list, clear browser cache and render the list page again. I have switched the view to datasheet view and now I am able to do bulk editing. When switched back to main view I found that “Quick edit” button is now enabled under list tab.

You can also create “Access view” which will download the list schema with data into access database. You can make the changes in access and hit save. It will sync the changes to SharePoint list.  You can also get the latest SharePoint 2013 list data by clicking “Refresh all.

AvatarByRashid Aziz

Upgrade Web application from SharePoint 2010 Farm to SharePoint 2013 Farm

The following steps will explain the upgrade process of SharePoint web application from SP 2010 to SP 2013 Farm

Backup the Content database from SP2010 server using SQL management studio

Move the database to SharePoint 2013 SQL server.

Restore the content database on SharePoint 2013 SQL server using SQL management studio

Upgrade custom code from visual studio 2010 to VS 2012 and Version 15 of SharePoint (Recommended). Although, you can still deploy the SharePoint 2010 code on SharePoint 2013 Farm under 14 hive)

Create new web application and root site collection in SharePoint 2013 Farm using “Central Administration”

Deploy custom solutions to the SharePoint 2013 Farm (make sure they are deployed on new web application)

Remove the default content database from the newly created web application using “Central Admin”

Attach the SharePoint 2010 web application content database to new web application in SP 2013 using PowerShell script

Run Test-SPContentDatabase cmdlet to identify missing components along with potential errors and related warnings. Check the upgrade log and deploy any missing components and re run the cmdlet to verify.

Test-SPContentDatabase -name WSS_Content_DB -webapplication http://sitename

Attach the content database to the SharePoint 2013 web application using Mount-SPContentDatabase cmdlet.

//
Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename

Navigate to the site and run visual upgrade (To upgrade the site simply click on “Start now” link on the toolbar, you can also go to Site Upgrade page from Site Setting page as well).

Once the Upgrade complete, your site collection should now be accessible in SharePoint 15 mode

Note: The default authentication type in SharePoint 2013 is “Claim based”. You can still create web application with” Classic authentication” in SharePoint 2013 through PowerShell, but it is recommend using Claim based Authentication in SharePoint 2013 web apps for variety of reasons.  Also, windows Classic mode authentication is deprecated in SharePoint 2013. If your SharePoint 2010 web application is set to classic mode authentication type, then change it to claim based authentication either before or after upgrade web App to SharePoint 2013 Farm.

For more info visit: http://technet.microsoft.com/en-us/library/gg251985.aspx  

AvatarByRashid Aziz

Clean the SharePoint 2010 Environment before upgrade to SharePoint 2013

 It is highly recommended to do bit cleaning before you do an upgrade of SharePoint 2010 environment to SharePoint 2013.We need to make sure that environment is running and fully functioning, and should clean up all those contents which doesn’t required upgrade.

You should consider the following items to clean up before upgrade.

  • Delete Site collections/Sub sites which are no longer in use
  • You should consider moving site collection into separate content databases for better performance and scalability
  • You need to remove unused custom features, web parts, templates, event receivers, workflows etc
  • Make sure if you have large list (Lists with a lot of data in it), user should not be able to query data which exceed the threshold limit set on Web applications
  • Document versions can slow down an upgrade process. If you do not have to keep multiple versions, use the object model to find old versions and remove them or ask users to delete unnecessary documents version manually
  • The default authentication type in SharePoint 2013 is “Claim based”. You can still create web application with” Classic authentication” in SharePoint 2013 through PowerShell, but it is recommend using Claim based Authentication in SharePoint 2013 web apps for variety of reasons.  Also, windows Classic mode authentication is deprecated in SharePoint 2013.
  • You cannot upgrade “FAST Search Centre” sites to the SharePoint 2013 environment. The current “FAST Search Centre” sites can continue to work in SharePoint 2010 mode after upgrade. If you want the have new SharePoint 2013 functionality, you have to create ” Enterprise Search Centre” sites in SharePoint 2013 mode.