Silent Bob

I have to admit that I don't use neither AutoRIS nor AutoImage myself (though I'll have a look at the latter when there's time), but I really admire your work. I have a fully working RIS server with very customized images. All scripts and programs comes from a central file store, independent of the RIS server or images. I've got -one- script pr image, which launches the other scripts from the file server dependant of image properties. All batch-based, since I haven't had time to learn VB yet (shame on me). Anyhow, the case is, to build a new image (which happens frequently), I copy one original SP2-based image, integrate BTS driverpacks with RISult, integrate hotfixes with the /INTEGRATE switch since there is no norwegian update packs for RVM yet, integrate NIC drivers and then write a script for the image which decides registry tweaks and software. All of this have been done pretty much automatically, except for the write part which basically is just editing a sample script. But now, the Driverpacks API has changed and RISult is currently useless. And AutoImage seems to have picked up the API and managed to automate the process of including them in RIS already. I did it myself manually, but it's not a funny job. So I'm considering to switch to AutoImage, which will work fine for just me, but I need to write a full documentation of my work along with a guide for making a new and updated image with drivers since I'm not working here anymore a few months from now. And it needs to be easy to understand. It was very simple until the Driverpacks API changed. And finally - the question: Is there any way to script AutoImage? That would save me for a whole lot of work. All I need is the ability to integrate the Driverpacks automatically, the rest I have my own solutions for. Or, is it possible that you add the ability to integrate hotfixes with the /INTEGRATE switch (to make it easy to update later), or kind of like nLites method? If any of those two were possible, it'd be incredibly easy to make a new, updated image with drivers and all, and i could make a guide and/or a script that even my grandmother would understand. The question got wrapped in a whole lot of useless information. Here's the short version: I need a way to automate the process of integrating BTS Driverpacks and hotfixes without RVM, and I'm basically wondering if you could help me. Thanks a lot for your precious time, you are a real hero here on msfn. If you ever come to Norway, drop me a note and I'll buy you a beer

I haven't tried this, but your line doesn't look right. Try: REG ADD %KEY%\005 /V 1 /D ""\\server\it$\Software\Office\Office 2003\CD1\setup.exe" TRANSFORMS="\\server\it$\Software\Office\Office 2003\cd1\New Custom Setup File.MST" /qb-" /f If you remove the spaces from your MST and Office folder, you might launch without the quotes (if they are the problem). I'd probably rename the MST and do it like this: SET OFC="\\server\it$\Software\Office\Office 2003\CD1" REG ADD %KEY%\005 /V 1 /D "%OFC%\setup.exe TRANSFORMS=%OFC%\Custom.MST /qb-" /f But basically I just think your RunOnceEx line is wrong. Try the one I pasted first

Yeah, I'd love to use RVM, the only problem is that I need Norwegian images, hence also Norwegian updates. I've thought about trying to make a Norwegian update pack for RVM a long time, but I just don't have the time. I've got like a million projects at once right now. Maybe I could try to gather up some of the Norwegian members (I've noticed quite a few of them around) of the board for help, but I haven't got that far yet. About BTS driverpacks, they're already included in my images. That went surprisingly easy, and I'm about to build my own driverpack for everything BTS doesn't cover on our PCs. The only downside of integrating BTS in RIS images is that it is hard to maintain and update (compared to a CD source), but it is still way easier than installing all drivers after install. I'll take a look at RISult eventually (tried AutoRIS though), but both mainly to see different solutions of things and/or inspiration. Or, now that I feel kind of comfortable with RIS, maybe I'll be more willing to let someone else do the job for me. I just like to know what's going on "under the hood" before I do things

Hmm. Thanks for the answer. I'll look into what I can do from VBscript (or give my boss a real kick in the a**). I've just started with RIS and I'm planning to try out some of your scripts from the guide in the near future. Now I've got like 10-15 batch scripts, and half of them could be replaced by a few more powerful VBscripts. A little practical question while we're at it: How do you implement updates in your RIS images when you're not using RVMs Update Packs? Now my image is just a plain vanilla slipstreamed XP Pro SP2, but I want to integrate all hotfixes too. I've thought of running a few "critical" (like Windows installer etc) from svcpack.inf and then the rest from RunOnceEx (just a script to start all hotfixes in a directory on a file store for easy maintenance), but I'd like to hear other methods. Is it safe/recommended to integrate a bunch with nLite on a CD source and build a risetup-image of the updated source? And again - thanks a bunch for your precious time and effort, I've practically learned everything i know about RIS and unattended setups from this site

Hi. I've been playing around with RIS on a Windows 2003 server the last month, and have started to install PC's at work from the server rather than from my unattended XPCD (they're practically the same, all scripts and programs are launched from a central file store of practical reasons). As I've played around, I've found more and more methods to make my work easier. And now I want clients to be able to reinstall their machines themselves. I'm using risetup images with BTS Driverpacks and some programs via RunOnceEx. But now I want my clients to be local administrator on their laptops. Does anybody have any suggestions on how this could be made? The only thing I've tried so far is to have the users (who need local admin rights) in a group, and assign local administrator rights on that group during install. That works, but my boss doesn't like it, he wants only the owner of the laptop to have adminstrator rights. I've thought of one solution myself. That is to get the username from a .osc file during text-mode setup and use it later in the install process with net user or something like that, but I don't know exactly how. So - any help or suggestions would be appreciated

I use: start /wait %FSUA%\dotnetfx86-2.0.exe /q:a /c:"install /l /q" from a script to install .Net Framework, and it works perfectly. Download from here. Tried the same switches on the language pack, and it seemed to work too. I'm pretty sure a quick search would give you the same result. And the same switches on the executable from RunOnceEx shouldn't be a problem. About the other problem, what parts are english? What more have been done to your source (like nLite, etc)?

Try: [NetOptionalComponents] NetMonTools = 1 ...from what I could see in ref.chm

Hi, could someone PM me an invite for Live Messenger? And Live Mail if possible? Oh, and if mail is easier, send to aaaargh at googles mail service (also called gmail.com)