Br4tt3

I think this has been discussed earlier as there are a limited way of deploying an image with intergrated applications within it: I will suggest what I think u should do; 1. RipRep - several images possible. Downside is of course, the number of images to maintain over the time... also, riprep is pain in the back to support when it comes to hotfixes and so on... I recommend: 1. One generic flat RIS image, for example WinXP SP2 integrated into it... 2. On the question onto having one image, with custom added applications depending on who is going to use it, u could solve that with the usage of the .osc screens that comes with the RIS installation. This will provide a more flexible way of customizing ur install depending of which groups of students that will utilize the client upon final install. A link where we discussed something like this; http://www.msfn.org/board/index.php?showto...80211&st=15 the actual feature that makes u able to select which application that gets installed, comes on page #3.

Just load diskpart from the command prompt and check wheather u have access to the local disk... personally, I have only seen it failing on some RAID/SATA/SCSI devices, no ATA... Are u using the boot.wim from the Vista DVD as the boot OS within WDS? Have not tried that version u r refering to but the earlier ones, required u to use that boot.wim from the CD to get the WDS client working...

Did u actually obtain drivers specific for Vista to Dell GX260?

maby, right now the firware levels and BIOS versions are all A01 from Dell so...

Hi! This is not really an issue, more of the curious nature... The thing is, I use WinPE 2005 which is burned to a DVD, when booting the WinPE CD on a machine configured with one RAID controller (RAID0) and some 418 GB C: volume, the CD boot process wont work... If I reconfigure the same controller, same machine to use a C: volume with for example 50 GB, the CD boot goes just fine... any ideas??? Curiousity killed the cat, right?

Yup... I guess that does it! never seen that one before...

Never heared of read load, guess that is reg load...

Dunno to much about the riprep technique as I am using flat RIS images... easier and better IMHO, anyway, wrong forum, move to RIS and they will help u out...

Hi! I dunno for sure.. but reading the registry: (following key) HKLM\SOFTWARE\CLASSES\ Below this key, u will find for example each known file association, for each file ending there is a value: Content Type - RegSZ - application/<application> For example, my HKLM\SOFTWARE\CLASSES\.doc which one would expect to be associated with Word reads: Content Type - RegSZ - application/msword Should be easy to test if this is the place to do it.... prolly could do this using read load or something!

Hi! If using the same boot image for the two machines and 1 is working while other is not, I would say it is drivers... The loader (white loader bar) is using UNDI so that will prolly work with all machines when booting them. U can try to take the same .wim and burn onto a CD/DVD and boot from that one and check if u can detect a NIC and everything else.. also try to use the physical NIC of the none working machine model when running for example VM-Ware on it or VPC. That way u will know if there is for example anything wrong with the NIC driver...

It will verify: 1. Verify that services are started properly (BINLSVC) 2. SIS (Single Instance Storage) service is enabled and working 3. Verify that the IP address that the machine is listening to, is authorized in the AD 4. Verify that it can find a DHCP server which can service clients... I also found out that it (on Win2003) changes the inital boot files if they have been changed, for example the startrom.com if it has been renamed into startrom.n12....

The current design of what can be called RIS 2.0 from Microsoft, to support inhouse Win2003 deployment of Vista and later OS's is called WDS (Windows Deployment Services) an can be obtained from Microsoft as a beta software. Currently it is planned to be RTM upon release of the Vista OS flavours to companies... atleast when I spoke with my MS dude the last time! WDS features converting riprep images into .wim which is the new image format for Vista. I have not used this feature as I personally think riprep is a pain in the a**, but maby it is something good anyway! As long as ur network is fully switched, the load from an OS install to a client should not cause any issues for you..

Seems cool, gonna download it and check it out... bbl!

The closest I can come up with when the WinXP setup is reading the specific parameter, JoinDomain is T-29!

[Unattended] Repartition=No If I am not mistaken, the Repartition entry of the winnt.sif file is only valid for RIS based installations, not CD/DVD unattended installs...

Hi! I assume u have tried running: risetup.exe /check.... and also, I have personally seen where the DHCP UI tells u that RIS is authorized in the domain but when checking the Sites & Services console, enable NetServices from the View menu, then expand the Services object and then at u will find NetServices, u will not be able to find the IP address of the RIS box listed in there... I am not saying it is this, but check it! also, did u change the IP of the machine recently? is the machine multihomed? and is the RIS box creating the computer accounts in an OU other than Computers (which is a CN and not an OU)? sometimes I have gotten wiered messages when creating the accounts in other OU's and lacking permission to do so... (oh, u r domain admin.. guess not then!) but I can say I have seen this exact msg...

Hi! I strongly encourage u to: 1. Create a script that will install and configure the native RIS component for u in an unattended fashion.. 2. The RIS box mostly will be dependent on disk I/O and network connectivity during client installations.. it will not consume loads and loads of RAM or CPU resources... no need to worry as long as u have reasonable RAID controller in the machine.. 3. To save space on the RIS machines and not spending hours on wiered riprep errors, USE a flat RIS setup... better, safer and all other superlatives IMHO!!! 4. Consumation of network bandwidth u say... 2 clients a day on a 100Mbit cable, no worries.... 5. Will you be using Win2003 or Win2000 RIS? I would recommend 2003.. 6. If u r gonna place ur RIS component on a DC, be sure that u (lik u mentioned) have a seperate drive volume for that component... u dont wanna have the SIS (Single Instance Storage) process running thorugh ur ntds logs or something 7. For performance boosts, I guess all u can do to pimp ur RIS box is to have the volumes split (OS on one channel and the RIS component on another channel) over the RAID controller. 8. And if u read Microsoft documentation before doing certification tests on Win2003 there is one golden rule: "Add more RAM" - Adding RAM is never wrong!

I guess u have two options that I can think off: 1. Hve some kind of OS that u can execute the command from (WinPE or BartPe) or; 2. Winnt32.exe /? provides you with the following optional parameter(s): Ex. <Winnt32.exe /cmd:command> Description: "cmd:command_line Instructs Setup to execute a specific command before the final phase of Setup. This occurs after your computer has restarted and after Setup has collected the necessary configuration information, but before Setup finishes." Hope it helps..

dunno, but [GuiRunOnce] seems to do the trick for me unless u want it even earlier...

As long as u wanna boot a client/server over the network onto a remote source (this is called PXE..) u r pretty limited to having DHCP around. This has nothing to do with RIS, there are hundreds of PXE server softwares out there with atlest one thing in common... they all work with DHCP! U really need to get DHCP up and running as the client machine (the one u r pressing F12 from..) is hardcoded to broadcast after an available DHCP server for a lease.....

We are also using a Linux DNS/DHCP at our place and it works out nicely with RIS.... however, booting a client without a DHCP solution into PXE will NOT work, this is not a limitation of RIS, rather the boot chip on the client. U will get an error something like: "Error requesting IP address - PXE client error"

Post the original .inf / .oem files content or attach the files so that we can have a look at them...

Hi! I am using an unattended install CD/DVD to install Windows 2003 SP1 into our domain. The CD/DVD is working smoothly on all other machine models except the new models from Dell. I have added drivers for the NIC but the unattended install fails to create the temp AD account during install. I have specified the: [Identification] JoinDomain=MyDomain.com into the unattend file. However, I have succesfull in adding the new models as well a coupple of time, but it fails most of the times. When reading the c:\windows\debug\netsetup.log file, I can find the following entries: LOG BEGIN: 08/18 08:50:19 NetpDoDomainJoin 08/18 08:50:19 NetpMachineValidToJoin: 'MyCompany-VM1NWO8BV9' 08/18 08:50:19 NetpGetLsaPrimaryDomain: status: 0x0 08/18 08:50:19 NetpMachineValidToJoin: status: 0x0 08/18 08:50:19 NetpJoinDomain 08/18 08:50:19 Machine: MyCompany-VM1NWO8BV9 08/18 08:50:19 Domain: MyDomain.com 08/18 08:50:19 MachineAccountOU: (NULL) 08/18 08:50:19 Account: MyDomain.com\MyComputerAccounter 08/18 08:50:19 Options: 0x40001 08/18 08:50:19 OS Version: 5.2 08/18 08:50:19 Build number: 3790 08/18 08:50:19 ServicePack: Service Pack 1 08/18 08:50:19 NetpValidateName: checking to see if 'MyDomain.com' is valid as type 3 name 08/18 08:50:19 NetpCheckDomainNameIsValid [ Exists ] for 'MyDomain.com' returned 0x0 08/18 08:50:19 NetpValidateName: name 'MyDomain.com' is valid for type 3 08/18 08:50:19 NetpDsGetDcName: trying to find DC in domain 'MyDomain.com', flags: 0x1020 08/18 08:50:23 NetpDsGetDcName: failed to find a DC having account 'MyCompany-VM1NWO8BV9$': 0x525 08/18 08:50:23 NetpDsGetDcName: found DC '\\DCSEHBG-NT6002.MyDomain.com' in the specified domain 08/18 08:50:23 NetpJoinDomain: status of connecting to dc '\\DCSEHBG-NT6002.MyDomain.com': 0x0 08/18 08:50:23 NetpGetLsaPrimaryDomain: status: 0x0 08/18 08:50:23 NetpGetDnsHostName: Read NV Hostname: MyCompany-vm1nwo8bv9 08/18 08:50:23 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS domain name: MyDomain.com 08/18 08:50:23 NetpLsaOpenSecret: status: 0xc0000034 08/18 08:50:23 SamLookupNamesInDomain on MyCompany-VM1NWO8BV9$ failed with 0xc0000073 08/18 08:50:23 NetpJoinDomain: status of setting machine password: 0x534 08/18 08:50:23 NetpJoinDomain: initiaing a rollback due to earlier errors 08/18 08:50:23 NetpLsaOpenSecret: status: 0x0 08/18 08:50:23 NetpJoinDomain: rollback: status of deleting secret: 0x0 08/18 08:50:23 NetpJoinDomain: status of disconnecting from '\\DCSEHBG-NT6002.MyDomain.com': 0x0 08/18 08:50:23 NetpDoDomainJoin: status: 0x534 LOG END: I am almost certain that it is a case of either a bad driver for the NIC (that only sometimes is fast enoguh to get an Ip and join the computer to the domain) or the network switches that are messed up... strange thing, when in installing another model onto the same switch port, everything works, but when changing the "none working" model to a working port, it fails... Driver or? some one know any good way to proceed troubblshooting this one?

Hi! I previous tried booting a WinPE 2.0 .iso of the HDD which had the XP bootloader onto it, but I gave up, couldn't do it! When I launched the WinPE 2005 from the same drive, that could be done, with the old RAM boot parameters specified into a .sif file, but not anymore... I just faced the fact that the bootloader for the RIS and the WinPE 2.0 are not working great with eachother...

Sorry, could not resist the temptation... ur nick sounds really funny in swedish!