Technology Burner Technology Burner

So you've collected information about your IT needs, you've thought deeply and grokked your problems. Now what?

read more

Suppose you had about 20 Windows servers to manage. Furthermore, suppose that you’ve lost track of what file shares are on each server — and who has permissions to them.

That’s the situation I’m in. I really need to document the shares and associated permissions for all of my servers. If nothing else, just to get a line in the sand and have something to use as reference when new shares are requested.

Help me find a better way!

Right now I visit each server (via remote desktop) and go to the Computer Management console. Expand “Shared Folders” and click on “Shares”:

I had my first experience with obtaining and installing an EV SSL (extended validation) certificate this week. I had expected the entire process to be much more grueling than it really was. Not that I’m complaining, but for the money you pay for these things… well, I expected to be worked over a bit more!

The EV SSL cert is intended to show that the cert holder has been a bit more rigorously validated and their identity “proven” via a background check. The idea here is that when you see an EV SSL on a site, you should feel even more comfortable than if you see a “regular” SSL certificate. Marketing folks love things like this that generate a “feel good” impression…

I had my first experience with obtaining and installing an EV SSL (extended validation) certificate this week. I had expected the entire process to be much more grueling than it really was. Not that I’m complaining, but for the money you pay for these things… well, I expected to be worked over a bit more!

The EV SSL cert is intended to show that the cert holder has been a bit more rigorously validated and their identity “proven” via a background check. The idea here is that when you see an EV SSL on a site, you should feel even more comfortable than if you see a “regular” SSL certificate. Marketing folks love things like this that generate a “feel good” impression…

Last night I headed downtown to one of my data centers to upgrade a server. The server, an HP DL380 G5 (I usually add some Tim Allen style grunts after saying that) has been running a single quad core CPU since I rolled it out last fall. I’ve had the second CPU “kit” sitting on a shelf at work for a few months, but am just now finally getting the chance to install it.

With my new CentOS (Linux) servers, I wanted to be sure that I didn’t fall in to the trap of having them do any sort of automatic updates. I don’t do that with Windows servers and I sure don’t intend to start with Linux servers either! That way lies madness, right?

I have two servers on which I still use MozyPro for backups. The clients associated with these servers need offsite and secure backups and MozyPro has traditionally worked well for me for that.

Actually, let me clarify: MozyPro worked well for me until the backups got too big. Then it became awful and I switched over to LogMeIn Backup which I’m still quite happy with. But as mentioned above, I still have two servers with relatively small backup sets that I left with Mozy.

Had another lost afternoon today. Same problem. Different server. Previous solution didn’t work. Maddening!

Said “screw it” this time and convinced the developer to “strong name” it and it worked fine from the GAC.

I can never decide how long to keep server boxes around. For instance, I’m in the process of doing a few production build-outs and have a bunch of boxes stacked up. Typically, once the servers are racked at the data center I’d hide the boxes for a few months and then ultimately pitch ‘em once I needed the room.

That’s not very methodical, is it?

That stack in the picture (in my office) inspired these musings