Networknet.nl Blog

  I received the following error message when opening and running a cmdlet with my Exchange Management Shell:

[PS] C:\Documents and Settings\admin>Export-Mailbox -identity user1 -PSTFolderPath c:\user1.pst
WARNING: An unexpected error has occurred and debug information is being generated: Unable to determine the installed file version
from the registry key ‘Software\Microsoft\Exchange\Setup’.
Export-Mailbox : Unable to determine the installed file version from the registry key ‘Software\Microsoft\Exchange\Setup’.
At line:1 char:15
+ Export-Mailbox <<<<  -identity user1 -PSTFolderPath c:\user1.pst
    + CategoryInfo          : NotSpecified: (:) [Export-Mailbox], TaskException
    + FullyQualifiedErrorId : Microsoft.Exchange.Configuration.Tasks.TaskException,Microsoft.Exchange.Management.RecipientTasks.ExportMailbox

Just looking on the error message it seems that something was missing in the Windows Registry. I opened Registry Editor and browsed to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange. The Setup key was missing. Exchange 2007 management tools were installed to another server than Exchange Server was installed. I logged on the Exchange 2007 server, opened Registry Editor and browsed to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange key.  The Setup folder was visible and I right-clicked on the Setup folder and exported the Setup branch.

I went back to my Exchange 2007 Management installed server and imported the reg file.

After importing the reg file my problem was solved and I had another challenge with Export-Mailbox cmdlet.

After installing VMWare ESX 3.5 hypervisor host server I would like to manage this system with SSH remotely. Server is manufactured by Dell and the DRAC mgmt card interface is available but I prefer to use SSH. SSH is enabled by default but disallows access for root.

See my work log and screenshots how to enable this feature:

• Login with root from the console
• Change directory with “cd /etc/ssh”
• Open sshd_config with “vi sshd_config”

• Locate Authentication section and change “PermitRootLogin no” to “PermitRootLogin yes”; for going into edit mode type i; press ESC to exit

• Type “:wq!” to save and exit the file
• Restart the SSH deamon with “service sshd restart”

• Start putty.exe or any of you favorite SSH remote management tools to connect to your ESX 3.5 server.

This procedure also applies to version 3.x. With this procedure I achieved to manage my ESX server remotely so I don’t need to use my remote management access card. SSH daemon also support secure file copy protocol which can be used to connect with WinSCP and download or upload any file/virtual machine to your VMFS file system.

Please be aware of any security implications! I enabled this kind of access because the management interface is sitting in a different VLAN than the vSwitch networks within virtual machine which are trunked amongst different networks.