Editing the MSGina

[garethedmondson]

Has anyone on here edited the standard msgina to create a better looking logon box? I want to replace the WindowsXP Proffessional logo with our school logo :-) and some other information.

I've been reading about reshacker which is an application that lets me do this, but I just wondered if anyone had done it and was it an easy process to follow.

I've also read about pGina but am not sure about using software that isn't maintaned any more by the developer.

Many thanks

Gareth

[dalehopper]

Im sure if you do it breaks the Microsoft EULA, but yes ive done it before

[OutToLunch]

I haven't done this after fire and brimstone warnings that modifying the file would break the Microsoft T&Cs and leave you unlicensed... Based on that, pGina seems a better option!

[DSapseid]

Hi Gareth,

I did this about 2 years ago and was very easy to do and in my opinion makes the logon screen look a whole lot more professional!

Here is the page that i used to help me do it Change the Classic Logon Image | Skeletorscorpse i then created a script that copied the msgina to the c drive and added the registry key.

Dan

[DrCheese]

Yes, I modified ours a few years back and replaced the image with a nicer looking one(attached). I just used reshacker to change it.
I didn't replace the standard gina in the windows directory, rather I modify the registry on our machines to point it to another file eg,

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"GinaDLL"="C:\\windows\\system32\\sgina.dll"

[jmcdermott]

We have done it using reshack and it looks good, would recomend against messing around with boot screen, and make sure you have the new gina in place before you switch.

[srochford]

If you just want a more attractive login, try the FrontMotion Login

This uses Flash and you can create your own SWF files to go with it. It's free for personal use. The web site says "For permission on commercial use and customized distribution please email" - not sure where an education institution comes.

[powdarrmonkey]

Note: hackling the build-in GINA dll is in contravention of your EULA and therefore your license (though replacing it with something that you are licensed for is acceptable - building your own, for example). If you're going to home-brew one though there are some useful resources on the MSDN.

[krisd32]

with this do you also need to copy the images over the pc's aswell? Or is this all contained in the gina.dll file?
Cheers

[powdarrmonkey]

with this do you also need to copy the images over the pc's aswell? Or is this all contained in the gina.dll file?
Cheers

They're embedded in the .dll as resources.

[Michael]

Powdarrmonkey's right, this does go against the EULA. Something Microsoft do take very seriously.

As a compromise using BGInfo I set the startup background, so the school name is at the top right. You can also insert the school logo (optional) which makes it look professional, but also consistent across the school.

@DSapseid and jmcdermott, slightly different topic, but one little reg tweak I find useful is to grey out 'Log on using dial-up connection'. Stops the kids ticking it and being unable to logon.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"RasDisable"="1"

Either run this manually or automatically at startup and it's then impossible to tick

[Tamarside]

If you're going to try and custom write a GINA replacement, be aware of what exactly this file does, in addition to displaying pretty pictures.
One of the easiest ways to subvert an entire network is through an insecure custom GINA as the GINA receives the user's password in plain text.
A custom GINA could for example write username & password combinations to a central log, or even upload via HTTPS. Your firewall won't interfere with that at all, and even if your firewall asks for authentication the custom GINA could simply hand over the credentials it is about to upload somewhere.

I'm not trying to spook you, but instead wanted to make you aware of the risks.

My advice would be to RESHACK the msGina and push it out under a different name, as a custom GINA, alongside with the relevant reg entries, then if ever queried by Microsoft claim ignorance and state you believe by leaving the original untouched you remained with your EULA.