Jump to content

Sinistrality

Member
  • Posts

    21
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Sinistrality

  1. I added the inf files from this setup. http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-74429 Not sure if you are using MDT2010 or what, but I was having the same difficulties: Started the Deployment Workbench, Drilled down into Deployment Shares, My Deployment Share, Out-of-box Drivers, WinPE Driver, Imported the above driver after download and extraction. Updated the Deployment Share (Forced Regeneration). Started Windows Deployment Services Drilled down into Servers, My Deployment Server, Boot Images, Add Boot Image, browse to your WIM that was generated above (Mine is named litetouchPE_x86.wim) Next, Next, Finish (You can name it if you want). When you PXE boot you will a have menu option showing your old build and the new one you just created in WDS. You can disable the old one if you want after it works, or delete. It got me past the error, but Windows is not starting properly further in, I may be including too many drivers from Lenovo. I'm going to reduce the driver set and see if I have any better luck.
  2. Typically quotes are only required when you have spaces in the folder names. e.g. "C:\Documents and Settings\All Users\Documents\BGinfo.exe" "C:\Documents and Settings\All Users\Documents\testclient_BB.bgi" /all /timer:0 If you use the system variable uid0 used above it should not require quotes: e.g. %ALLUSERSPROFILE%\Documents\BGinfo.exe %ALLUSERSPROFILE%\Documents\testclient_BB.bgi" /all /timer:0 or if you were to put the bginfo.exe and testclient_BB.bgi file in c:\windows (where I put mine) e.g. c:\windows\bginfo.exe c:\windows\testclient_BB.bgi /all /timer:0 (I don't use the /all switch, not necessary for my purposes as I load it from HKCU/..../run) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "BGInfo"="C:\\Windows\\System32\\bginfo.exe c:\\windows\\system32\\default.bgi /timer:0"
  3. Edit: Link to Manual Integration Method. RAID/SATA Drivers Here is my txtsetup.sif entry for Intel® 82801FBM SATA AHCI Controller. This is based on the txtsetup.oem file that is a part of the manufacturer's F6 Floppy. [SourceDisksFiles] iastor.sys = 1,,,,,,_x,4,1 [SCSI.Load] iaStor = iastor.sys,4 [HardwareIdsDatabase] PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor" [SCSI] iaStor = "Intel® 82801FBM SATA AHCI Controller"
  4. If you wish to apply changes to the Default User Hive after T12, here are are instructions on how to do so. (e.g. If later on down the road you realize you need to apply additional settings to All new users) To modify the default user hive, highlight the HKEY_USERS window and click Load Hive from the Registry menu. Select the Ntuser.dat file (usually from %windir%\Profiles\Default User directory). Type NTUSER in the Key Name dialogue box. Now you can add or modify any Key or Value within this hive. When you finish, highlight NTUSER and select Permissions from the Security menu. Add Read permission to the Everyone group. Check the "Replace Permission on Existing Subkeys" box and click Ok. Select Unload Hive from the Registry menu and exit Regedt32. I C&P'd this from the following link. Some of the best tips and tricks for windows collected in one place. I had quite a fright when I saw that the maintainer of the original site (jsiinc.com) put up a notice of his retired status. Define initial settings for new users
  5. I had the same problem. The trick is to add the SATA driver to the CD as per the instructions here. I was never successful utilizing F6 to get the SATA drivers loaded from the floppy, I'd get the cannot read iastor.sys error. MSFN's Unattended Windows: RAID/SATA Here is my txtsetup.sif entry for Intel® 82801FBM SATA AHCI Controller. This is based on the txtsetup.oem file that is a part of the manufacturer's F6 Floppy. [SourceDisksFiles] iastor.sys = 1,,,,,,_x,4,1 [SCSI.Load] iaStor = iastor.sys,4 [HardwareIdsDatabase] PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor" [SCSI] iaStor = "Intel® 82801FBM SATA AHCI Controller"
  6. Disable Driver Signing Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing] "Policy"=hex:00 Enable Driver Signing Windows Registry Editor Version 5.00 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing] "Policy"=hex:01 I imagine you could simply add entries in RunOnceEx like so: "REGEDT32.EXE /S disable.reg" Install Application Here "REGEDT32.EXE /S enable.reg"
  7. Having these entries in your winnt.sif file should format the the C: drive automatically. [Data] AutoPartition=1 UnattendedInstall="Yes" [unattended] Repartition=Yes Filesystem=NTFS
  8. EncryptedAdminPassword="Yes" prevents auto login. (Given that you've configured it with an encrypted password) However I found out the hard way....
  9. Don't rely on Windows Update to tell you that all your patches are installed properly. Instead use the QFECHECK.EXE utility and the Microsoft Baseline Security Analyzer QFECHeck.exe will do a check to verify within your system what hotfixes are installed properly. MSBA will go out and pick up update information off of Microsoft's website, and let you know if there are any vulnerabilities you need to worry about. You can also run the MSBA utility from a command line for more detail information. No one responded to my post, Check it out. Oh and I only read the first 4 lines of your post.
  10. The side effect of this fix appears to be that the "Windows Update" (RunOnceEx) dialog is not shown, e.g. Installing Application 1,2,3,4 etc. As much as I miss it, I enjoy watching my unattended install actually operate properly. (other the evil "to improve the appearance of visual elements, blah blah blah" hoping that is just because I'm using VMware) Now as far as letting me know where it is at in the progression of installs... Message boxes that pop up and go away on their own?, or a message box at end of RunOnceEx Process? Or simply have it reboot when it is done... Thanks for your work. FYI, Personally I try to avoid third party programs when I can. I know a good portion of the posts I see in these forums are nLite stroke jobs.. from what I've read it is a great tool, but before I'd use it my environment I'd need go over it with a fine toothed comb. And as for "Installer Packages" created by other users; Sorry, but I'll pass. I don't know you personally, and I don't know what you've put in the burrito.
  11. I'd try Microsoft's Diskpart.exe utility. It might be able to do what you need. DiskPart
  12. Here is my winnt.sif windows firewall configuration. [WindowsFirewall] Profiles = WindowsFirewall.Domain [WindowsFirewall.Domain] Type = 3 Mode = 1 Exceptions = 1 Notifications = 0 Services = WindowsFirewall.FileandPrinterSharing PortOpenings = WindowsFirewall.RealVNC [WindowsFirewall.FileandPrinterSharing] Type = 0 Mode = 1 Scope = 1 [WindowsFirewall.RealVNC] Protocol = 6 Port = 5900 Name = RealVNC Mode = 1 Scope = 1 In my WindowsFirewall.Domain you may notice notifications = 0 By default this vaule is 1, which enables notifcations Under the same heading Type options has 3 possible values. 0 specifies a domain type of profile 1 specifies a standard type of profile 3 specifies both domain and standard profiles. I have used a vaule of 3 so the settings under the WindowsFirewall.Domain effect both workgroup computers and domain PCs created with my unattended install. This information is available in the ref.chm file that comes in the XP SP2 Deploy Tools (KB838080) Hope this helps.
  13. Thanks for your input, however I can't get around the fact that the workstation service is failing to start, no workstation=no ip address/no network. I've managed to get around it by executing a second "runonceex" at the end of my initial runonceex.cmd, because on the next reboot the network works fine
  14. Unable to overcome my completionist nature, I have question that may have been solved in a previous post or two, but firefox doesn't like the forum search tool , and I personally despise IE. On my test VM station, I have run the QFECHECK.exe utility. The result of every hotfix identified is: Current on system. Except for the following 8 hotfixes, which all display the "This hotfix should be reinstalled" result: KB914388 DHCP Vulnerability Fix KB920213 Agent Vulnerability Fix KB920683 DNS Vulnerability Fix KB921398 Windows Explorer Vulnerability Fix KB922582 Error Updating Computer Fix KB922819 TCP/IP Vulnerability KB924270 Workstation Service Vulnerability KB926255 Windows Vulnerability I've also run the MS Baseline Security Analyzer 2.01 (shows as 2.0.6706.0 on the report) The results of which indicate that no Windows Security Updates are missing with a Security Assessment of: Strong Security. In the past, to verify that all windows updates were applied properly I'd simply run the Windows Update utility in a custom manner and install updates until no more updates remain. I imagine that the Windows Update check isn't worth beans. But of the first two utilities (QFECHECK and MSBA) which should I put my creedence in? Thanks for your time and any insight you might provide.
  15. yeah... I tried that in my first post. Via the sc query lanmanworkstation command I have determined that the workstation service isn't started prior to the runonceex process execution. Nor will it allow me to start the service. I've made the change specified in JSI Tip 5638 and Error Message "The Workstation Service Has Not Been Started" When Using Cmdlines.txt with not positive effect. The result of the net use command is this: System error 67 has occured The network name cannot be found Not suprising since the workstation service isn't started and the computer isn't picking up an IP address. At this point I'm inclined to start over from starting again from scratch. Or just run another runonceex.cmd after yet another reboot and start my network based installs with rundll32.exe c:\install\iernonce.dll,RunOnceExProcess (given that IE7 breaks the runonceex process, pointing it to an older version of the file thank you Microshat.) I think I'll do the latter and save my sanity's break for another day
  16. Looks like the netcheck fails, comes up with the 10 minute warning.. Running a paused ipconfig during runonceex phase shows the following: IP Address 0.0.0.0 Subnet Mask 0.0.0.0 Default Gateway: Blank DHCP Server: Correct DNS Servers: Correct I'm thinking maybe the workstation service isn't started? Or maybe I need to do a release & renew. Guess I'll add an command to check the workstation service state... /shrug Along with a Ipconfig /release and Ipconfig /renew... whee!
  17. Greetings all, I am having difficulties in my attempts to map a network drive during the first login attempt after XP is installed. I have attempted to map the drive via a command in the winnt.sif [GUIRunOnce] section.... [GuiRunOnce] "net use z: \\sovmtest\shared test /user:sovmtest\test /persistent:no" as well as within the RunOnceEx.cmd... @echo off SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%15 /VE /D "Mapping Network Drive" /f REG ADD %KEY%15 /V /1 /D "net use z: \\sovmtest\shared test /user:sovmtest\test /persistent:no" I've also attempted to map the drive by creating a netuse.cmd file: @echo off start "NetUse" /wait net use z: \\sovmtest\shared test /user:sovmtest\test /persistent:no exit and placing it in the $OEM$\$1\Install folder and executing it from both Winnt.sif... [GuiRunOnce] "%systemdrive%\install\netuse.cmd" ....and RunOnceEx @echo off SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%02 /VE /D "Mapping Network Drive" /f REG ADD %KEY%02 /V /1 /D "%systemdrive%\install\netuse.cmd" /f With any of the methods shown above it is still failing to map the drive. However once the computer restarts after the RunOnceEX process completes, I can run netuse.cmd and it works correctly. And yes I have verified the credentials used to access the share are correct... User:test Password:test I came across a forum post mentioning The Workstation Service has not been started. I made the change to the hivesys.inf file as it indicated, with no effect. Any help would be appreciated. Sinistrality
  18. You could add a String Value of nusrmgr.cpl to HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce during your "Tweaks" phase. It should come up on the reboot..
  19. Yeah but it doesn't explain it clearly If it showed a couple more examples it would be made more clear This is my Runonceex.Cmd entry for my Java installer.. I've simply renamed the java_1_5_0_10.exe to jre.exe for ease of typing. REG ADD %KEY%30 /VE /D "Java Runtime" /f REG ADD %KEY%30 /V /1 /D "Z:\Install\Java\jre.exe /s /v \"/qn ADDLOCAL=ALL IEXPLORER=1 MOZILLA=1 NETSCAPE6=1 REBOOT=SUPPRESS JAVAUPDATE=0 WEBSTARTICON=0\"" /f Yours might look like this REG ADD %KEY%25 /VE /D "Java RE 5 Update 10" /f REG ADD %KEY%25 /V 1 /D "%PP%java\java_1_5_0_10.exe /s /v \"/qn ADDLOCAL=jrecore IEXPLORER=1\"" /f As for your Nero... crap you use a lot of quotes: REG ADD %KEY%10 /VE /D "Nero Burning Rom 7.5.9.0 Lite" /f REG ADD %KEY%10 /V 1 /D "%PP%nero/nero7590eng.exe /VERYSILENT /Lang=\"English\" /USER=\"xxx xxxx\" /COMPANY=\"xxxx\" /SERIAL=\"xxxxxxxxxxxxxxxxxxxx\" /COMPONENTS=\"nero_core\"" /f Be sure to test it by executing the runonceex.cmd file on a computer, you can simply delete what reg entries it creates after you see the happy words: The operation completed successfully spam 100 times over Feel free to ignore my Z:\ stuff.. still trying to figure out how to add a mapped drive via runonceex.cmd and install apps from a network location.. Ran out of space on my CD, and I don't yet wish to touch RIS Hope this helps.
×
×
  • Create New...