Tripredacus

From what I can tell is that pin 5 on 6P6C (RJ12) needs to connect to any pin on 8P8C (RJ45) that isn't being used (4, 5, 8). The N/C means that particular pin does not make a connection to whatever it plugs into. Since it is actually laid out in the diagram that it connects to pin 5 on the other side makes me think it might be used for grounding? Anyways, this type of cable seems to be fairly inexpensive to buy.

Well since your system isn't untouched, the fact your settings are incorrect is because of one of these two issues: 1. You fiddled with the BCD. 2. The OEM uses some non-standard way to run recovery. 3. There is always something else possible. You can see all of Reagentc switches with /? While it is normal to see the winre.wim in C:\Windows\System32\Recovery, the one to actually use in booting is typically in the recovery partition. So I'd guess that your manufacturer is either using a 3rd party tool, or some in-house method of handling recovery, rather than using the official Microsoft guidance. For example, even your reagentc /info data is lacking... Windows RE staged should be 1 not 0 Setup enabled should be 1 not 0 WinRE.WIM directory should have a path Setup Files should have a path That path is the same as the one in Recovery Environment. But since you are back to working, I wouldn't worry about going about and fixing (breaking) it now. It may be by design as not everyone does it the same way.

Your motherboard manual doesn't list that speed as being supported. Only these: PC2700 PC2100 PC1600 Also says only 2 DIMMs support PC2700 (333MHz), if you add more it drops the memory speed to 266MHz. I am looking at info on Page 26 of this PDF: http://mtz01-a.stanford.edu/machines/manuals/a7s333.pdf The PDF has a modify lock, which also apparently doesn't let me copy (Ctrl+C) data off of it.

It seems to me that it doesn't physically remove them, but makes it so they do not install. Having not actually used it, not sure about that but just a guess. Looking at this, seems that you need to do additional steps to remove the winsxs data:

The only way is to use an unattend to install the package. I'm not sure about DirectX, but MSSE has an "uninstall requirement" in order for it to be bundled into an OS. This is a licensing thing, and probably a good thing, since packages injected into the OS can't be uninstalled, which would be a big legal problem if a computer was sold with it included in that way. For DirectX, there may be an MSU available. For example, here is a DX11 MSU for Vista: http://www.microsoft.com/en-us/download/details.aspx?id=3274 With some research you might be able to find one for Windows 7.

Well before you jump to conclusions... When was the last time you ran Fix It Center? Was it immediately before installing Weatherbug? I find it doubtful that absolutely nothing was done between the "days ago" and now besides just that. Do you see anything in the Application Log in Event Viewer relating to Fix It Center during installation?

Quoted from above Windows Boot Loader ------------------- identifier {500cf7cd-c423-11e1-b5b0-14dae9e74180} device ramdisk=[C:]\Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fefa\Winre.wim,{500cf7cc-c423-11e1-b5b0-14dae9e74180} path \Windows\System32\Boot\winload.exe description Window 7 Recovery Environment (system partition) locale en-US osdevice ramdisk=[C:]\Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fefa\Winre.wim,{500cf7cc-c423-11e1-b5b0-14dae9e74180} systemroot \Windows detecthal Yes winpe Yes ems Yes Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Microsoft Windows 7 locale en-US osdevice partition=C: systemroot \Windows resumeobject {0540b4cc-c367-11e1-9849-806e6f6e6963} Windows Boot Loader ------------------- identifier {fec54f22-c74c-11e1-ada2-14dae9e74180} device ramdisk=[F:]\sources\BOOT.WIM,{fec54f21-c74c-11e1-ada2-14dae9e74180} path \Windows\System32\Boot\winload.exe description Windows Setup locale en-US osdevice ramdisk=[F:]\sources\BOOT.WIM,{fec54f21-c74c-11e1-ada2-14dae9e74180} systemroot \Windows detecthal Yes winpe Yes ems Yes This seems kinda strange to me (although I am no expert) ... so some guesses from me. Firstly, I know that some OEMs do things a little different and this may explain why this looks strange to me. I am going to guess that your recovery partition is not hidden? You can see it in Computer? If so, was it always this way? OR it is possible that you have a Windows 7 installation DVD inserted! Now some things that I do know. See the object marked as {current}, this is your OS. You are missing some information there! You are missing (at least) the recoverysequence and recoveryenabled settings. These are in place to point Windows to the GUID for your recovery partition. Anyways, the first "identifier" is for your recovery partition, however it is pointing at your OS volume.... Try get some results if you run this command elevated: reagentc /info

Boot into your OS, run this and paste results in code tags: bcdedit /enum all

First you need to determine where this "Operating system not found" message is coming from. The BIOS (unfortunately) isn't very helpful in telling you what it is trying to boot from when it shows you this message. It could very well be that that notebook isn't even attempting to boot off the USB drive and goes directly to the HDD and fails. You should try taking out the internal HDD, and then try to boot off the USB HDD to see if that works or not. There are some other questions we might have such as: 1. What is the size of the boot partition? 2. Do you have multiple partitions on the USB drive, and if so, is the WinPE partition the first one on the disk?

Unpinning this topic. Will add a link into the Deployment Documentation thread.

Try also regsvr32 jscript.dll Also it appears that Weatherbug uses some not-so-great methods.... Try looking here: http://blogs.msdn.com/b/heaths/archive/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions.aspx

There was a major problem with this product. It was sold and supported under the server line, but anyone who bought it would use it on a desktop board. Even Intel only had support for WHS on their Workstation and Server products. I remember getting escalations to me from tech support at my last company where customers bought it couldn't find drivers. But there was nothing we could do since there are few official drivers for desktop boards for Server 2003. Its possible this month. I am and am not looking forward to it. Partly because I can't wait to get all this past me, and also I'll have to update to the new WinPEs finally.

So I take it that you don't get the error anymore? 0x7B is missing or corrupted Mass Storage Controller driver. Reinstall your chipset (or RAID if applicable) drivers to resolve it.

Just an FYI for anyone who is using this board. There is something flaky with BIOS version 0071 for the Intel D2700MUD. Boards this BIOS update relates to: - Intel® Desktop Board D2500HN - Intel® Desktop Board D2700DC - Intel® Desktop Board D2700MUD 0071 release notes only show this as a change: v0070 behaviour - Normal version, can PXE boot. - Board reports Arch 6 to PXE Server (on Server 2008 R2, this is in the Deployment-Services-Diagnostics event log) v0071 behaviour - PXE response times out, resulting in executing Abort PXE command on the client. - Keyboard does not work (F11 or F12) after downloading the boot rom from the PXE server. - Both PS2 and USB keyboards tested - Can PXE boot if set WDS to boot all known and unknown clients without requiring F12 to be pressed. - Board reports Arch 0 to PXE Server (see above for location) Changing the PXE boot response on the server to auto boot proved that the Abort was due to a time-out in the PXE process, due to the keyboard not working. The keyboard does work at other times, can go into BIOS, can get boot menu, can reboot after the abort with the "any key" or Ctrl+Alt+Delete so it isn't a 100% keyboard failure. And obvious Intel changes more than "security check issue" between versions if the Arch value is different! So just a heads up that you probably should use version 0071.

Ok. I felt that is is better to have the topic in "News" since it is "News" today... Even though it is actually "Olds" but those not keeping up on security may not know about it. But just watch, It'll turn out that one of my machines are infected! PS: congrats on the Patron badge!

7... I can't play facebook games because (for some reason) Facebook says it is OK for app developers to use XSS. Since my browser security blocks XSS, none of the programs work properly. Those games were fun when they were written responsibly. And to think, Zynga actually says "enable an XSS exception for Facebook domains" No way pal...

I hid your duplicate topic... This story seems to be reported wrong in the news. Already this morning I have texts from friends that are scared about some virus attack on Monday. They called it the "Monday Virus". But as you found, it is from last year. FBI took over the C&C but did not know where all the clients were. So they sanitized the servers and let them keep running. Now the problem is that for some reason they are on a time-table (probably a budget thing or whatever) and there had been meetings and deadlines pushed past already. So for some reason they can't just let these things run in a closet somewhere and have to turn them off by Monday. You'd figure it wouldn't be overly complicated to send a command back to the clients and have them set their DNS to auto or something but its probably more complicated than that.

1.) I don't know anything about printers. 2.) How were the network drives handled before? Were they done manually or through a GPO? Anyways, you say you are migrating some clients... but you don't say from what to what. What OS on the servers? What domain (if any) to which functional level? Were the users already in OUs or are they now? etc

What wireless NIC do you have? Is it in a notebook or desktop? What is the make and model of the router?

What was the error? Did you look in Event Viewer?

That's not very fair. It seems to me that you sabotaged your system with Windows 8!

Andreas Waldetoft - Swashbuckling Privateers - from the overly complicated Europa Universalis III (PC)

Your XML seems strange. Why do you have multiple Reseal objects? You seem to have 3 Microsoft-Windows-Deployment components specified at the end of the file. Do you really need all of those? There are also a few components that have no objects in them. I would guess (hopefully) that you have redacted parts of the XML to keep in confidence. A quick look: InputLocal has the wrong data. Should be 0409:00000409 and not en-US. There are many changes between Server 2008 RTM and Server 2012 Beta. Have you validated this answer file against a Server 2012 catalog in WSIM? I see that some people encounter this error (mostly in VMWare) when a deprecated setting is present.

That ball is already rolling. In the ADK, there seems to be a bunch of info about how to create help files with HTML5. I personally love CHMs.

Post your answer file?