$theTitle=wp_title(" - ", false); if($theTitle != "") { ?>
About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like
21 Oct // php the_time('Y') ?>
Yesterday I needed to set a few registry keys remotely from a 32 bit windows machine to a 64 bit machine.
I used reg.exe to set the key but even though it returned success the key wasn’t altered.
As I suspected the key was written to the Wow6432Node. In the help I couldn’t find any switch to force reg.exe to use the 64-bit view.
On a 64 bit machine this is not a problem since both 32- and 64 bit versions of reg.exe exists. The 32 bit version of reg.exe defaults to the 32 bit view and the 64 bit version defaults to the 64 bit view.
But luckily reg.exe has a switch (that is not listed in the help) to force the View:
18 Oct // php the_time('Y') ?>
In Windows 7 and 2008 R2 all IP Addresses are by default registered in DNS.
If you don’t want certain IP addresses to appear in DNS you can alter this behavior with Netsh using the skipassource flag.
Use the following syntax to add an additional IP Address with skipassource flag:
12 Oct // php the_time('Y') ?>
I came across an interesting tool today called Binwalk.
Binwalk is a firmware analysis tool that scans a given binary file for embedded files and executable code.
Binwalk requires a Linux machine, I used the Backtrack VM I used from my article about WEP keys.
Note there is no binary distribution of Binwalk so you will need to compile it but this is a breeze.
4 Oct // php the_time('Y') ?>
Another interesting Move Mailbox error and in this case I am really unsure how this would be possible!
Let’s look at the Move Mailbox log:
1 2 3 4 5 6 7 8 9 10 11 12 | 1-10-2011 11:49:18 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox. <baditem id="0000000088B41EB2A774E14BA3B29759527EBBD007007A08E4E185746A45BF5C6EF2A17E8D5500000590285800007A08E4E185746A45BF5C6EF2A17E8D550000059028720000" flags="0x00000000" errorcode="0x80004005" errortype="MapiExceptionMaxSubmissionExceeded"> <folder id="0000000088B41EB2A774E14BA3B29759527EBBD001007A08E4E185746A45BF5C6EF2A17E8D550000059028580000">Top of Information Store</folder> <sender>John Doe</sender> <recipient></recipient> <subject>archive.pst</subject> <messageclass>IPM.Document.PSTFile</messageclass> <size>38621879</size> <datesent>01/19/2006 14:30:57</datesent> <datereceived>01/19/2006 14:30:19</datereceived> <errormessage>Message (size 36.83 MB (38,621,879 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell. Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242) |
This error occurs because of a size constraint just like the one in the previous part.
But the strange part is that it seems to be a PST file (type IPM.Document.PSTFile) located in the Root folder of the Exchange mailbox (which is not possible AFAIK).
4 Oct // php the_time('Y') ?>
The previous part (part 3) addressed Mailbox Size but did you know that even Message Size (or rather Item size) can prevent a successful move as well?
Here’s an example move mailbox log:
1 2 3 4 5 6 7 8 9 10 11 12 13 | 2-10-2011 3:18:58 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox. <baditem id="00000000469F68BB3AD7E745B2B8A041FC1B688C07007A08E4E185746A45BF5C6EF2A17E8D55000001537A9D00007A08E4E185746A45BF5C6EF2A17E8D55000001540FF30000" flags="0x00000000" errortype="MapiExceptionMaxSubmissionExceeded" errorcode="0x80004005"> <folder id="00000000469F68BB3AD7E745B2B8A041FC1B688C01007A08E4E185746A45BF5C6EF2A17E8D55000001537A9D0000">verzonden nov 2004-aug 2005</folder> <sender>Jane Doe <recipient></recipient> <subject>Foto's afscheid John Doe 10 februari jl.</subject> <messageclass>IPM.Note</messageclass> <size>76121694</size> <datesent>02/15/2005 15:28:06</datesent> <datereceived>02/15/2005 15:28:06</datereceived> <errormessage>Message (size 72.6 MB (76,121,694 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell. Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242) Diagnostic context: |
As you can see in the log this mailbox there is one item with a size of 72 MegaBytes.
Let’s see this in Outlook:
It gets even worse when we open the Message:
It was addresses to several internal recipients and as you know Exchange 2010 no longer supports Single Instance Storage.