Boredguy

I used a SIMS report to do this and powershell. We now have a group per student that contains all teachers of them, including ones where the class is split over different teachers. Not bad for free. {edit} Attached should be a screenshot of the SIMS report fields I am using

Windows 10 Education is basically Windows 10 Enterprise but without ReFS support, so it should be fine.

There is no longer an educational version of Steam available

Steam isn't exactly designed for a secure environment, so there is not likely any way to prevent users from signing out and then in as themselves, assuming you have the firewall/filtering allowed.

Notepad++ at least @ICTDirect_Dave

We just set our lockscreen/logon wallpaper into C:\Windows\System32\oobe\info\backgrounds, called backgroundDefault.jpg and that path is set in the GPO. Works fine, but does need a 2nd reboot or a logon/off for the fortnightly change to display

MICROSOFT DSKTPEDU ALNG LICSAPK OLV would only cover having the latest version of windows on the client, and the cal to access Server 2019, but would in itself not allow you to install 2019 as that should be a different code from my understanding. Some suppliers do all 3 components (Office, windows upgrade and cals) in 1 bundle, others in the 3 separate ones depending on which works out cheaper at the time. If your servers have a datacentre licence that has software assurance as part of your ovs-ees, then that would allow you to upgrade them to 2019.

BGinfo only generates 1024x768 images if you want it for a logon screen based on our experience.

HAHAHAAHHAHAH that's funny, Solus being automated. The choice of having 1 instance of Solus to deploy updates from to multiple SIMS databases, once knowing it's working ok (which rules out the automatic deployment) verses multiple copies is a simple option.

We populate our MDT database with workstation name, MAC address, task sequence, screen resolution, OU location. We either manually update a record if we're just switching a PC, or for a whole new unit we have a CSV and Powershell script to bulk update the database. That way it's a case of launch the litetouch image to start the build process and check later to see if the software has all gone on

If it's just from their inbox, you can set a mailbox retention rule to remove mail over X days. It does not affect items in sub folders from our testing (since we're rolling out 1 year retention policy for staff at the start of the new year)

I had one of those automated scam calls the other week when I was off, promptly hung up then took great delight in adding it to the BT block list (which is where the TalkTalk scammers also get added to)

I should win cause I have to put up with a very punny @DJ-1701 all the time

Likewise all our stations are running DBA with zero issues as it gives a student licence to the device. We do use the onmicrosoft tenancy for our 365 activation though

We disable 365 group creation via powershell as our students are assigned a different mailbox policy via our licencing script (we're not using the Azure Auto assign) Set-OwaMailboxPolicy -GroupCreationEnabled $false There is also this method, but I've not tried it yet even though all our staff do have azure basic edu assigned https://docs.microsoft.com/en-us/office365/admin/create-groups/manage-creation-of-groups?view=o365-worldwide

Had my ticket booked for Tuesday since the start of the month. Picked a nice early afternoon showing when most people are at work. So far only 23 other people have booked that session according to the seating plan online

If the account is a Cloud based one, it's not gotten to the 180 day password age and failing to authenticate until you change it. You can turn this option off via powershell for specific accounts (AD Sync ones are not affected)

So far our local SMTP relay to 365 (via authorised account and port 587) is still working fine

Nope @snagrat it's available in the free section

Well you could assign the users via a local group in AD, and that in turn automatically updates the licence and the apps. That way no script is needed and it's just a case of adding user to a group

Are you not using Azure AD Sync for putting your users into 365 in the first place @cookie_monsta or you just relying purely on CSV? If you are using the sync, then the Azure AD portal will let you assign licence based on your local AD group membership, and it is included in the free section of Azure.

Its unlikely they would let you run cabling prior to completion, so you would have to do it once you move in.

When we migrated e-mail systems, we transferred the bulk of the e-mail over prior to the MX record getting updated, but continued to sync the old mail for a few days after the migration. It just depends which route you prefer.

To be honest, it's not that bad to update in bulk, Select a load of users in AD Users and Computers -> Right click -> properties -> Account Tab, tick UPN suffix and select the one from the drop down and click ok. Now if the e-mail addresses does not follow the same naming convention as the network user name, that is a pain

I did roll it out last night, but warned the admin staff this morning. They should have a fix by the time we get back from half term (hopefully)