Silicon Shecky

So this week has been an interesting week for me from an install standpoint. I got to load up from scratch my first Windows Server 2008 machine, and let me say that I am actually impressed.

The machine is going to a remote office, and needed to be laoded upto be a DC and file/print server on a Windows 2003 SP1 network, which I thought would make life interesting. Usually you find all sorts of odd things when integrating different Server OSes. Not as much in this case.

Active Directory was going to be my biggest worry, yet once I ran the adprep off the 2008 disk on the 2003 DC, everything jsut slipped right into place. The wizards that 2008 uses are fairly simple and straight forward, and did a great job of promoting the server.

The other item of big importance was DFSR for file replication and again, the install and setup of it was amazingly simple.

Yes, 2008 uses that darn Vista GUI, and yes I still don’t like how exploring files and folders (especially the network) is set up with it, its a small, superficial complaint to the ease of 2008. After install I found that 2008 booted faster than 2003, and was just as capable of a server OS. The other complaint I have about it is that it is too simple. I did not see a chance to customize my install initially, which I would like to have the option of.

The whole install and configuration took me 1 day and the file data replicated overnight easily, bringing all the NTFS security information with it.

Honestly, as much as I think Microsoft gets a lot wrong, so far I would say the did something right with server 2008.

Keep watching as my test server finally came in and I am going to be doing a review of SBS2008, installing from scratch soon.

So, while reading the other blogs and news sites I check daily, I came across this interesting article. It seems that Microsoft’s .NET 3.5 SP1 has caused yet more problems. This time with Exchange 2007 on SBS 2008.  With this latest issue that has now cropped up with .Net 3.5 Its time to remember a few things…

1) In Microsoft’s defense, they can’t test everything before releasing stuff. That is why hot fixes exist.

2) Never just accept patches. Always find a way of testing them yourself, even if it is on a personal machine, and research the patches also to see what problems other’s have had. The more reports you find, the more prepared you can be about any issues with it.

I know they are simple thoughts, but just watching how Microsoft has screwed up with this latest version of  .Net it just amazes me that people don’t think of these things. Course, I am one to speak.

So, being in the world of IT, there are many hats we all tend to wear. Sometimes many at once, sometimes at different times. Within all of the different hats there are certain things that stay the same, and can make each of us better. Here is the list of things I tend to do to try and make life easier, not only on me, but on my clients and company.

1) Plan Plan Plan! I can’t stress enough how important a good plan is for anything. Whether it is a move (physical or jsut moving shares), a new deployment, or even trying to fix a problem. Having a plan of attack will always make things go smoother.

2) Keep an open mind! We as techs tend to keep our sight narrowed, but this honestly is one of the worst things we can do. Closing your mind to the possibilities, no matter how far out they might seem, limits us, and can cause problems down the line. A great example was years ago when I was learning how to build machines I spent 6 months trying to figure out why I was getting no sound. The one thing I didn’t try until I was cleaning up my work area was making sure I had the jacks plugged into the right spots. Turned out I have the mic plugged into the speaker spot and the speakers pkugged into the mic. My narrow focus on a hardware problem cost me a lot of time and wasted energy.

3) Think of worst case scenarios! If you think of all the things that can go wrong, come up with what you would do if those things do happen, things will go a lot more smoothly. Not only will it save you time, but you will come out looking even better in the end because you thought things through. As a rule of thumb I always add time beyond what it should take when planning out a project as a standby in case things go wrong. As Scotty from Star Trek Said about multiplying his repair time estimates by 4, “How else do you think I got known as a miracle worker?”

4) GOOGLE!!! It never hurts to google thoughts and ideas. You can come up with both potential issues, find out if people have done things the way you are planning, and other ways to complete a project.

5) Check and Double Check everything before you start! Just to make sure you didn’t miss something. Ona recent in house project not only did I map everything out, but I went over the mapping 5 times to make sure I knew everything inside and out before I started.

Using these sorts of guidlines will not only help make you  a better IT guy, but in what can be a thankless job, will make you look great to your bosses and the people who count!