Step by Step Directions for Techs
I keep running into this so I thought I would put it up here.
If you have a customer without on-premise Active Directory and they use Office 365, you can leverage that with Windows 10. It is a bit cumbersome for some things, like adding users to the admin group. Here is a workaround:
Regarding the user name: It isn’t the name they login in with. This is the display name all run together. For example, if they are listed as “Bill Jones” in the directory and they login as “bill_jones”, it would be “BillJones”. If they are listed in the directory as “William Jones” (again the display name) but login as “bill_jones”, it would be “WilliamJones”.
Well, you can’t. Have a great day!
Aside from this being super helpful, I have a workaround for you based on this post from Microsoft (it has a few minor errors) – http://social.technet.microsoft.com/wiki/contents/articles/15905.how-to-use-powershell-to-automatically-assign-licenses-to-your-office-365-users.aspx
This file (rename it to ZIP) has the Powershell files: O365LicenseScripts
This assumes that you have the MS Online Services Sign-In Assistant (you already have this if DirSync is installed) and Microsoft Online Services Module for PowerShell (found here http://g.microsoftonline.com/0BX10EN/423).
How to get it working:
If you run Get-LicensingInputFromAD.ps1, you will see what the system thinks the users should be and their corresponding licenses.
If you run AssignLicense.ps1, it will assign the licenses based on what the Get-LicensingInputFromAD.ps1 script output was (stored in the queuedLicense folder created during setup).
If you want to schedule it, you can use the Schedule.ps1 script. I won’t go too far into the weeds, but the command is “powershell.exe” (without the quotes) and the arguement is “-file C:\O365LicenseScripts\Schedule.ps1” (without the quotes).
There is one difference in my scripts. You will find 2 lines that are commented out in case you don’t want to set the license type in Active Directory. I often find that most customers only use one license type, so I put in an attribute to say which accounts get the license and then hard set the license in the script (set it in the TMP file otherwise the setup script will delete your work!).
Who really wants to see all those pesky accounts and groups up in Office 365? Not me (and probably not you if you are reading this). I want to see accounts that I need to give licenses to.
Disclaimer – you can really mess up Office 365. Be careful!
These filters are for things you don’t want. As you can see in the image above, I am filtering for users that DO NOT contain “365” in the ExtensionAttribute15 (you can edit that in Active Directory). By using this, I will only get users that have it. Consider it a “negative filter”.
Now, before you work on this too long, let me give you some hints:
That should get you going. Good luck!
If you need DirSync to initiate a directory synchronization immediately, you can perform the following procedure:
That’s it. I know it isn’t very impressive. Where is the status? How do you know if it worked? I will show you that too!
This gives you the status of all of your jobs that have ran, including the current one that was initiated from the script!
A quick and easy way to see which domain controller authenticated you is to run this command from a command prompt:
Quick and easy.