Καλησπέρα στην κοινότητα. Θέλω να μοιραστώ μαζί σας τα προβλήματα που αντιμετώπισα σήμερα σε ένα Hybrid Configuration με Exchange 2010 SP3 UR6. Δεν είναι κάτι τραγικό, ούτε κάτι που δεν έχουμε αντιμετωπίσει στο παρελθόν αλλά πιστεύω ότι όσο μοιραζόμαστε τόσο μαθαίνουμε.
Παραλείπω τα αρχικά, Domain verification, DirSync, Certificate request, το Outlook Anywhere ενεργό, όλα τα virtual directories φαίνονται μια χαρά, telnet 443 μια χαρά, OWA μια χαρά, γενικώς καλά και φτάνω στο Hybrid Wizard.
When we create a VM on Azure, at the same time we create a Cloud Service. Later we can create more VMs on the same cloud service. Each cloud service has a unique Public IP. For as long the Cloud Service has at least one VS running this Public IP remains the same. If all VMs of a Cloud Service are off then the Public IP is released and next time the VM is powered on it will take a new Public IP.
Using PowerShell we can reserve a Public IP for as long as the Cloud Service exists, with or witho
Today I received my copy of the Lync Server Cookbook, from Packt Publications. I am one of the reviewers of the book.
The link to the book is: https://www.packtpub.com/networking-and-servers/lync-server-2013-cookbook
The DirSync by default runs every three hours. And you will realized that there is no GUI way to change that. To change the sync interval we need to change a configuration file. 1. Go to the below directory on your DirSync Server: C:\Program Files\WindowsAzureActiveDirectorySync (there are two similar directories, one with spaces between the words and one without. We want the one without spaces) Here we will find the main executable of the DirSync Scheduler, the “Microsoft.Online.DirSync.Schedul
This is a fast way to manage Calendar permissions of a mailbox. Same commands are for both Exchange on-premises and Exchange Online (Office 365). For Exchange Online first connect Powershell to Office365, as described to previous posts.
# To check current permissions
Get-MailboxFolderPermission -Identity "firstname.lastname@example.org":\calendar
# To add calendar permissions, permission can be Editor,Reviewer,Author etc
Add-MailboxFolderPermission -Identity "email@example.com":\calendar -User "mana
You can easily provide Full Access Permissions using the GUI, just Edit the mailbox you want, go to Mailbox Delegation and provide Full Access. Both Exchange 2013 and Online is the same. But if you have to provide Full Access massively then you need PowerShell.
The command for a single user is:
Add-MailboxPermission -Identity "employee" -User "manager" -AccessRights FullAccess
with that command user “manager” will be granded with Full Access permissions to user “employee”
Now lets see
1. Check if the password is set to never expire for one user:
Get-MSOLUser -UserPrincipalName username | Select PasswordNeverExpires
2. Check if the password is set to never expire for all users:
Get-MSOLUser | Select UserPrincipalName, PasswordNeverExpires
3. Check if the password is set to never expire for a list of users:
create a txt file listing the required users, line by line with title “username”, and save it as c:\pwdexpire.txt, like this:
username testuser1 test
Αυτό το post είναι οι σημειώσεις μου από διάφορα migrations Exchange 2007 & 2010 σε Office 365 Hybrid Deployment. Για Exchange 2013 είναι σχεδόν το ίδιο, αλλά αρκετά πιο εύκολο! Όπως είπα είναι οι σημειώσει μου μαζί με διάφορες προσθέσεις από διάφορα blogs, κάτι σαν Checklist και όχι Tytorial ή Guide.
1. Τι χρειάζεται: 2 x ADFS NLB (for identity federation) 2 x ADFS Proxy Servers NLB (for identity federation) 1 x domain member server for DIrSync 1 x SQL 2008 R2 server that will store the
To move a mailbox to Exchange Online from Exchange 2013 first connect Windows PowerShell to Exchange Online with a Global Administrator:
$UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/-Credential $UserCredential -Authentication Basic -AllowRedirection Import-PSSession $Session Provide the on-premise administrator credential
Then connect to the local Exchange 2013:
This post is bout Exchange/Office 365 Hybrid Deployments, when for some reason we need to completely delete a user account and mailbox from Office 365 in order to re-sync it.
First you need to exclude the user from DirSync
Open the “Synchronization Service Manager” (cn be fount at “C:\Program Files\WindowsAzureActiveDirectorySync\SYNCBUS\Synchronization Service\UIShell\miisclient.exe”)
Navigate to “Metaverse Search” and click on “Add Clause”
Be sure that you choose Displayname as Attri
Microsoft offers for free it’s antimalware service. When you create a new VM you have the option to enable it. This will install the System Center Endpoint Protection client to the VM managed by Azure. If you have added this but now you want to remove it and add some other antivirus/antimalware solution you cannot do it by just uninstalling the client from the VM. The client will auto re-insalled by Azure. There are two ways to completely uninstall the program and remove it from Azure. One is us
I was looking for a free solution to have an email notifications for Azure backup. After reading other blogs and technet site I end up to use PowerShell Send-MailMessage attached to the Azure Backup Logs. In short, when the Azure Backup log is created, the script lists the last 2 days events, creates an html file and mails the report with the html as attachment to you.
First find the Azure backup Event Log, it under “Applications and Services Logs, CloudBackup, Operational” and select to att
There are many reasons to have your Disks stored at separate Storage Accounts, per Cloud Service. One is that a Storage Account in Azure provides 20000 IOPS and every disk in Standard Tier 500 IOPS. Azure support suggests to don’t have more than 40 disks per Storage Account. Also you may want to have your disks lined (go to Azure, Cloud Services, selsect a Cloud Service and you can see the “Lined Resources” tab, there you can link storage accounts to the Cloud Service) to the same Cloud Services
First of all, the VM must be within a virtual network to be able to add a static Private IP address
There are two ways to set a static private IP. One is using the new Azure Portal "portal.azure.com" and one via PowerShell.
Using the new Portal, browse a VM, select settings and then IP addresses. There at the Private IP address you can select "Static" and add the IP address.
Using PowerShell, first connect to the Azure (details on this post), and use the following commands:
First we need to install the Azure PowerShell module from http://go.microsoft.com/fwlink/p/?linkid=320376&clcid=0x409
Then open PowerShell and follow the below commands:
#Get your subscription file - The browser will open, you will need to login to the Azure Subscription and finally it will download the <subscriptonname>.publishsettings file Get-AzurePublishSettingsFile
#Connect to your Subscription Import-AzurePublishSettingsFile -PublishSettingsFile "full path to download