WHS: Network Disabled

Alright, its my fault. In the process of tweaking for Jumbo Frame support I mistakenly right-clicked and chose the first option "Disable" instead of the second option "Status" (which would have taken me to the network configuration page) on the Network Connection icon. Dang!

This is obviously a headless machine and I am currently lost. Thankfully its not the first time something like this ever happened and tips from HomeServerLand gave me a clue.

If you have a headless device like the HP MediaSmart Server you can:
1. Connect an USB keyboard and wait about 30 seconds.
2. Next press CTRL + ALT + DELETE and then enter your WHS Administrator password and hit the ENTER key.
3. Then enter "windows + R", (where windows is the windows key on your keyboard) this will open the run dialog and then enter "ncpa.cpl" (without the quotes) this opens up network connections dialog.
4. Press the DOWN ARROW key (only once) and [Jamz: press the RIGHT ARROW key once] then press ENTER enter which will enable the NIC card,
5. If you have multiple NIC adapters you can toggle using the right and left keys [Jamz: or up and down keys] and YES you have to do it blind so make sure every keystroke counts.

I'm doing my darnest to get this working right now with fingers crossed.

[Edit: 10:44am] It worked! Hooaah!

WHS: Reference Account Locked Out?

Once in a while when I mistakenly log-on to the server shares I get the error message:

"The referenced account is currently locked and may not be logged on to."

Thats not too bad and easy enough to fix unless you have not clue how to RDP into your WHS. There are various help suggestions across this blog and elsewhere if the latter is a secondary issue. :-)

Moving along.... Basically what happened is Windows has locked you out for security purposes. So all you have to do is remote log-in (or physically if you can) into the server and reset the "Account is Locked Out" radio button.

You'll find that particular option by navigating:

My Computer --> Manager --> Local Users and Groups --> Users --> (login account) --> Properties --> (uncheck) Account is Locked Out

WHS: Upgrades with Zip Zoom Bang!

So I finally caved in and got some new hardware. It was fortunate that I found cheaper options for the NetGear FVS336G and the only place for Seagate Barracuda 1.5 TB drives at NewEgg. Figured with the shipping I may as well let it ride.

Following the basic memory and chip upgrade instructions the only difference would be the use of an AMD LE-1660 (Lima) 2.7 GHz.


G.Skill 2GB DDR2 667Mhz PC-5300 which was on sale for $30 that week.







First things first, remove the installed drives and label them so you know which order to put them back. WHS uses DE and you don't want to confuse the operating system and inadvertently trashing your data. The main bay is locked and I used a quarter to twist this clockwise (a large screwdriver would work but beware the groove marks if its tight).






Slide the gray top cover forward gently and it should slide out from the grooves. There are four actions items from this angel that you need to do.

Make sure to mark where the cables match up and be careful not to switch things around later (it could be bad).




Gently remove the black cable as well and gently move it out of the way.








Twist the blue tabs outward to unlock the backplane. Its this backplane that serves to connect the SATA disks.





Put your hand in and reach for the spaces with your fingers, then gently pull up. Be careful as there's a (barely used) thermostat you don't want to damage as you do this.
Remove the two-(2) small black screws on the front lower right side of the casing.






There's an insulated cable in there thats pressed against it and will usually cause it to pop out (don't loose the screws!). Do this gently (I keep saying that) since too much pressure on these small screws could ruin their tread -- mine's almost that way.

Use a medium sized Philip's screwdriver to remove the two-(2) anchoring screws between the casing and power supply.



Gently pull this tray out while gently pushing left as the components tend to snag.







Welcome to the guts/brains of your HP EX475 system.









Disconnect the power supply cable from the board and move it out of the way.






Remove the stick of memory as well. You'll need all the space to remove the heatsink from the chip by unscrewing it in an X-pattern so as to relieve the pressure on the chip gradually.

Then with a twisting left and right action gently remove.








With pure alcohol (pick one type as long as its more than 70% proof such as vodka or isoprophyl) make sure to clean the heatsink and set it aside to dry.

For those who've never replaced a chip before, there's a lever that needs to be lifted before you can remove the chip for replacement. Be careful to re-orient the new chip's pins the same way (don't forget to wipe the beads of sweat off your brow as any of it dripping onto the board isn't good ... and close your mouth).

A little goes a long way in terms of the heat seal, just a 1.5 grain of rice will do.







Then put Humpty-Dumpty together again and reverse the steps above.






Since I was using pure isopropyl and drinking that could cause major gastric distress (check the label), best I could do was step outside for a beer and a smoke. :-)

Windows XP: Service Pack 3

I've got two-(2) Windows XP machines being backed up using HP MSS (mostly gigabytes worth of .PST files) and its all working fine. Machines are of course top of the line updated via Microsoft Update to avoid some of the common distractions like botnets scanning for victims. Of course all of this is behind a serious hardware firewall in combination with the default Windows Firewall.

The thing is, Windows XP SP3 has been out for some time and its a humongous update. Lots of things that I didn't think were too broken appear to be critically so. But I won't update, not too soon.

And why is that? Well, simply the fact that on a basis there are two-(2) factors. Perhaps the underpinning issue is that I'm running WHS PP1 which is sort on beta stage; and the other is that SP3 appears to have broken RDP to the WHS -- not good considering that the WHS Console is a basic RDP subset to control the system.

Nothing to do with issue #1 as something has go to get fixed from the 60's (get my drift?). Besides that, I'm still using the core basic system unchanged for warranty's sake (am breaking down on this stance real soon now if it gets MSS to a level faster than Windows XP on a Pentium II). Of course for issue #2 I've got RDP Beta running on my Mac (thanks MS guys!) and can probably survive somewhat, but that basically does make WHSC useless in the interim, eh? :-(

Give me a few days, will update the experience and the machines by then.

WHS: Power Pack 1

I've finally gotten TVersity running on the MSS, but its a tad slow though due to the memory requirements of codec translation. Pretty much that chip and memory upgrade regardless of the warranty breaking is looking like a decent proposition right now if it can boost productivity (come on HP, give it up and let us poor folk who bought this expensive hardware do it already!). Joe's already done it with one of his systems taking a cue from that other guy from HomeServerHacks.

Anyway, moving along. Joe personally invited me to beta test the supposed new WHS SP1 coming out in June last month. My lazy excuse here is that so many projects in the works and I've not been on personal email too much recently. What I did do though is sign-up for the WHS Beta Program as mentioned in another forum which allowed me to get WHS Power Pack 1 just the other day. Skipping the instructions I simply dumped everything in the MSS/Software directory and initiated a Remote Desktop session and installed it from there.... Done!

WHS MSS upgraded and my WHS Connect Software as expected complained about a need for an upgrade by flashing (!) on the taskbar icon as well as (oh, thank you MS guys for thinking of backward compatibility issues) in the original WHS Connect console. Looking good so far.

------------------

I've gone back to the document today to see if I missed some steps and to verify the installation. Its still a multi-disk system but am not ready to just turn on disk duplication back on for my critical multi-media files just yet. The aim of my beta test is to (1) ensure the installation works, and funny enough it was Patch Tuesday yesterday so there's possibly a new update available and so (2) ensure that patches are installed successfully.

There two-(2) consoles I'm using WHSC on and per the update instructions there's a manual way to get the update from the WHS (on page #19), which I did. And why is that? Simply because using the download instructions from the beta document got me a possible update from Microsoft but it wasn't connecting to my MSS! Best assumption then is to get what was really packaged where it was installed thus the above steps done.

Right then, on to verification but not before seeing what would happen if I followed the written instructions on page #12. Clicking on the "Update Now" button resulted in the following window inside WHSC.

Ah, so was this a result of the Power Pack 1 update or were these patches from Patch Tuesday? Looks to me that IE 7's being updated so it must be the latter. More on this later.

And suddenly, an Application Error on [homeserverconsole.exe]. Uh, WTF? Clicking on the "OK" button resulted in that WHSC v.1 session crashing. Fine, closed it and moved to the WHSC v.2 session which was of course locked off from registering and connecting to the MSS due to inability for a concurrent session.

Now WHSC is based on Windows 2003 server, so why aren't concurrent sessions allowed?!!

Once more check if the update pushed through, and apparently it did (oh really?).






Here's the version check as mentioned from page #17. It plainly shows WHS with PP1, and components at version 6.0.1771.0













When in doubt, check again. So I made an RDP session and discovered that apparently the updates continued to go on regardless of the previous application error, and is now requiring me to reboot.














In fact, the reboot timer did this for me. And yes, just last night I refused the reboot on my Windows XP production machine since I had a couple of emails that were pending and earmarked for response... But nooooo, the system went ahead and did it in my sleep!













Bummer, now I've got to go back and re-read and possibly miss responding to some items. (Hello MS Office 2007 guys, a good feature would be to re-open messages in similar cases. Someone work with the patch update team please?!).

Alright, so the HP MSS EX475 rebooted successfully. I did a once over update check again and WHSC reports no more updates available. Via RDP the system profile shows I'm still running WHS SP2 after the update. Unfortunately, the WHSC still tells the story of Hotel California, that my update is current as of 1969.



"Good night", said the watchman. We are programmed to deceive. "You can check out any time you like, but you can never leave."

PS> A quick comment on the new WHSC is that during all the tests it was running alot better, by that I mean it had faster response. Something tells me the WHS Team may have sped up some connection problems either as part of the update or inadvertently. For that, I'm really thankful! You guys rock.

AND NOW, on to other hurdles like configuring the server to host either this blog or a portion of it; as well as figuring out how to start serving pictures and video for the family back home in Baguio City. Mama Linda, Jeng, Ashley, Jaune, Jay, Tin, Gavin, Len, Craig -- we miss you!

HP MediaSmart EX475

This is probably my 2nd system reset attempt tonight and its driving me nuts!

After seeing my friend's Joe and Laura's use of the EX470 for their web server use I decided to look around for similar products.

I've already got a Promise NS4300N which also serves as my FTP and file storage backup, just recently upgraded to have an iTunes and BitTorrent plug-ins (and before that my lowly LAN|Drive was dong all the FTP and file sharing).My blogs (this one included) are happily hosted by Blogger. To reach me on whatever protocol I've already used DynDNS to redirect wherever. My trusty old Netgear WGRv4 has been so far redirecting all traffic where it needs to. So why even?

The answer is simple. Even after switching to Gigabit ethernet my NS4300N wasn't performing to the standards. File transfers were ok but iTunes took a little more buffering time. Besides, I technically don't own it and so it makes sense for me to move all my personal stuff off of it in the off hand just in case, you know?

Looking thru an online bulletin board I happened on someone selling about a hundred bucks cheaper than what I would pay even if I did go with Fry's sale price this weekend. Justifying the need vs cost, I went for it.

The big problem here is that the EX475 (a 1TB implementation of the EX740) had already been pre-configured for someone and I didn't want to have to call the seller until the last option After all, this gadget guru wasn't going to give up on a system until it gave way to splitting its innards ... which is really close on this system mind you.

------------------

Its almost 4am, time for a nap.


(image courtesy of HP.com)