Br4tt3

I am not a expert on programming but does Delphi appz need runtimes? I have some things that pop into mind but I dont wanna use another runtime unless it is vb or .net that is to be provided. Thanks...

No native support for it that I am aware off... only way around it, is if u boot into some other deploy OS from RIS and then kick of the install from there, then again, that wouldn't be a "RIS install"

I do it exactly like this, depending on who is logging on, if they r member of that application group, the icon is displayed, otherwise hide it. That way I dont "confuse" the end users...

I am having issues getting one of my new models joining the domain when using the unattended CD/DVD installations. Another model, using the same NIC, the same software driver version and the same physical cable as the one that didn't work joins the domain with no problems... and of course, the same CD as well. What I am searching for is the T-x minutes timeline, but I cant find a good layout of it. I wanna pin down at which point the unattended setup tries to execute the value: [Identification] JoinDomain=mydomain.com That way I can see if there is a temp AD object created and troubbleshoot it from there... Thx in advance!

Hmmm.... I dont understand it but anyway... reommend: [GuiRunOnce] Command0 = "Start /Wait cmd.exe /c c:\install\Install-Application-1.cmd" Command1 = "Start /Wait cmd.exe /c c:\install\Install-Application-2.cmd" Command2 = "Start /Wait cmd.exe /c c:\install\Install-Application-3.cmd" And it still doesn't work? Then try adding one application and then the next one until done... to figure out if there is one specific install that messes up the flow..

Dell is also using some kind of Linux distrib. to boot the machine initially. Anyway, I am not much of a penguine guy but I think they have like 9909099 sorts of filesystems.. the other guys are running Red Hat of the machines but there is no probs reinstalling the machines using RIS and Windows. I am using the following within my .sif file: [Unattended] ExtendOemPartition=0 FileSystem=ConvertNTFS [RemoteInstall] Repartition=Yes Usually when a new machine arrives, I have to go into the RAID controller UI and set up the logical volumes and so on.. have u cjecked that this has been done from the controller?

Reading from the deploy.chm file, they use the same entry as for setting the domain suffix as u do... Only diffrence from what I can tell, is that they have the [params.MS_TCPIP.Adapter1] with a 0 in front of. I dunno if that makes a diffrence, also they specify the same entry (DNSDomain) up in the [params.MS_TCPIP] section as well... In case it doesn't work out, I think u can specify the same setting using the netsh.exe command which is scriptable as well for u during installation.

Hi again.... From what I can pick in ur post, u r adding/telling the installation to add setup actions of applications (through the use of RunOnceEx) from the cmdlines.txt (T-12)? My question is why? Maby there are some features to this that I am not aware of, the only thing that pops into mind is that it is a good place to add entries to ur default profile/hive and so on.... I strongly recommend u to launch the installation sequence(s) from the [GuiRunOnce] section of the unattend file. That way u have better control over the flow when using either batch files with the Start /Wait functionality or using Windows Scripting Host (.js or .vbs) where u will have excelent control over the installations... Check the previous posts, and there is examples on using the WScript.Run features to control the behaviour of the app installations. NOTE: Make sure that the installations sources in unpacked when using the for install. For example: Some applications (especially .exe files using InstallShield according to me...) that comes in the format of .exe's sometimes unpacks a .msi or something else to a temp dir, once done it will launch another process to handle the actual installation (for example setup.exe or setup.msi). In this case, the .vbs script will not work because the script looks at the first process to end before continuing. So unpack if necessary is my advice... Over to the sausages again...

Hi! We also use machines shipped with the new TOE (TCP/IP OFFLOAD ENGINE) NIC's. As a part of this to work we also of course needed to deploy the SNP pack to the servers and clients. However, I didnt include it in the WinPE image.... So far, I have seen improvments on large files when copied, however, it does not seem to do much for me when copying many small files. Also, as for now, the biggest win is for iSCSI devices we use! I will have a go on this one and see if I run into the same problems as u... Just some info: 1. Which WinPE are u using? WinPE 2005 or? 2. Based on Win2003 SP1 or XP? 3. What does ur code do? what is it searching for? NOTE: I have seen that the installation of the Broadcom drivers/app adds WMI instances when installed from within the full OS. I am using a Broadcom NIC, driver version 2.6.14.0...

Unless u ran: (when creating the syspreped image) sysprep.exe -nosidgen the mini setup will auto regenerate a SID for u....

Hi! I personally have changed settings to the sysprep.inf after an image has been created with no problems, but my guess is that it would depend on what settings u wanna change... I just added new directories to be scanned when running mini setup (OEMPnPDriversPath) with no apparent issues..

Hi! I agree.... same goes when u wanna service pack clients, they in some cases need the source files/i386 depending on how the clients have been installed.

Sure... go ahead and try it out, either using the shutdown.exe or something else. Keeping the champange on the rocks for u.... gl & hf.

My code for performing the installations(winnt.sif): [GuiUnattended] AdminPassword = "MyPassWord" <-- More than 8 char. enclose pass in "" AutoLogon = Yes AutoLogonCount = 3 Maby this will do it....

Hi! Like I said, I never used RunOnceEx or cmdlines.txt so no expert on that part but as from what I can gather in ur previous posts: 1. Autologon features was working when launched from cmdlines.txt! Then keep that code within this file and the autologon part should be working later on in the installation... as I see it, there is no need to link to another file that will be executed and install software from this point. Do that from the [GuiRunOnce] section of ur winnt.sif file instead. 2. Once the setup will perform an autologon for u, the execution of software installations are easiest handled from the [GuiRunOnce] seciton of ur unattend file. Please specifiy it as; [GuiRunOnce] Command0 = "Start /Wait c:\install\<software-install-all-clients>.cmd" Command1 = "Start /Wait c:\install\%software-install-selected-clients%.cmd" <-- variable feat. disucssed COmmand2 = "cscript.exe c:\install\<what-ever-else-to-do>.vbs" Note: In the batch files, supply a "Pause" so that u can stop and halt and check which file is running and so on.. Once u r comfortable with the flow of the install, remove the "Pause" and it will be totally unattended, same goes for vbscripts and wscript.echo. Also, try to just to get the autologon feat. working first from the cmdlines.txt part with no software installs. Then, go and add the entries of the [GuiRunOnce] section and u will see it comes together. Checking in later, getting a sausage... mmm... mmm.. Never tried it, but I dont think so... unless .vbs or .js scripts can be run at the T-12 mark. Easier if u just get the autologon feature working. Once there, just add the installation scripts to the [GuiRunOnce] section assuming the code within these scripts are working (which u said they did). Danish sausages r0x..

There are loads of info on how to use/cutomize WinPE with the WinPE forum, basic flow of the installation sequence when launching XP from WinPE is: 1. Creating a custom WinPE, using the OPK 1. Boot into WinPE 2. Startnet.cmd runs 3. Execute diskpart script 4. Execute format of drive 5. Launching Winnt32.exe to run a GUI setup of WinXP/2003...

Hi! Cant say I have seen this earlier... what media are u booting from into WinPE? Are u running WinPE from HDD/PXE/USB/CD/DVD? If u run the diskpart script (I assume u r using this to partition and format the drive) will it throw up an error or something that's related to a file lock on the drive or anything?

Hi! We have two Dempsey's here that we are not using cause we upgraded to Woodcrest. I want to put them into use, which socket on the mother? Saw some guy mentioning < Socket 771 > - Is that correct or?

Hi! Please check out this thread as it seems as u could be facing the same problem as discussed in here... Guess, u need to decide if to install something, but dont know where to search or determine the criterias for the decission (hope I spelled that one right)...

Hmm... Yup, sounds like if u r on to something there. I assumes the login.cmd contains the same code as u were running in the RunOnceEx.cmd file (which was working) and is applicable to all the clients, either if installing the specific software for one department or the other, correct? Then move that code back to the cmdlines.txt file (if it was working from that point..) and keep the specific department installation script in the [GuiRunOnce] section? Also, dunno know if u already seen this, but u can also specify the correct domain autologon with the regkey: HKLM\SOFTWARE\Microsoft\Windows NT\Current Version\WinLogon\AltDefaultDomainName When using batch files for execution and u wanna have control on it, then execute the script with Start /Wait params to get the process, to halt and wait until the first process has been performed before moving onto the next one.. Use ECHO to display something in the screen so u can keep track during development. P.S Once done, try moving from batch to WSH (Windows Scripting Host) instead because u have much better possibilities to control what is happening when launching sequential actions. Oh, and one other thing, when launching multiple actions from the [GuiRunOnce] section u need to specify it as follows: [GuiRunOnce] Command0 = "my first command" Command1 = "my second command" Command2 = "and so on..." If not using the Command0 before each <command> to run, setup will perform the first action and then move along (as a result claims.cmd is not being executed). Hope it solves it for u...

Hi! Sorry I am not following u on what it is u need to get it to work at this point? please elaborate... Is it the part with the autologon or what? or is that it loggs u on using local credentials rather than domain credentials?

Thats right kids, stay of the crack! and welcome to msfn dude...

lo and welcome to the msfn forum... nice to have u along with us!

U stated above u had a file named RunExOnce.cmd (now, I am not familiar with RunExOnce at all so bare with me.. ) but instead of having one file, u create multiples, for example named: 1. Claims.cmd 2. Ensign.cmd 3. Legal.cmd 4. Accounts.cmd Now these files will of course contain the code for installing software based on their departments, so far so good... For the time being we assume u store these scripts in ur root c: drive ($OEM$\$1) Now, if u create a custom .osc screen that will allow u to assign an variable that will handled/translated into an value (as written in the .osc screen) and then executed within the [GuiRunOnce] section of the .sif file it would be something like: .sif file before written to the client disk: [GuiRunOnce] Command0 = "c:\%RunExOnce%.cmd" We assume u tap in "Legal" in the .osc screen when pressing F12 and following the wiz. Once the .sif is written to client, the %RunExOnce% is translated into, guess what? "Legal" and the .sif that is to be executed on the client contains the following entry: [GuiRunOnce] Command0 = "c:\Legal.cmd" In other words, if u write Accounts, then it would say Accounts.cmd and so on... should solve ur dilemma if I understood u correctly! Hope it helps.. otherwise I am out of possibilities unless using the .msi/AD/SMS thingy's.

Hi again! Software to be installed on all machine: Intergrate into the main RIS installation is the easiest. Personally, I dont like intergration unless it is security patches. Software to be installed on a selection of machines: All I can think of is etiher as discussed, having some kind of criteria to base the decision on and a script to handle that criteria so it becomes automatic or if u r using tactic to place out the newly installed RIS clients in the correct OU structure. If u r placing the clients automatic into their correct OU structure (prestaging) then it is eazy. Just assing a login/startup script to that OU and have the installation take place from there. Of course, u can also have a combination of them, create a .osc screen where u can choose to place ur computer into the correct OU, a script will move to computer to the correct OU, once there, the startup/login script will take care of the installations...