Jump to content

bear263

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    United States

About bear263

Profile Information

  • OS
    Windows 10 x64

bear263's Achievements

0

Reputation

  1. Gosh danggit. Forgot about the label command. Thanks
  2. I know the experts here has an answer for this. I have tried searching and came up with a whole bunch of topics for "local disk" and "rename" but none that applies to my question. How in an unattend install can you rename Local Disk to whatever you want? I searched through the registry and found a key that stores this name: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\{42a92161-6650-11d9-81bc-806d6172696f}] "BaseClass"="Drive" "_LabelFromReg"="Local Disk" So I change the name and it doesn't work. Tried rebooting also. Anyone know how to do this? Thanks
  3. Thanks I figured it out. If you read the guide it states: OemPnPDriversPath="Drivers\000_intel_INF;Drivers\001_gigabit_LAN;Drivers\002_monitor" "Note: Separate different directories with a semi-colon ";" So I was under the impression that ";drivers" would be a seperate directory. This must not be the case since I have no driver directory. But adding the ;drivers worked. Now on to fix 1,3 and 4.
  4. I have been working on this unattened setup for about a week now and got things in order. Everything works but these few problems. First the part of my winnt.sif thats relevant: [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall=Yes AutomaticUpdates=Yes [unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes FileSystem=* DriverSigningPolicy=Ignore OemPnPDriversPath="Drivers\Nic\Chipset\Sound;drivers\Printer;Drivers" TargetPath=\WINDOWS [GuiRunOnce] %systemdrive%\install\RunonceEx.cmd 1 Even though I have automaticupdates=yes, it still asks. I know I can add the unattendswitch=yes to get around that but it always wants to log in as administrator instead and not me. So I go through the welcome to windows....etc..... 2 Fixed 3. Even though I have my runonceex.cmd in the proper place, it imports the registry keys but doesn't run the key until I reboot. 4. I have placed the oobe.ini in the $oem$\$$\Sytem32 folder but it doesn't work. Tried also, $oem$\$$\Sytem32\oobe If I can get these problems solved, it would be a perfect install. Any help is appreciated. Thaks
  5. While I know that this post is nearly a month old, I thought I'd make it my first contribution. Not good a making batch files yet but this is the command. Office must be installed first. "C:\Program Files\Microsoft Office\OFFICE11\proflwiz.exe" /r "<path>\new settings file.ops" /q Hope this helps somone


×
×
  • Create New...