Jump to content

Br4tt3

Member
  • Posts

    557
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Sweden

Everything posted by Br4tt3

  1. Hi, So I also use the WinPE 2005 (2003 SP1) based installation, supporting the Dell Perc 5 RAID adapter. This works just fine.... I have all the files in place which I can share if u want me to. However, if we assume that u have added all the relevant entries to the txtsetup.sif file from the percsas.inf file, and then also added the percsas.sys file to the PE i386\system32\drivers (include .cat as well, just in case...) folder, then you, just like u said, should be good to go.... 1. Just bare in mind that megasas.sys and mraid35x.sys is for the "old" PERC drivers, u need to add the specific percsas entries to the txtsetup.sif file. 2. U dont have to add the percsas.inf file to the PE's i386\INF directory, if the required entries from the percsas.inf file was migrated to the txtsetup.sif file. Below follows the entries that I have in the specific files: TXTSETUP.SIF [SourceDisksFiles] percsas.sys = 1,,,,,,_x,2,0,0 [HardwareIdsDatabase] PCI\VEN_1028&DEV_0015&SUBSYS_1F011028 = "percsas" PCI\VEN_1028&DEV_0015&SUBSYS_1F021028 = "percsas" PCI\VEN_1028&DEV_0015&SUBSYS_1F031028 = "percsas" [SCSI.Load] percsas = percsas.sys,4 [SCSI] percsas = "DELL PERC 5/E Adapter RAID Controller" percsas = "DELL PERC 5/I Adapter RAID Controller" percsas = "DELL PERC 5/i Integrated RAID Controller" I use the following version of the percsas.sys file: 1.18.0.32 (which is old, I know, but it works...) If u wanna get the same PERC controller support within Win2003 (not PE) then u also need to edit dosnet.inf to reference the percsas.sys file. Good luck to you, man! And have a happy Walpurgis weekend!!!
  2. Hi Michael! Welcome to MSFN!!! Nice to see you checking out this forum and thanks for a great product in BDD. Awsome.... Any time and name on the replacement/upgrade that will support Longhorn server deployments using the BDD concept? Again, enjoy ur stay here and hope to see more of u in here....
  3. Hi! I have actually had problem with PE and WMI, but that was on prior versions of PE, not the new vista PE. Then I fixed it by redoing the whole PE image, but that I can see that u have already done. The only thing I can think of is to run some kind of WMI tool included or downloaded that will work normally within PE. For example, there were both wbemtest.exe in previous versions of PE(xp/2003). Starting this app might just give u a clue if WMI is totally f***ed up or just some wiered thing.... good luck to you....
  4. Hi, personally, I am using RIS and WDS (mixed mode) at the same time with no issues, so I cant say that I have the same issues as described.... however, I have seen where WinPE halts (unexpectedly) at the same prompt as u describe! When it did that for me, I rebuilt the very same WinPE image from scratch and everything went workin again! No final solution or explenation. Redo. You have prolly done it 20 times already but anyway.... Hope it does it for you... otherwise, no clue.
  5. Maby post the content of the .xml file? Inform us about what is not working? Are u using the WSIM to build the .xml file for u? Is it returning any errors when building it? Have you surfed the forum? etc etc.....
  6. Dunno about the mkisofs application, I would suggest that u try to use the OSCDIMG.EXE application for building the .iso files! This app comes with the WinPE 2005 build kit from MS.
  7. If it is a installer applications that you are trying to excecute from this point, then try to change the name into some of the following; 1. Setup.exe 2. Patch.exe 3. Upgrade.exe 4. Install.exe Cause Vista "launches" applications for installation based on their names as well... If u have a install app named MyApp1.exe, Vista does not know it is a installer. Change it into install.exe and it is hardcoded to detect the 4 above strings and launch them within a "installer" environment. Of course, this only referes to installers, not to normal execution of Win32/64 appliations. GL!
  8. Hi keythom! Awsome first two posts.... love the work, thanks for sharing.
  9. Hi! On my 32-bit operating systems, I am using the System Management Server built in log paser (trace320.exe) for reading files within WinPE. However, since I am changing over to x64 WinPE now, the same application wont work anymore! Anyone that can recommend any other log parser application, that is free and features color coding for errors and so on? Must work natively on x64 is the only requirement! Thanks in advance....
  10. With the newly released SP2 for Windows 2003, I cant seem to find the proper name of the [Component] for unattended installations of the newly introduced WDS feature! Anyone come across it? I know the name of the old RIS component, but that does not seem to do the trick for me.... Thanks....
  11. Hi! I am trying to deploy a simple dataimage that I have created using a .xml file that is to automate the WDS deployment. However, the dataimage is never deployed. Following is done: 1. Boot into a standard boot.wim image placed on the WDS server 2. The WDS client software loads, and requests u to choose language and keyboard settings, then logon.... 3. Once logged on, I have to choose which image to apply... which I wanna do. 4. The .xml file that I provided to the WDS server for automating the WDS client part looks like the following: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Boot</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration> <UserData> <ProductKey> <WillShowUI>OnError</WillShowUI> </ProductKey> <AcceptEula>true</AcceptEula> <FullName>My Department</FullName> <Organization>My Company</Organization> </UserData> <WindowsDeploymentServices> <ImageSelection> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> </ImageSelection> </WindowsDeploymentServices> <ImageInstall> <DataImage wcm:action="add"> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <InstallFrom> <Path>\\DEVSEHBG-NT0001\RemInst\DRIVERS.WIM</Path> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>DRIVERS</Value> </MetaData> <Credentials> <Domain>My_Domain</Domain> <Password>My_PassW0rd</Password> <Username>My_UserName</Username> </Credentials> </InstallFrom> <Order>1</Order> </DataImage> </ImageInstall> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/image_64bit/install.wim#Windows Vista ENTERPRISE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> 5. The main image that I select from the WDS client interface, is applied, and is working.... 6. The DataImage supplied through the .xml is never applied... why? hints, tips or tricks? lucky charm? anything? Thanks in advance....
  12. Yeah, my BDD LTI environment looks like that, more or less..... but I dont see how that relates to the WDS client software? The LTI PE images created, does not even show up the WDS client software UI as when using the orig boot.wim on a Vista CD/DVD and put on the WDS server.... Thanks for the reply!
  13. Hmmm.... I am also using LTI (BDD) to create the reference images, but I have not seen where the PE that is auto created has the WDS client software enabled within it? When mounting that .wim PE file, it looks more of none WDS enabled PE image to me, maby I missed something........
  14. Hi! I wonder if someone knows how or if it is possible to execute some .hta or script prior and post to the WDS client software execution point? What I wanna do is to; 1. Boot a client into PXE 2. Boot onto the WDS client (WinPE) and choose the correct image to apply to the local machine from the WDS server 3. Once the image has been applied, envoke a custom script or .hta so that I can customize the install 4. Continue into Windows Vista setup mode... Anyone know how to envoke the script to be launched at that point in time?
  15. Hi people! When using BDD 2007, there are two diffrent scenarios: 1. LTI 2. ZeroTouch #1 is for us that are not blessed with SMS and so on... However, once u choose ur scenario to use: the BDD expierence can be devided into two seperate pieces: 1. Creating a reference image using the Capture scenario 2. Deploying the reference image using the BDD capabilities.... and here is my contribution to the world: If u just wanna use BDD for creating reference images, NOT deploying them using the LTI mechanism (as I wanna), u have to make the following adjustments to get ur custom settings applied during the creation of the custom image: 1. Create a fully automated unattend.xml file to process the unattend installation using the WSIM app. 2. Create a script that will delete the cached unattend.xml file in the c:\windows\panther dir prior to launching the sysprep command/script 3. Create a fully automated sysprep.xml file to process the mini setup using the WSIM app. 4. Place the sysprep.xml file in the $OEM$ so that it equals the c:\MININT path/dir. 5. Copy the sysprep.xml file to the c:\windows\system32\sysprep dir, when "moving" the file from the MININT to the SYSPREP dir, make sure u save the file as unattend.xml 6. Edit the LTICleanup.wsf script and remove the part where they overwrite our "sysprep.xml" file with their own "unattend.xml" file..... 7. Lastly, remove the Exclusion list entry, c:\windows\panther in the wimscript.ini file on ur BDD server.... First now, the custom image will act as u expect! if u dont perform the steps above, any odd things might show up: 1. The mini setup is not automated 2. There is no unattend.xml file saved in ur image below the C:\Windows\Panther dir 3. Autologon and FirstLogonCommand will not work as expected even if ur sysprep.xml file works fine when running it manually..... now finally, it's sausage time.....
  16. Thanks people for all of the suggestions! I am going for Clubertis suggestion and then parsing the info for "keywords".....
  17. Sorry Cluberti... that did not do it...... the "DataWidth" WMI property only seemed to return the current loaded operating systems datawidth much like that "addresswidth" property.... In other words, if running the script on a x64 capable machine (Core 2 Duo) but it has an x86 operating system loaded, the script returns "32"....... Thanks anyways man, I guess I need to talk some C++ dudes to be able get that sorted out!
  18. n1....
  19. I guess I have to pay attention.... Thanks man....I will give it a go tomorrow and try it out!
  20. Thanks for the replies... Fair enough, but what u guyz are saying is that I will have to create some kind of dictionary that I will base my decision on? Like if, the script returns "Intel Core 2 Duo" then x64 will be fine.... I was more looking for some WMI property or something that would return x64Capable = True/False, 1/0 or something..... Thanks....
  21. Do u guyz know of any way of how to determine if a specific machine is capable of running x64 based operating systems using either WMI or some CLI tool? I wanna be able to have a script return if it is possible that this machine will allow u to run x64 based operating systems even though a x86 OS is installed! Thanks....
  22. Oki, might be a little hasty but still... If I dont create my custom WinPE 2.0 image but use a LightTouch image from the BDD product that is based on WinPE 2.0, the same .hta works... still, checking the peimg /list /image=c:\my_path\win_pe\windows it shows that it has the same packages as my custom image.... confused.
  23. It's working..... I have been able to figure out that it is the onLoad feature that is not working as intended in WinPE 2.0! I found another .hta that is delievered from MS within BDD and that is executed from within WinPE 2.0 that I am gonna play around with but still very strange.... another simple thing that didnt work was that I added a gradient to my .hta, that one totally went nuts within WinPE, but is also working within full Vista, XP, WinPE 2005 and so on....
  24. Oki, so I have added the scripting package (WinPE-Scripting-Package) and the hta support package (WinPE-HTA-Package) to my custom WinPE 2.0 image. I then map a network drive (UNC) so it equals z: - if I then try to launch a .hta file from that z: drive: mshta.exe WinPE.hta or cmd /c mshta.exe WinPE.hta it does not work?? I can see that the mshta.exe process is running whenever the command is launched. When running the same command from within Windows (not PE) it works, and if I take the same .hta file and execute it directly from the startnet.cmd file locally to WinPE it works.... ??? Read somewhere in the forum that one should execute the .hta file from the local PE x:\windows\system32 dir but to no use.... anyone seen this behavior before? The same file works in WinPE 2005! Also, is WMI included in the WinPE-Scripting-Package package as it is not displayed as a seperate package from what I can gather.... Thanks.....
  25. Both Yes and No.... Yes, other boot menu, u need to configure some stuff, the BINLSVC is removed and replaced with wdsserver, you need to add a boot image and some other stuff... No, as long as u r running WDS in mixed mode, the orig RIS feature is still operational as expected..... however, if u set it to native, then forget about RIS. Then again, u can switch back and forth all of the time if u wanna...
×
×
  • Create New...