Does anyone have PP3? I can’t seem to get it from MS Connect anymore?

Also, is it still a beta? Or is it basically RTM now?

That worked perfectly, thanks alot :)

Place the inf entries after this line in the hivesys.inf:

HKLM,”SYSTEM\Setup\AllowStart\SamSs”,,0×00000010

I’ve been trying this using KerrAvon’s guide, once i enter my VLK for Server 2003 and try to proceede i get “Setup sources are corrupt: cannot check the product key”

I used windows server 2003 standard and slipstreamed sp2 into the build, then extracted the files from that image.

Step 5 of KerrAvons guide says add the reg keys at the bottom of the last [addreg] section that last section in my hivesys.inf is just a bunch of character returns?

then has the [strings] section of the inf

any ideas as to where i’m going wrong?

Much appreciated

thanks

Microsoft did not explain it very well. WHS is not a retail product – it is only sold through OEMs (like HP). You cannot get support for a home-built WHS.

AntiWPA is a risky option because MS can detect it during updates and disable it.

The VLK option is your best bet – but you must have access to the necessary files to build it. VLK images of Windows Server 2003 Standard Edition are only available to MSDN or Volume Licensed customers of Microsoft. If your company has such a license, you may be able to get a VLK iso from your IT department. Otherwise, you will have to find a copy of the correct files I mentioned. There is a procedure to reinstall WHS on top of an existing install without destroying the data. You can google that for details.

Good luck.

Only trouble is the last step in the installation which didn’t happen, and so the installation doesn’t recognize itself as WHS, but as SBS instead..

Can any messing around be done purely in regedit to change this? Not sure if the problem is with the WHS setup we’ve got, coz we’ve tried reinstalling a couple of times and it’s the same problem every time..

Any ideas?

I have WHS installed on my server, but the System Properties only says “Windows Server 2003 for Small Business Server (SP2)”

I have applied the WPA crack and now I don’t have an activation problem.

Only thing is that, in regedit, under “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSe\Control\ProductOptions”, it says “Small Business
Small Business(Restricted)
Terminal Server”

No mention of WHS anywhere.

Are there changes I can make exclusively to the registry to make this copy get recognized as a WHS instead of Server 2003 for SBS?

Please please please do reply!

TQ

In the Install.cmd file change
SET SysPrefix=%SysPrefix:~0,8%00C04944
to
SET SysPrefix=%SysPrefix:~0,8%00604A24

Fresh installs are usually best, though.

Microsoft is always trying to thwart tools like AntiWPA so I can’t see it working forever. My version is completely valid – all Microsoft components and no hacks.

Currently I am using the AntiWPA method, and it works just fine even with all the updates installed (as of April 16/09), including PP2. Comparing these two methods, which do you guys think would hold up better to Windows Updates in the future?

………………………………………………………………………………………

Easy Way to Activate Windows Home Server (Crack and Bypass Activation)

Windows Home Server is a home-based server operating system from Microsoft, where interested user can request for a free evaluation kit with installation DVD with 120 days activation free grace period to be delivered to user’s doorstep. To continue using Windows Home Server beyond 120 days free evaluation trial period, user will require to purchase a legitimate license, or try the following hack to crack and bypass the Windows Home Server activation requirement.

1. Click on Start button.
2. Click on Run.
3. Type regedit into the Run text box and press Enter.
4. Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents
5. Note: From this step onward, the cracking process must be performed as quickly as possible, as it hacks activation stuff and Windows may change back the setting if there is a delay of more than few seconds.

Locate a string value named OOBETimer.
6. Right-click on OOBETimer, and click on Modify.
7. Change the value to FF D5 71 D6 8B 6A 8D 6F D5 33 93 FD.

Activation OOBETimer
8. Click on OK.
9. Right-click on WPAEvents and select Permissions….
10. Click on Advanced button.
11. Uncheck the check box for Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here.
12. Click on Apply.
13. When prompted, click COPY.
14. From there, highlight the SYSTEM line, and click Edit.
15. Choose the Deny option to ban all users from accessing and editing the key.
16. Click on OK.
17. Reboot the computer.

After the hack, Windows Home Server should run completely as a free copy, with users able to access Windows Update to get latest hotfixes and patches. The crack does not require BIOS mod.

To verify that the activation crack works after restarting the system, go to Start -> All Programs -> Activate Windows. The dialog should say Windows is already activated. Alternatively, go to Start -> Run and type oobe/msoobe /a.

Note: Some users reported that the method does not actually remove the activation grace period, even though it makes the system activated.

Disclaimer: This article is provided for informational purpose only.

Mark