aac
Members-
Posts
206 -
Joined
-
Last visited
-
We have used Unifi Protect here for years now and it has been great. No subscription costs and we install the cameras ourselves so save quite a lot of money on cabling costs. I have bought an Enterprise NVR here as we did have some issues with stacking of the UNVR Pro's in the early days but his ensures plenty of capacity moving forward. We have also installed UniFi Connect on the NVR so use it for digital signage as well as CCTV.
-
We are moving away from an old Solarwinds product called Webhelpdesk to OneDesk as Webhelpdesk is going subscription based now and they want thousands of pounds a year does both the ticketing and asset management. Ask for for the educational discount and it has costed us less then £500 for the year. Fully cloud hosted...
-
See the script below. I just added it in the software library/scripts section of SCCM then just run it on affected machines each month. Even if it says password rotation for machine failed after running on affected machine just reboot the affected machine and you will see it worked fine. I personally don't think 25h2 fixes anything but reimaging an affected machine does. Unfortunately in my scenario I just don't have time ATM to reimage the affected machines some of which have a few extra apps to install after reimaging so I will just run the script for now as I am building a new image and will reimage all machines later... try { Write-Host "Starting machine password rotation..." Write-Host "Running as: $(whoami)" # Define credentials (plain text password converted to SecureString) $Username = "domain\username" # Replace with your delegated account $Password = ConvertTo-SecureString "password" -AsPlainText -Force $Cred = New-Object System.Management.Automation.PSCredential ($Username, $Password) # Specify a domain controller explicitly $DomainController = "test.domain.internal" # Replace with your DC name # Reset the machine account password using provided credentials Reset-ComputerMachinePassword -Server $DomainController -Credential $Cred -Verbose # Verify secure channel if (Test-ComputerSecureChannel) { Write-Host "Machine password successfully rotated." Exit 0 } else { Write-Host "Password rotation failed: Secure channel test failed." Exit 1 } } catch { Write-Host "Error rotating machine password: $($_.Exception.Message)" Exit 1 }
-
Hi there your not alone with this. We had a 2019 and a 2025 DC and issues with group policy not applying so in the end to resolve the group policy issues we upgraded the 2019 DC to 2025 and that sorted it but to this day we are still finding some machines do not rotate machine password and therefore loose trust with the domain thus I am having to run a script on these machines monthly to rotate the passwords manually. Even if it has already lost trust with the domain it still works and saves a trip to the machine re-joining manually...
-
Hi all I am looking to lock down my Intune devices so that only users in a specific Azure AD group can logon to Intune managed devices. Has anyone achieved this as I have spent days looking into how this can be done but have yet to find a way that works...

