Tripredacus

Opening up the topic now, as I have encountered a problem during deployment. They were: - started deploying from 64bit WinPE, durr MBR.EXE is 32bit app! - started deploy from x86 WinPE but didn't have NIC drivers installed - now the wrong partitions get hidden. Using the following: MBR.EXE 0 0 /h Hides the BOOT partition instead of the WINRE partition. I need to research the MBR.EXE commands to figure out why it did this. Also the second diskpart script above in deployment is tentatively on hold as it removes the drive letters for all the volumes, instead of R. The recovery partition works, with the only problem being that JPG I am using is the wrong size... OR setres isn't working... Update1: The problems with the XPe image not booting after deployment was caused by the XPe install itself. It was created with the idea the C drive was the first partition. It would not boot because the BOOT.INI was pointing to the wrong partition. Also the RAM Overlay is protecting the wrong partition as well. Going to remake the entire XPe install and start over. Also going to use GPO to remove the ability to delete the recovery partition from Windows. I am likely going to take out the 'nodefaultdriveletter' option as it does not seem to make any sort of difference.

This is a new project using WinPE v3.0 x86 to make a custom recovery partition along similar lines to this: That project ended up failing because XP support in the OEM Channel was finished. In this case, SoftThinks does not work on the target motherboard (nor on the new Wind models) and XPe is still supported in the channel. NOTE: As with previous topics, I am using the OPK Tools not WAIK. If you use WAIK the paths will be different for adding packages! The system we are going to be making this for is a 2 partition Windows XP Embedded (XPe) that is using the EWF bootloader and RAM Overlay on the Boot partition. The partition order I have planned will be as such: 0 0 WINRE 10240MB NTFS HIDDEN 0 1 BOOT 10240MB NTFS 0 2 STORAGE (remaining space) NTFS The previous attempt to use this for a WinRE replacement failed and was not solved. Hopefully I will not have these problems this time. This thread is to document my entire process. Here are the steps as I complete them: 1. Find all source files from previous project and arrange them into a new folder. The files are as follows... x:\windows\system32\fscommand\admin.exe (wrapper to open command prompt) x:\windows\system32\fscommand\restart.exe (program to restart the computer) x:\windows\system32\resources\custom.png (branding image) x:\windows\system32\resources\imagex.gif (animated gif to appear when recovering) x:\windows\system32\resources\setres.exe (sets screen resolution at boot) x:\windows\system32\resources\welcome.png x:\windows\system32\resources\winpe1024x768.jpg (image background of HTA) x:\windows\system32\full.hta (runs the full recovery) x:\windows\system32\full_diskpart.txt (for full recovery) x:\windows\system32\MBR.EXE (to hide drives, set F key for boot) x:\windows\system32\recovery1024x768.hta x:\windows\system32\repair.exe (runs a repair recovery) x:\windows\system32\setres.bat x:\windows\system32\winpe.bmp x:\windows\system32\winpeshl.ini 2. Rebrand winpe1024x768.jpg from original PNG file. 3. change various infos in the HTA files, specifically the name of the WIM. I will not document these changes now because I may end up changing them later. 4. Develop a ballpark Deployment workflow: [diskpart] sel vol c assign letter=j sel vol d assign letter=k sel disk 0 clean create part pri size=10240 assign letter=r format fs=ntfs quick label=WinRE create part pri size=10240 sel part 2 active assign letter=c format fs=ntfs quick label=Boot create part pri sel part 3 format fs=ntfs quick label=Storage assign letter=d [/diskpart] imagex /apply z:\folder\winre.wim 1 r: (the recovery partition) imagex /apply z:\folder\image.wim 1 c: (the OS partition) [diskpart] sel disk 0 sel vol r att vol set nodefaultdriveletter [/diskpart] mbr 0 /install selm 5 11 "Press F11 for Recovery" 0x7 0x17 mbr 0 0 /h 5. Capture the OS to the WDS Server. 6. Create the WinPE for the recovery partition: copype.cmd x86 c:\winpe_x86\S_RE xcopy c:\winpe_x86\S_RE\winpe.wim c:\winpe_x86\S_RE\ISO\sources\boot.wim Dism /Mount-Wim /WinFile:c:\winpe_x86\S_RE\ISO\sources\boot.wim /index:1 /MountDir:c:\winpe_x86\mount Dism /image:c:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-hta.cab" Dism /image:c:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-mdac.cab" Dism /image:c:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-scripting.cab" Dism /image:c:winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows OPK\tools\PETools\x86\WinPE_FPs\winpe-wmi.cab" ** copy source files to mount\windows\system32 ** copy imagex from the Tools folder to system32 Dism /unmount-Wim /MountDir:c:\winpe_x86\mount /commit ** these files are the ones listed above. I will be doing this manually. 7. Test standard redeployment of the OS image (from step 5) onto a machine PASSED 8. Take the entire S_RE folder, copy MBR.EXE into the root. Copy the image.wim into the root, then: Imagex /capture c:\winpe_x86\S_RE c:\winpe_x86\winre.wim "WinRE" /compress fast 9. Test deployment from a 32bit WinPE, as the MBR.EXE is a 32bit app. *** more steps to follow/correct ***

Look for an IR window on the PC then. Here are some pics. Second picture on this page shows you an IR port on a notebook: http://www.tomsguide.com/us/compaq-nc8230,review-488-4.html All they are is a dark red square of plastic, like on old TVs and remotes. Here is a picture of one on a desktop (in outer space apparently) http://www.jdresearch.com/irdrive/icon/irdrive2.jpg

Can you just use the command to shut the machine down instead? It is: wpeutil shutdown

I confirmed that USB Drives are running at 2.0 speeds. Also installed a Logitech USB gamepad with no problems and even worked without rebooting or having to configure it first!

I can see this coming in handy one of these days.

I've seen this happen on notebooks that are over-heating and/or the wireless cards are failing. This was a known issue (for example) on the HP DV notebook series.

If you are getting a "MEMORY_MANAGEMENT" STOP error 0x0000001A, last time I had this happen, memtest revealed the memory was bad. I'm no pro at reading these dumps, just an idea.

Looks like someone forgot to pay their bills!

Welcome to the MSFN!

IRDA = Infrared Data Association. So the PC is reporting an IR device is accessing the computer. It isn't likely another user. Most PCs do not come with Consumer IR support, but some notebooks certainly do. You say it does not have network support, then later you say it can't access the internet. How does this PC connect to the internet?

I have used WireShark and Microsoft Network Monitor

Exactly, that hasn't stopped people from using Win 9x.

Yes, but I have spent hours looking over google results, and haven't found anything useful. I have no idea what "VM Additionals" is. VM Additionals is for another VM Program (I forget the one, I don't use it anymore) that gave additional functions to the VM. For example, without it you could not access network shares, etc. Have you checked dependencies?

This error is all over google. Is VMWare Tools related to say VM Additionals?

From First To Last - Ride the Wings of Pestilence

You can add the site into the trusted sites section. Here is a general example (only go to step 3), obviously you type the domain name in the field, not the entire contents of the address bar. For example, http://www.msfn.org/ http://www.share360.com/supportcenter/s360v2/manuals/manualbyvolume.cbml?volumeID=053&chStart=8&prodName=Share360%20Outlook%20Sync

Here are some questions (before you give up) as I've experienced this a long time ago... 1. What other roles does your WDS Server hold? 2. What is the OS version of the WDS Server? 3. What is the OS version on the DHCP Server? 4. Are either of these servers running DNS? 5. Are you using hostnames or IP Addresses for your DHCP/WDS Server options? 6. How much RAM is on the WDS Server? 7. What speed are the NICs set for on both servers, any switches in between and the client? Note: I am asking about the OS version. I know you said 2008 R2 but there are many different versions it could be. Make sure to include architecture.

If you open that little shield that is telling you may have a problem, somewhere in there you can find notification options. Unfortunately, my Windows Defender is not turned on (I think MSE disables it) so I can't see those settings.

So you are trying to have the WinPE be the host? Make sure to disable its firewall. Also do you get any errors?

Unless you are using a plug-in (I do not know of any, sorry) I do not think a browser can do that for you. There are some search engines that do index FTP sites, last one was Lycos but I don't know if that one even exists anymore.

I've been going about my Office 2010 training (self-paced) and came across some interesting info. Of course I can't tell you it verbatim, but fortunately there is some info on Social with a hint: http://social.technet.microsoft.com/Forums/en-US/officesetupdeploy/thread/4615d7bf-27f6-4b5d-b2ec-1480ef8a5214 Basically, if you have a computer with Office 2010 Starter installed, you will have an option (via Office To-Go) to install portable Office apps on a USB Key. I figured someone here might like that idea.

My only complaint about Hibernation is that there does not seem to be a good hardware support for letting you know a PC is in Hibernate vs being off. This has caused many headaches for me as I move computers around a lot. Some do not like being unplugged when in Hibernate and plugged in again and woken up. But I agree, Hibernation is better than sleep, but for my own computers (except my netbook) I do not use Hibernation or Sleep, only on displays and disks. The netbook doesn't seem to care if it gets unplugged while hibernating but that may have something to do with the battery. I remember my first experience with Vista hibernating (it did it by default) but I thought it was off. Boy does it act funny when you replace hard drives or memory in a hibernating PC that you think is actually off!

To put it simply, Sysprep prepares Windows for the end-user. If you install your OS and when it is done you have the sysprep box on the screen, it means you are in Audit mode. Unfortunately, you wouldn't want to use your computer in Audit Mode as some features of Windows are disabled. Some of which include Aero and it will also hide some pop-up messages, although they still get logged to the Event Viewer.

Right, the only reason why you'd ever need to "clone" a volume is if it has specific boot data that is kept on the hard disk outside where the file system resides. Otherwise, if its just data, you can use anything even a copy/paste.