Tripredacus

For the user account, you just make a new one. Put it in Domain Users or whatever extra group you need. Then that user (or group) just needs the correct permissions to whatever shares you will be using.

Its how it is programmed. MS obviously uses the same Setup launcher for all their products in the same family. So even if you have an install.wim with 1 or more install images inside it will give a prompt. Using an Autounattend.xml is the way to hide the selection screen. But in the XML you would actually have a setting to tell Setup what image to use, which in effect hides that page.

Great, thanks for telling us how you fixed it. Many people seem to have trouble with Unattend Join, but I've never tried it myself.

Why would you want to delete the default drivers? Are you using a special tool or something? DISM can't even see the built-in drivers.

Well OK Resource Monitor in Win7 is pretty cool. So they just made it look different in Win8 by (basically) adding it into Task Manager.

BoA - Every Heart (English Version)

Did you test the DC jack with a multimeter?

I always wonder why people try to use the AD root Admin for adding PCs to the domain... Take a look over this thread, maybe it will help:

Honestly, I'm not quite sure what you're referring to here besides the few obvious things. The Copy-To and Move-To are good. Also the CMD/PowerShell from anywhere also. These were always reg-hacks since forever ago, but now built in. Show hidden files/extension on the ribbon (notice it was a lot harder to get to Folder Options in Vista/7) Pause/resume on file copy File replace for media files now has a preview thumbnail instead of the file type icon. Task Manager including grouping processes by user. Analyze Wait Chain. Taskbar properties for multimonitor. Multimonitor that allows for stacking, tiling. Those are basically covered on pages 2 and 3 of the Ars link.

At least that Metro app has an off switch! Anyways, just read a huge in depth article on Windows 8 at Ars Technica. You can see there are MANY improvements that are great for us techies, but it also points out the problems of course. I see that one is that the multi-monitor taskbar is configurable, which I hadn't seen in my tests. I made a complaint about it somewhere in this thread.

If they are MSU files you can add them into the WIM using DISM. This example uses .cab files but you can use .msu as well: http://technet.microsoft.com/en-us/library/dd744559%28v=WS.10%29.aspx

For one, if using PXE, the boot image NIC drivers aren't used but the PXE ROM. Just because you were able to load a boot image does not mean that the boot image has network support. Either way, it would seem that isn't your problem since you are getting a credential error. I would strongly recommend that you do not use the domain admin account to do deployments. Create another user specific for that purpose.

Yes there are multiple ways to use sysprep. What you will need to do is install Windows to Audit Mode using an answer file. Then in Audit Mode you can install programs and make changes. When in Audit Mode, you are using a disabled Administrator account. So any programs you install, you need to make sure they install for All Users. After you get further along you can go find out how to enable that account after OOBE if you want. So you wouldn't want to set any Theme elements in Audit Mode either. When all finished, you run sysprep /generalize /oobe /shutdown and then capture the image with Imagex or DISM. If using the Setup DVD you should be able to install the image manually, and as long as it works you can make an Autounattend.xml to use with it. Here is a sample Autounattend.xml I posted to get Windows to install into Audit Mode:

The Powershell one looks promising. I have no problem writing the scripts and I already know what the classes are. Typically, I use the WMI Object Browser because I know what data I am looking for, but do not know what class or instance it is in. But I will definately check a couple of those out!

I could use some help on the weekend.

Board: Intel DX79SI. UEFI Boot is disabled. BIOS is latest version. PXE Boot to WinPE 3.0 x64, tested Windows 7 Home Premium x64. AHCI = OK IDE = OK RAID using RAID1 = OK Here are the scenarios that cause a problem. 1. Failure if OS volume is RAID0, BCDBoot returns error: "Failure when attempting to copy boot files" using this command: bcdboot c:\windows 2. Failure if OS volume is RAID0, BCDBoot completes successfully, BOOTMGR is missing error on restart using this command: bcdboot c:\windows /s c: 3. Same as #2 but different command: bcdboot c:\windows /s c: /l en-us 4. Unexpected result if OS volume is on RAID0, BCDBoot completes successfully, Set OS Partition to Active. Result is OS boots but System Reserved partition is assigned a drive letter. I've already got some emails out about this problem, but was wondering what I could possibly try or run from WinPE x64 to test and maybe find out what the problem is? Update: 7PRO64 does not work on RAID1 or RAID0. I have tried getting a new BCDBOOT.EXE as well as building a boot image using WinPE 3.1 x64 from the WAIK Supplemental ISO.

Yes sorry you are missing the switch to tell sysprep how to exit. /shutdown /reboot /quit One of those are needed. I usually use /shutdown just so I can make sure that I don't accidently reboot into the image again.

I can't find a lot of new information on this. Have you see this backup program? http://www.live-writer.net/2009/03/07/windows-live-writer-backup-rc-released/

I'm not sure exactly what Memdisk is, but it looks like a DOS program? If it contains 16bit binaries, it won't run in WinPE. Or have you been able to test it? As far as ISOs, I see that some projects (Make_PE3, Win7 PE SE) use a program called IMDISK to mount ISO files.

.cmd files will only execute with cmd.exe. So as an example, if you have an older OS that has its command interpreter set to COMMAND.COM, a .cmd file will not (supposedly) execute. .bat files will work with either command interpreter. This change came about when NT systems dropped support for DOS' COMMAND.COM and added support for cmd.exe. Typically, .bat files will always work on a current system, but as a matter of practice I always create or rename to .cmd. As for thread location, it depends. Are you having trouble mounting an ISO from within WinPE?

Sysprep is in a folder called Sysprep. Try this: C:\windows\System32\sysprep>sysprep.exe /oobe /generalize /unattended:C:\Windows\System32\Sysprep\Unattended.xml

We keep a bunch of links in this sticky topic: There are multiple ways to use sysprep. By "using" sysprep there is a switch to include an answer file. What exactly do you want to accomplish or think sysprep can do for you? Maybe if we know that we can give you a better answer.

When doing initial research for how to make my programs better, I rely on an old program: WMI Toolkit Mostly just the WMI Object Browser. Well this either does not work with Windows 8 or IE 10. While it is fine for me to manually connect to root\CIMV2, and I can see *some* classes, the values (even for those) do not appear. For example, while Win32_BaseBoard does not show up in the classes list (classes that can have instances) in the Object Browser, I can actually read data from it using a test program. Are there any other WMI object tools that will work on Windows 8 or IE 10?

Welcome to the MSFN!

I think that's how I found this site too.