RogueSpear

Unfortunately I don't have the previous generation of BTS DriverPacks or slipstreamer. The other thing to consider is that AutoRIS probably has some issues with Windows 2003 Server RIS.

I can tell you that the .NLS and .SYS files can remain comressed. As far as the others go, I'm not sure if there are some that can be compressed or not under 2003, but I'm going to guess that a good deal of the .DLL files can be.

@muiz, I'm just curious... do you mean my script didn't work? or decompiling the .exe file didn't work?

It might help to know a little more regarding your circumstances. Was anything removed from the install source with nLite? Are you in an Active Directory environment where Group Policy could be affecting you service settings?

Well under Windows 2000 you can have more file compressed (or uncompressed) and under Windows 2003 some of these same files are mandated to be uncompressed. Perhaps I'm splitting hairs here, but it really does nothing but create inconsistencies from one platform to the next. On another note, it appears that I finally have AutoImage Windows 2003 RIS compliant. Thank god for VMware and 2GB of RAM lol.. created a whole domain with a DC/RIS server, clients, etc.

You also have to make sure that the Application Layer Gateway Service is not disabled.

The guide was written with Windows 2000 Server RIS images as a base. I think I mentioned that in the guide. Anyway, I'm currently discovering some differences with 2003 RIS vs. 2000 RIS. I'm going to guess that some of the files can be compressed, but obviously not all of them can be. You need to compress all of those files to make your image appear as a stock disc based image. What I found out when making the guide was that I didn't have to decompress anything back for the RIS image to work properly. Like I said this was under 2000 RIS. I honestly don't know why Microsoft would have performed this "downgrade", because that's really what it is. But it is what it is and I'm actively looking into what the differences are.

Actually if you d/l AutoImage, the most recent set of driver is in there. Even if you don't want to use the program, all you have to do is copy them.

$OEM$ should be parallel to i386, not within it. Windows |-i386 |-$OEM$ |-$1

I did not put in any password on the new Daemon Tools installers. And I specifically checked the box to allow for decompilation. You should be able to use the AutoIt tool to simply decompile each installer. EDIT: Here are the scripts exactly as I wrote them: #NoTrayIcon Opt("TrayIconHide", 1) FileInstall("SPTDinst.exe", @WindowsDir & "\") Run(@WindowsDir & "\SPTDinst.exe add") WinWaitActive("SPTD setup V1.25", "This program will install SCSI Pass Through Direct") ControlClick("SPTD setup V1.25", "This program will install SCSI Pass Through Direct", "Button1", 1, 1) WinWaitActive("SPTD setup V1.25", "You need to reboot for changes to take effect.") ControlClick("SPTD setup V1.25", "You need to reboot for changes to take effect.", "Button1", 1, 1) #NoTrayIcon Opt("TrayIconHide", 1) FileInstall("DAEMONTools.exe", @WindowsDir & "\") Run(@WindowsDir & "\DAEMONTools.exe") WinWaitActive("DAEMON Tools 4.03HE (32 bit)", "Welcome to the DAEMON Tools 4.03 Setup Wizard") ControlClick("DAEMON Tools 4.03HE (32 bit)", "Welcome to the DAEMON Tools 4.03 Setup Wizard", "Button2", 1, 1) WinWaitActive("DAEMON Tools 4.03HE (32 bit)", "License Agreement") ControlClick("DAEMON Tools 4.03HE (32 bit)", "License Agreement", "Button2", 1, 1) WinWaitActive("DAEMON Tools 4.03HE (32 bit)", "Choose Components") ControlClick("DAEMON Tools 4.03HE (32 bit)", "Choose Components", 1017, 1, 1) ControlSend("DAEMON Tools 4.03HE (32 bit)", "Choose Components", 1017, "{TAB}") ControlSend("DAEMON Tools 4.03HE (32 bit)", "Choose Components", 1032, "{DOWN}") ControlSend("DAEMON Tools 4.03HE (32 bit)", "Choose Components", 1032, "{SPACE}") ControlSend("DAEMON Tools 4.03HE (32 bit)", "Choose Components", 1032, "{DOWN}") ControlSend("DAEMON Tools 4.03HE (32 bit)", "Choose Components", 1032, "{SPACE}") ControlClick("DAEMON Tools 4.03HE (32 bit)", "Choose Components", "Button2", 1, 1) WinWaitActive("DAEMON Tools 4.03HE (32 bit)", "Choose Install Location") ControlSend("DAEMON Tools 4.03HE (32 bit)", "Choose Install Location", 1019, "C:\Program Files\CD-R\DAEMON Tools") ControlClick("DAEMON Tools 4.03HE (32 bit)", "Choose Install Location", "Button2", 1, 1) WinWaitActive("DAEMON Tools 4.03HE (32 bit)", "Completing the DAEMON Tools Setup Wizard") ControlClick("DAEMON Tools 4.03HE (32 bit)", "Completing the DAEMON Tools Setup Wizard", "Button4", 1, 1) ControlClick("DAEMON Tools 4.03HE (32 bit)", "Completing the DAEMON Tools Setup Wizard", "Button2", 1, 1) RegDelete("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run", "DAEMON Tools") If Not FileExists (@ProgramsCommonDir & "\CD-R") Then DirCreate (@ProgramsCommonDir & "\CD-R") EndIf FileCopy (@ProgramsCommonDir & "\DAEMON Tools\DAEMON Tools.lnk", @ProgramsCommonDir & "\CD-R\DAEMON Tools.lnk", 1) DirRemove(@ProgramsCommonDir & "\DAEMON Tools", 1) If FileExists (@WindowsDir & "\DAEMONTools.exe") Then FileDelete (@WindowsDir & "\DAEMONTools.exe")

You cannot run rissetup.exe against a source that has been modified (RVM, nLite). It has to be a stock source. What you need to do is run RVM or nLite against the image generated by rissetup.exe, but this has problems of it's own. You may want to check out my RIS guide here in this forum. It's a sticky at the top.

Ok.. a couple of things. I have not put in any capabilities for AutoImage to run unattended or through the command line. It's a possibility for the future, but it won't happen real soon. The other thing is that I have not put in any capabilities for integrating hotfixes. I figure between RVM and nLite, that would cover most people's need for hotfixes. Lastly, while I have been using AutoImage successfully on RIS images for a few weeks now, it really has not been tested that thoroughly by anyone other than me (that I know of). And I'm beginning to discover some anomolies with non-English sources. If you do decide to give AutoImage a shot, please test it out somewhat before pushing out any clients. So I didn't really give you any answers that help too much. You may want to see if using nLite with AutoImage can assist you with integrating hotfixes. Wish I had some better answers for you Best of luck to you..

Thanks for the notification on that. Hopefully that's the last of the bad links.

Update - 20060716 Updated Microsoft .NET Framework V1.1 SP1 (.zip Addon also available). Removed Microsoft Visual J# V1.1 Redistributable. Added Microsoft .NET Framework V1.1 SP1 and Visual J# V1.1 combo installer (.zip Addon also available). Updated Microsoft .NET Framework V2.0 to install from svcpack.inf and also include KB917283 (.zip Addon also available). Removed Microsoft Visual J# V2.0 Redistributable. Added Microsoft .NET Framework V2.0 and Visual J# V2.0 combo installer (.zip Addon also available). Added Microsoft .NET Framework All-in-One combo installer (.zip Addon also available). This installer includes V1.1 SP1 and V2.0 of the .NET Framework and V1.1 and V2.0 of the Visual J# Redistributables. Updated the RogueSpear Runtimes Package to V1.1 (.zip Addon also available). All of the .zip Addons require either the RyanVM Integrator V1.4 or nLite V1.01 in order to properly integrate. I removed the individual Visual J# installers because they each require their respective .NET Framework as a prerequisite. So instead I made combo installers, in almost every permutation imagineable, for you to chose from.

Hey if it works great. Something to keep in mind, and this would hold true with AutoIt as well, is that whenever you try to put the mouse cursor on a set of coordinates you're really asking for trouble. What if the screen resolution is not always the same, does the application always open in the same part of the screen? Ask yourself questions like that. There are indeed times where it seems as though coordinates are your only option. SpywareBlaster is such a circumstance. They obviously programmed that utility with the intention of thwarting such automation. Presumeably in order to sell subscriptions to their autoupdate service.

I've been coding in VBS for a few years now and I'm honestly unaware of how you can move the mouse cursor with it. You can send pretty much any sort of keyboard command. You may want to investigate using AutoIt which really shines in that sort of thing. And if you're able to figure out VBscript, you'll have no problems figuring out AutoIt.

This has seriously become one of my all time favorites. So much so that I find myself using it rather the Cisco VPN client as a way into the office. It's not always necessary to VPN client to network, and in those cases where client to client will suffice, Hamachi can't be beat.

Update - 20060715 Updated DAEMON Tools V4.03HE to include the new SPTD V1.25. As with the previous release, a copy of SPTDinst.exe is left inside of %SystemRoot% should you need to uninstall the driver. Also new is the first ScriptPack Addon. You can download the .cab Addon Pack for integration using the RyanVM Integrator. SPTD.exe will be integrated as any svcpack.inf based installer would be. 050_DAEMONTools.exe will be placed in \OEM where the ScriptPack will automatically pick it up for RunOnceEx processing.

I am not really able to sit down and develop any sample code for you because I have so many ongoing projects at the moment, however I will point to some of the tools that I use. First, a book called The Windows 2000 Scripting Bible, published by McGraw Hill has some excellent introductory ADSI material. There is a VBscript book published by Wrox that is excellent as well and contains some more detailed and advanced ADSI topics. Then there is the Microsoft tool ADSIscriptomatic that will generate some sample code for you. Keep in mind that ADSI is a very deep and complex topic - more so than WMI in my opinion. What you are looking to do is fairly simple, but I think that you're going to need to understand some of the basics first before you'll be successful in creating the script. Given a little time and research I'm sure that you'll have no problems with it.

If DNS resolution works for local things, and you sure would know if it weren't since AD would fail miserably, yet DNS does not resolve anything to the outside, then there is a DNS issue. Unfortunately with the setup you have, I would be terribly unqualified to give you much advice. Either DNS itself has a config issue, or ISA for whatever reason is blocking incoming DNS traffic to selected hosts. While I have not experienced this particular problem before, I certainly feel your pain. EDIT: btw the reason I come to this conclusion is that your non-browser apps seem to be communicating fine. Most of the time these smaller apps tend to have an IP hardwired in the code, so DNS is not needed. Furthermore, they all tend to go over port 80 since almost everyone leaves that open.

Given the following: Computer A cannot web browse A virtual computer installed on Computer A can web browse Non-browser type applications can find their home server DNS resolution does not appear to be working I would say there is an issue with a service. Make sure that the TCP/IP NetBIOS Helper service is running, even though you probably do not use WINS on your network. Make sure that the UPnP and SSDP Discovery Service are disabled. Make sure the DNS Client service is running and if it is, double check any group policies to see if there is a custom DNS option configured. Are you able to resolve DNS for your local intranet? I have next to no experience when it comes to ISA Server, but it sounds as though you have it configured in a fairly relaxes pass thru kind of mode, so that does not sound like the problem to me - especially given how some other clients are blowing right through it without any issues.

I really don't know what the interaction is with NetBIOS because I've had it disabled since the day Windows 2000 was released. I'm guessing in my circumstance that everytime I manually enter in a remote path that it plops an entry in My Network Places. Periodically I get fed up with it all and just delete them all. I would imagine that even with NetBIOS enabled the items listed are still no more than convenient shortcuts a la MRU.

If you are indeed referring to "My Network Places", that's just a glorified most recently used (MRU) of network traversal. I routinely delete things that clutter it up just like you'd delete a file. What's in there are little more than shortcuts, albeit slightly more functional than a shortcut.

Ok, I guess just to be on the safe side I'll just make them new each release. I've actually got it down to a system since I have three different settings that get gradually more detailed as I go along. So first I make the least, then the next one and so on just modifying the previous.

You should test out your install in a virtual environment before using it on a physical machine. It's not a perfect process, but generally if something screw up in a VM, it will surely screw up on a real machine. Microsoft's VirtualPC is now free, so there's really no reason to not do this. I can tell you that since I made the switch to method two, which was well over a year ago now, I've yet to encounter a driver signing pop up.