Matt_Renato

You can but they require sensors a bit like a Wiimote.

What sort of screen have you got in the cabinet? The older lightguns require a CRT and won't work with newer displays.

This should work if you have the proxy addresses in a single column in you CSV separated by a semi-colon Import-CSV "C:\Scripts\Proxy.csv" | ForEach-Object { $name = $_.user $proxy = $_.proxyaddresses -split ';' Set-AdUser -Identity $name -Add @{proxyaddresses = $proxy} }

Here is some simple code to get you started. It assumes you have the username and default path for each user stored in a CSV file with the headers Username and Path ### Enter path to CSV $CSVPath = "C:\Powershell\UserDetails.csv" ### Import the CSV $CSVImport = Import-CSV $CSVPath ### Grab the username of the logged on user, match it with the file path and set it to the variable $UserPath $UserPath = ($CSVImport | ?{$_.Username -eq $env:username}).Path ### Display the variable in the console Write-Output $UserPath You will need to change the path to the CSV to match the location on your system. The script sets the path value for the logged on user to the variable $UserPath, the last line just displays the variable in the PowerShell console. The built in help for PowerShell is pretty good and it can be accessed directly from the console. If you wanted to find out more about the Import-CSV cmdlet I've used in the above example you can just type Get-Help Import-CSV The are some good videos on YouTube too.

For anyone looking to use Microsoft Azure to store their backups this might be of interest.

Can you get it to work if you follow through the steps here?

A guide on PST import for Office 365. The practicality of this will depend on the number and size of the PST files you need to import as well as the speed of your internet connection. If you are setting up a new tenancy I would always recommend linking it back to your on site AD. It makes controlling accounts and password so much simpler. You can still do this if you import the old emails via PST.

Glad that solved it because I was all out of ideas! As for the cause, I would guess that some program applied the setting back when you were using a proxy at the school. It's possible to set the WinHTTP proxy to use whatever settings have been configured in IE with this command. netsh winhttp import proxy source=ie Even if the proxy settings in IE are then removed, they will remain for the WinHTTP proxy. This article is a really good explanation on how the different proxy settings in Windows work.

It's a long shot but try running this from an elevated command prompt netsh winhttp show proxy It should come back saying Direct access (no proxy server). If it doesn't and it shows a proxy server make a note of what it is (just in case we need to add it back later), and then run the following to remove it. netsh winhttp reset proxy If you do need to add the proxy setting back in it can be done with this netsh winhttp set proxy proxy.address:PORT

Do you have a proxy set under the connection settings in Internet Explorer at work?

Did you use the same machine at work and at home?

Does this help? https://support.office.com/en-us/article/Manage-mobile-devices-in-Office-365-dd892318-bc44-4eb1-af00-9db5430be3cd From the screenshots it looks like it's using the older version of the portal. I think the same page can be reached from Resources > Mobile management in the new portal. Just had a look at this on our demo site and I couldn't get the page for the CSR to display on the new version of the portal.

No problem, glad you got it working.

If you're using the new portal load the Active Users view then click the "More" drop-down there will be an option to setup multi factor authentication. If you select that you will be presented with a list of users and their multi factor authentication status, just search for the account you are using to log in with. If you are using the old portal the same page can be accessed via a setup link at the top of the active users page. The other thing that could be preventing it from working could be any filtering you have in place. If you are able to it might be worth testing on your home connection to rule that out.

If you just launch Powershell and type connect-MsolService without any switches does that allow you to connect? It will also fail if you're using an account with multi factor authentication, does that apply to the account you are trying to log in with?

Once it's installed and setup it tends to require very little support. The latest version even updates automatically.

It's useful to be familiar with as there are some things which can't be done through the portal.

My bad, you'll need the Azure AD cmdlets for Powershell too. https://technet.microsoft.com/en-ca/library/jj151815.aspx#bkmk_installmodule

The below Powershell code will update the depart from a CSV file. The first column in the CSV needs to have the header login and should contain the email address the user logs in with. The second column should have the header department and needs to contain whatever value you want the department to be set to. Change the variable $CSVPath in the code below to point to the location of the CSV file. You might also need to install the Microsoft Online Services Sign-in Assistant which can be found here https://www.microsoft.com/en-gb/download/details.aspx?id=28177 ### Enter path to CSV $CSVPath = "C:\Scripts\Users.csv" ### Import the CSV $CSVImport = Import-CSV $CSVPath ### Connect to O365 Connect-MsolService ### Run through each user in the CSV and update their department $CSVImport | ForEach {Set-Msoluser -UserPrincipalName $_.login -Department $_.department }

How many users do you have? If you can get the details into a CSV then it isn't a very complicated Powershell script to update each user.

Interesting about the part where they say they will allow you to host your own servers. Certainly something to keep an eye on.

The other option is to get your hands dirty with some Powershell.

You can create custom filters (these are called views in the old admin portal), which might be possible depending on what information you included when you created the accounts originally.

Right just this second sent you another invite, let me know if you receive it.

Just done a quick bit of digging for you and found this on the official Xbox forums I'm assuming the first doesn't apply, but have you had any bans or warnings from Microsoft?