Allistah

Hi there. Sometimes they're not joined to the domain. I have some configs that join them to workgroups. Do you happen to know anything about this adminpw.osc file and how to use it? It seems that the TYPE=LOCALPASSWORD is undocumented or something. I haven't been able to find any info on it. Yes, I'm doing RIS installs that were made from the files from a CD. I'm not adding anything special, just adding my NIC/sound drivers in the $OEM$ dir. No other packs or anything. Any idea on this?

Hey all.. So I have some more information about this. I've got a little farther, but it still isn't working right. I modified the oschoice.osc file to point to the adminpw.osc file. Then the adminpw.osc file points to warning.osc like the oschoice.osc file used to. All of that works. The screen comes up fine and allows you to enter your password. It will even complain if the passwords aren't the same (you have to enter the password twice to make sure you typed it in right). I think the part where I'm going wrong here is in the sif file. Before I get to that, let me show the variable names that are being used for the password in the adminpw.osc file: Password: <BR><INPUT NAME="*ADMINISTRATORPASSWORD" TYPE=LOCALPASSWORD MAXLENGTH=20> <BR> Confirm Password: <BR><INPUT NAME="*ADMINISTRATORPASSWORDCONFIRM" TYPE=LOCALPASSWORD MAXLENGTH=20> Now typically you'd just put the input name into the sif file surrounded by % %. For example, if you had <INPUT NAME="PID" MAXLENGTH=29> in your osc file, you'd put %PID% in the sif file to inherit the data that was entered for that variable during the CIW (Client Installation Wizard). I thought about just putting %*ADMINISTRATORPASSWORDCONFIRM% but I just don't think that's correct. I'll give it a try in a bit to see if this will work but I don't know if this is the right way to do this. If anyone has any information on this, please let me know. Thanks, -Allistah

So there is a file called adminpw.osc. I want to make use of this file so that the user can set an admin password during the CIW setup, before windows even starts loading. Anyone know how to do this? Thanks, -Allistah

Hm, I thought there might be a way to put a command in the RunOnce or something and have that kick off the unattended setup of Office. Is that not the right way to do it or is that not possible? Here at work they have something like that and I wish I could figure out how they did it. They have the option to install Office in the OSC file, and then when Windows is done installing, the Office setup kicks off and does it's install. Any idea how they did this?

Hey all. Does anyone have any simple examples of what I would need to do to add an option in one of the OSC files to install Office 2003 and then have it auto install once the RIS install was done? I've tried googling for the answer and searched here but I haven't found any answer. If I knew how to do this, I could do this with any other apps too provided they had a full unattended setup option via the command line. Thanks for any information anyone might have for me. -Allistah

Thanks for replying. I'll make sure that I only do method 2. So at this point I should be setting RunBTS to NO in the autoris.ini file right? Now since I'll be doing that, do I just follow the instructions for his stuff manually? I mean, I've already run the slipstreamer file and it unpacked(unzipped, whatever) something which was pretty fast, unlike method 1 where it unpacked stuff for a number of minutes. Is that what you see when you do a method 2 (it unpacks stuff really fast and then is done)? So after I do that, is there anything else that I should be doing manually before I run autoris? The reason I ask is that I went ahead and did an run with AutoRIS with what I thought was all the drivers and when the OS was done installing, it didn't detect my Intel Pro 1000 MT NIC. So I thought I must have done something wrong with the BTS portion of the setup. Thanks for the help RogueSpear, I appreciate it. All the other stuff and AutoRIS seems to be working just fine. :-) Hey btw, since you've got a lot of experience with RIS setups, have you been able to get two DHCP servers in a 50/50 config to work where the RIS server is only on one of the DHCP servers? Thanks again, -Allistah EDIT: Hey, can I just skip all the BTS steps and add my own drivers to the $OEM$ dir once the image is on the RIS server? I've manually done that in the past for my Intel Pro 1000 and it seemed to work fine. EDIT: If I do this: "If you do not need to integrate mass storage drivers into your RIS image, all you need to do is copy the Driver Pack 7-zip archive files into the $OEM$\$1 subdirectory and use my Method 2 Helper Addon On." can I just copy all of the driver packs to this directory and all the drivers will be included? Also if I do this do I need to set OEM=Yes in the autoris.ini file? Whats special about mass storage drivers? If I want those in my drivers, do I have to do something different? Sorry for all the questions, I'm just trying to understand all this stuff to make sure I'm doing things the right way.

Hi RogueSpear, I have a question about your instructions.. On Step 9 or 10 (can't remember off hand) when I'm supposed to make a fresh RIS image on my server, is that supposed to be XP SP0 or XP SP2? Also in the instructions, I struggled a bit with the BTS part because I had no clue what that was. Also it says the "first part" and I didn't know what the first part was. I'm still going through this and trying to get it to work so I'm hoping I'll be able to post back soon with some good results. Thanks! -Allistah UPDATE: Ok, so I did a full install with the AutoRIS image and it worked. I did not however get my NIC detected. It should have been though since it's an Intel Pro 1000 and I added the BTS NIC driver pack. I'll play around with it again and see if I did anything wrong. BTW, when I'm doing the BTS stuff, should I be choosing method 1, 2 or 3? I want the method that works the most often without issues. Thanks again, a great tool. :-)