The next thing is you need is Exchange Management tools. (link)

Note that I already had powershell installed, so I’m not sure if you need it before Exchange management tools..Or if the installer will warn you.

Then you will need to install Outlook 2003 or 2007 locally. I went with 2007..

Now for the export. Start up the Exchange management shell and use the following command: Export-Mailbox –Identity “mailboxUser” -PSTFolderPath “pathToSavePST”
(link)

I got an error. It turned out that my admin account did not have the right permission on the mailboxes.

I fixes this with the following command:

Get-Mailbox | Add-MailboxPermission -User “YourUserName” -AccessRights FullAccess
(link)

That’s it.

The problem is that the number of linked clones quickly becomes unmanageable and the need for a good overview is needed. There is such a view, but when I tried to “update usage” nothing happened..

After a lot of searching the web I found a KB page that said that you could change the time-out value in the SQL database. This fixed my problem and I thought I would share it.

Start by modifying the dbo.Config table.

Change the InventoryWait value. I added a zero..It solved my timeout.

Enter MacFusion. A free alternative that does the same thing with a big increase in performance as well!

Download: http://github.com/nall/MacFusion2/downloads

This week I have played around quite a bit with the latest version of ThinApp from VMware (version 4.0.4). The goal have been to make a ThinApp package of Microsoft Office 2007.

ThinApp is a wonderful application!

Today I came across a KB article about the problem with VI-Client in Windows 7.

Link: Cannot launch vSphere Client after installing in Windows 7 or Windows 2008 R2

I had completely missed this feature, witch allows you to resend a mail. Kind of trivial but still, great feature!

via Quick Tip – Send Again.

1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.

2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (+%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+).

3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a <runtime> element and a <developmentMode>element as shown below. Save the file.

<?xml version=”1.0″ encoding=”utf-8″?>
<configuration>
…
<runtime>
<developmentMode developerInstallation=”true”/>
</runtime>
</configuration>

3. Create a batch file (e.g. *VpxClient.cmd*) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,

SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
“%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe”

4. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.

You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.

Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.

Fernando

Via Fernandos post at VMware Communities: vsphere client on Windows 7 rc.

via How-to auto Login to Virtual Center with VI Client.

The only drawback is that it doesn’t support google apps type accounts yet.

via Notify keeps an eye on your Gmail inbox.

via Access Hidden Regional Themes in Windows 7.