The time has come to say goodbye. It’s been a while since I’ve done anything technical in IIS, hence no recent posts here.
I’m now moving onto management path and don’t expect to come back to server administration in foreseeable future. I also don’t expect to be posting any technical stuff here anymore.
The blog did serve its purpose. I never went full scale into blogging, but the experience of sharing knowledge with others online (in a language that’s not my mother’s tongue) was enriching. Thanks to all who’ve been reading this blog. I’m happy for the few of readers that did let me know they’ve found a solution to their problems here.
I believe the best way to proceed about this blog will be to keep it available for future reference.
If anyone would like to keep this blog live by posting IIS (or related) stuff here, please contact me – I’m happy to let you guys post on this site.
So long, and thanks for all the fish!
Sometimes you may face a situation when W3SVC (AKA the World Wide Web publishing service) is hung in “stopping” state.
From the services panel, you can’t do anything to it, all options are already greyed out.
A great way to stop a hung service is to kill its process – but how to find it? For W3SVC it’s svchost.exe – quite a common system process.
You can find the right one by executing the following command in command prompt:
tasklist /svc | find “W3SVC”
This will show you the PID of the exact svchost.exe running W3SVC.
Then you can go to Task Manager, select View -> Select Columns, enable proces ID and kill the specific one.
That’s it! W3SVC is now stopped, without the need to reboot the whole server.
From past 4 years of using RAID 5 as primary home storage drive experience, I can say: don’t go this way. It’s not as fast as you’d expect. Even with server-grade drives, there are issues every now and then. And the drives just constantly write something, making that familiar noise. It’s more expensive even than mirrored drives, which also give you 1 drive fail safe.
I went from el cheapo Samsung drives to WD server class drives. Sure, the server ones are generating less heat, don’t fail out of nowhere, but still. From time to time I was even getting OS locking up for a second or two, when there were too many things waiting to be read/written to the drives.
On the flipside, RAID is great as an additional storage device. I just switched to Samsung 830 series SSD as my OS drive and kept my RAID for storage. How does that work? Let me get back to you on that in a few months.
Windows Vista brought in a series of security features. One of those is that most of system files are no longer owned by Administrators. Instead, there are special account created that own those files. During normal usage, that’s not a problem – but I just installed a new version of Windows on a new hard drive and wanted to delete the previous one.
Turned out – I can’t, as I don’t have the permission to delete those files. I can’t even get that permission as the files are not owned by me, but by those special accounts (Trusted Installer etc.). I would have to take ownership of each file, that grant myself the delete permission. Luckily, there’s an easy way to do that recursively using command line. Just run those two commands against specified folder.
takeown /f D:\folder /r
cacls D:\folder /t /e /g username:f
If we take a slight detour into hardware and ethics, I hope you will excuse me. You may or may not have heard that Apple pulled out of the Electronic Product Environmental Assessment Tool (EPEAT) registration system that makes it easier for consumers to buy computers that meet basic levels of environmental friendliness in early July, 2012. The company said that the environmental certification no longer fitted their “design direction”.
It’s one thing for one of the world’s largest computer companies to say that green is no longer a direction they wish to travel, but it is something else if consumers don’t like it. This is what happened in this case and Apple had to u-turn and go back into the system after just two weeks. It just goes to prove that consumers may use their computers for poker.de and watching movies rather than writing essays on ethics, but that doesn’t mean they aren’t concerned about the impact of all the gadgetry they are buying on the environment.
All that was known about the decision was that Apple computers failed the certificate on design – it is thought that this meant that the batteries were glued to the case, which made it much harder to recycle them both separately. The company, perhaps fearing that they would lose US Federal contracts, admitted that getting rid of the certificate was a ‘mistake’ and disappointed many of its customers. Cornell University, the University of California and the city of San Francisco were all preparing to ditch Apple from their list of approved suppliers.
Apple may be the commercial behemoth that often seems to be unstoppable, but the company can sometimes be made to think about the results of its actions. On the good side, it is also actually rated 4/15 on the Greenpeace Guide to Green Electronics.