RogueSpear

I exclusively use method 2. A little while back I was using my own hybrid of 1 and 2, but I've found 2 is almost always the faster install and it's certainly the best for space. One of the inherant benefits of method 2 is the WatchDSP.exe. That should be preventing the warning you are getting. So I guess I'm curious if WatchDSP.exe is somehow not executing for you. Perhaps your presetup.cmd is looking in the wrong place. Presetup.cmd, while great, can be very difficult to debug because you don't get any error messages.

I'm just wondering if it's best to start over with my various presets when I update to a new version of nLite or if it's safe to keep my existing ones. For instance, when things change in the tweaks section or if a removal is seperated into two seperate parts - stuff like that - will the newer nLite recognize the no longer valid entries in a pre-existing settings file? Some of the settings I have, depending on the target, can be pretty detailed. Up to now I've been starting over with every new version just to be safe. Just thought I'd inquire if I can skip the ritual.

Method 1 or 2?

From the error message, it appears to be a browser security issue. Since you're using RIS, you're probably in an AD domain. Are there any GPOs setting IE security someplace?

This utility just keeps on getting better! Keep up the great work

Honestly, it could be any number of things. I am going to go on the assumption that all of your RIS clients join the domain that the RIS server is a member of. And that the user account that you are initiating the RDP session with is a domain account that has the right to RDP to the target. These are all basic things that we sometimes forget about. I was looking over my .SIF file that I use in my RIS deployments and noticed the following entry: [TerminalServices] AllowConnections=1 You may want to stick that in your template file and see if it helps.

First, it would be better if you started a thread at the new support forums. Second, I'll need a little bit more information. The AutoIt error is an error in the BASE slipstreamer and from looking at the screenie it appears to have something to do with 3rd Party DPs. If you have a log that would be helpful in determining if the issue is BASE related or AutoImage related. I'm leaning towards BASE as I've seen similar screen shots over at Bashrat's forums regarding 3rd Party DPs.

Like I said, I've been deleting that account for years. And I live and breathe by RDP. It's possible it's needed for Remote Assistance, but I've never used that before.

Remote Desktop does not require the HelpAssistant account. I don't know if you're using any of my scripts or tools, but they delete that account by default.

Version 1.03 is released and can be found here. While very long overdue, this release is not very big on new features but there are a lot of changes to maintain compatibility with Bashrat the Sneaky's DriverPacks and to blend in with AutoImage. And of course there are some improvements and bug fixes. I have a few ideas for new features to be implemented in v1.04 which should not take nearly as long now that the major changes and testing with AutoImage have been completed.

Ok, it's not perfect, but I think it's good enough for some widespread testing... Here you go!

KB888111 seems to be the most infamous.

Everything that you've documented to me looks pretty good. Here are the relevant parts of a .SIF file that I use. You may want to take look over it and see what differs. You may want to double check your entries against the help file found in deploy.cab. There are some entries that require a 1 or 0 while other require a yes or no. Some seem to require quotes while others don't. ;SetupMgrTag [Branding] BrandIEUsingUnattended=Yes [Components] AccessOpt=Off chat=off deskpaper=off freecell=off hearts=off hyperterm=off media_clips=off media_utopia=off minesweeper=off msnexplr=off OEAccess=off pinball=off solitaire=off spider=off templates=off WMAccess=off WMPOCM=off zonegames=off [Data] AutoPartition=1 DisableAdminAccountOnDomainJoin=1 floppyless="1" LocalSourceOnCD=1 MsDosInitiated="1" OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" OriTyp="4" UnattendedInstall="Yes" [Display] BitsPerPel=32 Vrefresh=75 Xresolution=800 YResolution=600 [FavoritesEx] [GuiUnattended] AdminPassword=<<encrypted password goes here>> DetachedProgram= EncryptedAdminPassword=Yes OEMSkipRegional=1 OemSkipWelcome=1 TimeZone=%TIMEZONE% [Identification] DoOldStyleDomainJoin=Yes JoinDomain=%MACHINEDOMAIN% [Networking] InstallDefaultComponents=Yes ProcessPageSections=Yes [OSChooser] Description="WinXP SP2 - Custom" Help="This will install Windows XP SP2." ImageType=Flat LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" [RemoteInstall] Repartition=Yes UseWholeDisk=Yes [SetupData] OsLoadOptions="/noguiboot /fastdetect" SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [Shell] CustomDefaultThemeFile="%WINDIR%\Resources\Themes\royale.theme" [TapiLocation] AreaCode=555 CountryCode=1 Dialing=Tone LongDistanceAccess="9" [TerminalServices] AllowConnections=1 [Unattended] AutoActivate=No CrashDumpSetting=0 DriverSigningPolicy=Ignore FileSystem=LeaveAlone Hibernation=No NonDriverSigningPolicy=Ignore NtUpgrade=No OemPreinstall=Yes OemSkipEula=Yes OverwriteOemFilesOnUpgrade=No TargetPath=\WINDOWS UnattendMode=FullUnattended WaitForReboot=No [UserData] ComputerName=%MACHINENAME% FullName="User Name" OrgName="Company Name" ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXXB [WindowsFirewall] Profiles = WindowsFirewall.TurnOffFirewall [WindowsFirewall.TurnOffFirewall] Mode = 0

I don't know what "LegacyNIC = 1" means and I can't seem to find reference for it in the help files from Deploy.cab. You may want to omit that entry. Another thing to try is to verify that when the OS is installed, that PnP enumeration will detect your driver as suitable for the NIC when you manually point to the driver (from Device Manager).

I have have really come to despise the way Microsoft made this unnecessarily confusing. Ok, it sounds like you have the PXE boot up part of things working just fine. I am guessing that since you did, you either edited the .inf file yourself or downloaded a specially made driver with the .inf file already edited for you. The part where confusion can come in is here. Make sure you are not using the same .inf file in both places. The .inf file in \i386 is the specially edited one. The .inf file that is called by OemPnPDriversPath should be unaltered. In fact driver signing will fail if it is. Another common omission (guilty of it myself) is forgetting to put OemPreinstall=Yes in your .SIF file.

It could be that he wants one computer to be a member of two different subnets as a router, gateway, etc.

Technically speaking, it's two NICs on a single PCI card, but yes.

3Com, Intel, and Broadcom all make PCI based NICs with dual interfaces. I've difficulties bonding the interfaces on a 3Com, but no problems at all with Intel and Broadcom. With all three you can set the interfaces independant of each other no problem at all. The cards tend to be rather pricey as they're aimed at the server audience and for some reason almost anything server oriented is always triple the cost. Another option would be to get a motherboard with dual NIC interfaces which seem to be more and more common these days. Personally, I would avoid any nForce board because their NICs are just a complete PITA.

Let's not start that crap here. Please.

Update - 20060709 Updated Paint.NET to V2.64

You should check out this utility.

Well I use Maxthon, not Firefox. I did use Firefox for about 9 months but I grew tired of it, tried Maxthon and never looked back. I don't use Thunderbird either. I either use Outlook, OWA, or Gmail. BTW something must have distracted me when I updated ieSpell. It looks like it's the old version I have up, but I know I made an updated installer. It may be at work, so I'll check when I get back to the office tommorow.

I did make a tutorial for making these installers. It's not all encompassing, but it's a good start. Search the phrase "AdminSudio" in this forum and it should be in the top 10. And I'll check in the ieSpell link now. This is the first it's been reported to me as not working.

Desktop Sidebar operates that way. I believe it's closed source freeware, but there's an SDK for others to make their own plugins. The system works rather nice. On the downside and as was pointed out by Alanoll, it would likely require a huge amount of recoding to make things modular.