Slashdot Mirror
Vista to Allow "One Significant" Hardware Upgrade
fiorenza writes "Ars Technica spoke with Microsoft concerning the controversial changes in Windows Vista's licensing, and they have learned that Vista will permit one 'significant' hardware change before requiring users to either appeal to Microsoft support or purchase another license. Automatic re-activation online will fail after one use. Microsoft is using a new algorithm to monitor hardware changes and enforce licensing compliance, and the company says that it is more forgiving now than it was with Windows XP."
So now the only reasonable option for the OS you purchased after you do something common like toss in a new video card, is to go out and get a pirate version? Well whatever, if MS wants to drive more people towards using superior pirated products, so be it. This seems to be part of a larger industry trend of artificially limiting products when there are uncrippled products out there if people look around, which just makes people want to look around. These sorts of tactics are going to bloat the pirate population, pass the rum me-hearty, y'aarrrrrrr.
That isn't as far-fetched as it sounds.
Last week, our phone guy decided to reinstall the OS on our main voice mail server. Since it was running a "lowly" copy of Windows 2000 Pro, he decided that it needed a "server-grade" OS, and bought Microsoft Windows 2003 Server for Small Businesses. He installed in near the end of the week, and then took time off to put a new roof on his house.
Well, this morning, the machine in question shut itself off. I turned it on, it shut itself off again in a couple of hours. I looked in event log, and found that the machine was turning itself off because we violated the EULA by not setting it up as a domain controller.
Yep. Just because we didn't need to authenticate users, the machine keeps shutting itself off. Isn't that user-friendly?
Oh, you're not stuck, you're just unable to let go of the onion rings.
MS has this ridiculous system service called "SBSCore" that exists only to turn off the computer every hour if you aren't running as a DC. Install SysInternals' Process Explorer, suspend/pause sbscrexe, go into the registry to set the service to disabled, then remove all read permissions for every account from the actual file. The file is in \windows\system32\sbscrexe.exe. Then you can terminate the process. Don't delete the file, though, that really got Windows upset when I tried that.
c es\SBCore
Reg key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi
In regedit, right click, give Administrators permission to the key and all child nodes. Then change the Start DWORD that will appear undernearth that to 4.