Skip to main content

Installing Windows Server 2012 for SharePoint 2013






I follow Corey Roth’s blogs. In his blogs he has given so much information regarding SharePoint 2013 that I got inspired and started my journey of learning SharePoint 2013.

My first task was to get SharePoint 2013 installed on my laptop. I have Intel i5 2.4 GHz (2) with 8 gig memory. I am running on Windows 7 Professional 64bit. I already have VMWare (8.0.4 build-744019) installed where I do my development on Windows server 2008 R2 with SharePoint 2010. So my obvious choice was to get SharePoint 2013 image and install it on my already running VMWare Server 2008 R2. I downloaded the 2.1 gig image and tried installing it on my VM. But failed. There were varied reasons for the failure.

So I decided to get Windows Server 2012 and create a new VM from it and then install SharePoint 2013 on it. I downloaded the Server 2012 Hyper-V Release Candidate (8400.0.WINMAIN_WIN8RC.120518-1423_X64FRE_SERVERHYPERCORE_EN-US-HRC_SHV_X64FRE_EN-US_DV5.ISO). Then tried to create a fresh new VM from VMWare. 
But during installation, when the server restarts for the first time, the system would get hung. It would not proceed further. No errors. Just the black screen with the hung rotating image. I tried to do the installation twice. No luck.

But then I saw another blog post from Shail here: http://www.shailwx.com/2012/07/sharepoint-2013-development-image-part-1-creating-a-virtual-machine/.  Where he has provided step by step guide to install Server 2012. But in his blog he has used VirtualBox. So I also decided to install VirtualBox and try my luck. This time I was able to complete the installation successfully.

But after login screen, I get only command prompt. No UI. My colleague IT admin Mr Ganesh said that while installing (setting up) I have chosen Server Core and not Full Server installation. But I remember clearly that I did not get any such choice while installing the server.

Then we both started googling how to switch between command prompt to GUI (full server installation). I got lot of options, lot of trial and errors. But nothing worked. Below are some of the steps I tried out…

Step 1: To use Windows PowerShell to convert from a Server Core installation to a Server with a GUI installation (http://technet.microsoft.com/en-us/library/hh831786.aspx)
  1. Create a folder to mount a Windows Imaging File (WIM) in with the command mkdir c:\mountdir
  2. Determine the index number for a Server with a GUI image (for example, SERVERDATACENTER, not SERVERDATACENTERCORE) using this command at an elevated command prompt: Dism /get-wiminfo /wimfile::sources\install.wim
  3. Mount the WIM file using this command at an elevated command prompt: Dism /mount-wim /WimFile::\sources\install.wim /Index:<#_from_step_2> /MountDir:c:\mountdir /readonly
  4. Start Windows PowerShell and run this cmdlet: Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs
  5. Alternatively, if you want to use Windows Update as the source instead of a WIM file, use this Windows PowerShell cmdlet: Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart

Step 2: Enable ServerCore-FullServer feature (http://www.sqlha.com/2012/05/14/switching-between-server-core-and-full-gui-with-windows-server-2012/)
  1. Dism /online /enable-feature /featurename:ServerCore-FullServer /source:d:\sources\sxs
  2. Add-WindowsFeature Server-Gui-Shell

With unsuccessful attempts, I decided to download Server 2012 RC (no Hyper-V this time) and install it on VirtualBox. 
I will update in my next post about my findings…

Happy SharePointing (2013)
Vighnesh Bendre
Labels:

Comments

Post a Comment

Popular posts from this blog

Error while activating feature - SharePoint 2010

Hi all, While I was working on SharePoint 2010 recently I came across some issues. I am putting them across so that anyone facing the same issue may find solution easily. Error: Error occurred in deployment step 'Activate Features': Feature with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is not installed in this farm, and cannot be added to this scope. Solutions: I was getting this error while ‘deploy’ing a feature from Visual Studio 2010. I searched the entire project for this GUID which is mentioned in the error. I did not find it anywhere. While troubleshooting, I opened the physical folder and opened ‘Feature1.feature’ file in notepad. This xml file was using the before mentioned GUID. I was not able to find it in VS 2010 :( I copied the GUID mentioned in the ‘Feature1.feature’ file and pasted it in the Feature ID section in ‘Feature1.Template.xml’ file. This solved the problem. Why I thought to mention it is because the exception thrown is confusing. It does not tell you...
10 comments
Read more

Working with large xml files in c# .net

Working with large (huge) xml files is always a pain in the … The reason? These files can’t be loaded in to memory. On my desktop, where I have 2 gigs memory, I can’t open the file in even notepad. I was presented with a challenge recently to manipulate one such large xml file. The xml file was of 550+ MB. I know many would say I have seen bigger xml files than this. But the heart of the matter is if I can’t open 550+ MB file in notepad or in xmldocument in c#, then I can’t open any file bigger than this. And hence the logic to play with these files would remain same. The scenario: We have an xml file from which we want to remove a single node without removing its children. In the below sample xml fragment, the node has to be removed. The children nodes, must then be attached to ( node’s parent) node. One Two 100.22 GoodDay 3 4 Five 200.09 Cra...
3 comments
Read more

Custom People Picker (Editor) in SharePoint 2010

[Modified:11 Oct 2010] Now you can find the source code for this example in CodePlex The out-of-the-box SharePoint people picker allows users to select users, SharePoint groups, Distribution Lists & Security groups . Users may accidentally add large AD groups to SharePoint groups and send notifications to hundreds of people. The administrator may want more control over the security of the people picker control. In some scenario the administrator may want to restrict the user to only select ‘users’ or ‘SharePoint Groups’. This can be achieved by creating a custom people picker control which inherits from SharePoint people editor. In below example, we are going to explore creation of custom people picker control, replace the OOTB people editor control, provide a people picker settings page in central administration and create menu to access the settings page in Central Administration. 1. Create custom people picker For creating a custom control (which inherits from SharePoint PeopleE...
4 comments
Read more