WinFS Beta 1 short after-install look…

So what’s the deal: Actually it’s the first release of the WinFS SDK. As I don’t have the time at the moment to review the SDK itself (got a approx. 1000km trip tomorrow) I just made some screenshots … later on there will be a review – not only because WinFS is one of the most promising features/products in the future of Windows:

Mission accomplished: Linksys Router is now “evilgate”

After some minutes the job was done – and openwrt instead of the original firmware was flashed into the two new linksys routers.










Please welcome OpenWrt – “White Russian RC2”.

Since the documentation is quite good it just leaves me with this citation:

“With the release of the Linux sources for the Linksys WRT54G/GS series of routers came a number of modified firmwares to extend functionality in various ways. Each firmware was 99% stock sources and 1% added functionality, and each firmware attempted to cater to a certain market segment with the functionality that they provided. The downsides were twofold, one – it was often difficult to find a firmware with the combination of functionality desired (leading to forks and yet more custom firmwares) and two – all the firmwares were based on the original Linksys sources which were far behind mainstream Linux development.

OpenWrt takes a different route, instead of starting out with the Linksys sources, the development started with a clean slate. Piece by piece software was added to bring the functionality back to that of the stock firmware, using the most recent versions available. What makes OpenWrt really unique though is the fact it employs a writable filesystem so the firmware is nolonger a static compilation of software but can instead be dynamically adjusted to fit the particular needs of the situation. In short, the device is turned into a mini linux PC with OpenWrt acting as the distribution, complete with almost all traditional linux commands and a package management system for easily loading on extra software and features.”

Source: http://openwrt.org/

there it is: WinFS (test)

Today the first test version of WinFS – the new and said to be revolutionary filesystem – was released by Microsoft.

“The beta version released on Monday works with Windows XP. Both Home and Professional editions are officially supported. It should also work on Tablet PC and Media Center editions of the OS, but Microsoft has done limited testing of WinFS with those flavors.”

So! If you have a MSDN Subscription… go and get it!!

Source: Cnet News

it’s all about power

hmm…seems like I have some things to optimize… the “old” server really was more powerful…

Believe it or not: That 15%-20% load there is just the Remote Desktop… I’ve never seen something like that…even on my P3-500 machine which is my mail-server at the moment it’s not more than 5%…

…Strange. I’ll have to find a reason for that behaviour…

update W2k3 Web Edition to W2k3 Standard Edition pt. 2

So this is part 2 of my little “how to transform a Windows Server 2003 Web Edition into a Windows Server 2003 Standard Edition if you only have Remote Desktop and limited “physical” keyboard access to the machine…

Since some hard-drive imaging experiments did not work today I decided to try the straight-forward way. Mounting the CD and installing…

I came across several problems and had to find a workaround or them. The first problem showed up: Since we would like to have Remote Desktop Access after the installation finished successfully installing a Windows Server 2003 Standard Edition WITH Servicepack 1 is not an option. One of the new features of Servicepack 1 is that after a clean Install you cannot access the machine from the network anyhow – You have to update the machine and then this “feature” disables itself.

So it is important that you have a non-SP1 Windows Server 2003 Standard Edition Install-CD…

Another problem occurs now if your currently running Windows 2003 Web Edition has Servicepack 1 installed already…

If you start the setup something like this will show up:



“Setup cannot continue because the version…”

So we’ll have to trick a little bit to fake a pre-SP1 environment for the setup: When you start the setup the “winnt32.exe” is launched which loads the “\Windows\AppPatch\sysmain.sdb” file and reads the version number that is stored there.

The trick is to replace the running systems “sysmain.sdb” with the one from the setup CD. (don’t get confused that the path is “C:\noSP1\” – just replace that with your CD-Drive name).

Anyway…just do this:



One note to the things above: the file is deleted from the dllcache first to trick the Automatic System File Protection…

Once you have completed this you can start the setup and it’ll run as desired. Ensure that you select the following advanced options:



Copy all installation files from the Setup CD

Now start the setup, fill in the product key and wait until the machine reboots.



If you had KVM access you’ll see this after the reboot:



Now it’s going to be fun! My ISP allows me to send keyboard commands to the machine… so this are the commands you’ll have to send (blind!) to finish the installation:

Enter (Welcome to Setup)
Escape (don’t repair)
Enter (Install)
C (Continue Setup)
L (Delete Windows folder)

After about 25 minutes and a reboot

Enter (Regional Configuration Dialog)
Username (Username)
Enter (Username>
Enter (Licensing Modes 5 concurrent connections)
Tabulator (passwords…)
password (your actual password…I recommend to leave it “password” or any other simple thing…
Tabulator (retype the password)
password
Enter(confirm the passwords)
Tabulator(that’s the password warning “Password to simple” if you’re absolutely sure this won’t come up…skip this and the next one)
Enter (password warning)
Enter (Timezone settings)
Enter (Typical Network Settings)
Enter (Workgroup name)

After about 30 minutes the machine reboots

After the machine rebooted it should be pingable…if so you should enable Remote Desktop Access remotely:

Step 1: start “regedit” on your local machine
Step 2: connect to the IP of your machine and login with username+password
Step 3: Change HKLM\System\CurrentControlSet\Control\Terminal Server\fDenyTSConnections from 1 to 0
Step 4: connect with your Terminal Service Client.



Now you should have this…

And that’s it as simply as it could be B-). One way to get Windows Server 2003 Standard Edition on a Windows Server 2003 Web Edition machine…