Tripredacus

Some Intel motherboards have onboard dual-head video. So in these cases there will be two display adapters in device manager. The ones I've seen with this have the DVI-D, DVI-A and HDMI port. I think the DH57JG and another micro-atx I've seen that does this... Perhaps the D510MO but there are more than just those two. It is these types of boards you may have problems with if you do end up putting a video card in the system. Even if you set the BIOS appropriately, in the end the IGFX chip still decides what to do (the Technical Product Specs call this a "feature" rather than an "annoyance" but whatever) and you'll end up getting a Code 10 on one of those drivers. This is especially true of cards that either do not report themselves properly to the BIOS, or that the board doesn't have full support for, like the Matrox Parphellia series.

I know you can export out your NIC settings, I don't think you can save the logon settings, but honestly its not to hard to do. After you reinstall x64 your Network Admin (or whoever) joins the PC to the domain, and then Windows will automatically use a logon screen when you start up. This logon screen is the behaviour that XP changes to once added to a domain.

It also has a lot of warez in it as well. Refresh on the forum rules.

Look into the User State Migration Tool. Different versions allow you to move User Profiles between different OSes.

I have installed Nero 9 with this, it might be similar: (@ComSpec & " /c c:\temp\nero9u\nero9\Setupx.exe /i /qb /NS SERIALNUMBER=" & Chr(34) & "XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XXXX" & Chr(34) & " REBOOT=" & Chr(34) & "REALLYSUPPRESS" & Chr(34) & " EXCLUDEAPP=" & Chr(34) & "unit_app_75,unit_help_75" & Chr(34)) This is in AutoIT. I'm lazy to convert it to normal words... Anyways, if you use /NS you still need to specify a serial number, which is used just to install. After the product has finished installing, the product key is automatically removed. Does this help at all? FYI the excluded item is the Ask toolbar I think.

Is this a video card in the system?

We have all sorts of things in the WInPE forum. I'll move this topic there.

This is interesting, I never really thought about it. I used to maintain USB keys that booted and allowed for BIOS updates and using Ghost clients. Originally we used the Win98 bootfiles that is in every version of Windows format tool since 98, but had to go to DOS 7.1 in order for certain NDIS drivers to load properly. We didn't run into any problems with creating these keys until we tried 4GB and 8GB keys. All the normal ones were 1GB keys and they always worked fine. Now it seems that USB Keys under 4GB are becoming a rarity. I never put 2 and 2 together and figured out why the 4GB+ USB Keys wouldn't boot into DOS 7.1 until I read this. If 1 and 2GB Keys end up going the way of the Altair, do you suppose there could be a way to fix this, at least for DOS 7.1?

I'm not entirely certain how to categorise products under the Live Essentials umbrella, but best guess is to relate them to Office. This idea that Live Mail is the evolution of Outlook Express, the stripped down version of Office product Outlook. I'll move this to the Office section, may see more action there since no one seems to like Vista anymore.

Might be this? net start SSDPSRV From here: I wish I knew a site that listed all the service names to use with Net Start.

Download here: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=13935&ProdId=2783〈=eng Open with WinRaR drivers in SOLinf folder mesrl.inf is for x86 mesrle.inf is for x64

These are different. The domain in UnattendJoin is when you want Setup to join the computer to an Active Directory domain automatically. The DNS Domain is likely the DNS Suffix, which is a domain name that is appended to the computer name, also it will search first within that domain for servers. Some network setups will require that the correct DNS Suffix is assigned to the computer, but this is only for static IPs. If your network has a DHCP server, you can have it send along the DNS Suffix with the IP address when the client requests it. So to better explain the DNS Suffix in a real world situation, we will use the example in the help file of FABRIKAM.COM. When your computer needs to go somewhere on the intranet/network, let's say you have a computer on the network called \\HELPDESK. Windows will send a request to the DNS Server for the IP Address for HELPDESK.FABRIKAM.COM. Also, your computer name would be COMPUTERNAME.FABRIKAM.COM (the FQDN) and usually the DNS Suffix is going to match the AD Domain the computer is on, but as I mentioned before, networks can be set up differently so this isn't always the case.

Different versions of Server 2003 have support for different amounts of physical processors. For example, Standard supports 4 physical CPUs. Does your vCPUs have multiple "cores" or are they being reported as 4 single core CPUs? There are also other versions of 2003 that may have a different CPU support printed on the install media. For example, remember that NT Server came in 1-2 CPU and 4 CPU install CDs.

There are two directions you can go with this: 1. Find out which program is causing the problem. 2. Ignore the failing program and decrease the wait timer. Both can be resolved in the following link from social: http://social.answers.microsoft.com/Forums/en-US/w7performance/thread/fb35a679-c9b8-4a97-95c4-39c60e218130 For the timer, search the post for this registry key: WaitToKillServiceTimeout

Akitaka Tohyama - You Are Smart

I experienced the Reservation corruption on a 2008 DC but it only happened after a rogue DHCP server was connected to the network. The 2008 had correctly blocked the initial DHCP requests from the offender (as per how DHCP Authorization works I imagine) but the offender intercepted DHCP Renews. I'm guessing something was maybe not configured correctly, but the offender was a Linux server, so I don't know if that makes a difference.

XP COAs are tied to specific Install CD part numbers. I've found this out in the past, so if you go about finding actual media to install with, don't be surprised if the first one doesn't work. All the OEM CDs I have for XP (the hologram ones) have the part-number of the COA written on the CD so I know which one to use.

If you can get me the HwID for the device you are trying to install, I can get the correct link for you. You can find this in the Properties of the Device in Device Manager, on the Details tab.

And why is that? They often provide a far better feature set at the exact same price point (like dual PCI-e x16 slots, or having USB3 ports, etc), and if you go with an OEM like ASUS or Gigabyte, you also get a better quality motherboard (the PCB itself, components used, the voltage regulator, the BIOS options, the cooling, the layout, etc) and everything else. Intel isn't leading in any significant way. Let's chalk that up to a mis-worded post. I meant to imply that Intel can't compare to others, one of those backwards grammar moments! Since I've learned more and more about Intel baord (to say the TechProdSpec doesn't scare me anymore) I've run into some misgiving about their boards, however I have no knowledge on whether these things are corrected or done better on other company's boards. Let me use the PCI Express slots for example. Most Intel boards that have at least 2 PCI-E slots seem to have been designed incorrectly. Not many Intel boards will actually run the x16 slot at x16 speed. The specs will say things like "x16 mechanically, x8 electrically." Then I think, perhaps I can not actually tell the difference between graphics of a PCI-E video card running at 2.5GT/s vs the 5.0GT/s that it should be at. There was one sales training I attended that talked about their "new" (probably old by now) workstation board, and asked about the slots, and the dude was just like "yes that's what they do" concerning why they would put an x16 slot but only run it at x8. I understood the reasoning behind it, because of how it was constructed and blah blah blah But does that even matter? Is it a big deal that I would be basically underclocking any video card I'd put in those boards, even if I am not using any of the other slots?

Moved some content from post 1 to post 2. Changed the intro to show as more of a project rather than just a support thread. Added "development opportunities" which is basically just a list of things that have been requested, or that I wanted to change as well. A little note about some of these... The App and Custom OS installer is something present in my version of the HTA, but is removed from the public version. Currently, my HTA has buttons (the mount/capture/append buttons) changed to install applications and deploy custom images such as Win7+WinRE, Server 2008 + WinRE, custom partition values with XP. These menus are hand-coded and I've recently come into a situation where I cannot easily maintain these menus anymore aka the actual server is no longer at my location. So I wanted to come up with a program that would look on the file share for a file, and that file would tell those menus what apps or images are available, and populate the menus appropriately. This idea also ties in with the "local os detection", custom partition support/browse for diskpart script items as well. If you have any other ideas or want to help out, feel free to post here!

Why do you want to remove the Administrator account? It is needed during installation and (later) in order to get to Safe Mode.

Post OS version! You can use DHCP Reservations, however these can become corrupted. If you use them, make sure to keep a document with your reservations in case you need to delete and re-create them.

Does your XML validate in WSIM? Also, do not install Google Chrome in Audit mode. You won't be able to use it after OOBE without a reinstall, unless Google came out with a special "all users" version of Chrome by now.

To add to the conversation about the re-arms. I will say that it "may" be possible to re-arm / generalize more than three times BUT it may only be available if you use an unattend option. I tried to re-arm an image last week that was done with just a regular install, and it returned an error. I didn't think it would work anyways.

You may want to try the official Intel driver instead. I have had no problems with this device. I always get these "two" devices mixed up, MEI, AMT, SOL, WOE... Intel uses all sorts. Different HwIDs have different driver package downloads, yet use the same INF name. WOE HwIDs for H55 platform: VEN_3B67 mesrl.inf / mesrle.inf for x64 v6.0.0.1179 VEN_3B64 heci.inf v6.0.0.1179 WOE HwIDs for Q45 platform: VEN_2E17 mesrl/mesrle.inf v5.5.1.1012 VEN_2E14 heci.inf v5.2.0.1008 The annoying thing is that the v6.x driver series (for Windows 7) does not have driver support for the 2E1x HwIDs, which apparantly only have Vista (v5.x) drivers. So make sure you have the right INFs (since different file versions have the same name but not same hardware support) and check for any signing issues. All the drivers from Intel for these devices (mine are just examples) have signed drivers.