Skip to main content

We learn by reinstallation..

After two weeks of scratching heads and thinking hard i finally got the IBM server up and running once again. It was really a great experience on my part being new to this stuff so i jot down some thoughts that might be of help the next time i fool around with the DNS server

1. Configuring the servers RAID setting was abit tricky and it presented some issues that i learned through the process
a. You cannot just remove a partition using fdisk if the drive is in an array. You need to enter the raid setup and manual remove the mirroring before proceeding with the next step.
2. Branded server like IBM provides installation CD that will help you configure and setup the server and the good thing about it is that it provides a way to set up scripts to do unattended installation of some NOS.
3. Installing windows 2003 server is as easy as installing Windows XP . Configuring it though is a little bit tricky.
4. DHCP setup is fine, DNS a little confusing and at last i got DCPROMO working!!!!!
5. Sharing the internet connection was a bit tricky..The trick i made was to make use of RRAS and everything went just fine that is before the DCPROMO.
6. after placing Exchange server and SQL server on the same machine everithing is rolling out fine.
7. Last step was for ISA2004 to be installed . before actually disconnecting our network from the temporary KERIO firewal and proxy i made sure that all necessary rules to enable internet connection was allowed and after a few transfer of cables .i on to a good start...publishing all other servers available (SQL,DNS...) and allowing necessary traffic to pass..

Things need to be done:

1. Install Terminal Services
2. Configure the Email Services
3. Publish Website

Seems a hard task considering this month of september is the pilot implementation of the new Student Information System created using C#..Damn im excited...cant wait to see my creation being used by other people...

Its good to ease some pressures off my head..till the next blog.........

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

The Story Behind the Name C#

I remember one time in an exam for employment , the first question was - who is the father of C#? I have been working with the language but never did I ask myself who actually started the language ( of course Mirosoft was the brainchild , right? ) . After a googling expedition I found out who was the culprit - Microsofts Anders Hejlsberg . I was not interested why it was called C# then , but opening my VS2008 today , I stumbled on one of the articles being shown at the VS2008 opening page - "Computer World: The A-Z of Programming : C#". Its an interview with Anders discussing the history and beyond of C# . Heres the cool part , the name for C# prior to its release was actually COOL (C like Object Oriented Language) . Below are some lines taken from the interview: Why was the language originally named Cool, and what promoted the change to C#? The code name was Cool, which stood for ‘C like Object Oriented Language’. We kind of liked that name: all of our files were called .coo...
Post a Comment
Read more