mmarable

I did a quick search on Google and came up with this page from Microsoft. http://www.microsoft.com/resources/documen...icb_ui_wbgu.asp I only quickly scanned through it, but it all has to do with running winnt.exe to install Windows from DOS. Since DOS doesn't recognize long filenames it trunkates them all. The setup program will look for a $$Rename.txt in a folder (any folder if I understand correctly) and then it renames the trunkacted files in that folder back to the long filenames they're supposed to have.

Well, I added it to my XPCreate setup and it installed it like it would WMP9. I did have to accept the license agreement, but after that it was automatic. My guess is that since it's still a beta there's little we're going to be able to do. I don't think that there is a switch to install it completely silently like we're looking for, at least not with the beta. I'm sure that the final release will have something, OEM installers are going to expect it. Knowing the resourcefullness and talent of the people here, if it hasn't been found yet, I don't think a "fix" exists. Just my opinion.

When you run ShrinkOffice, does it do its work "silently"? I'm trying it out now, and the last I saw was the "Gathering Information" progress bar after I pointed it to my MST. Task Manager shows it still running, but there are no dialogs or anything. It's using 98% of the CPU but it's been running now for almost 2 hours. Is this normal?

Alex, There is something else going on here. I started with an original (pre SP1) Windows XP Pro CD. My I368 folder is 470MB. I added nothing and just ran the XPCreate script. After downloading SP1 and all the patches my final ISO is only 628MB. What are you starting with?

I like this GM, I really like this. I first tried XPCreate when it still had menus and such and I've got to tell you, going to this current method has been fantastic. XPCreate is well thought out and executed very cleanly. You've done a excellent job, GM.

I have it doing the first run now, but I wanted to ask. You mention a couple of times that it will do various things on the first run. Does that mean that it will only need the source CD that first run, and then use the files already copied to "CDSOURCE" any other times it is run, or am I jumping the gun here? Thanks

Can the XPCTHLST file be accessed locally, or only from a web host? Can I point XPCreate to a hotfix list that I have on my C drive? If I wanted to test a hotfix, or a different set of hotfixes than what is being used by the "standard" file that is hosted on a web host? Let's say that we move on to SP2, so the hotfix list has SP2 and some post-SP2 hotfixes, but SP2 doesn't work with some of my apps, and I need to stay with SP1? Can I create a hotfix list and access it from my local hard drive, or would I have to put it up onto a web host and point XPCreate to it there?

Okay, let this be a lesson to everyone, read the documentation! I started small with XPCreate and never went back to read more of the documentation. I completely overlooked the FILESCD folder until tonight when I went back and read everything on XPCreate. I'm sorry GreenMachine, now it all makes perfect sense.

I ran across the same thing with Office 2003. The Office install would start and then Photoshop would kick off at the same time. My guess is that "Setup.exe" executes some other program and then unloads from memory. The START /WAIT sees it unload and then moves on to the next.

No, it's my fault for being wordy and unclear. From what you two say it will do exactly what I was hoping for. I start with my original XP CD I add in any hotfixes I update the stuff in my $OEM$ (sitting in CDROOT) Run the batch file.... Bada-bing, I have an up to date unattended XP disk. I then just let it all sit until I come up with some changes (new app, new hotfix, drop this, etc.) I make the changes to my files in ..\CDROOT\$OEM$, drop in my original XP CD, run the batch file... My concern was that if I kept doing this a couple of times without having XPCreate erase the CDROOT folder each time that I would end up with some horked up system file(s). I didn't know if it would be better to let XPCreate wipe the CDROOT folder clean each time and I just drag my $OEM$ folder into the freshly created CDROOT and then manually run CDImage. It will do what I was hoping it would. Excellent work GreenMachine. Real nice work.

Okay, please bear with me here. I'm loving XPCreate it's made things so much easier and less time consuming than before for me. This is probably a really silly and simple question, but I'm going to ask anyway. I'm one of those guys who keeps revising my unattended install disk. I add a new app here, update another there, drop this add that, new hotfixes,... you get the picture. I use XPCreate to slipstream in all the hotfixes and such. Can I drop in my $OEM$ folders and such and (making sure I don't have it delete the CDROOT folder) keep running the batch file to update my disk when a new patch comes out? This is wordy, I know, but essentially, can I keep "reusing" my XPCreate files? Seeing that it recreates everything each time I'd image that all the Windows files are overwritten each time. My goal is to run XPCreate and build my disk, and then leave it all sitting on my hard drive. When MS04-018 comes out, I can just drop it in the right folder and run the batch file again to get an up to date ISO. Thanks Mike

I ran into the exact same problem using UnattendedXP and XPCreate to slipstream SP2 into my XP-SP1 CD. It worked prefectly if I slipstreamed SP2 into my original "gold" XP disk though. I don't want to say that there's an issue with slipstreaming SP2 over SP1, but it has never worked for me. Unfortunatly, right now it's all chalked up to the fact that SP2 is still in beta release and not final. So, you're kind of stuck unless you have an XP gold CD to use. I just went back to SP1 and slipstreamed in all the patches, besides XPLode doesn't work with SP2, so I really didn't have a choice.

Can anyone point me in the direction of some good info on MSI installations? I'm slowly piecing together my Unattended CD and I'm getting into trying to set up some apps with MSI installers. I've seen MSTs mentioned, and talk of using Winstall to modify the MSI directly. I'm looking to change the install directory, but if I can also tweak what optional components are also installed for a given app, that would be more than what I was hoping for. Thanks Mike

Thanks Alanoll. I appreciate it.

I'm searching around the forums for this but so far I'm coming up empty. I'm working on an Win2000 unattended CD and I thought I remembered a post here that said that some of the $OEM$ folders are not supported in Win2000. Something like $1 and $$ would work, but not $Progs or $Docs. Is this true, does anyone remember the post(s), or am I imagining things in my old age again? Thanks

I get the error in the XPLode log file below. This is straight from the ZIP file, both the 1.1.2 and the 1.1.0 releases. I just uncompressed them, and ran the "run_with_logging.bat" batch file. Any ideas? thanks -=-=-=-=-=-=-> XPlode start at: 04/04/28 15:49:25XPlode { Loading Plugins (SDK2.0) { Load successful: C:\XPlode\XPlodeAdduserPlugin2.xpd2 Load successful: C:\XPlode\XPlodeExamplePlugin2.xpd2 Load successful: C:\XPlode\XPlodeExecutePlugin2.xpd2 Load successful: C:\XPlode\XPlodeFSOpsPlugin2.xpd2 Load successful: C:\XPlode\XPlodeRegistryPlugin2.xpd2 Load successful: C:\XPlode\XPlodeShortcutPlugin2.xpd2 } Registering commands { Command: addgroup, (0,1) Command: adduser, (0,0) Command: copy, (3,0) Command: delete, (3,2) Command: example, (1,0) Command: execute, (2,0) Command: move, (3,1) Command: registry, (4,0) Command: shortcut, (5,0) } Commandline Parameter: '/help:', Value: '' Commandline Parameter: '/xml:', Value: 'C:\XPlode\XPlode.xml' Parsing XML: C:\XPlode\XPlode.xml { Error opening XML file: C:\XPlode\XPlode.xml Invalid XML syntax. Check UNICODE encoding? } Starting dialog { } Execution thread { }-=-=-=-=-=-=-> XPlode end at: 04/04/28 15:49:25Like I said, this is straight out of the ZIP file. I haven't even begun to try and edit the XPLode.XML file.

Well, this will teach me to read up on something in the forums before I try it. Spent the morning building a slipstreamed SP2 disk (thanks to UnattenedXP), decided that while I was reworking my disk I might as well move up to XPLode from XPInstall. Oh well, I'll give XPLode 1.0 a shot.

I set up my files just like I posted above with the correction you pointed out in the TXTSetup.sif file. Thanks again for your help.

Ausmith1, I tried your suggestion and it worked like a charm! Thanks a lot, I really owe you one. Mike

I took a look at the guide you wrote Ausmith1 and it seems pretty straight forward, but just to be sure here is the txtsetup.oem from Emulex: # # TXTSETUP.OEM - This file is used by Setup to install the Emulex Scsi # Miniport driver lpxnds.sys for Boot-time installation # # (for Emulex LightPulse PCI Fibre Channel Host Adapter) # # Emulex BIOS may be found on our ftp site. It currently supports INT13, # and multi-boot environments, with Private FC-AL an F_Port fabric support. # The BIOS is loaded to the adapter with either the NT or DOS utility. # # format for txtsetup.oem. # # General format: # # [section] # key = value1,value2,... # # # The hash ('#') introduces a comment. # Strings with embedded spaces, commas, or hashes should be double-quoted # [Disks] # This section lists all disks in the disk set. # # <description> is a descriptive name for a disk, used when # prompting for the disk # <tagfile> is a file whose presence allows setup to recognize # that the disk is inserted. # <directory> is where the files are located on the disk. # d1 = "Emulex LightPulse SCSI Software Diskette", \lpscsi, \ [Defaults] # This section lists the default selection for each 'required' # hardware component. If a line is not present for a component, # the default defaults to the first item in the [<component_name>] # section (see below). # # <component_name> is one of computer, display, keyboard, mouse, scsi # <id> is a unique <within the component> string to be associated # with an option. scsi = LP8000 [scsi] # This section lists the options available for a particular component. # # <id> is the unique string for the option # <description> is a text string, presented to the user in a menu # <key_name> gives the name of the key to be created for the component in # HKEY_LOCAL_MACHINE\ControlSet001\Services LP6000 = "Emulex LP6000 PCI-Fibre Channel HBA", lpxnds LP7000 = "Emulex LP7000 PCI-Fibre Channel HBA", lpxnds LP8000 = "Emulex LP8000 PCI-Fibre Channel HBA", lpxnds LP9000 = "Emulex LP9000 PCI-Fibre Channel HBA", lpxnds LP9802 = "Emulex LP9802 PCI-Fibre Channel HBA", lpxnds LP10000 = "Emulex LP10000 PCI-Fibre Channel HBA", lpxnds LP850 = "Emulex LP850 PCI-Fibre Channel HBA", lpxnds LP950 = "Emulex LP950 PCI-Fibre Channel HBA", lpxnds LP982 = "Emulex LP982 PCI-Fibre Channel HBA", lpxnds LP1050 = "Emulex LP1050 PCI-Fibre Channel HBA", lpxnds # This section lists the files that should be copied if the user # selects a particular component option. # # <file_type> is one of driver, port, class, dll, hal, inf, or detect. # See below. # <source_disk> identifies where the file is to be copied from, and must # match en entry in the [Disks] section. # <filename> is the name of the file. This will be appended to the # directory specified for the disk in the [Disks] section to form the # full path of the file on the disk. [Files.scsi.LP6000] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP7000] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP8000] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP9000] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP9802] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP10000] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP850] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP950] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP982] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat [Files.scsi.LP1050] driver = d1, lpxnds.sys, lpxnds inf = d1, oemsetup.inf dll = d1, cocpyinf.dll catalog= d1, lpxnds.cat driver = d1, lpxftr.sys, lpxftr inf = d1, lpsimdev.inf catalog= d1, lpsimdev.cat # This section specifies values to be set in the registry for # particular component options. Required values in the services\xxx # key are created automatically -- use this section to specify additional # keys to be created in services\xxx and values in services\xxx and # services\xxx\yyy. # # <key_name> is relative to the services node for this device. # If it is empty, then it refers to the services node. # If specified, the key is created first. # <value_name> specifies the value to be set within the key # <value_type> is a string like REG_DWORD. See below. # <value> specifies the actual value; its format depends on <value_type> [Config.scsi.LP6000] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP7000] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP8000] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP9000] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP9802] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP10000] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP850] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP950] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP982] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [Config.scsi.LP1050] value = Parameters\Device,DriverParameters,REG_SZ,"SimulateDevice=0;Topology=2;" value = Parameters\Device,MaximumSGList,REG_DWORD,0x81 value = Parameters\Device,NumberOfRequests,REG_DWORD,0x96 value = Parameters\PnPInterface,5,REG_DWORD,1 [HardwareIds.scsi.LP6000] id = "PCI\VEN_10DF&DEV_1AE5&SUBSYS_1AE510DF", "lpxnds" [HardwareIds.scsi.LP7000] id = "PCI\VEN_10DF&DEV_F700&SUBSYS_F70010DF", "lpxnds" [HardwareIds.scsi.LP8000] id = "PCI\VEN_10DF&DEV_F800&SUBSYS_F80010DF", "lpxnds" [HardwareIds.scsi.LP9000] id = "PCI\VEN_10DF&DEV_F900&SUBSYS_F90010DF", "lpxnds" [HardwareIds.scsi.LP9802] id = "PCI\VEN_10DF&DEV_F980&SUBSYS_F98010DF", "lpxnds" [HardwareIds.scsi.LP10000] id = "PCI\VEN_10DF&DEV_FA00&SUBSYS_FA0010DF", "lpxnds" [HardwareIds.scsi.LP850] id = "PCI\VEN_10DF&DEV_F085&SUBSYS_F08510DF", "lpxnds" [HardwareIds.scsi.LP950] id = "PCI\VEN_10DF&DEV_F095&SUBSYS_F09510DF", "lpxnds" [HardwareIds.scsi.LP982] id = "PCI\VEN_10DF&DEV_F098&SUBSYS_F09810DF", "lpxnds" [HardwareIds.scsi.LP1050] id = "PCI\VEN_10DF&DEV_F0A5&SUBSYS_F0A510DF", "lpxnds" So, in my DOSNET.INF I would have: [Files] d1,lpxnds.sys And in TXTSETUP.SIF I would put: [SourceDisksFiles] lpxnds.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] ; Emulex LightPulse SCSI Adapters id = "PCI\VEN_10DF&DEV_1AE5&SUBSYS_1AE510DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F700&SUBSYS_F70010DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F800&SUBSYS_F80010DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F900&SUBSYS_F90010DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F980&SUBSYS_F98010DF", "lpxnds" id = "PCI\VEN_10DF&DEV_FA00&SUBSYS_FA0010DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F085&SUBSYS_F08510DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F095&SUBSYS_F09510DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F098&SUBSYS_F09810DF", "lpxnds" id = "PCI\VEN_10DF&DEV_F0A5&SUBSYS_F0A510DF", "lpxnds" [SCSI.Load] lpxnds = lpxnds.sys,4 [SCSI] lpxnds = "Emulex LightPulse SCSI Adapters" This part I don't understand, but then again it's like 4:30am and I probably should be sleeping. [SourceDisksFiles] lpxnds.sys = 1,,,,,,4_,4,1,,,1,4 I just copied what you had and changed the SYS filename to the Emulex one. Finally, to HIVESYS.INF I would add: I don't know. Looking at your guide, I kind of see where in the OEM file to find the info, but from there it falls apart. In the Adaptec sample, there's only one card to build the reg entries for, but with the Emulex there are 10. The settings are identical in each, but do I need to separate them somehow? Here's my crack at the HIVESYS.INF: [AddReg] ; Emulex LightPulse SCSI Adapters HKLM,"SYSTEM\CurrentControlSet\Services\lpxnds\Parameters",,0x00000012 HKLM,"SYSTEM\CurrentControlSet\Services\lpxnds\Parameters\Device","DriverParameters",0x00000002,"SimulateDevice=0;Topology=2;" HKLM,"SYSTEM\CurrentControlSet\Services\lpxnds\Parameters\Device","MaximumSGList",0x00010003,0x81 HKLM,"SYSTEM\CurrentControlSet\Services\lpxnds\Parameters\Device","NumberOfRequests",0x00010003,0x96 HKLM,"SYSTEM\CurrentControlSet\Services\lpxnds\Parameters\PnPInterface","5",0x00010003,1 This part just loses me: ; Adaptec I2O RAID Adapters HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\dpti2o","EventMessageFile",0x00020002,"%SystemRoot%\System32\IoLogMsg.dll" HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\dpti2o","TypesSupported",0x00010003,7 I found these Registry keys in the OEMSETUP.INF: HKLM,SYSTEM\CurrentControlSet\Services\disk,TimeOutValue,0x00010001,0x3c HKLM,SYSTEM\CurrentControlSet\Control\ScsiPort\SpecialTargetList\GenDisk,LargeLuns,0x00010001,0x00000001 HKLM,SYSTEM\CurrentControlSet\Control\ScsiPort\SpecialTargetList\GenDisk,SparseLUN,0x00010001,0x00000001 Oh, and the directory: $OEM$\$1\Drivers\Emulex9000 I386\SVCPACK Copy lpxnds.sys to \i386 Copy lpxnds.cat to \i386\SVCPACK How far off am I? Thanks again for the help. Mike

I'm hoping that someone might have a suggestion as I'm searching the forums here on this one. I've put together a Win2003 Standard Server auto install CD for work. The CD works great when you don't need to load any additional drivers at the F6 prompt at the start of the install. The problem they ran into today was when they were trying to use it to install Windows on a SAN boot server. At the F6 prompt they loaded the Emulex HBA drivers, the install partitioned and formated the drive, but when it came time to copy the files, it immediately failed to copy the Emulex drivers from the floppy disk. If they skipped the Emulex drivers, the rest of the unattended install ran as normal, but the server bluescreens at first boot. Anyone have any ideas? I'll work on getting a copy of the WINNT.SIF here shortly in case anyone wants to take a look at it. Thanks Mike ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] UnattendMode=DefaultHide OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS Repartition=No WaitForReboot="no" DriverSigningPolicy=Ignore OemPnPDriversPath="Drivers\Emulex9000" [GuiUnattended] AdminPassword=* AutoLogon = Yes AutoLogonCount = 4 EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 [UserData] ProductKey=99999-99999-99999-99999-99999 FullName="Corporate Infrastructure" OrgName="Borders Group, Inc." ComputerName= [Display] BitsPerPel=32 Xresolution=1024 YResolution=768 [LicenseFilePrintData] AutoMode=PerServer AutoUsers=5 [Branding] BrandIEUsingUnattended=Yes [URL] Home_Page=http://corpinfo.bordersgroupinc.com [GuiRunOnce] [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes

I'm trying to find a way to set the position of the Windows Task Bar during the setup. I want to move it to the top of the screen (I have a couple of various task/dock bars that are placed at the bottom). I've been trolling through the registry for so long now that my eyes are crossed. Does anyone know how I can set this automatically? It's no big deal really, just one of those little things I'd like to do just for the sake of doing it. Thanks

This is probably an easy one, but I've been searching through the posts looking for it. Is it possible to use a different account other than "administrator" to do the unattended install with? I've found where I can specify an account to use to join a domain, but I would like to us an individual account that has everything installed under. Thanks