Jazkal

Anyone else seeing issues with the new RTM version of WinPE v2.1 (Windows 2008) boot loader?

Here is what I use: (VBS script) Here is the output: "X:\hardtest.ini"

Windows XP can't be loaded as you describe. However, you can configure BartsPE to look and behave like XP. You would need something like the XPE plugin for BartsPE.

In some of our Win2k and Win2k3 deployments using Winpe2, we have to create multiple partitions before laying down the image. When the system has 2 or more partitions sometimes the second and third partitions don't get created and or formatted. I've tried using the diskpart builtin format feature, as well as a format command after diskpart is finished. The same exact diskpart script works fine under winpe1.6 (minus the format command of course). Anyone else seeing this?

Try putting bootmgr.exe in both folder: c:\tftpboot and c:\tftpboot\boot Our linux setup required us to do that. Can't tell you why, I'm the Windows guy, not linux.

I have been looking for a way to change the video resolution on WinPE x64. There are a number of command line apps out there for x86, but I couldn't find any for x64. And when I say x64, I mean a compiled, native x64 EXE. So, I wrote my own. The attached file, will reset the WinPE video res to 1024 x 768 x 16 It is an AutoIt3 script built in native x64. ChangeRes64.zip

Very nice work.

After I reset the Admin password, I used: ntrights.exe -u Administrator +r SeBatchLogonRight ntrights.exe -u Administrator +r SeTcbPrivilege But I still get access errors. Arrrgggg

After further testing, it looks like WinPE uses the "NT Authority\System" account as the logged in 'user'. All my searching online tells me that you can't/don't want to change this accounts password (which by default does not have a password). So I need to find a way to use something like su.exe or runas.exe. That is what I am currently looking at now. EDIT: To be able to use RunAs.exe and run psexec as the Administrator account, I will need to add these rights to that account: "Act as part of the operation system" "Logon as a batch job" Anyone know how to do 'User rights assignment' via command line?

Thanks for the info. I just need to figure out why it won't work. I'll mess with it on Monday.

after much googling, found that the local user account you are running psexec from cannot have a blank password. Windows wont let you run anything remotely if the account the request comes from has a blank password. So now how do I set the local WinPE2 user account password? Much less how do I determine what account it uses?

Wanted to see if anyone knows why psexec.exe wouldn't work on WinPE2? Running the same command line that will work on my workstation, I get this error on WinPE2: And I can ping the box at the IP. Any thoughts?

I am installing Win2k8 RC0 (Longhorn) from network attached WinPE2.0 or WinPE1.6. WinPE1.6 works without error, however WinPE2.0 has an issue. I am using the same set of scripts on both platforms, so I know I have the basic process working. After starting the Longhorn install from WinPE2, I get the following error message before the install fails: Error Window Title: "Install Windows" Error Window Text: "Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation." I've done searches for this error, and I can't find it anywhere. Anyone else seeing this now or in the past?

I use VMWare Workstation. But I don't see why the free Server version wouldn't work.

Ok, after some testing, the latest release of the WAIK (RC0) seems to have fixed the "issue".

I've tracked it down to the latest builds of Longhorn WinPE. The VistaPE that anyone can download works fine with vmware. But the versions that come with Beta3 longhorn doesn't work. I'm going to track down all the multiple versions come Monday and find out what versions work/don't work.

If you figure this out, let us know. As far as I have heard, one guy claimed to have got it working, even posted screen shots on his blog. But he never posted his method, and never said anything about it again. EDIT: I was talking about WinPE2(VistaPE). I know of one package for WinPE v1.6 that works. EDIT2: To early in the morning, I miss read your title, let me find the link to that package. EDIT3: Here is a link: http://www.colinfinck.de/en/peplugs/dotnetfx20pe/

After looking all over the internet, it seems this is a known issue with VMWare. As of today, there is no fix. (well besides using WinPE v1.6 anyway)

None of the links work in the first post. Anyone have a mirror link for this? EDIT: Found this thread that is supposed to have all this info, in it. http://www.msfn.org/board/Vista_Guide_Inte...fix_t95950.html

I have tested this on VMWare 5.x, 6.00 and 6.01 PE version I've tested with: VistaPE Current, Longhorn Beta 3, Longhorn RC0 I removed all components from the VM except Hard drive, RAM (512), Nic, And CPU (1 and 2). Still having the problem.

When I boot up VistaPE (WinPE2) on VMWare, we see the bar for loading files. It gets all the way across the bottom of the screen and then reboots the VM. The VM has 512mb of RAM. Have tried on both IDE and SCSI. Have all the VMWare Tool drivers loading in PE. Anyone have this working with out issues?

What type of system is this? Can you post the output of this: devcon.exe find pci*

It sounds like you don't have the MSD driver installed. Are you plugging the problem drive into the exact same connection that your other working drives were plugged into?

Very nice indeed

I know this is an old post, But I was looking for this same problem. Found my solution here: http://support.microsoft.com/kb/929835