Sometimes, even you work with things awhile, some shiny stuff get discovered :-) You missed sometimes a stupid easy wildcard search für Usernames in Office 365 for Powershell? –> Here we go…
xxxx = simple search string –> ‘contains’ OR ‘end with’ OR ‘starts with’ …whatever you like to know…
|
1 |
Get-MsolUser -SearchString xxxx |
simple? yes :-)
cheers, Alex
sdfsf
Issue – In the beginning of your Tenant-Creation you have played around with some cloud-only user, you gave them an E1, or E3/4 License or licensed Exchange Online solely. Last but not least, you provide this MSOL-User with a valid smtp alias.
Now, you are stepping forward in project and you establish a Directory Synchronization either with DirSync, AADSync or the soon coming AAD Connect tool. After the sync you realize that in Office 365 still the old username is valid and neither the UserPrincipalName (UPN) or the choosen Alternate Login Name, get used as a new Username for login. Username is still the “old” one -> “whatever@YourTenantName.onmicrosoft.com”
Solution – Even the softmatch is merging your cloud-only ID with the on premises Active Directory Object, you have to change the Username manually in Office 365 with following Powershell Cmdlet:
|
1 |
Set-MsolUserPrincipalName -UserPrincipalName 'Current UPN' -NewUserPrincipalName 'New UPN' |
cheers, Alex
Issue – Running Exchange 2013 Hybrid Configuration Wizard (HCW) fails at the very beginning with following error:
Unable to access the Federation Metadata document from the federation partner. Detailed information: “Unable to connect to the remote server”
Solution – This is mostly related to a missing Proxy-Server configuration which is in between your Exchange on premises server and Exchange Online.
Firstly, you should check that the Internet Explorer has the right entries:
Secondly, check your winhttp settings with:
|
1 |
netsh winhttp show proxy |
If there a “Direct” connection is configured you should import your IE settings with:
|
1 |
netsh winhttp import proxy source=ie |
Thirdly, also check your Exchange 2013 Server for a correct setting:
|
1 |
Get-ExchangeServer -Identity yourservername | select *proxy* |
If that is empty, set the correct values:
|
1 |
Set-ExchangeServer -Identity yourservername -InternetWebProxy http://10.200.200.200:8091 |
Note: If your company security division forces a Proxy Authentication for that, this stuff is broken for ever ;-) – So get rid of that proxy authentication, at least for that piece of Exchange Server. There are ways to handle proxy auth but to be honest –> KIS – Keep it simple!
Finally, your HCW should allow to get finished now :-)
cheers, Alex
“51 4.7.0 Temporary server error. Please try again later. PRX4” You will find this error on following situations:
a) Tony wrote already a very good blog about one clue: http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages/
b) …and that is a tricky one on the right hand and so simple on the other hand -> Check:
|
1 |
Get-ServerComponentState –id ServerName |
If your HubTransport is on “Draining” – perform this:
|
1 |
Set-ServerComponentState -identity ServerName -Component HubTransport -State Active -Requester Maintenance |
Mail delivery is back :-)
have fun, Alex
You may receive the error-message: “One or more users currently use a mailbox store on this server. These users must be moved to a mailbox store on a different server or be mail disabled before uninstalling this server.”
Use a newer Server 2008 Domain Controller “Active Directoy Users and Computers” (or 2008 R2 / 2012 / 2012 R2) and perform a “Find” for all of your users inside your Domain(s). Extend the search result pane with the column “Exchange Home Server” and you may see (only here!) some users pointing to your legacy Exchange 2003 server.
And now? Go to them with your AD Attribute Editor and clear the Attribute: mxExchHomeServer
Voila, you are ready for the last last call –> de-installation – bye bye Exchange 2003 :-)
cheers, Alex
You may receive the error-message: “Setup encountered an error while checking prerequisites for the component “Microsoft Exchange”: 80072030 (8240): There is no such object on the server.”
and check in your AD Configuration Container: Services -> Microsoft Exchange -> Your Exchange Org -> Global Settings -> Message Delivery. Right mouse -> properties -> msExchAdminMailbox
If there is any orphant object like this:
just clear it an provide any (your choice) existing User-DN (Distinguished Name). Voila, you are ready for the last last call –> de-installation – bye bye Exchange 2003 :-)
Note: This was a mandatory Postmaster-Account in the past
cheers, Alex
and migrate from YOUR source into the Mailbox onPrem. If you are coming from Lotus Notes, I would suggest tools from Binary Tree or Quest
thats for the Delta-Migration time, days or weeks before your Outlook-Rollout. With this you can ensure that already migrated Exchange Online Users can send email to your legacy users
|
1 |
Import-Csv "C:\MigUserGeneral.csv" | ForEach-Object {(Get-Mailbox -Identity $_.EmailAddress | Set-Mailbox -ForwardingSmtpAddress $_.ForwardingSMTPAddress)} |
Example for this “MigUserGeneral.csv”
|
1 2 3 4 |
EmailAddress,ForwardingSMTPAddress,UserPrincipalName,License,UsageLocation,MBXLanguage,TimeZone Donald.Duck@sleekexchange.net,Donald.Duck@coex.sleekexchange.net,Donald.Duck@sleekexchange.net,"SleekExchange-Tenant:ENTERPRISEWITHSCAL",DE,DE-DE,"W. Europe Standard Time" Daisy.Duck@sleekexchange.net,Daisy.Duck@coex.sleekexchange.net,Daisy.Duck@sleekexchange.net,"SleekExchange-Tenant:ENTERPRISEWITHSCAL",DE,DE-DE,"W. Europe Standard Time" |
Connect your Powershell to Exchange Online
|
1 |
Set-MigrationEndpoint -Identity NameOfYourEndpoint -Credentials (Get-Credential contoso\xxxxxx) |
(Note: If you don’t have already a MigrationEndpoint you have to create one. After this you can re-use this endpoint for each batch over and over. http://technet.microsoft.com/en-us/library/jj218611%28v=exchg.150%29.aspx)
|
1 |
New-MigrationBatch -Name XXX -SourceEndpoint NameOfYourEndpoint-TargetDeliveryDomain YourTenant.mail.onmicrosoft.com -CSVData ([System.IO.File]::ReadAllBytes("c:\user.csv")) -AllowIncrementalSyncs $True -AutoStart -BadItemLimit 100 -NotificationEmails alexander.hofer@sleekexchange.net –PrimaryOnly |
(Note: This CmdLet is without the paramenter -AutoComplete which means that the move will suspend at 95%. Further the flip of the Cloud MailUser to the UserMailbox will not occure. The benefit is, that you can move the big data weeks before and cool down :-) Remember: In this state = AutoSuspend the Migration-Service will contact your MRS-Proxy (Mailbox Replication Service) each 24h and will check for new content, and in the case of new content, move the stuff to the cloud. Here you will find information about the user.csv http://technet.microsoft.com/en-us/library/dn170437%28v=exchg.150%29.aspx
|
1 |
Import-Csv "c:\MailUserGeneral.csv" | ForEach-Object {(Get-Mailbox -Identity $_.EmailAddress | Set-Mailbox -ForwardingSmtpAddress $Null)} |
Remember that Microsoft has already done everything your you. MX Records for @yourtenant.mail.onmicrosoft.com is already in place i.e sleekexchange.mail.onmicrosoft.com
|
1 |
Complete-MigrationBatch -Identity XXX -NotificationEmails alexander.hofer@sleekexchange.net |
(Note: the status AutoSuspend will switch to InProgress and finalize with Completed)
Connect your Powershell to Exchange Online & Office 365
Following Cmdlet will perform:
|
1 |
Import-Csv "MailUserGeneral.csv" | ForEach-Object {(set-MailboxFolderPermission -identity "$($_.UserPrincipalName):\Calendar" -User Default -AccessRights LimitedDetails) ; (get-MsolUser -UserPrincipalName $_.UserPrincipalName | Set-MsolUser -UsageLocation $_.UsageLocation) ; (get-MsolUser -userprincipalname $_.UserPrincipalName | set-MsolUserLicense -AddLicenses $_.License) ; (get-MailboxRegionalConfiguration -Identity $_.UserPrincipalName | set-MailboxRegionalConfiguration -LocalizeDefaultFolderName:$true -Language $_.MBXLanguage -DateFormat "dd.MM.yyyy" -TimeZone $_.TimeZone)} |
(Note: Use same .csv from Step 2)
have fun, Alex
Recently I implemented two KEMP LM2600 at customer site (Exchange 2013 CU3 multi role servers). At the next day customers help desk got a lot of user complaints because battery life time of their mobile phones was reduced dramatically (iPhones using EAS – Exchange Active Sync)
Solution: In Network Options uncheck “Enable TCP Keepalives”
Kemp documentation is recommending this as well http://kemptechnologies.com/files/downloads/documentation/7.0/Configuration_Guides/Configuration_Guide-WUI.pdf
Enable TCP Keepalives By default the TCP keepalives are enabled which improves the reliability of TCP connections that are long lived (SSH sessions). Keepalives are not usually required for normal HTTP/HTTP Services. The keepalive messages are sent from the LoadMaster to the Real Server and to the client. Therefore, if the client is on a mobile network, there may be an issue with additional data traffic.My comment: At the end of the day I am asking why this setting is active per default? And why this can not be set for each VS – Virtual Service? Be aware that this is a global configuration and it my affect other Services / Real Servers. To be honest, this was the first time of seeing such a behavior.
While updating Plugins or WordPress itself you get above error, or in German language “Das Verzeichnis “wp-content” konnte nicht gefunden werden”. As a side-effect, content-upload like picture uploads etc. will work after this instructions very smooth!
Don’t play around with 777 Permissions (like other blogs are doing…) on your folders. Host Europe has an own Security-Modell which make the stuff around more secure on the one hand but make WordPress work more difficult on the other one.
Add two directories to your WordPress Root-Directory with your favorite FTP Programm:your-Root-of-WP/tmp & your-Root-of-WP/wpcontent/upgrade
Add this to the end of your wp-config.php (in the root of your WordPress)
|
1 2 3 4 |
/** HostEurope **/ define ('FS_METHOD', 'direct'); putenv('TMPDIR='. ABSPATH .'tmp'); define('WP_TEMP_DIR', ABSPATH . 'tmp'); |
Login to https://kis.hosteurope.de and change 2 settings:
1. In “Dateiverwaltung” change the user (Benutzer) from “ftpxxxx” to “wpxxxxx”, check “recursive”
2. In “FTP-Zugänge” also change from “ftpxxxx” to “wpxxxx”
Finally: HERE WE GO :-) Have fun with this lifetime safer.
…and you are checking the big picture of your migration status with:
|
1 |
Get-MoveRequest -MoveStatus inprogress | Get-MoveRequestStatistics |
StatusDetail shows: “RelinquishedMDBFailover”
|
1 |
Get-MoveRequest -MoveStatus inprogress | Get-MoveRequestStatistics -IncludeReport | select * |
and you will see something like this:
16.04.2014 06:54:22 [DB3PR02MB060] Relinquishing job because the database failed over to ‘AM3PR02MB051.eurprd02.prod.outlook.com’.cool, isn’t it? :-) MS is performing DAG failovers while you are sweating under your pillow ;-)
cheers, Alex