Search the Community
Showing results for tags 'R2'.
-
Hello All, I am learning all I can about networking and at 48 yrs old, I am beginning college next month for studies in just that. In the meantime, I'm trying to learn all I can on my own, as well as apply as much as possible to a hands on experience. A couple days ago I configured Windows Server 2008 R2 for Active Directory, DHCP, DNS, and File Services roles within my home network of 3 machines and two devices; successfully too....... What I am attempting to do is set up a VPN to enable a select few family members to some of my media. I have installed Networking Policy and Access Services including Routing and Remote Access. Beginning the configuration, selecting VPN & NAT, I come to the decision of what interface to use. This is where I'm stuck. This server is on a laptop with only 1 LAN and 1 WLAN connection. The installed roles (mentioned above) use the local area connection that's assigned a static IP outside the DHCP pool used for the domain users. It's connected to a home user type router/WAP with which DHCP is disabled. The other listed is the WLAN which states DHCP yet does not show up in ipconfig /all. Should I use the interface that all else is on or the wireless? If wireless, do I have to config the router to assign a IP to the wireless or use static? Why is the wireless interface not showing up in ipconfig or the router? I know this is newbie stuff yet any help would be greatly appreciated.
-
Have you ever looked at the logon screen in Windows Server 2003 R2 and thought "Wait a minute. Something looks a little bit off here." Well, you'd be right. In every version of Windows NT 5.x there are two banner bitmaps that are used on the logon screen. One used for the logon prompt, and the one used for the status messages between the differing stages of logging on. That is every version, except Server 2003 R2 (and also Windows XP Embedded, but anyway.). It looks like this: For some reason Microsoft just never bothered to make two bitmaps. But I did: See. Much better. Most of you will probably think that this is totally stupid and doesn't matter in the grand scheme of things. But for those of you that do think it matters, here are what you need. These registry values for Server 2003 R2 Standard Edition (only). Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CustomBrand][HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CustomBrand\{F20B21BE-5E3D-11d2-8789-68CB20524153}]@="r2brand.dll, -1001"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CustomBrand\{F20B21BF-5E3D-11d2-8789-68CB20524153}]@="r2brand.dll, -1002"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CustomBrand\{F20B21C0-5E3D-11d2-8789-68CB20524153}]@="r2brand.dll, -1010"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\CustomBrand\{F20B21C1-5E3D-11d2-8789-68CB20524153}]@="r2brand.dll, -1011"And this modified version of "r2brand.dll" with the new added bitmap images. http://www.mediafire.com/download/786f3e33er8vao4/r2brand.dll Note: This is not for the x64 Editions of Windows Server 2003 R2. Replace r2brand.dll - through the Recovery Console or whatever method you have - first, then run the registry file. _______________________ For those of you not running Server 2003 R2 Standard Edition, you'll need to delve into the registry a little bit. Got to that part of the registry and you should find references to the same resource in r2brand.dll. The bottom two references are the banner for the logon prompt. One is a black and white basic image, and the other is the full colour version. (the one that needs to be changed). The full colour version that we need to change in this case is the 3rd one down in that list of four keys. Change the value in that key to the number that corresponds to your version of Server 2003 R2. Example: If you have Enterprise Edition, use 1013. If you have Datacenter Edition, use 1015. Reboot, and that should be that. Sooner or later I'll come up with a registry file that works on all three major releases of Server 2003 R2, and then maybe the x64 Editions.