Tag Info

Hot answers tagged

6

Sure, free solution: you can use volume shadow copy and ImageX to do this on your own. vssadmin create shadow /for=C: vssadmin list shadows Then grab the shadow copy's volume ID. (Usually looks like \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopyXX.) imagex /capture \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy10\\ image.wim "Server Image" Then get rid ...


4

HP provides the Array Configuration Utility, which contains a CLI component you can use to configure the RAID devices. You would need to bundle these tools into your WinPE WIM or make them available via a network share.


4

TPM is secure because it's "watches" the boot process; when your normal Windows installation boots, it follows the "normal" boot path and TPM recognizes this and will only store/retrieve keys when this process has been followed. If you boot any other way, even just safe mode, you'll "change" that process and TPM will not "unlock". Technically the key is ...


3

That's a generic "Can't talk to the Management Point" error. This is usually one of a couple things: The MP isn't assigned correctly in the TS file (which if you're using a generated PXE image, it's right, unless you have SCCM wildly misconfigured) The MP isn't in the local subnet and WinPE can't get to it (there's a whole variety of possibilities here, ...


3

Yes and No. Yes it's possible to copy the binaries to WinPE and run the RDP Client. But WinPE is licensed only for administrative purposes. If you're using it as a thin client OS, you're in clear violation of the license. See my answer to this related question for the list of files: Boot to Remote Desktop


3

Freecommander is what you are looking for. Its free and lighter than TC. http://www.freecommander.com


3

I recently had this same issue and here's the basic steps of how to do it: Mount the WIM file like this: dism /Mount-Wim /WimFile:<x:\img.wim /Index:1 /MountDir:<x:\mountPath> Add the driver: dism /image:<x:\mountPath /Add-Driver:<x:\path\to\drivers> /Recurse Commit changes and unmount the WIM file: dism /unmount-wim ...


2

Thanks for the suggestions, redblacktree, but the XML file was in fact well formed, and it was working fine off a USB key. I found out I could use /unattend with setup.exe, so I copied the entire Windows install DVD to a file server, booted the same WinPE image via PXE, then ran: net use w: \\server\share w: cd x64 setup.exe /unattend:w:\unattend.xml And ...


2

Yes, it is. You're also going to want to add it to install.wim as well, so that it gets installed, otherwise your system likely won't boot after.


2

In WDS there are two unattend files. One for the install image and one for the boot image. You set the settings that you're asking about in the WinPE section of the answer file for the boot image.


2

It appears at the moment this was caused by the lack of HyperV drivers in the WinPE boot wim. The x64 version of the boot wim booted up fine. After looking at both in sccm, I noticed the 64 bit boot wim has an Intel emulated nic driver, while the 32 bit one does not. Not sure where I'll be going from here.but this happened after upgrading our Windows ...


1

The word storage in this case was a misnomer, or a red herring at best. In this instance, the VM's RAM was the culprit. It was set to dynamic, 512MB minimum, 4GB max. The new WinPE wims are rather large, so I bumped up the minimum RAM to 2048MB, and that did the trick. I don't know why WDS/WinPE doesn't request more RAM, or actually why it doesn't detect ...


1

From what I'm reading an uncaught throw results in the exit code being one. Also, your passing in the script path through the -command switch, when it should be passed through the -file switch, see the reference, -command will treat your string as a command, since it's a file path, it will throw on of those same red-letter exceptions we love in the ...


1

To answer my own question. Refer to the bottom of this page. Still need to find out how to clear the gateway via the iPXE script.


1

I have noticed this too. When I'm done with any particular set of updates, I export the image to a new one. The less memory used on a PXE boot, the better. When you modify an image, DISM stores additional resource files that increase the overall size of the image. Exporting the image will remove unnecessary resource files. ...


1

I don't know how you've created the WinPE ISO, I presume it's with the WAIK? When you're building the image, create a new text file in notepad called Winpeshl.ini and store it in the build_directory\mount\Windows\System32. In that file, call the batch file. To make it a bit easier and quicker, see if this link will help. I used it to see when I was trying ...


1

Bitlocker encrypts the data with a key , so no matter if another user boots up the environment he will not have access to the data directly . The downside is that he can try to crack the encryption because he has physical access to the hard disk (which can be partlly prevented with an usb start-up key . As far as I know the TPM / USB key is unusable when ...


1

Upgrade the RAID controller firmware. The newest revisions add access to the hpacucli command line utility during the BIOS screen. Otherwise, you could automate your SmartStart installs. Look for the conrep utility.


1

It sounds like a Ghost bug. One thing I don't see, or may be missing: Have you tried scripting diskpart to clean, create, activate, and assign all at once?


1

Can you hit F8 during the boot and go into command line recovery mode? If you get there try either FIXBOOT or, if that doesn't work, run CHKDSK /r.


1

Unfortunately this question only just showed up today in my RSS reader, so even though it's a couple years old I thought I'd offer what is probably the right answer for future readers. I'm not familiar with the particular model you describe as affected, but this does sound rather similar to a problem which occurred in certain models of ThinkPad (my memory ...


1

You could try Total Commander, which is Shareware. Supporting every major version of Windows, plus Android, it presents a side-by-side view of files and folders. There doesn't seem to be any pictures on the main site, but you can find a range here.


1

You need to assign as well in diskpart otherwise it will be mounted but not have a drive letter. http://blogs.msdn.com/b/7/archive/2009/10/08/diskpart-exe-and-managing-virtual-hard-disks-vhds-in-windows-7.aspx


1

While not directly answering your question (because I'm not sure you can make mstsc.exe work in PE), why not try to work around the problem? Like you mentioned, try VNC. I've packaged other executables in PE environments and had them work just fine. As long as you have network drivers and capability it could do the trick. Edit: According to Microsoft, ...


1

You can use free implementation of RDP client (like FreeRDP or rdesktop).


1

If all you need to do is install the OS you could use Diskpart to partition the drive, ImageX to copy a custom .wim file to the partition and BCDboot to copy boot information to the system partition. Check this out for more info.


1

Personally, I use GRUB4DOS to do things like this. It's a boot loader capable of booting from ISO images, floppy images or partitions located on any media (USB, CDROM/DVDROM etc.). I personally have a USB stick with WinPE/ImageX, a huge collection of diagnostics and install media for Win7 and a few linux distros.


1

Maybe you can try ImDisk. I've used this to install Windows 7 from a USB disk where Windows wouldn't install if it did not see its files on a DVD. I used the steps here to install the driver from the command line.


1

Add and Remove Drivers Offline Driver Servicing Command-Line Options Assuming you have your driver files extracted to a local folder on the same system you have your WinPE image mounted with dism: dism /image:<image path> /add-driver /driver:<driver path> Technically, you don't have to inject drivers to an existing Windows 7 installation while ...



Only top voted, non community-wiki answers of a minimum length are eligible