Dev Team Assemble

I was trying to install install SharePoint 2007 onto Windows 2008 r2 and was getting a strange error referencing KB article 962935. Funny enough this article is not live yet so it left me a little unhappy. Apprarently Microsoft does not support the distributed SP1 installation package of SharePoint for this version of the OS. Turns out Jei Li posting on his msdn blog detailing how to go about creating a slipstreamed installation for SP2 on this server Click here for the article. Basically the steps are (pretty much word for word from Jei Li's blog):

• Install .Net Framework 3.5 SP1 in the features applet
• Copy the installtion media contents to a folder on the computer (c:\install)
• Download the WSS x64 SP package and the MOSS 2007 SP2 x64
• Delete everything inside Updates folder in the install folder you setup.
• Open a command prompt,  change directory to the folder you put the downloaded patches, and run the following two commands: 
  • wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:[Path to installation bits]\Updates /quiet
  • officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract: [Path to installation bits]\Updates /quiet
• Delete the wsssetup.dll filein the updates dir. This is a very important step so please don’t miss it.
• If you also need the Cumulative Updates to be applied when install SharePoint, download the latest Windows SharePoint Services 3.0 and SharePoint Server 2007 Cumulative Update packages and extract them into Updates folder like step 4.
• Your slipstream build of SharePoint Server 2007 is done!
• Go and install it on your Windows Server 2008 R2 box, after the installation, the site version will show 12.0.0.6421 or possibly a higher version.

Please reference Jei Li's post for furthur instuctions.  I only posted all the steps here because things have a mysterious way of dissappearing or not appearing at all on Microsofts site.

After doing all of this everything seems to be fine...seems to be  

Links

• http://technet.microsoft.com/en-us/library/cc261890.aspx
• http://blogs.msdn.com/sharepoint/archive/2009/10/02/install-sharepoint-server-2007-on-windows-server-2008-r2.aspx
• http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b7816d90-5fc6-4347-89b0-a80deb27a082
• http://www.microsoft.com/downloads/details.aspx?familyid=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

Technorati Tags: Configuration, server, SharePoint, Windows, windows 2008 r2, x64

Recently I acquired some server class hardware (Dell PowerEdge 2950)  and I thought, hey this is a great opportunity for me to setup a virtual environment at home so I can test out some beta products and do some tinkering with Linux. I have VMWare Workstation installed inside of Windows Vista machine at home and I have ubuntu 8.10 running in it and this seems to work ok but I have come across some issues with it that annoy me.

I was undecided on whether to install VMWare ESXi or Windows 2008 Hyper-V server. Based on the title of this article you can probably guess which route I took. I didn't decide to do this simply because I think Microsoft's virtualization platform is superior...I chose it simply because I use VMWare ESXi and ESX at work and was interested in seeing the capabilities of this free product in comparison.

After configuring the server with RAID 0 (faster and this is test) I popped the disk in and started installing. Truth be told the installation was a breeze...so much so in fact that I started the install, watched a soccer game and when I came back it was ready for me to login. I was a little confiused at first because at no point did I provide a username and password for the admin account but it prompted me at the login screen. Didn't take long to figure out it was Administrator/-blank- to login.

This all seemed a little too good to be true and I quickly found out that it was...after downloading and installing the Hyper-V Manager MMC into my vista machine I found I could not connect to the server. found this odd as the very purpose of this server is too allow connections. Turns out there were a few steps I had to do:

1. I had to add my user account (the vista one) to the server in order to pass my creds through.  I believe that once you have connected to it you can turn this off via the Hyper-V settings panel.
2. I had to turn off the server's firewall (I know, I know this is a bad thing but its a test box that will never see the outside world so...).  You can use the following command netsh firewall set opmode disable
3. I was able to connect to the server...BUT when I tried to create a machine I would get an error about Access Denied.  So I added myself to the Administrators group on the server.  At this point I can now use MMC to do most admin work on the server from my Vista client
4. I then started getting the following when trying to connect: Hyper-V Access Denied. Unable to establish communication between ‘SERVER’ and ‘CLIENT’ .  Funny thing is it would let me create a virtual machine but I could never seem to connect to it.  This one was quite confusing so I turned to my trusty friend Google to help me resolve this...I came across a blog post of one Adrian Dimcev here and it had the solution I was looking for.   Word for word heres the instructions from his site:
   • Click Start, Run, type DCOMCNFG. Click OK.
   • Expand Component Services, expand Computers. Right-click on My Computer and click on Properties.
   • Click on COM Security.
   • In the Access Permission area, click Edit Limits.
   • Select ANONYMOUS LOGON in the Group or User Name area. Then set the Permissions for ANONYMOUS LOGON to Allow for Remote Access.
5. After the previous breakthrough I got the following error (oh joy)  : The application encountered an error when attempting to change the state of the 'machinename'.  The hypervisor is not running....WHAT????? Ummmm yes it is......
   Ok turns out there is a very good reason for this as explained here in this Microsoft article.  All I had to do here was enable hardware-assisted virtualization in the BIOS.  After doing that it I was able to create my first machine in this environment == Ubuntu 9.

After reading a little further on the internet it seems that my setup at home (using a workgroup) is not the best way to do this and is partly to blame for some of mine and other peoples issues.  All in all the installation was a success but seems a little more confusing than installing ESXi.  Either way my environment is up and running.

Technorati Tags: hyper-v, Linux, server, virtualization, Windows