creol

I'm not an expert, but I would imagin that whatever boot CD you are using requires the SATA drivers. Or maybe you are not using a CD? I think with RIS you can use PXE network boot, in that case there must be some way to setup the SATA driver on the RIS server so that it can recognize the HD. Like I said I am no expert so I may be speaking out of my butt. I am booting to BARTPE and doing a network install just using a sharepoint. I do not have controll over DHCP or DNS in our environment so this was the best I could come up with. But my HD's are also SATA and I do not have problems. Hardware is Dell Optiplex GX620 I am interested in what you findout.

I noticed that once I slipstreamed about 20 different patches into my install files, the install is now taking about 10min longer. I also noticed that the kb######.exe files are in the I386\svcpack folder. Could this mean that the patches are reinstalling? Can I just remove the files and the patches are already applied? WinXP unattend install SP2 with many patches via BartPe Thanks for your help!! Creol

This is the unattend command that I use. Keep in mind that I am booting using BARTPE and grabbing the install files from another server. I:\winxp\i386\winnt32.exe /debug2:I:\LOG\Debug.log /makelocalsource /s:I:\WINXP\i386 /unattend5:I:\WINXP\BOOT\Unattend.txt /syspart:c /tempdrive:c The I:\ drive is a maped drive to \\Server\Installpoint The benefits over Ghost are: 1. I don't need to have 10 different images for 10 different machines. 2. I can slipstream patches to the installpoint anytime I want. 3. I can automate via runonce or script any install I need prior to the userlogon. 4. I can add drivers for new hardware anytime I want (or remove them for that matter) 5. I have made BartPe setup so that I can put the CD in the PC and walk away and it will finish the entire install without any user intervention. Back to my original question... I can see that during the inicial install it copies over the entire I386 folder. why can't I make it keep that folder in place once it completes instead of deleteing it? Is there some way to do this? Thanks again!!

I know that with BartPe you need the RpcSS plugin just to modify the HD. Then I use DISKPART with a textfile that contains the commands that first clear all partititons and then recreates the ones that I need. Here is the text of my files: ______________________________________ ::NEWPART.BAT DISKPART /s newpart.txt Format c: /fs:ntfs /Q /V:Local /Y Format D: /fs:ntfs /Q /V:Local /Y ______________________________________ ::NEWPART.TXT select disk 0 clean create partition primary size=6000 assign active Exit ______________________________________ Works great for me. I launch this in the autorun plugin that is provided. P.S. I use BartPE 3.17

Yeah I am doing that now. (I should have mentioned that) but it seams that if the install makes a local copy already why couldn't it just leave the copy there once it completes. Maybe this is silly but I am trying to speed up the install as much as possible. Actually I am using the unattend method, but it pulling the files off of another server. The total install time seams to be about 30-40min. Not too bad when you figure that a Ghost image is about 15min and we are always making changes to the image requireing us to re-sysprep. Plus we were doing alot of application setup that I can script on the fly now without making new images each time.

This is probably a trivial question, but for some reason I cannot figure it out. I tried /makelocalsource and /copysource:Foldername. I just want to leave a copy of the I386 folder that is used during install on the HD once it is complete. Any help would be appreciated! Thank you, Creol

Wow that sucks!!! I have just created the generic work around where I copy the Default profile directly over the local WS profile during the install. I really did not want to go that route. I might even have to create a script that runs with elevated privliges to overwrite the local default profile anytime I update it on the network. What a hack job Novell did on this one!?! In our environment I cannot go Linux. Too bad!!! If anyone has a better solution I would still be very interested in it.

I am trying to roll out XP SP2, and I have one last issue. I wanted to use a Default Roaming Profile that is shared out from the AD server. It is all standard, the Default User folder is found in the NETLOGON folder etc... It works great when I try using it without the Novell Client, but after I install the Novell Client then it will only grab the Local Default User profile. Here is the setup I have on the Network: Workstations = Windows XP SP2 Servers = Win 2003 (no SP yet) Network File Server = Netware 5.1 (thus the need for the Novell Client) Novell Client ver. = 4.90 SP2 Has anyone run into this problem? Please don't tell me it's by design!!! Your help is appreciated!!

I am trying to roll out XP SP2, and I have one last issue. I wanted to use a Default Roaming Profile that is shared out from the AD server. It is all standard, the Default User folder is found in the NETLOGON folder etc... It works great when I try using it without the Novell Client, but after I install the Novell Client then it will only grab the Local Default User profile. Here is the setup I have on the Network: Workstations = Windows XP SP2 Servers = Win 2003 (no SP yet) Network File Server = Netware 5.1 (thus the need for the Novell Client) Novell Client ver. = 4.90 SP2 Has anyone run into this problem? Please don't tell me it's by design!!! Your help is appreciated!! Title Edited - Please follow new posting rules from now on. --Zxian