RogueSpear

The Japanese stuff I can see.. but I actually use the others.

You can also inject all of these values right into the msi file directly. I managed to make a switchless silent installer that works from svcpack.inf and it's at 63.2MB.

Update - 20051219 Added WinRAR V3.51 Removed .NET Framework V1.1 and V2.0 Updated MSN Messenger to V7.5.0322 Updated RAW Image Thumbnailer & View to V1.0 Build 50 Updated VMware Tools to V5.5 I was unable to locate any correspondance in my e-mail showing that I received permission from RyanVM to post his switchless silent installer of .NET 1.1 so it has been removed. Plus he has it posted right on the front page of his web site. After my little outburst in the previous post, I decided to see if I could back up the one and only installer that I did not make with a permission correspondance. I found an issue with my .NET 2.0 installer that only affects some installs. Don't know why, but I'll make an installer once Microsoft fixes the bug that prevents it from being installed from cmdlines.txt. For the time being, once again, I suggest using Ryan's installer as it seems to be perfect. The MSN Messenger installer has several small inprovements in addition to the version update. I did remove the .msi installer however as pushing the .msi from Group Policy resulted in the app being broken. I've never seen anything like it before. I could install direct from the .msi file or the switchless silent installer and everything is fine. Run it from a GPO push and it crashes Anyhow, the switchless silent installer works just fine.

Look here to read about WatchDriverSigningPolicy.exe. The first post is a little choppy and not quite complete IMO but the author, Pyron, hasn't been seen in a while now. Too bad because he was pretty good at this stuff.

I forgot to mention. When the app is installed, the msi file looks for a file called grc.dat in the same directory as itself. If it finds one it will be used, if not then it goes to default (or to any msi switches that might be defined).

Unfortunately Symantec's documentation is just one step above useless. Look on your CD in \Tools\Nosuprt\ConfigEd and run the executable in there. Config everything the way that you want it, the interface is pretty self explanatory, then save your settings as GRC.DAT. Take that file and drop it into the root of your distribution directory. That is where the .msi file is located that group policy is calling the install from.

Some time ago I attempted to run a VBscript from DetachedProgram and was unable to do so. You can however run them from cmdlines.txt but with two serious limitations - WMI is not available at that point and neither is wscript interpretation.

Actually it has not. If you look at their web site it clearly says when it's scheduled for release. If you post anymore crap in my thread I'm going to report it to the moderators. EDIT: Also if you post anymore of my installers anywhere else without asking me first, I will do everything I can to get kicked off of that site too.

Take a look inside of a svcpack.inf file that has some stuff in it and it should be pretty clear. Also you may want to do some reading in the MSFN Unattended Install Guide in order to brush up on the basics. I'm not trying to be a jerk, but this is pretty basic stuff and this thread is not the place for it either. We all gotta start somewhere and the guide is a great place to get more info than you can shake a stick at.

Yea I've haven't had this problem before either, though I have seen some complain about it in regards to the battery driver.

Nevermind.

Well that's a shame. If you want the hacked WGA you can get it in my pack or find it elsewhere. This thread isn't a free for all request line.

Sounds like something for SMS, which would probably be almost necessary anyway after the installs are completed.

I've never used orca before, I'm a AdminStudio guy myself, but if I had to guess I'd say that any msi editor should be able to edit the thing just fine.

By default all users are allowed to install up to ten (10) computers via RIS. At least in a 2000 domain.

I think Kel keeps up a version of his pack with the hacked WGA in it. It's quite enough work for me to keep up these installers and my update pack. Granted I don't update my pack on a daily basis, because it doesn't need it. But there are enough choices out there for you.

I think that OemPnPDriverPath is hard coded to look inside $OEM$\$1\UserDefined. They issue here being that $OEM$\$1 obviously translates to your hard disk, not the CD. It may not do this however, give it a whirl, but I think that's the case. SetDevicePath.exe populates the registry, as I stated earlier, with the path to your drivers. Windows looks here for your drivers. If you have Advanced Registry Tracer or RegShot, try running it against a subdirectory and you'll get the proper reg key and see what it does.

You can set it in the registry quite easily. In fact there's a recent thread in this forum in which Cluberti outlines the registry keys that control autologon. From your description of what is happening, it sounds as though your installation is not properly joining a domain during setup. Is this intentional or by design?

Are you using RyanVM's Update Pack? If so you can find portcls.sys inside of driver.cab. The BTS slipstreamer should detect if RVM had been used on a source and if so it won't actually perform any functions with KB888111. EDIT: Sorry I just noticed you said you haven't done any other modifications.

Actually I think what might get you the results you're looking for would be to use SetDevicePath.exe in conjuction with DetachedProgram. Have DetachedProgram call a batch file named Drivers.cmd which could like like this: SET TAGFILE=\WIN51IP.SP2 FOR %%i in (c d e f g h i j k l m n o p q r s t u v w x y z) DO IF EXIST "%%i:%TAGFILE%" set CDDRIVE=%%i: %CDDRIVE%\D\SetDevicePath.exe %CDDRIVE%\D START %CDDRIVE%\D\WatchDriverSigningPolicy.exe EXIT This assumes that on your CD/DVD the drivers are all within a subdirectory called "D" and that you place SetDevicePath.exe and WatchDriverSigningPolicy.exe in the same subdirectory. I forget what the exact registry key is, but SetDevicePath.exe populates it with the path to your drivers. And there is a limit to length which it can be, which is why I named it "D" instead of "Drivers".

Just an FYI here.. I've haven't had a need for the source cache yet. I use a switchless silent installer that I keep up to date with the post SP2 hotfixes. Install is done from svcpack.inf. Just to see I went to a machine that was installed some time ago, so it was SP2 with no subsequent updates. Went to Microsoft Update, let it download and install the updates, there was no complaining about needing the source. So needless to say I'm a little confused now. I clearly remember running into this problem back with SP1.

I haven't, but this isn't the first report of an issue that I've gotten. What I would recommend is to use the installer that RyanVM made. Same usage, install from GuiRunOnce or RunOnceEx. I know for certain there are no issues outstanding with his installer. I think I will be taking the entry for mine offline until I can get back to it.

BTS made the entire Driver Pack project very modular so that you can do exactly what you just asked. In fact I use some of the third party packs here and one of my own creation. You just need to follow the proper conventions for directory naming and layout and for naming the driver pack itself. I think there's still a sticky thread for creating your own.

Are you able to or have you tried to perform an install on this computer from CD or DVD? If you were able to do it that way, it should translate over to RIS with little or no modification. You may want to take a peek over in the Device Drivers forum and in the Driver Packs forum as there have been numerous discussion regarding nVidia mass storage drivers and the difficulties people have had with them. I think that folks have it up and running now but it took some work to get it down.

It's to my understanding that there is a Dutch and a German version made by others. Not sure about the German. Anyhow, integrating Flash right into the source is not very hard, so I won't be making an installer for it.