July 30th, 2012 by ian0x0r
After a couple of days now playing with the Beta of Veeam Explorer, all I can say is I’m thoroughly impressed with the product. It makes single mail item recovery a doddle. There were a couple of things which struck me for feasibility use case for the product.
The first being dependent on your Exchange mailbox deleted item retention period and your Veeam Exchange backup retention period. If the Veeam backup on disk is shorter than deleted item retention, then there may never be a need a need to use this.
The second being permissions. I was able to browse anyone’s mailbox with my administrator account from within the backup, which does not have access to these mailboxes in the Exchange organisation. That said though, you need to have appropriate permissions to be able to launch the Veeam backup in the first place, so this can be controlled at the backup recovery level.
As promised, here’s the link to Beta download: http://www.veeam.com/beta_invite/5b146deece82af279f0a6a7e680d3706/ Have a play, make your own mind up. Enjoy!
February 5th, 2012 by ian0x0r
Came across a strange one today. Got the error message in the title. A bit of further digging revealed that the windows installer service would not start with Error 14007: The requested lookup key was not found in any active activation context.
The source of the problem stems from a P2V with VMware converter. For some reason it had disabled the DCOM Server Process Launcher service. Re-enable this and reboot the VM, the problem should be resolved.
November 11th, 2011 by ian0x0r
In Exchange 2007 or 2010, you do not have an option to specify a recipient for “send a copy of NDR reports to” from within Exchange management console.
In Exchange 2007/2010 you have the option to specify a recipient for internal and external NDR messages. By default, email@example.com receives the external NDR messages.
The Powershell command to set an internal recipient for NDR’s is:
“Set-OrganizationConfig -MicrosoftExchangeRecipientReplyRecipient <Recipient Identity>”
so to set Administrator to be the recipient the command would be:
“Set-OrganizationConfig -MicrosoftExchangeRecipientReplyRecipient “Administrator”
The Powershell command to set an alternate external recipient for NDR’s is:
“Set-TransportServer <Hub Transport Server Name> -ExternalPostmasterAddress <External Postmaster SMTP Address>”
So to set this again for the administrator account type:
“Set-TransportServer HUB1 -ExternalPostmasterAddress firstname.lastname@example.org“
If you need to increase the maximum message size for the NDR message to match the maximum inbound message size for your Exchange organisation, the Powershell command is as follows:
“Set-TransportServer -ExternalDsnMaxMessageAttachSize <FileSizeInBytes>” and
“Set-TransportServer -InternalDsnMaxMessageAttachSize <FileSizeInBytes>”
So to set the value to 30MB for example, the command would be:
“Set-TransportServer -ExternalDsnMaxMessageAttachSize 31457280″.
You can check the current size by running:
“Get-TransportServer | fl ExternalDsnMaxMessageAttachSize,InternalDsnMaxMessageAttachSize”
NOTE: For Exchange 2010 you will have to substitute TransportServer with TransportConfig so “Get-TransportConfig | fl ExternalDsnMaxMessageAttachSize,InternalDsnMaxMessageAttachSize”
The reason you may chose to increase the max message size for NDR is to retain any large attachments that have been rejected for delivery to a users mailbox.
If you are looking to catch the NDR’s for messages that are too large you also need to add the DSN for large messages to Exchange 2007. You can do this in the exchange management console by going to:
- In the console tree, click Organisation Configuration, and then click Hub Transport.
- In the result pane, click the Global Settings tab.
- In the action pane, click the Properties link that is directly under Transport Settings.
- Click the Message Delivery tab. In the DSN area, do one of the following:
- To add a DSN code, enter the 3-digit DSN code as x.y.z, and then click Add.
- To edit an existing DSN code, select the DSN code, and then click Edit. Modify the DSN as necessary, and then press Enter.
- To remove an existing DSN code, select the DSN code, and then click Close.
Or in powershell run the command:
“Set-TransportConfig -GenerateCopyOfDSNFor 5.2.3″
Note If you run the above command in powershell it will remove any exisiting DSN codes. You have to enter all codes into the command at once, so make a note of exisiting DSN
5.2.3 is the DSN code generated in the NDR when a mail does not reach the recipient because it is too large.
October 17th, 2011 by ian0x0r
If vCenter was in linked mode running version 4.1 and you upgrade to version 5, when you try to join linked mode again you may find that you receive an error along the lines of Operation “Join instance VMwareVCMSDS” failed: : Action: Prepare for Join
1.From a command prompt with administrator-level privileges, change directories to the vCenter Server installation directory.
2.Delete the VMwareVCMSDS directory.
3.Recover the local LDAP instance by typing jointool.bat recover.
If all is well you should see the VMwareVCMSDS has been repopulated by running “jointool.bat recover”
Now try and run the join linked mode vCenter operation again, hopefully this time it will work.
Help with VMwareVCMSDS from http://www.vmware.com/support/vsphere4/doc/vsp_esxi40_vc40_rel_notes.html