Simply end the process and PowerShell.exe will start back up immediately. Once that has done, take a look at the Exchange installation process, and you will notice that it will complete within about 15 seconds or so of stopping this process.
Showing posts with label Exchange 2007. Show all posts
Showing posts with label Exchange 2007. Show all posts
07 December 2016
Exchange 2007 Uninstall Hanging on 'Remove Exchange Files'
I was recently decommissioning an Exchange 2007 server for a client. When I was going through the installation process, I noticed that it was hanging at the 'Remove Exchange Files' section.
After giving it sufficient time to complete on it's own, I had to go into the Task Manager to stop the PowerShell.exe task.
23 November 2016
ExportO365UserInfo.ps1 | You cannot call a method on a null-valued expression
Recently I was performing an Office 365 migration for a client who's on premise Exchange environment was 2007. Once I had migrated the mail boxes, I needed to convert the users to Mail Enabled Users (MEUs). This is explained on Microsoft's website here.
There are two scripts you're required to run. When you're running the first one, which is ExportO365UserInfo.ps1, the MS website states you need to do this from EMS. This is incorrect. If you run this script from EMS, you will get the following error message:
You cannot call a method on a null-valued expression.
At C:\migrace\ExportO365UserInfo.ps1:53 char:52
+ $CloudEmailAddress = $CloudEmailAddress.ToString <<<< ().ToLower(
).Replace('smtp:', '')
+ CategoryInfo : InvalidOperation: (ToString:String) [], RuntimeE
xception
+ FullyQualifiedErrorId : InvokeMethodOnNull
In order to get around this, and to make the scirpt work, simply run this in normal Powershell instead of EMS. It will work well and it will create the required cloud.csv file.
Once you've done that, you can run the second command within EMS for it to work well.
Winthrop Australia provides IT Support and Consultancy in the Perth area.
There are two scripts you're required to run. When you're running the first one, which is ExportO365UserInfo.ps1, the MS website states you need to do this from EMS. This is incorrect. If you run this script from EMS, you will get the following error message:
You cannot call a method on a null-valued expression.
At C:\migrace\ExportO365UserInfo.ps1:53 char:52
+ $CloudEmailAddress = $CloudEmailAddress.ToString <<<< ().ToLower(
).Replace('smtp:', '')
+ CategoryInfo : InvalidOperation: (ToString:String) [], RuntimeE
xception
+ FullyQualifiedErrorId : InvokeMethodOnNull
In order to get around this, and to make the scirpt work, simply run this in normal Powershell instead of EMS. It will work well and it will create the required cloud.csv file.
Once you've done that, you can run the second command within EMS for it to work well.
Winthrop Australia provides IT Support and Consultancy in the Perth area.
21 November 2016
Un-hide users from GAL
Exchange 2007
I am in the middle of running an Office 365 migration and during this migration, it's required that I un-hide the users from the GAL (disabled users) in order for O365 to recognise them and migrate them.
My client wants the disabled user's mailbox migrated and then converted to a Shared Mailbox in order to maintain an archive of the mail. In order to do this, we need a list of all the mailboxes that are hidden, then we can hide them. Once we're done we can use that same list to hide them again.
Generate CSV for all mailboxes hidden from the GAL
Get-Mailbox | Where {$_.HiddenFromAddressListsEnabled -eq $True} | Select Identity, HiddenFromAddressListsEnabled | export-csv c:\HiddenFromGAL.csv
Set $Users parameter
$users = import-csv C:\HiddenFromGAL.csv
Un-hide the hidden users
Foreach($_ in $users) {Set-mailbox $_.identity -HiddenFromAddressListsEnabled $false}
This will then allow you to perform the migration (in this case I am doing a Staged migration) without O365 failing to find the user accounts. Once you're done, simply repeat the last two stages. The final stage, change $False to $True.
Contact Winthrop Australia to find out how we can provide you with IT Support in Perth.
I am in the middle of running an Office 365 migration and during this migration, it's required that I un-hide the users from the GAL (disabled users) in order for O365 to recognise them and migrate them.
My client wants the disabled user's mailbox migrated and then converted to a Shared Mailbox in order to maintain an archive of the mail. In order to do this, we need a list of all the mailboxes that are hidden, then we can hide them. Once we're done we can use that same list to hide them again.
Generate CSV for all mailboxes hidden from the GAL
Get-Mailbox | Where {$_.HiddenFromAddressListsEnabled -eq $True} | Select Identity, HiddenFromAddressListsEnabled | export-csv c:\HiddenFromGAL.csv
Set $Users parameter
$users = import-csv C:\HiddenFromGAL.csv
Un-hide the hidden users
Foreach($_ in $users) {Set-mailbox $_.identity -HiddenFromAddressListsEnabled $false}
This will then allow you to perform the migration (in this case I am doing a Staged migration) without O365 failing to find the user accounts. Once you're done, simply repeat the last two stages. The final stage, change $False to $True.
Contact Winthrop Australia to find out how we can provide you with IT Support in Perth.
Office 365 Migration | Unable to create endpoint | Unable to connect to remote server
I recently was running through an Office 365 Migration (Staged) where I was trying to create the Migration Endpoint. As I was going through the configuration I was getting the following error message:
After manually typing in the details, I got the following message:
This one was a tricky one as I was running the test through the 'Test Exchange Connectivity' website, and it was all passing without issues. So it wasn't an autodiscover issue from what I could see.
After looking into this one for a few hours and not being able to find what the issue could be, I came across an issue with the Autodiscover and IPv6. When I was on the on-prem exchange server and I tried to ping the FQDN, it resolved an IPv6 address, even though this was disabled on the NIC.
To get around this, I had to edit the Hosts file on the server itself to resolve the IPv4 address when I pinged the server name, and hte FQDN. After doing this, when I went through the process to create the new migration point, I was able to get past this point and it discovered the server details automatically.
14 June 2016
Exchange 2007 Uninstall hangs on Remove Exchange Files
Today I was decommissioning an Exchange 2007 server for a customer. The uninstall process got down to "Remove Exchange Files" where it just hanged and did not proceed. The environment was running Exchange 2007 SP2 on Windows Server 2008 Standard SP2.
After a quick search I found that I ran into a known uninstall issue. The hanging in removing the Exchange files is caused by a final Powershell script that won't run so instead of ending in failure it just hangs and gives the appearance that it is still processing the removal.
All you need to do is open task manager and kill powershell.exe. Doing this will automatically spawn a new Powershell and allow the removal to complete. In my situation, the removal completed within 10 seconds of the new Powershell launching.
After a quick search I found that I ran into a known uninstall issue. The hanging in removing the Exchange files is caused by a final Powershell script that won't run so instead of ending in failure it just hangs and gives the appearance that it is still processing the removal.
All you need to do is open task manager and kill powershell.exe. Doing this will automatically spawn a new Powershell and allow the removal to complete. In my situation, the removal completed within 10 seconds of the new Powershell launching.
Subscribe to:
Posts (Atom)