Do you need to convert an Exchange universal distribution group to a mail-enabled universal security group? You’re in luck! Try it out: In Active Directory Users and Computers, select the distribution group and go to properties. On the General tab, under Group Type, select Security Group. From the Exchange Management Shell, run the following command, substituting groupname for the actual name of the group. Use quotes around the group name if the name contains spaces: Set-Distributiongroup–identity groupname –MemberDepartRestriction Closed
If you use Exchange with OWA, there is a registry tweak that you can use to enable a function that allows Active Directory users to change their password after it has expired. Perform the following on the Exchange 2010 Client Access server: Run Regedit Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange OWA Create a new DWORD value (if it doesn’t exist), called: ChangeExpiredPasswordEnabled Set the value of ChangeExpiredPasswordEnabled to 1 Restart the IIS Services
Say you setup an on premise update server share for Office365 ClickToRun. What if you wanted to use multiple groups so that you didn’t have to deploy an update to your entire organization but didn’t set that up during the initial deployment? Fret not! You can modify this registry key on your clients with the new UNC path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration and modify the UpdateUrl string to reflect the new UNC path.
In this how-to article I am assuming that you have already setup/configured DirSync for Microsoft Office 365 and have found that the “stopped-extension-dll exception error” in the event viewer references an issue with the password of your sync/tenant account. What can cause this? The most common reason that I have found is that the account used to sync with the tenant has an expired password. By default, the passwords for tenant-based accounts expire every 90 days. This is controlled on…