SharePoint WFE install.

-
We have a Microsoft Office SharePoint Services 2007 (MOSS) farm and I was asked to add a new web front end (WFE) server to help with capacity.

Pretty simple process so I built a 64bit Windows 2003 server.  Fine.  Installed the MOSS binaries.  Fine.  Installed the language packs.  Fine.  Ran the Configuration Wizard.  oh.

I got an interesting problem where the wizard couldn't connect to the database, and infact caused a .Net exception!  After some Google-ing I couldn't find anything which directly mapped to my issue, mainly based on permissions. 

Then I remembered that we are running MOSS SP1.

So I installed SP1 for MOSS and everything worked.  Hoorah.  Just a stupid error message which could led you down the garden path.

Comments

Post a Comment

Popular posts from this blog

NetScaler VPX and Exchange 2010

-
Image
From the title you can guess that we have Exchange 2010 (SP1 CU6 - with Hotfix for EVault) and we are using NetScaler VPX to load balance the services.  I used the excellent document from Citrix to configure the NetScalers (we have two in active/active - sort of using VMACs to split the traffic RPC to one, HTTP(S) and SMTP to the other). However I found a document from Microsoft which points out that there is "significant performance penalty" if we configure incorrect persistence for EAS.  The Microsoft document is here: http://technet.microsoft.com/en-us/library/ff625248.aspx This put us in a pickle and no mistake.  This is because in a NetScaler persistence is per vServer.  We have one vServer for HTTPS as we have one IP address for all HTTP traffic.  This vServer would then deal with all HTTPS traffic including OWA,ECP,EWS,RPC over HTTPS and EAS.  OWA requires cookie based persistence, this is also the method the Citrix doc...
Read more

PXE booting, MDT and 802.1x

-
Image
Oh dear. We implemented site wide 802.1x when we moved. This has caused numerous issues which we are still tracking down and killing with fire. Again "only-when-we-needed-it" struck as we had a new starter and need to build a machine. Ah.   No PXE.  However thankfully we were able to make a bootable USB using 802.1x and get our build working again from MDT in our 802.1 environment. Here's how we did it.   Caveats:  I'm assuming you know MDT and how PXE works. We use Computer certificates as the 8021x auth method. 802.1x is working in our environment GPO is used to start the wired 802.1x service on built machines. GPO is used to configure the network profile to use 802.1x What you need Get a USB stick to take your WinPE 4GB may be enough Make sure you are running an up to date working MDT installation! Create a machine certificate which has a long expiry date, you don't want to be making USB WinPE images every month!! Export the machine ...
Read more

MDT and Dell BIOS updates

-
I have read a lot on how to implement a BIOS update but was unable to get any of the previous postings to work. So I incorporated some ideas into my own solution. I used both WMI queries and MDT applications.  The structure is set up so only the correct BIOS is applied to the correct model and only if the device requires the BIOS update. How I got BIOS updates to work... Download any BIOS updates you need and put them into separate applications Use the -noreboot -nopause as arguments Check the Hide this application in the Deployment Wizard Add a new group, called "BIOS Updates" to the relevant Task Sequences within the State Restore group and move it above the Install Applications action. Add a sub-group to "BIOS Updates" for the model of machine you are deploying example: Latitude E7240 Open the group and click the options tab create a WMI query - change the value to match the model number you are working on, this limits the scope to only those...
Read more