Wednesday, January 11, 2006 2:01 PM Jan Tielens

Installing Office "12" Server on a Single Machine

For all the Office "12" Beta testers out there who want to build a nice demo VPC image to show off all the new features: Martin has written a nice step-by-step guide.

Installing Office Server “12” Beta 1 on a single machine (either physical or virtual) is not entirely straight forward and having done it many times, there is a specific process that I go through which always works. In this article, I’ll share what works for me – hopefully it will work for you too!

Please bear in mind that this is just an unofficial guide to getting Office Server installed quickly and easily in a demo / test environment. This guide will not necessarily observe best practices with regard to security etc. For production setups, you should seek guidance from the official Microsoft documentation (on Betaplace). (full post)

Filed under:

Comments

# Something not related!

Thursday, January 12, 2006 4:03 AM by Alex

First of all, I have to apologize for 3 reasons
1. I post something that is not related to the main thread
2. My poor english
3. The rather silly question that is coming...
Here is the stupide question.
I created a Excel Import Webpart that fills up a contact list. Every field is correctly retrieved, but there is the lookup field exception.
I mean, i identify it with a test like follows:
if (list_Contact.Fields[myColumn].Type==SPFieldType.Lookup)

then, i get the list and field from which it is depending
string str_XMLview=list_Contact.Fields[myColumn].SchemaXml;
System.Guid myGUID= new Guid(getGUID(str_XMLview));
SPList list_Lookup = web_CurrentWeb.Lists[myGUID];

and i query this field
SPQuery sps_Query = new SPQuery();
sps_Query.Query = "<Where><Eq><FieldRef Name='"+getField(str_XMLview)+"'/><Value Type='Text'>" + myRow[myColumn]+"</Value></Eq></Where>";
SPListItemCollection sps_coll= list_Lookup.GetItems(sps_Query);

if my ListItemCollection.Count is greater than one (even equals one) i have a match, and accept the data
but when i copy it in the list it is ok until the fatidic
SPListItem item_ContactToAdd =list_Contact.Items.Add();
foreach (string myColumn in strA_ColumnTitles)
{item_ContactToAdd[myColumn]=myRow[myColumn];}
item_ContactToAdd.Update();

and then i have a protected field exception....
SNIF...
SNIf...
SNif..
Snif...
snif...
(crying aber not too loud)
Can you help?
I think that for such a guru it is a problem you already faced and solved, that'a why I dare to disturb you with my ignorance...

# re: Installing Office "12" Server on a Single Machine

Thursday, January 12, 2006 6:04 AM by MikeWalshHelsinki

I don't get this. Martin has in order to get Office Server 12 signed an NDA. In talking about this **publically** at all he is breaking that NDA.

In other words in order to blog this he is risking the eternal wrath of Microsoft. Is it really worth it?

# re: Installing Office "12" Server on a Single Machine

Thursday, January 12, 2006 7:43 AM by Jan Tielens

Martis is an MS employee, I don't think he risks the eternal wrath of MS. :-)

# re: Installing Office "12" Server on a Single Machine

Friday, January 13, 2006 8:17 AM by bob chauvin usa mi

Martin's link is broken...

# re: Installing Office "12" Server on a Single Machine

Tuesday, January 17, 2006 5:04 AM by Lawrence Liu

As the Community Lead for SharePoint Products and Technologies, I want to thank everyone who's evaluating O12 Beta to stick to their NDAs.

Did anyone notice that the said blog entry has been deleted? NDAs apply to internal MS employees as much as they do for non employees. Until Beta 2, only those in the Product Groups should be blogging or talking about O12 features and other info. Beta 1 testers should be using the private newsgroups to ask about and discuss O12, not blogs or other public forums.

# re: Installing Office "12" Server on a Single Machine

Tuesday, January 31, 2006 6:09 AM by Martin Kearn

Hi all, firstly - thanks for the link ;)

The reason that the installation guide has been removed from my blog is because it is a bit early in the product lifecycle to be talking publically at that level of detail.

I'm hoping to re-publish the article around the Beta2 timeframe so keep your eyes peeled as I know how usefull these kinds of things are.

Regards - Martin