Tripredacus

Look up "ProtectMyPC" in unattend.chm to find how to get that protect page to be hidden. You can't add the Administrator account in unattend because it already exists. For wallpaper, look up Theme in the chm. You need to provide background, a theme name and set the default to off. Sorry I didn't post links but I'm going from memory atm.

You can do as I did and (shell)execute the .theme file. This will leave the Personalize window open on first boot but it won't show up again.

I agree on this as well. Yes I can see the Tripredacus animation "better". I think you are right that the various differences in contrast to both the original outline color and the background compared to that of the Primus image are the reason that is true, since I would assume the "red" is the same in both color and dimension in both cases, and the letters themselves are the same color and dimension? (The images I included above are enlarged 400%.) But yet, to me, in the Tripredacus animation the red appears much brighter and the letters very slightly brighter. Against the respective backgrounds, the edge of the letters appears much sharper in the Tripredacus image, while the edge of the letters in the Pimus image appears almost fuzzy or blurry, since it blends in more with the background. I realize that this is sometimes a desired result, but I'm just saying ... When I look at this zoomed in look to the Primus version, I can see that there may be a color selection difference. Primus had used the pink/beige color in their album art, which may be why it was chosen in this example. However different looks may be achieved by using different "pulse" colors, including colors such as white or light gray. Red would work well for mine as I have only presented images which use the white-red-black type images. While these are my favorite colors, that doesn't mean that those creating images or animations need to limit themselves to those colors.

Why would you use an HP OEM key during the WinPE phase? If you want to provide a product key at this point you would use the applicable install key. http://www.cluberti.com/blog/2009/08/11/default-keys-for-vista-and-windows-7-deployment/ You can find the install key master list in the pid.txt on the Windows 7 DVD.

Silly question. Can you see images in the VM if you don't use the XML?

I ran into this exact problem on a Foundation Server, where the BFE service was missing. I did get this same fix done, but never figured out how that service disappeared. For that client, he said it happened to multiple servers (all Foundation) in a period of the last 6 months. I would imagine that it still happens, however since I gave him the fix, he has stopped calling me.

Well I certainly don't care about what you do in your day to day life but Microsoft put in limitations into WinPE for the sole purpose that people don't try to use it as an operating system or thin client. Experimenters will be experimenters, however but my experience with WinPE is strictly on the professional level and as such (being limited by license) I don't go into those areas of non-compliance* Some have managed to come up with some interesting findings with their projects, maybe those would be helpful. Most will agree that the mighty MS Hammer would rarely fall on an organisation that is misusing software, but that situation is definately possible. Maybe we just never hear from those people again. *

Are you using WinPE 3.0 as a thin client in your company?

Are you logged on with an Administrator account or an account in the Administrators group? Is the Base Filtering Engine service started?

Try using the newest DISM in the Windows 8 ADK.

Just a quick glance at this answer file makes me think it is used while the OS is in Audit Mode. Otherwise, a Reseal to OOBE isn't necessary, as a Windows 7 image (from install source) will boot to OOBE on its own.

Did you try using DISM to install those packages offline?

This is a last resort option really...

Welcome to the MSFN!

I can help with some "great info" http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules

I must add that I haven't tried to make a WinPE 4.0 yet, mostly because I don't see a reason for it. But I was disappointed that in Windows 7 SP1, you couldn't "make" the PE anymore, instead you got pre-built ones. Maybe that is for the better.

If it sticks to the plan, WinPE only will get updated when a new version of Windows, or a Service Pack comes out. That's been the way since Vista, but I'm not sure how WinPE 1.x related to XP and earlier OSes.

Some of that XML looks odd to me. I have heard similar stories of people trying to get Altiris to do this. I imagine your company doesn't have a Support Agreement with Symantec?

Of course MS will recommend the product that costs more! Maybe, but MDT can install programs too. I'm not sure about the "thin" image you mean.

PunkBuster is kinda hard to get rid of, but I wouldn't worry about it. It is the anti-cheat engine that runs in the background when you play some online games. Quake 3 uses it for example. While most games will open it, they rarely (if ever) will close PB down when you exit. But if the game is not running, PB doesn't do anything and shouldn't cause you any performance problems.

Well this isn't the first time I've heard of people finding things on their desktop that magically show up like this. Last time someone was asking about something similar, I recommended using the AU3 (AutoIT) Windows Info tool. This program is normally used to get detailed info from applications so they can be automated, but may also be able to tell you more info about whatever that is. You just drag the crosshairs onto that dot to see the info. You can't download the tool separately, but is included in the main installer download. http://www.autoitscript.com/site/autoit/downloads/

It is possible this issue exists for Vista as well but I did not test it. The Intel X79 SATA RAID driver (iaStorA.inf) current version for Windows 7 x86 is not compatible across all platforms. Problem description: After injecting the RAID driver (iaStorA.inf) with DISM into a 32bit Windows 7 image, after deploying the image first boot up returns a STOP error 0xC000035A. Boards tested: DH55TC = 100% replication using IDE and AHCI mode DH61BE = 100% replication using IDE and AHCI mode DX79SI = intermittant DQ67SW = 0% replication using AHCI DH67CF = 0% replication using AHCI DX79SI intermittant results, note that no changes were done to hardware (BIOS) or to the test images (Drivers or Updates) to get these results. - IDE and AHCI with 32bit worked 100% of the time. - RAID using JBOD failed (This new MSC does not support JBOD apparently) - RAID using mismatched drives in RAID0 on 6GB and 3GB ports failed. - RAID using mismatched drives in RAID1 on 6GB and 3GB ports worked. - RAID using matching drives in RAID0 on 6GB ports failed using Windows Setup DVD and F6 driver. - RAID using matching drives in RAID1 on 6GB ports failed using Windows Setup DVD and F6 driver. - The above RAID tests (except JBOD) that failed started working a few days later with no changes. Drivers used from Intel's website: - RSTE_3.0.0.3020_F6-Drivers.zip - RSTE_allOS_3.0.0.3020_PV.exe Note I did mention the older model Intel boards above. For the H55 and H61, STOP error for iaStorA.sys would appear if the image was deployed to it. It is a curios error since those boards (like the H67 and Q67) do not use the hardware (PCI\VEN_8086&DEV_2826&CC_0104) that iaStorA.inf supports. They would use ibexahci.inf or ibexide.inf (and ibexid2.inf) instead. So the first idea is to use DISM to take iaStorA.inf out of the image. Unfortunately, this resulted in those boards (which the image previously worked on before adding iaStorA) would then boot to a STOP 0x7B after deployment! So it was much safer to keep the iaStorA.inf in the image. Now as to why the error occurs on certain boards, it is because the driver is written incorrectly! Apparently, this isn't the first time this type of thing has happened. In fact, an older Intel driver (iaStor.inf) from 2009 had this same problem! Take a look at this from the iaStorA.inf 32bit: [Manufacturer] %INTEL% = INTEL, NTx86.5.2, NTamd64 You can see here that this driver is not (truly) compatible with Windows 7 x86! DISM doesn't seem to care about the wrong architecture being present, which I hope gets fixed someday in the future. The reason the STOP error occurs is because the 32bit driver appears to have been created using a 64bit INF as a base. The error is due to Windows being instructed to install the driver as 64bit on a 32bit OS, even though the actual .sys files are 32bit files. Since removing the INF with DISM after the fact does more damage than you would expect, the only current workaround I've found is to rename the INF instead. Instructions for that: 1. Mount image with DISM 2. Go into mount\Windows\inf 3. find the oem*.inf filename 4. Rename to oem*.bak (where * is the number in the filename of course! ) 5. Unmount/commit It may be possible to add the appropriate OS code into the Manufacturer section of the INF to fix this problem. I have not tried it, since there are instructions for installing it into an x64 OS in the INF as well.

What OS?

The New button is only available if there is enough space left on the disk to create a new partition. What size hard disk are you testing on?

A "whether you like it or not" type of approach only works when there is one option.