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:

Read the rest of this entry »

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:

Read the rest of this entry »

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.

Read the rest of this entry »

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:

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).

Read the rest of this entry »

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:

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.

In Part 2 I showed some details about Mailbox Rule corruptions that can disturb Mailbox Moves.

For this part the topic is Mailbox size, which can be an important factor in deciding which mailboxes you want to move first.

In my case the mailbox size was important because we agreed to move smaller mailboxes during the day but larger mailboxes only outside working hours.

For Exchange 2010 mailboxes it’s very easy to obtain the size using PowerShell.

Example:

But how can we get the Mailbox Size for Exchange 2003 mailboxes?

Read the rest of this entry »

Sometimes I want to process a list of “things” easily in PowerShell where the list is not in an external file but in the script itself.

Ideally this list would not be separated by e.g. a comma so it can be easily copy/pasted from external data sources.

Something like this:

Read the rest of this entry »

If you have read my earlier blogs about the RNS 510 then you may know I have been working on creating custom startup logo’s for some time.

For some time now I know how the images are encoded and decoded between Windows bitmap and the native RNS 510 image format.

Recently I identified the checksums in the image data, and the differing parameters for the Seat, Skoda and VW versions of the RNS 510 firmware.

Read the rest of this entry »

In part 1 we saw that a corrupted rule made the Mailbox Move fail.

I wanted to know if I had really a corrupted mailbox or maybe even corruption in the store or another problem.

So in this part I will describe how to break down the Mailbox Move Log.

First go to the Failed Move Request and select Properties:

Read the rest of this entry »

I am currently working on a migration project from Exchange 2003 to Exchange 2010.

Most Exchange migration projects use Mailbox Moves to move the mailbox data to the new Exchange environment.

But there are some things I observed during Mailbox Moves (from Exchange 2003 to 2010) that are worth mentioning.

Read the rest of this entry »