How to Set Up Git on Windows

Register and Sign Into GitHub

Navigate to the GitHub Website (https://github.com).  If you have already registered, Login.  If you need to register, provide a User Name, Email Address, and a Password and click Sign Up for GitHub.



Create a Repository

After logging into GitHub, click New Repository.

As the Owner, your User Name will appear as the Owner.  Provide a Repository Name.  Select Public or Private (there are costs associated with Private).  Click Create Repository. 

Once the Repository has been created, you will be brought to an information page with details about the repository, including the HTTPS address.

If you navigate to the repository URL, you will see that the new repository is empty.  Once you install Git for Windows on your local system, you can begin to push content to the repository.

Download Installer Files

Download the following installer files to the system where Git will be installed:

Git for Windows
https://git-for-windows.github.io

Git Extensions
https://gitcredentialstore.codeplex.com

Git Credential Winstore
http://downloads.sourceforge.net/project/gitextensions/Git%20Extensions/Version%202.48.03/GitExtensions-2.48.03-SetupComplete.msi?r=&ts=1420161094&use_mirror=hivelocity


Install Git

Right click on the Git installer and Run as Administrator.

Click Next.

Click Next.

Click Next.

Click Next.

Click Next.

Use Git from the Windows Command Prompt, click Next.

Checkout Windows-style, click Next.

Use MinTTY, click Next.

  

Click Next.

Click Next.

Click Finish.

Install Git Extensions

Right click the Gitextensions installer and Run as Administrator.

Click Next.

 Install for all users, click Next.

 Check all options, click Next.

Click Next.

Run all from computer, click Next.

Click Next.

Click Next.

Click Install.

Click OK.

Click I Agree.

Click Next.

Click Next.

Click Next.

 Click Install.

Click Finish.

Click English.

Click Finish.

Install Git Credential Store

Right click the git-credential-winstore installer and click Run as Administrator.

Click Yes.

References

Codeplex (2015).  Git-credential-winstore.  Retrieved October 7, 2015 from https://gitcredentialstore.codeplex.com.

Cstructor LLC (2015).  Getting Started.  Retrieved October 7, 2015 from http://cstructor.com/Home/Notes?classId=40&sequence=20.

Github (2015).  Git for Windows.  Retrieved October 7, 2015 from https://git-for-windows.github.io.

Sourceforge (2015).  Git Extensions.  Retrieved October 7, 2015 from http://downloads.sourceforge.net/project/gitextensions/Git%20Extensions/Version%202.48.03/GitExtensions-2.48.03-SetupComplete.msi?r=&ts=1420161094&use_mirror=hivelocity.

SPS CT: BI and Automation Tools for IT featuring SharePoint and SQL Server

Event:
SharePoint Saturday Connecticut
Saturday, October 10, 2015

Session Title:
BI and Automation Tools for IT featuring SharePoint and SQL Server

Abstract:
IT organizations are responsible for delivering and maintaining technology solutions and capabilities throughout organizations; sometimes at the expense of their own productivity. Resource constraints deter IT organizations from investing the time and attention necessary for process improvement, resulting in a reactive approach to problem solving. Now is the time to empower IT using reports, dashboards, and notifications.

This presentation demonstrates how to utilize SharePoint Server, SQL Server Integration Services (SSIS), and SQL Server Reporting Services (SSRS) to create business intelligence and automation tools for IT. This session covers high-level concepts as well as practical, hands-on instructions, tips, and tricks.

Slides:

BI and Automation Tools for IT Featuring SharePoint and SQL Server

SPS NYC: BI and Automation Tools for IT featuring SharePoint and SQL Server

Event:
SharePoint Saturday New York
Saturday, July 25, 2015

Session Title:
BI and Automation Tools for IT featuring SharePoint and SQL Server

Abstract:
IT organizations are responsible for delivering and maintaining technology solutions and capabilities throughout organizations; sometimes at the expense of their own productivity. Resource constraints deter IT organizations from investing the time and attention necessary for process improvement, resulting in a reactive approach to problem solving. Now is the time to empower IT using reports, dashboards, and notifications.

This presentation demonstrates how to utilize SharePoint Server, SQL Server Integration Services (SSIS), and SQL Server Reporting Services (SSRS) to create business intelligence and automation tools for IT. This session covers high-level concepts as well as practical, hands-on instructions, tips, and tricks.

Slides:

BI and Automation Tools for IT Featuring SharePoint and SQL Server

SharePoint Server 2013 New Web App "This Page Can't Be Displayed", Central Admin "Upgrade Required"

Description

This is a walk through of the process I took to solve a problem that I encountered in a SharePoint 2013 on-premises farm.

When attempting to create a new Web application, I received an error that said.

While the Web application appeared in Central Administration and the Content Database existed in SQL Server and was visible in Central Administration Manage Content Databases, I could not create a new Site Collection in the the new Web Application.  I attempted to create another Web Application and received the same dialog message, "This page can't be displayed".

After investing the farm health, I found that the Servers in Farm page in Central Administration was showing "Upgrade Required".

Meanwhile, the Upgrade Status in Central Administration appeared to be OK with all "Succeeded" messages and no errors.

I opened a Command Prompt and ran stsadm.exe -o localupgradestatus.  This took a few minutes to run but once the command completed revealed that there were 2 objects that "still need upgrade".  These two objects were the two Web applications I attempted to create earlier.

Internet Information Services (IIS) showed Web Sites and Application Pools for each Web application.  However, I discovered that the C:\InetPub\WWWRoot\WSS\VirtualDirectories\WebApplication directories for the problem Web Applications were missing files.  It appears that the directories were only partially created.

Solution


1.  Open Windows PowerShell for SharePoint 2013

2.  Put contentservice value into variable
 $contentservice = [Microsoft.sharepoint.Administration.spwebservice]::contentservice

3. Put contentservice of Web App into variable
$webapp = $contentservice.webapplications | where { $_.name -match "WebAppName" }

4.  Provision the WebApp
$webapp.provision()

5.  Verify the folder structure of  C:\InetPub\WWWRoot\WSS\VirtualDirectories\WebApplication directories.  It should look like the image below.

6.  Verify that stsadm.exe -o localupgradestatus shows zero (0) objects still need to be upgraded.

7.  Create a new site collection in the Web application and browse to it as a test that the Web Application is fully functioning.

8.  On the Web Front End server that is showing "Upgrade Required"; open the Command Prompt as an Administrator, change the directory to "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN", and run the following command:
PSConfig.exe -cmd upgrade -inplace b2b -force -wait

9.  Verify Central Administration Upgrade Servers in Farm shows Status of "No Action Required".


Key Words
New SharePoint Web Application Page Can't Be Displayed, SharePoint Upgrade Required


References

Maxwell, R. (April, 2013).  Why SharePoint 2013 Cumulative Update takes 5 hours to install?  Retrieved March 24, 2015 from http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install.aspx.

Error: SQL Server Integration Services: Error at SharePoint Site

Description

You configure a SQL Server Integration Services package containing a SharePoint List Source or OData Source in a Data Flow.

When attempting to execute the SSIS package in SQL Server 2012 Data Tools, an error returns:

!  Error at SharePoint Site:  System.ServiceModel.Security.MessageSecurityException:  The HTTP request is unauthorized with client authentication scheme 'Ntlm'.  The authentication header received from the server was 'NTLM'.--->System.Net.WebException:  The remote server returned an error:  (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory'1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpantimeout)
---End of inner exception stack trace---


Solution

1) Open the SSIS Project in SQL Server Data Tools

2) Right Click on the Project, Properties

3) Choose Debugging

4)  Change the Run64BitRuntime property from True to False (MS-SSIS Blog, 2012)

5)  Save the Project

6)  Attempt to run the package again


Key Words
SSIS, Run64BitRuntime


References

Codeplex (2011).  NTLM authentication error in SharePoint List Adapter for SSIS.  Retrieved February 25, 2015 from http://sqlsrvintegrationsrv.codeplex.com/discussions/269590.

Microsoft SQL Server Integration Services Blog (September, 2012).  Switch package from 64bit to 32bit.  Retrieved August 14, 2014 from
http://microsoft-ssis.blogspot.com/2012/09/swtich-package-from-64bit-to-32bit.html