1803 'Other User' Text on Login Screen

[speckledegg]

Morning all,

 

In Group Policy, I have an edit set up to modify a file which allows you to change the 'Other User' Text when you first start a computer and reach the login screen (to your school name for example).

 

https://community.spiceworks.com/how_to/140751-change-other-user-text-on-windows-10-login-screen

 

This was working perfectly in 1709 and below. However, when upgrading my computers to 1803 this has now stopped working.

 

I do have the en-GB and en-US versions in place to cover myself and have had no problems with this up until now.

 

I was wondering if anyone knew of any changes that have happened to prevent this? If so, does any one have a guide I can follow so I can update our GPO's?

 

Thank you! ;-)

[Arthur]

However, when upgrading my computers to 1803 this has now stopped working.

Have you tried editing credprovhost.dll.mui from a Windows 10 v1803 install? The 'Other User' string is still there, but the file may contain some other changes which prevents the use of a credprovhost.dll.mui file an older version of Windows 10.

 

The file would have also been overwritten during the upgrade.

 

Edited May 22, 2018 by Arthur

[KevinB]

I think this may be a local thing for you as I'm using the same credprovhost.dll.mui from a previous install of 1607 (masquerading as LTSB 2016) and it works as expected.

 

Did you remember to change the permissions on the file before replacing? We have two GPO settings, one to change the permissions on the file, then one to replace it so it actually takes 2 reboots to work.

[speckledegg]

Thanks for the advise guys! Yeah I did set my gpo to change the permissions originally and still have this in place. I will have a go at grabbing the latest version of the file and see if this fixes it after a gpupdate.

[speckledegg]

Morning all, I have now updated the files for both our en-US and en-GB installs. The new file worked on the en-US version but not en-GB. The login screen stays at 'Other User' even though the updated file has been successfully replaced on the machine.

 

I'm wondering if this is because I let the machines Upgrade to 1803 via Windows Update. Is there a way to refresh the login screen so that it uses the new file?

 

The new en-GB file is working on an image I made of 1803 as a test so I'm pretty certain that the file is not at fault. It seems to be a bug with that version when upgrading from 1709 via Windows Update.

 

I'm thinking I may just reimage them all over summer if theres no other fix, I need to update the image at some point anyway, such a pain!

Edited May 30, 2018 by anselmtech

[dr_Wiley]

I can't get this working on fresh install of 1803 even with a new file. Could this be down to a windows update?

[BOOT]

I've never been able to get it working. Always seems to render the PC unbootable.

[LytchettNM]

We had a GPO that seem to work with 1709 but testing with 1803 it didn’t for some reason, but with 1709 using the international English version of 1803 I had to replace the file in en-GB and place a copy in en-US.

[markwilfan]

Ahhhhhhhhhhhhhhhhhhhh. That is all. Why is Win 10 so hard to customise? We're having the same issue.

[KevinB]

Ahhhhhhhhhhhhhhhhhhhh. That is all. Why is Win 10 so hard to customise? We're having the same issue.

You vill be using Vindows how VE vant you to be using vindows, not how YOU vant to be using Vindows!

[markwilfan]

They have vays of making me balk

[FishCustard]

I've replaced the file (credprovhost.dll.mui) in our base image with one that says "Please log in" - works just fine in 1803. Edited August 15, 2018 by FishCustard

[markwilfan]

I've replaced the file (credprovs.dll.mui) in our base image with one that says "Please log in" - works just fine in 1803.

credprovhost.dll.mui or credprovs.dll.mui ?

[FishCustard]

credprovhost.dll.mui or credprovs.dll.mui ?

 

credprovhost.dll.mui, sorry!

[markwilfan]

credprovhost.dll.mui, sorry!

Just wanted to make sure I had my dog barking up the correct proverbial tree. Do you mount the wim and inject the file in or use the gpo method to replace the file? I'm using gpo but the file will just not replace

[FishCustard]

Just wanted to make sure I had my dog barking up the correct proverbial tree. Do you mount the wim and inject the file in or use the gpo method to replace the file? I'm using gpo but the file will just not replace

Mount the WIM and inject it that way. Its ACL is limited to only TrustedInstaller I believe, so even GPOs applied under the SYSTEM account can't touch it.

[cdwyer]

Hi there,

 

Just wanted to ask if anyone managed to get the en-GB version of the file working and how? as this is the exact issue i'm having. Any advice would be MASSIVELY appreciated. Thank you.

[junz]

Mount the WIM and inject it that way. Its ACL is limited to only TrustedInstaller I believe, so even GPOs applied under the SYSTEM account can't touch it.

 

Hi FishCustard,

 

I am currently looking into doing this and am struggling to do so. Do you by any chance have a guide on how to do this?

 

Thanks in advance

[forkies]

I do this in task sequence after image applies. Will share the details tomorrow when I get on SCCM.

[cdwyer]

I do this in task sequence after image applies. Will share the details tomorrow when I get on SCCM.

 

Brilliant thanks.

 

I have already built the majority of the machines unfortunately but if I can at least have it in the task sequence then I can slowly rebuild the machines and have it corrected going forward.

 

I look forward to your guide!

[cdwyer]

Mount the WIM and inject it that way. Its ACL is limited to only TrustedInstaller I believe, so even GPOs applied under the SYSTEM account can't touch it.

 

Strangest thing is, I have successfully replaced the file using GPO’s. if I open it in a hex editor it shows the updated string, but still doesn’t show on the login screen. This is with the en-GB version of the file only. en-US works flawlessly!

[forkies]

Brilliant thanks.

 

I have already built the majority of the machines unfortunately but if I can at least have it in the task sequence then I can slowly rebuild the machines and have it corrected going forward.

 

I look forward to your guide!

 

Ok so I edited the credprovhost.dll.mui from within C:\Windows\System32\en-GB\ using Resource Hacker as I had issues with resedit.

 

I then saved this file to my SCCM sources share, then create a PS1 file with the below code:

 

#Take OwnerShip of the file
TAKEOWN /f "C:\Windows\System32\en-GB\credprovhost.dll.mui"
#Set permissions for SYSTEM Account
ICACLS "C:\Windows\System32\en-GB\credprovhost.dll.mui" /Grant 'System:(F)'
#Copy the files
Copy-Item C:\Windows\System32\en-GB\credprovhost.dll.mui "C:\Windows\System32\en-GB\credprovhost.dll.mui.bak"
Copy-Item $PSScriptRoot\credprovhost.dll.mui "C:\Windows\System32\en-GB\"

 

I then created a package for that directory and distributed that to the distribution points.

 

In task sequence, assign the package towards the end and enter "ReplaceLogonScreenText.ps1" into script name. (I put all my customisations at the end, with the logon image as the last thing so I know from just looking at the computer if the build was successful). This works really well for me now as I changed from a English US build to English International build.

[junz]

Mount the WIM and inject it that way. Its ACL is limited to only TrustedInstaller I believe, so even GPOs applied under the SYSTEM account can't touch it.

 

Hi,

 

I have tried to replace the credprovhost.dll.mui but was wondering whether the permissions have to be restored once you do this

[caffrey]

Nope, they don't well I haven't ran into any issues