Archive | January, 2013

I finally did it! 10K+ visits in a month!

Not bad seeing as I was at 2K last year this time!

Today		 373
Yesterday	 504
This month	 10183
December	 9085
November	 9827
October		 9427
September	 9010
August		 9440
July		 9151
June		 8171
May 		 7352
April		 5027
March		 3966
February	 3160
January		 2741

PowerShell 3: Using Invoke-RestMethod to refresh a new oAuth 2 token

I wanted to translate this code into powershell. Below is the Powershell code to request a refresh token from Google using oAtuh 2.


$URL = ""
$Body= 'client_secret={0}&grant_type=refresh_token&refresh_token={1}&client_id={2}' -f $CLIENTSECRET,$REFRESH_TOKEN,$CLEINTID
Invoke-RestMethod -URI $URL -Method Post -Body $Body

Hope that helps someone.

Using cURL, BASH and Google oAuth to access Google Analytics

In this previous post, I used cURL (the command line version) to interact with Google Analytics. I wanted to do the same thing but using oAuth. I took a lot from this page, but there were a few things that I couldn’t get working, and a few things I didn’t know.

Follow Steps 1-6 on this page. These are steps that you need to follow to get your app registered with Google

In step 6, copy down the code, and keep track of it. It needs to be reused every time you need to get a new token. If you loose it, then you need to run step 6 over again. I didn’t know that.

Here is my script. I will jump through the code below it.

HEADER="Content-Type: application/x-www-form-urlencoded"

# I keep the ACCESS_TOKEN and the REFRESH_TOKEN in a file.
if [ -s ~/.google ];then
	ACCESS_TOKEN=$(cat ~/.gauth | grep access_token | awk -F"," '{print $2}' | tr -d ' ')
	REFRESH_TOKEN=$(cat ~/.gauth | grep refresh_token | awk -F"," '{print $2}' | tr -d ' ')
	# not used before
	NEWTOKEN=$(curl -s -d "code=$CODE&redirect_uri=$REDIRECTURI&client_id=$CLEINTID&scope=&client_secret=$CLIENTSECRET&grant_type=authorization_code"
	ACCESS_TOKEN=$(echo $NEWTOKEN | awk -F"," '{print $1}' | awk -F":" '{print $2}' | sed s/\"//g | tr -d ' ')
	REFRESH_TOKEN=$(echo $NEWTOKEN | awk -F"," '{print $4}' | awk -F":" '{print $2}' | sed s/\"//g | sed s/}// | tr -d ' ')
	echo access_token , $ACCESS_TOKEN > .google
	echo refresh_token , $REFRESH_TOKEN >> .google
EXPIRED=$(curl -s$ACCESS_TOKEN | grep 'invalid_token')
if [ "$EXPIRED" ]       
	echo "EXPIRED"
	REFRESHRETURN=$(curl -s -d "client_secret=$CLIENTSECRET&grant_type=refresh_token&refresh_token=$REFRESH_TOKEN&client_id=$CLEINTID"
	ACCESS_TOKEN=$(echo $REFRESHRETURN | awk -F"," '{print $1}' | awk -F":" '{print $2}' | sed s/\"//g | tr -d ' ')
	echo access_token , $ACCESS_TOKEN > .gauth
	echo refresh_token , $REFRESH_TOKEN >> .gauth
# now in your curl code to retrieve the google analytics data, you use --header "Authorization: OAuth $AUTH"

Lines 1-6: I am setting up my variables with data as described in the linked post.
Lines 8-11: I keep track of the current access token and the refresh token in a config file. If the file exists then parse out the values
Lines 12-19: This is the first time this has been run, so I need to create the file, and put in it a new token and the refresh token. Note the refresh token needs to be saved, and is only given to you once. I did not know that.
Line 20: checks to see if the access token is expired.
Lines 21-28: if the access token is expired, use the refresh token to get a new access token and then save it to the file.

That is it. I hope to translate into PowerShell next – I am sure this code exists, but this is how I learn.

Hope this helps someone.

My upgrade of SharePoint 2007 to 2010 “script”

One of my most recent projects was the migration of our intranet from SharePoint 2007 to 2010. Since we were going to change the name of the site, I was able to run through this “script” several times as practice to make sure I had everything correct.

I decided to do a detach and attach method. Here are some of the things we did.

  1. We preformed several test a detach and attach upgrades with the new URL. This allowed us to test everything using the new url, and make changes back in the original 2007 site so that it would work once we performed the final live cutover.
  2. All new code/pages/hacks were added to the 2010 site into New documents libraries. These were backed up using this script and restored after every new test detach an attach test. This way all new code would be in place with the final live cutover.
  3. Since we were doing a new Navigation, we created the navigation in the old 2007 site, and hid them by audience. Then one of the steps below is to change the audience which would un-hide the new navigation in the final cutover.

Step 1. Backup all the new code/pages/hacks that have been added to the new site that needs to be restored.

$folderDate=$(get-date -uformat "%Y-%m-%d")
$folderHour=$(get-date -uformat "%H")

foreach ($web in $(Get-SPSite | Get-SPWeb)){
    foreach ($list in $web.Lists) {
    mkdir -force "$backupDir\$($Web.Title.replace(' ','').replace('/','-'))\"
    Export-SPWeb $($web.Url) -itemurl "$($list.RootFolder.ServerRelativeUrl)" -path "$backupDir\$($Web.Title.replace(' ','').replace('/','-'))\$($list.Title.replace(' ','').replace('/','-')).cmp"

Now we have captured all the changes that were made to the new site (which we will be restoring after the next cutover test)

Step 2. Remove the previous test cutover site

Remove-SPWebApplication "SharePoint -" -RemoveContentDatabases -DeleteIISSite

Step 3. Re-create new app and apppool.

New-SPWebApplication -Name "SharePoint -" -Port 80 -HostHeader -URL "" -ApplicationPool "SharePoint -"

Step 4. remove the content database that is created by default

Get-SPContentDatabase -WebApplication "SharePoint -" | Remove-SPContentDatabase

Step 5. Backup 2007 site to a share and restore to new SQL server (or new db name on existing SQL server).


$sqlcmdBackup="BACKUP DATABASE [Content_Intranet] TO DISK = N'\\path\to\network\share\Content_Intranet.bak' WITH NOFORMAT, NOINIT,  NAME = N'Content_Intranet FullBackup', SKIP, NOREWIND, NOUNLOAD,  STATS = 10"
invoke-sqlcmd -query "$sqlcmdBackup" -Server $SRCSQLSERVER -QueryTimeout 1200


$sqlcmdRestore="RESTORE DATABASE [Content_Intranet] FROM  DISK = N'\\path\to\network\share\Content_Intranet.bak' WITH  FILE = 1,  MOVE N'Content_Intranet' TO N'K:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\Content_Intranet.mdf',  MOVE N'Content_Intranet_log' TO N'K:\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\Content_Intranet_log.LDF',  NOUNLOAD,  REPLACE,  STATS = 10"
invoke-sqlcmd -query "$sqlcmdRestore" -Server $DESTSQLSERVER -QueryTimeout 1200

Step 6. Mount the restored database and upgrade the uner experience.

Mount-SPContentDatabase -Name Content_Intranet  -DatabaseServer NewSQLServer -WebApplication -Updateuserexperience

Step 7. Re-import exported Document Libraries that contain the new code/pages/apps

Import-SPWeb -Path \\path\to\network\share\date\hour\LibraryName.cmp

Step 8. Clean up navigation by changing audience, change homepage to new page in restored Document Libraries.

Step 9. Alter web.config for Cisco WebVPN

Step 9. Allow inline PDFs

That was it. I did it several times, and it ended up being a smooth cutover.

PowerShell command to allow inline PDF viewing in SharePoint 2010

My users like to view PDFs in their browser on our SharePoint site. I needed to allow this in 2010:
Here is the powershell to allow inline PDF viewing in SharePoint 2010

$webapps = Get-SPWebApplication "SharePoint -"
foreach ($webapp in $webapps) 
} stats from last year

I missed my blogging goal of 2-per-week/104 for the year. I ended up 98 posts. Same goal for this year.
I also missed 10,000 in a month. I was on track at the beginning of December, but then I had a big drop during the holidays.

My monthly break down:

December	 9085
November	 9827
October		 9427
September	 9010
August		 9440
July		 9151
June		 8171
May 		 7352
April		 5027
March		 3966
February	 3160
January		 2741

Here is my year end traffic graph from Google Analytics:


And here is the breakdown for the traffic:


My 2013 goals are 2 posts per week/104 per year, as I said above. And 15,000 visitors a month. 15k may be out of my reach, but I would love it!

Powered by WordPress. Designed by WooThemes