SSS-IT Posted February 28, 2023 Posted February 28, 2023 Hi Guys, Has anyone managed to sucessfully replace the "Other User" text on the login screen VIA intune, so far we have tried wrapping a powershell script into a windows app, running powershell scripts. I have also tried poiting to an external source (one drive) to download the DLL file and replace it. If anyone has done this, I would greatly appreciate some help!
IT_JB Posted February 28, 2023 Posted February 28, 2023 What are you trying to replace it with? If you are trying to remove it you can provision the devices in "Shared PC" mode and it will remove the last logged-in and other user options and instead just show the username and password box.
SSS-IT Posted February 28, 2023 Author Posted February 28, 2023 We have changed the "Other User" text, to "Sandy Secondary School" (as seen in the picture) with a combination of registry keys and group policy settings for our on prem machines. To achieve this in intune is proving impossible thus far.
SSS-IT Posted March 9, 2023 Author Posted March 9, 2023 For anybody trying to do this, I have found a resolution. To change the "Other User" text you will have to change permissions to the file and move the file into the En-US folder to replace the current one in one script. This is what I came up with. Step 1: Code for the credprovhost.dll.mui file replacement; " # Set the file path for the file to be moved$file = "$PSScriptRoot\credprovhost.dll.mui"$destination = "C:"Copy-Item $file $destination -Force$filePath = "C:\Windows\System32\en-us\credprovhost.dll.mui"$acl = Get-Acl $filePath$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("Everyone","FullControl","Allow")$acl.SetAccessRule($rule)$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("Administrators","FullControl","Allow")$acl.SetAccessRule($rule)$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("SYSTEM","FullControl","Allow")$acl.SetAccessRule($rule)Set-Acl $filePath $acl$sourceFile = "C:\credprovhost.dll.mui"$destinationFile = "C:\Windows\System32\en-US\credprovhost.dll.mui"# Backup the original fileCopy-Item $destinationFile "$destinationFile.bak"# Replace the original file with the replacement fileCopy-Item $sourceFile $destinationFile -Force " Step 2: Package the .ps1 file (with the credprovhost.dll.mui file within the package) using "IntuneWinAppUtil.exe" Application. Step 3: Upload to Intune
dsmith8 Posted March 10, 2023 Posted March 10, 2023 For anybody trying to do this, I have found a resolution. To change the "Other User" text you will have to change permissions to the file and move the file into the En-US folder to replace the current one in one script. This is what I came up with. Step 1: Code for the credprovhost.dll.mui file replacement; " # Set the file path for the file to be moved$file = "$PSScriptRoot\credprovhost.dll.mui"$destination = "C:"Copy-Item $file $destination -Force$filePath = "C:\Windows\System32\en-us\credprovhost.dll.mui"$acl = Get-Acl $filePath$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("Everyone","FullControl","Allow")$acl.SetAccessRule($rule)$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("Administrators","FullControl","Allow")$acl.SetAccessRule($rule)$rule = New-Object System.Security.AccessControl.FileSystemAccessRule("SYSTEM","FullControl","Allow")$acl.SetAccessRule($rule)Set-Acl $filePath $acl$sourceFile = "C:\credprovhost.dll.mui"$destinationFile = "C:\Windows\System32\en-US\credprovhost.dll.mui"# Backup the original fileCopy-Item $destinationFile "$destinationFile.bak"# Replace the original file with the replacement fileCopy-Item $sourceFile $destinationFile -Force " Step 2: Package the .ps1 file (with the credprovhost.dll.mui file within the package) using "IntuneWinAppUtil.exe" Application. Step 3: Upload to Intune Was trying this out for a bit of fun but can't seem to get your script to run not sure if it's cause how the post formatted it. Seems to be gaps in $destination etc
chaplic Posted March 12, 2023 Posted March 12, 2023 Id suggest its implemented as a proactive remediation because Sod’s Law it’ll be changed back on every OS upgrade 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now