Things in Win XP but not in Windows 2003 Server


Recommended Posts

Here are some things that are supported in Windows XP but not in Windows 2003 Server. If you've read the thread and still want to configure Windows 2003 server as a workstation, I suggest you read the Windows Server 2003 as a Workstation Guide

Feel free to add to the list.

System Restore

Fast User Switching

The Welcome Screen

Support for MS Bluetooth Keyboard + Mouse

MS Intellitype

MS Intellipoint

Universal Plug & Play

Edited by Xeron

Also post 'workarounds' for things that are available in XP but not Windows 2003 Server, all other posts will be deleted - this thread is not for discussion = post a thread in this section of the forum reguarding your specific problem ....

Radish.

Here are some things that are supported in Windows XP but not in Windows 2003 Server. If you've read the thread and still want to configure Windows 2003 server as a workstation, I suggest you read the Windows Server 2003 as a Workstation Guide

Feel free to add to the list.

System Restore

Fast User Switching

The Welcome Screen

Support for MS Bluetooth Keyboard + Mouse

MS Intellitype

MS Intellipoint

You sure the Microsoft Bluetooth set doesn't work with win2k3?? Is it just an issue with drivers or what's the deal?

Here are some things that are supported in Windows XP but not in Windows 2003 Server.  If you've read the thread and still want to configure Windows 2003 server as a workstation, I suggest you read the Windows Server 2003 as a Workstation Guide

Feel free to add to the list.

System Restore

Fast User Switching

The Welcome Screen

Support for MS Bluetooth Keyboard + Mouse

MS Intellitype

MS Intellipoint

You sure the Microsoft Bluetooth set doesn't work with win2k3?? Is it just an issue with drivers or what's the deal?

That is correct. The Intellipoint software that is required to install the bluetooth mouse/keyboard cannot be installed in Windows Server 2003. I was hoping that this was just a limitation in the Beta and RC of Win Server, but unfortunately, it is not.

I've also tried emailing the support people and they confirmed that they are not supported at this time. :angry:

That is correct. The Intellipoint software that is required to install the bluetooth mouse/keyboard cannot be installed in Windows Server 2003. I was hoping that this was just a limitation in the Beta and RC of Win Server, but unfortunately, it is not.

It actually can by theory. The installer is preventing it.

So I tried editing the MSI file through InstallShield Developer... I changed the launch conditions and other conditions... And I got the installer to get to the copy files dialog. But when I get there I hit a wall right away with an internal error. (see attached pic) I only use InstallShield Developer for simple installs and I do not know how to sidestep this landmine. Any suggestions? The error code itself doesn't help me in finding what's wrong...

post-77-1051300538.jpg

Logitech Itouch doesn't work :( i'm using cordless optical freedom keyboard :(

actually that's just because it checks the os before you can install, if you enabled XP compatiblity mode on the installer it will install and work. However the 'first use' screens don't seem to go away

I read the guide and have looked through X-Setup; maybe I'm stupid, but there are a few settins that I can't find, is there another way to change these?

1. thumbnail size and quality for images and video in folders

2. folder locations of "My Music/Pictures/Movies"

I did manage to find the locations of Desktop/Startmenu and Documents

Is there a way to get rid of the required Ctrl - Alt - Del to login without enabling auto-login? I know it's superficial, but a bit annoying for me.

Personally I'm finding 2003 to be a better workstation than XP, it seems quicker to me. This may be because XP keeps giving me registry errors all the time (that's right, I zero the data on the drive, install XP and recieve a BSOD in the morning because "The Registry core is missing or inaccessable").

The only other thing that I have found to be missing is WIA support, no problem though, TWAIN is OK, just out of date I think.

Oh ya, MS Movie Maker 2 won't install, but that's no big deal... no really it isn't...

Is there a way to get rid of the required Ctrl - Alt - Del to login without enabling auto-login?

change the "DisableCAD" dword in "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" to 1.

edit: what stop error do you receive on the BSOD? ie. "Stop 0x0000007B" or something

the error flashes off so fast it's hard to read, but it goes something like this "The Registry Hive File is missing or inaccessable" then the computer restarts and then the computer works just fine till it sits off for 6 hours again.

SP1 really makes this error apparent, with SP1 installed I get an error about a damaged error and that it could not be repaired, then the OS has really really usability problems, applications appear to be unloaded from registry, file associations gone etc.

I've replaced all components in the computer except for the processor and motherboard, I'm suspecting that I may need to save up for a new Motherboard

the error flashes off so fast it's hard to read, but it goes something like this "The Registry Hive File is missing or inaccessable" then the computer restarts and then the computer works just fine till it sits off for 6 hours again.

SP1 really makes this error apparent, with SP1 installed I get an error about a damaged error and that it could not be repaired, then the OS has really really usability problems, applications appear to be unloaded from registry, file associations gone etc.

I've replaced all components in the computer except for the processor and motherboard, I'm suspecting that I may need to save up for a new Motherboard

Disable auto reboot on system failular ;)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      466
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!