Jump to content

dim

Member
  • Posts

    45
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by dim

  1. J - Very interesting.. I have added all those drivers ... Yours is on a Vmware Workstation correct? I am going to try to load my PE Disk on Vmware Workstation and see if I can get it to work on Workstation. In our Vmware ESX Environment, I am seeing those issues. I am going to start small from the BASE WIM and see what happens...
  2. Are you using bootsect.exe after you use diskpart and format the disk?
  3. Jazkal - "when you run that command by hand, what is the output? does it give you an error message? When PE is loaded, is the driver file actually one the X drive if you do a search? " I don't quite understand that statement. What do you mean by hand? I use the peimg and the ouput is successful every time. I will do a search on the X drive to see if it loaded the driver properly. The key here is, I think Microsoft is out to get Vmware, so it makes sense they eliminated the driver from WinPE 2.1, but with that said, winPE 2005 works like a charm, See attachment The whole idea is, I am not quite sure where those drivers are so I can properly inject them. I am just swinging at anything right now to find the correct driver
  4. To add rivers, the first thing I was doing was mounting the image imagex /mountrw c:\build_x64\winpe.wim 1 c:\build_x64\mount then I take the scsi driver that i have, and do peimg /inf=%driverpath%\*.inf cf:\build_x64\mount\windows then I commit the changes imagex /unmount c:\build_x64 /commit THe hardest point I am having is finding the correct driver to take care if this issue. IS there something i am doing wrong?
  5. Ok, while I managed to click past something similiar in my earlier post, this one appears to be a little bit more challenging. Apparently, Microsoft's latest WinPE 2.1 does not contain drivers for Vmware and it's disk drivers. I tried to inject the latest drivers into the .WIM file from the vmware tools directory, but I have not had any luck. When Viewing Diskpart I continuously get the following error: There are no fixed disks to show Which basically means it doesn't have the correct driver. Any thoughts?
  6. The issue is fixed.. I didn't think it would be this easy.. When creating a VM, make sure you select the x64 OS you are creating.. Whoops.. I bypassed that one too fast with a mouse click.
  7. I am trying rewriting our winPE 2005 process for WinPE 2.1 for a scripted installation and while testing it on a Vmware Guest I get the following error Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode. (Picture is attached) I have searched around this morning on the web and I can't find any information regarding this. Please tell me it's possible to build a scripted installation of x64 W2k3 using winPE 2.1 on Vmware. Currently, our Vmware Farm is 3.0. Thanks in advance -
  8. The PEshutdown.exe tool works great.. Here is what I did with the script Dim oWMI, StrManufacturer strComputer = "." Const HKEY_LOCAL_MACHINE = &H80000002 Const WaitOnReturn = True Const ActivateWindow = 7 Set Wshshell = CreateObject("Wscript.Shell") Set objEnv = WshShell.Environment("Process") StrTempDir = objEnv("TEMP") StrWinDir = objEnv("WINDIR") strSysDrv = objEnv("SystemDrive") unattend = Wshshell.ExpandEnvironmentStrings("%unattend%") Set oWMI = GetObject("winmgmts:{impersonationLevel=impersonate}\\" & strComputer & "\root\cimv2") Set ShutdownWMI = GetObject("winmgmts:{(Shutdown)}//./root/cimv2") Set cComputerData = oWMI.ExecQuery("SELECT * FROM Win32_ComputerSystem") For Each oItem In cComputerData strManufacturer = Ucase(oItem.Manufacturer) Next If Manufacturer() = "Dell" Then MsgBox "Please insert x64 WinPE Disk to continue the unattended installation and then select OK to reboot server. Remember to Press AnyKey to boot back into WinPE upon reboot.",vbInformation,"Schering-Plough Unattended Installation for Dell Servers" WScript.Echo "System is rebooting" Wshshell.Run unattend & "\tools\peshutdown.exe /reboot",ActivateWindow,WaitOnReturn End If Function Manufacturer() 'Manufacturer specific task Select Case ucase(left(StrManufacturer, 2)) Case "CO" Manufacturer = "Compaq" Case "HP" Manufacturer = "HP" Case "DE" Manufacturer = "Dell" Case "VM" Manufacturer = "VM" Case Else MsgBox "Unsupported Hardware", , "RunOnce Hardware Check" WScript.Quit End Select end Function
  9. I have found this code and it works great, but i am trying to run it via an Altiris Job and it keeps erroring out that self isn't defined, but when I break this out and run it from a command prompt via cscript it runs flawlessly.. Totally wierd... I don't quite understand the with .appActivate and send keys..
  10. I am trying to use this Vbscript to reboot a server in WinPE 2005 Set ShutdownWMI = GetObject("winmgmts:{(Shutdown)}//./root/cimv2") Set SySShutdown = ShutdownWMI.ExecQuery("select * from Win32_OperatingSystem") For each Sys in SySShutdown Sys.Reboot() Next Why will this not work in WinPE 2005. Is there not the proper allowance to that class? Also, what other methods do people use to automatically reboot in WinPE. I have tried like 5 different tools. Help!
  11. Ok, Guys before I get flamed here, Altiris currently only supports winPE 2005 until they fully release 6.9 which is in beta. So, with that said, is part of the limitation of WinPE 2005, is the limitation of some of the WMI classes and one of them being Win32_volume. If that is the case, is there a way I can add that class into winPE 2005 or am I just out of luck and have to use Format command I was trying to make this vbscript I have streamlined with all VB and not something like wsshell.run "format c:" Any thoughts would be great. Thanks
  12. Can this be automated? The reason I have this question is b/c we are thinking about going to WinPE 2.0 for automated builds using Altiris and we need a way to have Static IP's that can be changed on the fly. Currently we have a VBscript that changes our winimage file.. But that will not work with .iso. any thoughts?
  13. Here ya go bud... To get network client put the following in sysprep.inf file [NetClients] MS_MSClient=params.MS_MSClient and under your network settings you want the following [params.MS_TCPIP.Adapter01] DisableDynamicUpdate = YES DNSDomain = fabrikam.com DNSServerSearchOrder = server1.fabrikam.com, fabrikam.com
  14. It looks like from the data that you have to install Automatic Updates in Windows 2003 Sp1. But in the Data section of the unattend.txt you can do the following automaticupdates=0 That disables by default...
  15. Entries have been deleted from the following sections: [Components] section AutoUpdate ~~~~~~~~~~~~~~~~~~~~ This is in reference to the 2003 deploy tools... Autoupdate was deleted..
  16. I have reviewed the deploy.chm and ref.chm and they both refer to autoupdate = on|off am i missing something?
  17. No bud, if its a policy, just delete it temporarily until you are done and then move it to the correct OU. Thats the way to do it. There is no bypass to the OK.
  18. You need to create your computer accounts in an OU that applies no policies. Once you are done configuring your system, you can move it to the appropriate OU. Or, you an delete the following keys reg.exe delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system /v legalnoticecaption /f reg.exe delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system /v legalnoticetext /f
  19. It all depends on your hardware that you are installing it on.. Its tough to say why it is slower when there are no specs provided..
  20. Long time reader, first time poster .. I was just wondering if you guys know of a way to easily disable automatic updates in unattend.txt. In Sp0 on win2k3 Standard we make sure we specify under components, Autoupdate=off and we do the same with Sp1, but for some reason it still installs.. Also, I have been looking for a component to turn off Wireless Zero Configuration and Bits in the unattend file, but I haven't had much luck. Do you think its best to add a few lines in the runonce files?
×
×
  • Create New...