- Aug 11, 2000
- 23,168
- 0
- 71
what do you guys think? better than WinXP Pro?? it's a bit more expensive, but i have it from my Action Pack. mb i'll use it for my primary system.
Originally posted by: Nothinman
If you're assuming cost equates "overhead".
It supports up to 8 CPUs, 32GB of RAM, and clustering.
So wouldn't that be a lot of extra overhead and cause a performance decrease if you were to run Windows Server 2003 Enterprise Edition for desktop use instead of Windows Server 2003 Web Edition? Isn't it the Enterprise level features that make it cost so much more?
Originally posted by: PlatinumGold
one more advantage to 2003 web edition. it allows for 2 Remote Desktop clients on top of the console user, so i can have 3 users on this machine at once.
not a huge advantage but i think i can put it to use.
Originally posted by: rdubbz420
Originally posted by: PlatinumGold
one more advantage to 2003 web edition. it allows for 2 Remote Desktop clients on top of the console user, so i can have 3 users on this machine at once.
not a huge advantage but i think i can put it to use.
You can make winxp allow more than one remote desktop connection.
Originally posted by: PlatinumGold
Originally posted by: rdubbz420
Originally posted by: PlatinumGold
one more advantage to 2003 web edition. it allows for 2 Remote Desktop clients on top of the console user, so i can have 3 users on this machine at once.
not a huge advantage but i think i can put it to use.
You can make winxp allow more than one remote desktop connection.
how??
i have a utility i've been buying for clients that do it, but how do you do it?
Originally posted by: rdubbz420
Originally posted by: PlatinumGold
Originally posted by: rdubbz420
Originally posted by: PlatinumGold
one more advantage to 2003 web edition. it allows for 2 Remote Desktop clients on top of the console user, so i can have 3 users on this machine at once.
not a huge advantage but i think i can put it to use.
You can make winxp allow more than one remote desktop connection.
how??
i have a utility i've been buying for clients that do it, but how do you do it?
A tweak...
1. Extract termsrv.dll from build 2055: and overwrite to c:\windows\system32 (for my case, even I booted to safe mode, when overwrite this file, it said it is using by the system, so I boot by win98 boot disk to dos and overwrite it)
2. Click: Start - Run
And type: regedit
Go to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core
Right-mouse-click on the right pane and create a new DWORD: EnableConcurrentSessions
Double-click the value and type: 1
3. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Double-click DWORD: AllowMultipleTSSessions and change the value to 1
Originally posted by: PlatinumGold
Originally posted by: rdubbz420
Originally posted by: PlatinumGold
Originally posted by: rdubbz420
Originally posted by: PlatinumGold
one more advantage to 2003 web edition. it allows for 2 Remote Desktop clients on top of the console user, so i can have 3 users on this machine at once.
not a huge advantage but i think i can put it to use.
You can make winxp allow more than one remote desktop connection.
how??
i have a utility i've been buying for clients that do it, but how do you do it?
A tweak...
1. Extract termsrv.dll from build 2055: and overwrite to c:\windows\system32 (for my case, even I booted to safe mode, when overwrite this file, it said it is using by the system, so I boot by win98 boot disk to dos and overwrite it)
2. Click: Start - Run
And type: regedit
Go to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\Licensing Core
Right-mouse-click on the right pane and create a new DWORD: EnableConcurrentSessions
Double-click the value and type: 1
3. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Double-click DWORD: AllowMultipleTSSessions and change the value to 1
i'll have to remember this. i remember some guy at ArsTechnica forums was trying to get this to work. wonder if he ever did it.
where can i get the termsrv.dll from build 2055 file?
Originally posted by: Link19
Originally posted by: Nothinman
If you're assuming cost equates "overhead".
It costs less because it has the least server and enterprise level features, which is what you don't want or need for a desktop OS. I mean because it has the least server features, would it run any better for doing non-server tasks than 2003 Enterprise or Standard would? I mean just look at the specs for Windows Server 2003 Enterprise. It supports up to 8 CPUs, 32GB of RAM, and clustering. Todays desktops can only address up to 4GB of RAM. So wouldn't that be a lot of extra overhead and cause a performance decrease if you were to run Windows Server 2003 Enterprise Edition for desktop use instead of Windows Server 2003 Web Edition? Isn't it the Enterprise level features that make it cost so much more?
Originally posted by: PlatinumGold
Win2003 server web edition doesn't do domains, active directory or terminal services server. it's basically a desktop OS with heavier duty IIS.
overall, i think it might make a pretty good OS. i'll have it installed on my new box i'm building this weekend. i'll report back.
Originally posted by: dawks
Originally posted by: Link19
Originally posted by: Nothinman
If you're assuming cost equates "overhead".
It costs less because it has the least server and enterprise level features, which is what you don't want or need for a desktop OS. I mean because it has the least server features, would it run any better for doing non-server tasks than 2003 Enterprise or Standard would? I mean just look at the specs for Windows Server 2003 Enterprise. It supports up to 8 CPUs, 32GB of RAM, and clustering. Todays desktops can only address up to 4GB of RAM. So wouldn't that be a lot of extra overhead and cause a performance decrease if you were to run Windows Server 2003 Enterprise Edition for desktop use instead of Windows Server 2003 Web Edition? Isn't it the Enterprise level features that make it cost so much more?
Windows XP could actually support the same hardware. They run the SAME kernel, with a small exception, each version has some portions of the NT kernel disabled.
Originally posted by: PlatinumGold
Win2003 server web edition doesn't do domains, active directory or terminal services server. it's basically a desktop OS with heavier duty IIS.
overall, i think it might make a pretty good OS. i'll have it installed on my new box i'm building this weekend. i'll report back.
It is a crippled version of Windows XP with IIS 6.0.
Originally posted by: dawks
Originally posted by: Link19
Originally posted by: Nothinman
If you're assuming cost equates "overhead".
It costs less because it has the least server and enterprise level features, which is what you don't want or need for a desktop OS. I mean because it has the least server features, would it run any better for doing non-server tasks than 2003 Enterprise or Standard would? I mean just look at the specs for Windows Server 2003 Enterprise. It supports up to 8 CPUs, 32GB of RAM, and clustering. Todays desktops can only address up to 4GB of RAM. So wouldn't that be a lot of extra overhead and cause a performance decrease if you were to run Windows Server 2003 Enterprise Edition for desktop use instead of Windows Server 2003 Web Edition? Isn't it the Enterprise level features that make it cost so much more?
Windows XP could actually support the same hardware. They run the SAME kernel, with a small exception, each version has some portions of the NT kernel disabled.
Originally posted by: PlatinumGold
Win2003 server web edition doesn't do domains, active directory or terminal services server. it's basically a desktop OS with heavier duty IIS.
overall, i think it might make a pretty good OS. i'll have it installed on my new box i'm building this weekend. i'll report back.
It is a crippled version of Windows XP with IIS 6.0.
They would be wrong.I have heard many people say that Windows Server 2003 is better than Windows XP for a desktop once you tweak it.
No, it's a cripped version of Server 2003.It is a crippled version of Windows XP with IIS 6.0.
Originally posted by: spyordie007
They would be wrong.I have heard many people say that Windows Server 2003 is better than Windows XP for a desktop once you tweak it.
No, it's a cripped version of Server 2003.It is a crippled version of Windows XP with IIS 6.0.
Originally posted by: rdubbz420
Originally posted by: dawks
Originally posted by: Link19
Originally posted by: Nothinman
If you're assuming cost equates "overhead".
It costs less because it has the least server and enterprise level features, which is what you don't want or need for a desktop OS. I mean because it has the least server features, would it run any better for doing non-server tasks than 2003 Enterprise or Standard would? I mean just look at the specs for Windows Server 2003 Enterprise. It supports up to 8 CPUs, 32GB of RAM, and clustering. Todays desktops can only address up to 4GB of RAM. So wouldn't that be a lot of extra overhead and cause a performance decrease if you were to run Windows Server 2003 Enterprise Edition for desktop use instead of Windows Server 2003 Web Edition? Isn't it the Enterprise level features that make it cost so much more?
Windows XP could actually support the same hardware. They run the SAME kernel, with a small exception, each version has some portions of the NT kernel disabled.
Originally posted by: PlatinumGold
Win2003 server web edition doesn't do domains, active directory or terminal services server. it's basically a desktop OS with heavier duty IIS.
overall, i think it might make a pretty good OS. i'll have it installed on my new box i'm building this weekend. i'll report back.
It is a crippled version of Windows XP with IIS 6.0.
IIS 6 really seems no different than IIS 5 w/iis lockdown tool already installed.
Originally posted by: Link19
Why does Windows Server 2003 use the NT kernel 5.2, and Windows XP uses 5.1? I mean isn't 5.2 a new NT kernel that would be updated and improved? Because whenever you update Windows XP, the kernel isn't updated at all. It still says its Windows NT 5.1.2600?
Originally posted by: PlatinumGold
well, for me, i'm doing it because i'm running my pc more as a server than a workstation. obviously the lines have blurred a lot.
it's s dual 2.6 xeon with 2 gb of ram. it's my primary file server. i log onto it from multiple locations to use Outlook 2003. i have a couple of other databases running on it. i'm going to play around a bit with IIS.
it's not a gaming machine.
Originally posted by: dawks
Originally posted by: PlatinumGold
well, for me, i'm doing it because i'm running my pc more as a server than a workstation. obviously the lines have blurred a lot.
it's s dual 2.6 xeon with 2 gb of ram. it's my primary file server. i log onto it from multiple locations to use Outlook 2003. i have a couple of other databases running on it. i'm going to play around a bit with IIS.
it's not a gaming machine.
XP can run as a file server just as well. Its main limitation is 10 connections though. IIS on XP works fine, unless you want to use some advanced .NET code. IIS 5.1 is also limited to 10 connections. Outlook 2003 is a non-issue unless your needing to run Exchange 2000-2003. Databases like MySQL run fine on XP. MSSQL requires Server 2003 Standard or greater of course.
![]()
They actually have updated the kernel in XP several times, just most of the updates only fix bugs or security problems, and do not justify a version change.
Originally posted by: Nothinman
They actually have updated the kernel in XP several times, just most of the updates only fix bugs or security problems, and do not justify a version change.
There should always be a version change, how else are you supposed to know if you have all of the updates or not?
There are improvements to IIS under server 2003; but it's not the only version of IIS that will run .net code. So long as you have the .net framework installed under IIS 5.1 (XP Pro.) than you should be able to run your .net web apps from it. You can even do it under IIS 5.0 (Win 2K); not that I'm saying .net is as feature-full the further back you go, but the majority of your web apps will work just fine.IIS on XP works fine, unless you want to use some advanced .NET code
MSDE runs on XP. It is the MS SQL server (just limited to 2GB of storage per database and some performance limitations).Databases like MySQL run fine on XP. MSSQL requires Server 2003 Standard or greater of course.
Like I said before Server 2003 Web Edition is pretty crippled and there are a lot of limitations to using it. Unless you have a very specific reason for running it (i.e. you are hosting multiple web sites) than there really are not going to be good reasons for you to run it on your desktop.i have a copy of Web Edition as part of my service pack. so what is the problem with me using it?