Sunday, December 17
Dr. Strangeinstall
(Or how I quit worrying and learned to love Remote Installation Services)
Ok, if you are a regular reader, you might remember way, way back in 2003 I was in a Coma for a while.
At that time I had recently upgraded a bank to Windows 2000, and had setup Microsoft's Remote Installation Services (RIS) on one of their shiny new servers, complete with a separate Image Partition. We were supposed to roll out all new computers to the bank that year, and I was looking forward to working out RIS, and getting the PCs setup that way.
Then came the Coma, and I was out for a little over three months.
While I was out, all the systems got installed, but no one bothered with RIS.
Flash forward to 2006 and now the guy I worked for at that bank is my new boss.
I get to install RIS.
Ok, so I've got a junked Compaq DL380 server with 4 9.1 GB HDDs that I can use as a test bed. Ok, setup one drive for booting, the other three as a 18GB RAID 5. Loaded Windows 2003, patched, joined the domain. Loaded and configured RIS as per the following documents from Microsoft:
Step-by-Step Guide to Remote OS Installation
An old Windows 2000 White Paper on installing RIS that a friend sent to me and I can't find a link for any longer.
Ok, loaded RIS and ran the RIS setup with my handy dandy HP Windows XP SP2 CD-ROM with no problems.
Loaded my new HP system using their media and my Windows NT SIF setup floppy without issues. However, when I went to run RIPrep.exe, it failed out. E-mailed my buddy, I have to go and find the updated version of RIPrep.exe for Windows XP.
Still had issues, getting the image up to the server worked well, but pulling the image back fails with an issue that no network card driver for my hardware was present in my image.
Back to the research. So, I found this article How to Add OEM Plug and Play Drivers to Windows XP at Microsoft Support, and using the instructions to create the Drivers directory structure in the Root of C:, then creating the Sysprep directory and configuration file.
Now I could push the image up and pull the image down. I have a good base image for our current standardized system.
Next step, try it with the machine joined to the domain, fully patched and with Office 2003 installed.
Works great.
As a final step, we actually have four discreet banks, and some of the software is unique to each bank, so I created four more loads, each prepped for one of the banks we own.
To test this we rolled out a RIS imaged set of systems to a brand new bank. It worked great. The only issue we encountered was the need of a DHCP server at the site where we were working. To resolve this problem, I found a great piece of software called ipLease that is a little tricky to use, but a great DHCP server. I used it to create a 2 address scope with a 60 second lease. So the two addresses are usually free after you set the static IP on your machine, you just have to remember to do an "ipconfig /release" command just before setting your static IP address.
Overall the project was a huge success, the time it took to rollout a new branch was much less than any branch rollout I have ever done. I even created and tested a Ghost DVD for system restore purposes and it worked with flying colors. RIS is a really great product.
Here is one more guide to Remote OS Installation I found while working on this project.
I'm off to Waco to setup a new branch this week and train our tech support company from that regoin on how to roll out a branch to my new standards. Should be a fun few days.
Ok, if you are a regular reader, you might remember way, way back in 2003 I was in a Coma for a while.
At that time I had recently upgraded a bank to Windows 2000, and had setup Microsoft's Remote Installation Services (RIS) on one of their shiny new servers, complete with a separate Image Partition. We were supposed to roll out all new computers to the bank that year, and I was looking forward to working out RIS, and getting the PCs setup that way.
Then came the Coma, and I was out for a little over three months.
While I was out, all the systems got installed, but no one bothered with RIS.
Flash forward to 2006 and now the guy I worked for at that bank is my new boss.
I get to install RIS.
Ok, so I've got a junked Compaq DL380 server with 4 9.1 GB HDDs that I can use as a test bed. Ok, setup one drive for booting, the other three as a 18GB RAID 5. Loaded Windows 2003, patched, joined the domain. Loaded and configured RIS as per the following documents from Microsoft:
Step-by-Step Guide to Remote OS Installation
An old Windows 2000 White Paper on installing RIS that a friend sent to me and I can't find a link for any longer.
Ok, loaded RIS and ran the RIS setup with my handy dandy HP Windows XP SP2 CD-ROM with no problems.
Loaded my new HP system using their media and my Windows NT SIF setup floppy without issues. However, when I went to run RIPrep.exe, it failed out. E-mailed my buddy, I have to go and find the updated version of RIPrep.exe for Windows XP.
Still had issues, getting the image up to the server worked well, but pulling the image back fails with an issue that no network card driver for my hardware was present in my image.
Back to the research. So, I found this article How to Add OEM Plug and Play Drivers to Windows XP at Microsoft Support, and using the instructions to create the Drivers directory structure in the Root of C:, then creating the Sysprep directory and configuration file.
Now I could push the image up and pull the image down. I have a good base image for our current standardized system.
Next step, try it with the machine joined to the domain, fully patched and with Office 2003 installed.
Works great.
As a final step, we actually have four discreet banks, and some of the software is unique to each bank, so I created four more loads, each prepped for one of the banks we own.
To test this we rolled out a RIS imaged set of systems to a brand new bank. It worked great. The only issue we encountered was the need of a DHCP server at the site where we were working. To resolve this problem, I found a great piece of software called ipLease that is a little tricky to use, but a great DHCP server. I used it to create a 2 address scope with a 60 second lease. So the two addresses are usually free after you set the static IP on your machine, you just have to remember to do an "ipconfig /release" command just before setting your static IP address.
Overall the project was a huge success, the time it took to rollout a new branch was much less than any branch rollout I have ever done. I even created and tested a Ghost DVD for system restore purposes and it worked with flying colors. RIS is a really great product.
Here is one more guide to Remote OS Installation I found while working on this project.
I'm off to Waco to setup a new branch this week and train our tech support company from that regoin on how to roll out a branch to my new standards. Should be a fun few days.
Labels: coma, health, microsoft, ris
Friday, October 27
Ob-La-Di, Ob-La-Da
Life goes on brahhh....
It's been a crazy two weeks since I started at the bank. Active Directory (AD) replication was broken when I got here, DNS was hosed up, WINS was not working properly. There were also a lot more sites, servers and users than I initially had been told.
Fixed DNS, that exposed AD replication problems and shut down one site for most of a day. Fixed that and discovered that a domain that had been phased out is still lurking aroiund in DNS, and have been working on expunging it from the current domain and DNS. Fixed WINS everywhere. Things are running fairly smoothly.
Mapped out the WAN in an E-Sized Plot, showing our nearly 20 point-to-point T1 connections. Looks like we are going to convert to MPLS and Local Fiber. That should be a fun project next year.
Haven't made it out to many branches yet, just getting everything documented and waiting for a new branch roll-out that keeps getting delayed.
Been working with Microsoft Remote Installation Services (RIS) to get ready for roll outs. what a pain in the ass. Typical Microsoft, great idea, poor documentation. Have had to search through countless Microsoft Knowledge Base Articles, get help from friends and generally be exasperated when I keep getting errors about missing NIC drivers that I know are present.
I'll try to put up some RIS resources in another post once I get this crap all sorted out and working.
This job is great. Never liked one better. Only complaint is that the coffee here is horrible. Guess I'm going to have to get my own coffee maker and stash it in my cube somewhere.
It's been a crazy two weeks since I started at the bank. Active Directory (AD) replication was broken when I got here, DNS was hosed up, WINS was not working properly. There were also a lot more sites, servers and users than I initially had been told.
Fixed DNS, that exposed AD replication problems and shut down one site for most of a day. Fixed that and discovered that a domain that had been phased out is still lurking aroiund in DNS, and have been working on expunging it from the current domain and DNS. Fixed WINS everywhere. Things are running fairly smoothly.
Mapped out the WAN in an E-Sized Plot, showing our nearly 20 point-to-point T1 connections. Looks like we are going to convert to MPLS and Local Fiber. That should be a fun project next year.
Haven't made it out to many branches yet, just getting everything documented and waiting for a new branch roll-out that keeps getting delayed.
Been working with Microsoft Remote Installation Services (RIS) to get ready for roll outs. what a pain in the ass. Typical Microsoft, great idea, poor documentation. Have had to search through countless Microsoft Knowledge Base Articles, get help from friends and generally be exasperated when I keep getting errors about missing NIC drivers that I know are present.
I'll try to put up some RIS resources in another post once I get this crap all sorted out and working.
This job is great. Never liked one better. Only complaint is that the coffee here is horrible. Guess I'm going to have to get my own coffee maker and stash it in my cube somewhere.
Number of people who will never get their time back from reading this page:
