I rarely ever edit anything having to do with UEFI, but I found a situation where I was getting "invalid partition table" on a new Windows 7 installation from DVD.
The problem was that I was booting to the DVD from UEFI and then botting Windows from legacy BIOS (or so I think). When pressing F12 on my Dell Latitude E7240, I got these options:
I was booting to the DVD ROM using "UEFI: HL-DT-ST DVD+/-RW GU60N"
However, presumably when the machine rebooted, it was trying to boot from the legacy hard drive. If I booted to the UEFI hard drive when botting from the UEFI DVD drive, it would work. But if booting to the Internal HDD from the legacy boot, I get "invalid partition table."
That's my theory as to why I was getting "invalid partition table"
Based on a sample size of one, this holds true.
Showing posts with label legacy. Show all posts
Showing posts with label legacy. Show all posts
Wednesday, July 1, 2015
Monday, July 14, 2014
Moving Legacy X.500 addresses to Office 365 from on-premise servers
I migrated from SBS 2003 to Office365, but I didn't use one of the standard method. I recreated the users in the cloud and impored PSTs via Outlook. This works fine except for the problem with internal routing where internal addresses use X.500 addresses and generate NDRs when sending to internal staff.
This is a helpful article on using the NDR text to create the X.500 address, though I found its instructions not quite right.
http://support.microsoft.com/kb/2807779
In my case, I found a slight adjustment needed to make it work.
Let's say you're getting an NDR that says:
IMCEAEX-_O=DOMAIN_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=JSMITH@namprd07.prod.outlook.com
For the user jsmith, create a new Exchange email address with a type of X500 (no period in the type - it is X500 not X.500), and enter the value with adjustments as suggested by MS in the article above:
Replace any underscore character (_) with a slash character (/).
Replace "+20" with a blank space.
Replace "+28" with an opening parenthesis character.
Replace "+29" with a closing parenthesis character.
Delete the "IMCEAEX-" string.
Delete the "@mgd.domain.com" string.
Add "X500:" at the beginning.
It looks like this. It takes 5 to 10 minutes or so from when you add the email alias until it works, but it does work when you do it.
This is a helpful article on using the NDR text to create the X.500 address, though I found its instructions not quite right.
http://support.microsoft.com/kb/2807779
In my case, I found a slight adjustment needed to make it work.
Let's say you're getting an NDR that says:
IMCEAEX-_O=DOMAIN_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=JSMITH@namprd07.prod.outlook.com
For the user jsmith, create a new Exchange email address with a type of X500 (no period in the type - it is X500 not X.500), and enter the value with adjustments as suggested by MS in the article above:
Replace any underscore character (_) with a slash character (/).
Replace "+20" with a blank space.
Replace "+28" with an opening parenthesis character.
Replace "+29" with a closing parenthesis character.
Delete the "IMCEAEX-" string.
Delete the "@mgd.domain.com" string.
As an example, I turned this:
IMCEAEX-_o=ExchangeLabs_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=e0c06d4eee7e4ec8b8a38d105ca7793c-joe@namprd08.prod.outlook.com
into this:
/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=e0c06d4eee7e4ec8b8a38d105ca7793c-joe
In the case above, I moved an Exchange mailbox from one account to another (via exporting the old mailbox to PST and importing into a new mailbox on a new account).
Subscribe to:
Posts (Atom)