jonbd

Another vote for OSDCloud here. Seems to be working well for us, and allows an easy way to quickly get Windows on multiple device models with all the needed drivers etc

I used this guide when setting up deploying Winget apps via Intune as System, and it's been working great for me: https://scloud.work/how-to-winget-intune/ There is also a guide at the start for packaging up Winget itself, but i've not used that as we're using Windows 11 which has it already installed. We do use a script to manually install Winget during Autopilot enrolment if it's older than a certain version though, as at some point they changed the CDN that Winget pointed to, so older versions had issues installing anything until updated.

We had similar issues with this. Winget versions 1.2 and below are pointing to the old CDN that has been deprecated, so can't connect to anything. If you upgrade them to 1.6 or above they should start working again. We downloaded the msix from github and pushed it out to affected devices.

We are seeking to appoint an experienced and enthusiastic IT Manager with strong technical abilities and experience. This is a pivotal role within our school community with responsibility for all IT systems and the development and delivery of the IT strategy. https://www.eteach.com/job/it-manager-1160899

Katharine Lady Berkeley's School require an IT Technician to provide technical support across the school on a daily basis to users of data equipment, software and other related technical equipment. The post is 37 hours per week, all year round. Responsible to the Network Manager. You will be working as part of team of two but much work will be undertaken independently. https://www.eteach.com/job/it-technician-1109576 ICT Technician JD PS 2020.docx letter for job.docx Support application form updated March 2020.doc

We have Nano HDs and AC Pros here. I've found the AC Pros to be the most reliable. Some of the Nano HDs crash now and again and have to be power cycled, but the AC Pros have been rock solid.

Another vote for Unifi here too, although i've found the AC-Pros to be more reliable than the Nano HDs here.

I moved over to Shared Device Licences a couple of weeks ago, using Adobe's new Azure Connector. Quick and painless to set up following their guide. I was looking to do it over the summer, but the old way looked stupidly over complicated so I waited. Glad I did now!

I'm currently going through the process of setting up Azure AD Connect for SSO on prem and have set up the connect software in staging mode on a test OU with a few test users in, some of which have corresponding accounts in Office 365. I've matched the UPN suffix and Email attributes in AD to the correct office 365 domain, but how do I know if the users in AD are matching up to the correct existing users in Office 365? There are no errors in the Synchronization service software, but I can't tell from the info in there if it's going to create new users in Office 365 or match them up to their Office 365 counterparts. Is taking it out of staging mode the only way to see if it's matched them up correctly, or is there something I can check on the AD Connect server to verify before I flick the switch?

Managed to work out the type of cert I needed from my CA but the direct access server kept deleting the DNS record for the NLS every time I tried to apply the settings through the wizard and failed. I'm guessing it thinks it's clearing out the self cert DNS record, but with the new cert from my CA using the same DNS name, it then can't find a record for it. In the end I set up a seperate VM as the NLS instead of on the DA server, linked it to that and am back in business!

ok so i'm not getting anywhere with renewing self signed certs. Does anyone know how I would go about creating the right templates on my internal CA that I could generate certificates to use instead?

Hi all, Looks like the self signed certificates on my 2012 R2 Direct Access server have expired while I was away, so i'm trying to renew them. I've been following the guide here https://directaccess.richardhicks.com/2019/05/02/renew-directaccess-self-signed-certificates/ but seem to get the following error “a parameter cannot be found that matches parameter name ‘-FriendlyName'” I'm not much of a powershell user so don't know how to get around this problem. Anyone have any idea what i'm doing wrong? does -friendlyname work on server 2012r2? Is there another way to replace/renew the certificates?

Thanks guys. My main concern was that adding the UPN would affect current users in some way while I test, but it sounds like I can add the UPN and some test users without issue.

I'm looking to get Azure AD connect up and running so we can sync users and have SSO for OneDrive/Office365, but wanted to get a couple of bits straight in my head before I dive in. Our office365 domain and internal AD don't match (school.sch.uk vs school.internal) so I need to add a UPN suffix to sort this. usernames are the same though, so SCHOOL\jbloggs will be jbloggs@ school.sch.uk. Can anyone help answer the following at all? 1 - Just adding the UPN Suffix to AD won't affect anything will it, it will just sit there until I apply it to a user? 2 - If I change the UPN suffix of a user, can they still log onto a PC with the usual username and password, or would they then have to use their email address instead? 3 - If they can login as usual (username not email address), would that affect SSO to Office 365/Onedrive, or will it not matter? Thanks Jon

I had something similar on a friends PC a few weeks ago. In that case it turned out that the default BIOS setting for the CPU voltage wasn't high enough. I googled the correct voltage for that CPU model, as well as the safe voltage range, and once i upped the voltage enough it started working fine. That was with an I7-860 I think. I used to see it quite a lot with CPUs from that era.