Persist/Save Azure login credentials in a PowerShell session

When working with Azure its very common to open multiple PowerShell windows in order to execute multiple PS scripts in parallel to get the work done faster. One of the repetitive task we have to do is to login to Azure portal in each new PS window.

In order to avoid the above mentioned hassle we can save the Azure login credentials to a json file and re-use it across multiple PS sessions/windows. The save credentials are valid for 12 hours.

#Login to Azure subscription
Login-AzureRmAccount

#If you have multiple subscriptions associated with the login, view all subscriptions
Get-AzureRmSubscription

#Select the subscription for the current session
Select-AzureRmSubscription -SubscriptionId <guid of Azure subscription>

#Save the credentials to a json file
Save-AzureRmProfile -Path C:\Projects\AzureLogin.json

Once the credentials are saved using the above procedure, whenever you open a new PS window you can re-user the credentials as below;

#select the persisted Azure credentials from the json file (in new PowerShell window)
Select-AzureRmProfile -Path C:\Projects\AzureLogin.json

SharePoint online (o365) add-in workflow – AppOnlySequence

If you are going to use “AppOnlySequence” workflow activity in a SP add-in, make sure you follow the below activities in order to grant the required permission by the workflow to execute successfully. If you have missed any of the steps, then the workflow will be suspended with the error “Exception: Access denied. You do not have permission to perform this action or access this resource.”

Step 1:

Enable the feature “Workflows can use app permissions” at site level (site settings -> site actions -> manage site features):

image1

Step 2:

In visual studio open AppManifest.xml and grant the app “Manage” permission.

image2

Step 3:

Tick the option “Allow the app to make app-only calls to SharePoint”

image3

You can also update the raw xml of AppManifest.xml with AllowAppOnlyPolicy=”true” instead of using the VS designer.

XML :

<AppPermissionRequests AllowAppOnlyPolicy=”true”>
<AppPermissionRequest Scope=”http://sharepoint/content/sitecollection/web&#8221; Right=”Manage” />
</AppPermissionRequests>

The Variations Create Hierarchies job failed

 

If you get the following message in variations logs (Site Actions –> Site Settings –> Site Collection Administration –> Variation Logs)  when the “Variations Create Hierarchies Job Definition” executed, it could be due to missing language packs.

“The Variations Create Hierarchies job failed with the following error message: File or arguments not valid for site template ‘CMSPUBLISHING#0’. Parameter name: WebTemplate.”

When installing a language pack in SharePoint 2010 Server make sure the following is followed.

Lets say for “Spanish” language pack

  1. Download SPF 2010 Spanish language pack from http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=646e311a-aaf3-4d30-b03c-2f3c70d19a22
  2. Install the Spanish language pack.
  3. Run the SP configuration wizard.
  4. Download MOSS 2010 Server Spanish language pack from http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=046f16a9-4bce-4149-8679-223755560d54
  5. Repeat step 2 & 3

Usage and Health Data Collection Proxy : Stopped

After installing and configuring SharePoint 2010 farm and if you notice that the “Usage and Health Data Collection Proxy” is still in the stopped state, follow the below to provision it.

Run the following PowerShell command to view the GUID of the service

Get-SPServiceApplicationProxy

image

Copy the Id of the SSA “WSS_UsageApplication”

Execute the following by replacing the GUID copied from above output.

$UP = Get-SPServiceApplicationProxy | where {$_.ID -eq "<GUID of the WSS_UsageApplication>"}

$UP.Provision()

image

 

Now check the service status from central admin site.

image

SharePoint 2010 Managed Accounts

When you try to add a managed account to SharePoint 2010, it was throwing a error

“The specified user DOMAIN\SPFASTContentAdmAppPool could not be found. Some or all identity references could not be translated.”

But the user exists in the active directory. When I investigate further I found out that SharePoint does not accept user names which are more than 20 characters in length.

So new rule to the pre-installation documentation. “Manage account ids should be less than 20 characters”.

image

Publishing Pages : check-in file programmatically

One of the common scenarios when working with content migration is to handle the files checked out by other users. Following code is written to check-in all files check out by any users.

class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine("Please enter site url");
            
            using (SPSite site = new SPSite(Console.ReadLine()))
            {
                using (SPWeb web = site.OpenWeb())
                {
                    PublishingPageCollection publishingPages 
= PublishingWeb.GetPublishingWeb(web).GetPublishingPages(); foreach (PublishingPage page in publishingPages) { SPFile file = page.ListItem.File; if (file.CheckedOutByUser != null) { Console.WriteLine("The page {0} is check out by
user {1}. Check-in in to take control."
,
file.Title, file.CheckedOutByUser); file.CheckIn("checked in by script",
SPCheckinType.MajorCheckIn); SPModerationInformation moderationInformation
= page.ListItem.ModerationInformation; if (moderationInformation.Status
== SPModerationStatusType.Pending) { file.Approve("Approved by script"); } if (moderationInformation.Status
== SPModerationStatusType.Draft) { file.Publish("Published using script"); file.Approve("Approved by script"); } } } } } } }