office Professional 2010 x86 Beakersoft Blog Blog

[proxy545]

0 So, we at the moment have a RIS server setup on Windows2000, its now incredibly out of date, the base image has only got XP SP1 on and I cant see anyway I can just upgrade it, we could only ris clients through the subnet the servers on,office Professional Plus 2010 x64, and we wanted to run the DHCP services about the server.
So we made the decision to create a new Windows2003 based ris server. This really is what I had to go through to have it operating:
oFirst of all I required a duplicate of Windows XP with service pack two on it, to use as my XP base image about the server. There’s quite a good web site about it here
Basicly you duplicate the contents of the XP cd to your hard disk, extract the sp2 download to your hard disk (xpsp2.exe -x:c:sp2), then run the update app in the i386update folder of the extracted sp2 and point it to your original xp file. Then you’ll have a very nice and up-to-date copy of Windows XP. Copy it onto cd or a server assessable by the new ris server
o Now just install the RIS service by using the control panel/Add remove programs/Windows Components. Then you should get a Remote Install services under admin tools. Before running that you need to Authorize the RIS server to the domain. You do this (for some reason) using DHCP manager. See the Microsoft article here. Once you have authorized the server, run the new RIS setup application, point it at your new xp setup files and you should have the RIS server ready to go.
o The next thing we needed to do was not run the DHCP server about the same server as RIS, and get ris functioning across subnet’s. When we first installed ris I couldn’t find any way of doing this, but I have this time!
There are 2 scope options you can set in DHCP:
066 – Boot Server Host Name (Basicly the TFTP server the client will use)
067 – Boot File name (the file to utilize around the server to boot the PC)
Set the boot server host name option to be the IP address of the ris sever (give the server a static address) ,windows 7 ultimate x64, and set the boot file name to be OSChooseri386startrom.com
Add these options to each DHCP subnet you want to implement this RIS server on and the PXE consumers should be able to find the RIS server and its boot file.
o Now one of the most tricky parts. Adding 3rd party drivers to the base image so that a) the basic RIS setup program will run, and b) the Windows XP setup will run.
We did most of the hard work with this when we setup the old RIS server. The best article I found on it is here. This article basicly says duplicate certain driver files to certain parts of the folder structure,microsoft office Ultimate 2007 product key, and update your .sif file to look for the files in these location. When we did this originally we had to manually hack the drivers inf files to acquire them doing work on Dell GX270′s and 280′s but I don?t think that’s required anymore. If you need the drivers email me and I can send you them.
o At this point you should be able to now boot your client pc,microsoft office Standard 2007 key, and it should pick up the ris server and boot from it (as long as you have setup the DHCP options for the subnet your client is in).
Before doing this I copied in the existing ripref.sif file in the old server, as this contained all the options about joining the domain, the product key ect. Its probably worth sorting this file out before doing an install or the install will ask you questions and it still wont be unattended There are various sources to the web that will tell you about the settings, or use can use the RIPrep wizard, as described here
o Something that I never came across about the Windows2000 RIS was it failing to join a domain (if you set that option in the .sif file) If this happens you might have to run the delegate control wizard at the root of your domain in active directory users and computers. Just add the domain admin’s and any other groups that will be RISing, and make sure they have the ability to add computer accounts to the domain.
o The final problem I came across was when I pushed an image back to the server. It went back no problems, so I copied into the templates folder of the new picture what i thought was a good .sif file.
When I then tried to use the new image,office Professional 2010 x86, i kept getting an error saying
‘txtsetup.sif is missing or corrupt. Error 21′
I had a look around for this error and it turned out the problem was with the .sif file I had copied in. There were some new options in the [OSChooser] section, that the image necessary to find the original mirror. So I re-created my new picture, and instead of copying the good .sif file over the one it created, I just added all the sections I essential to this one.
That was it, took me a few days to get it functioning correctly but its definitely worth it in the long run, when you have 150 machines to setup!