This caused me a few headaches the other night.

Start off by enabling MPIO support from the command line – “start /w ocsetup MultipathIo” does the trick;

Next run up the MPIO control panel applet – simply “MPIOCPL” from command prompt

On the subsequent window, browse to “DSM Install” and type the path to your hp MPIO driver file. Then click install. It will prompt you to reboot, do so.

Run a disk scan and you will see MPIO isn’t working yet. *sigh* back into MPIOCPL, and go to “Discover Multi-Paths” – you will see a new device here now (that wasn’t there before);

Click the Device Hardware Id and click “Add”. Again, reboot when prompted and run a re-scan when the server is back up – and voila you should have MPIO presented LUN’s!!!

Based around the new CAS access methods, and encryption. Easy enough fix, not a bug more of a “Don’t use Outlook 2003 with Exchange 2010 if you can help it”-ism.

http://blogs.msexchange.org/walther/2009/08/30/exchange-2010-and-outlook-2003-clients-connection-issues/

When installing Beta2 I had issues with getting the 64-bit version of Office installed.

Long story short, it didn’t like me having any 32-bit versions of Office already installed. This seemed logical, so I removed and did a fresh install (installing Visio and SharePoint Designer 2007 (32-bit) afterwards).

However, when I come to upgrade to the Public Beta – I get the same warning message.

Given that I am not “upgrading” SharePoint Designer, or Visio, why am I not allowed to install 64-bit Office 2010?

Grr. Annoying.

I think I found my first bug.

Doing a Easy Install on Server 2008 R2 – first it complains that the key is wrong (though that could just be a copy/paste issue lol) then;

But the Easy Install has finished!! Powered the VM off and back on again, still the same.

Oh well, no VMware tools!

It’s hidden away down at the bottom

But I like it.

It’s like a smaller, more compact Outlook. Everything is there (Clicking the Home / Send/Recieve / Folder / View buttons makes the Ribbon hover up until you click focus elsewhere), yet it feels cleaner and sharper than before.

Now this may just be me, or it may be a beta2-ism.

But my Windows 7 laptop with Office 2010 beta installed will not stay asleep. No matter what I do (closing the obvious applications and even installing the “Microsoft Send a Smile” application) it wakes up, drains my battery, and makes Windows 7 complain about being dirtily shut down.

It could just be Windows 7, it could just be my laptop. It could be the copy of Office 2010 I have (can’t wait for the public beta!), but its darn annoying.

Hibernation seems to work fine though

So I downloaded it and tried it out.

I like it – a lot. And it’s the subtle differences that I like.

For instance – the added support for Windows 7 Taskbar

I have my taskbar vertical (as you can see) – and I like the way I get “Hover Previews” (what is their official name anyway?) of all my favourite Virtual Machines – even the suspended ones!

VMware tools under Linux seems (it may not be, but it “seems”) easier to install – less of the headaches and more “pre-compiled” modules for my Linux operating systems

Not found any real bugs yet (the first I thought I had turned out to be a corrupt ISO download – *sigh*), but will post anything up I can find as I get to using it

Now if only I had a Mac to try out VMware Fusion 3 – but I flattened my “Hack Mac” for Windows 7

I like it.

A lot.

Aside from;

Pointing the new “Social” side of Outlook 2010 at SharePoint 2007 SP2 tells me that “The server version is not supported”.

Why not Microsoft?

I would presume that either;

a) there will be a post-Office 2010 patch for SharePoint 2k7 to make it “supported”

b) Office 2010 users will have to use SharePoint 2010 to integrate into Outlook. Which is a real shame.

Aside from that, thumbs up from me to Microsoft. Only on Beta2 but I like it and cannot wait for RTM (whenever that is!)

UPDATE:

Still doesn’t work with our SharePoint 2007 farm in the Public Beta, however the SharePoint Workspace application (which is new) points that it is only supported in SharePoint 2010 – which now has a public beta.

Still a shame, I wanted to test both features but don’t have an SharePoint 2010 server to point at… Yet.

Having some issues recently with my RC1 laptop;

Whenever I try to open a program that has at some time accessed a network resource on my AD domain, my laptop hangs and I have to hard reboot

I will install RTM over the weekend and see if it persists

There are four places where Message size is set in Exchange – in 2003, these were all in the gui, in 2007 three are powershell (although MS supposedly are adding it back in) and one has no admin tool at all – you get to use ADSI Edit to set it in the "raw" Active Directory. You must however set the parameters in all four places to the same value – the *lowest* of all four is used, as each is applied to the message in turn to decide if it should be rejected.

So, from the top:

Global setting:

—————

The system wide default is held in Active Directory and is set to 10MB by default (this is 10240 K, the setting is just a number but is in K)

Using ADSI Edit, navigate to:

CN=Configuration, CN=Services, CN=Microsoft Exchange,CN=Domain Name,CN=Global Settings,CN=Message Delivery.

Hit the properties on the Message Delivery object and the attributes you want are:

msExchRecipLimit (default 5000)

submissionContLength (default 10240)

delivContLength (default 10240)

However in SP1 these are not set, and you must use PowerShell to set them;

Transport Setting

—————–

Site Default is set in powershell; use Get-TransportConfig to get current settings, then:

Set-TransportConfig -MaxRecipientEnvelopeLimit <nn> -MaxReceiveSize <nn>MB -MaxSendSize <nn>MB

current setting:

Set-TransportConfig -MaxRecipientEnvelopeLimit 5000 -MaxReceiveSize 20MB -MaxSendSize 20MB

Receive and Send Connectors

—————————

Again, we use Powershell. First to list the connectors, you can use the two following commands:

Get-ReceiveConnector

Get-SendConnector

you can get detailed information (including the current settings) by using the Format-List pipe:

Get-ReceiveConnector | Format-List

Get-SendConnector | Format-List

Now, for EACH connector you need to modify, use the following:

Set-ReceiveConnector "<connector name>" -MaxMessageSize <nn>MB

-or-

Set-SendConnector "<connector name>" -MaxMessageSize <nn>MB

Or;

get-recieveconnector | set-recieveconnector –MaxMessageSize <nn>MB