cluberti

http://www.microsoft.com/security_essentials/

Under XP it's add/remove programs. You can get there directly by running appwiz.cpl in the Run box under the Start menu.

For RIS, what server OS and patch level are we discussing here? The TFTP request is generally made after DHCP provides the server data - I've honestly never seen this before, and most folks seeing this are running a non-Windows RIS server, so hence the ask about the server (knowing there are RIS solutions that are Linux-based).

Well, honestly I can't repro it on any machine (or VM) I've tried. Intel GMA, ATI graphics (Radeon 9800, x1350, 200m, and 3650), Nvidia 9800 and 7950), and even vmware and microsoft VM video "chipsets". None of them reproduce the issues you are seeing, so it can't be specific to Windows, as if it was I should have been able to repro it (note I tested XPSP3, Vista SP1 and SP2, Server 2003 SP1 and SP2, Server 2008 and SP2 - I haven't tested Win7 or 2008 R2 as of yet, although I could if I had to. I am going to rebuild this box that's currently running Vista SP2 to Win7 in the next week or so when I have some downtime, but I don't remember my other Win7 machines doing this either.

We don't generally delete accounts, as this can mess with the backend database. Please PM if there's a specific reason.

Unless you're saving out to a log, the data overwrites itself on a set time - in this case, it would seem to be a 5 minute loop. If you want to set up and collect data over time on an XP system, consider using perfwiz to configure and gather .blg logs for you over time. As to why a system is slow when it's hardware should be newer/faster, assuming it's not bad hardware you have to assume that the load then comes from something you've installed on top of windows that would have the potential to cause perf issues (like antivirus or firewall software that loads filter drivers, or bad hardware drivers, for example). If you're loading these machines exactly the same, new vs old, then it's likely they have something in common other than Windows.

Done.

I believe that code is a part of the homegroup code, and as such won't exist on 2008 R2, even with Desktop Experience enabled.

There is, but you're gonna have to learn a dev language if you don't know one already, and write some code. The reason programs can do this is because the developer has taken a value, read it in as a string, created a new value, and written it to the registry via the RegSetValueEx function in the application's code.

2GB would be fine for x64 Vista on a desktop, but a laptop probably not so much. If it was Win7 you'd probably have better luck, but most likely the reason your laptop came with x86 instead of x64 Vista was likely down to drivers and the amount of RAM they installed.

Sounds like a permissions issue or an architecture issue. If you look at the permissions for the image group that contains the captured image, does the user (or a group the user belongs in) have rights to read the image file? If not, the user will not see it (and if it's the only image in the image group, the user will get this error). Second, make sure you are using an x86 boot.wim as the boot image if you plan on deploying any x86 captured WIM files - x64 boot.wim cannot see x86 WIM files, so if you're using an x64 boot.wim and this is an x86 XP WIM image, you will also not see the image in the list (and again, if it's the only image in the image group, you'll get this error).As to your second issue, I've never before experienced that problem, although it could be a DNS issue. Are you doing this directly on a domain controller, or are you doing this from a remote workstation using AD or RSAT tools?

Then that would indicate that the hardware supports it, but the driver isn't implementing the interface.

Make sure you right-click in that window and make certain that "show disabled devices" is checked, as well as "show disconnected devices". Other than that, if it doesn't show, it would seem it wasn't installed for some reason. Note it won't display if the audio driver or device doesn't support the wave out (in software driver or hardware DAC, respectively). Are you saying thait "disappeared" from a running OS where it used to work, or did you upgrade Windows from a previous version and now it's gone?

Because Server 2008 is Vista, and Server 2008 R2 is Win7? It was removed from Win7 because they wanted the interface to die, and for people to use the new start menu / taskbar. Classic is comfortable because we've been using it for ~15 years, but after moving to the new interface I can't say I feel like I'm missing anything.To each his or her own, of course, but I feel I do less clicking and less searching with the new interface. If you really want the old and still want to use Win7, this project is probably for you then.

What I do is build my machine as I want it in a VM, then take a snapshot, then run sysprep and image the drive. I reboot the VM once it's been captured and make sure sysprep worked - if it did, the image is good and can be deployed. If the image fails, I go back to the snapshot point and run sysprep again. However, if it fails a second time, I rebuild the VM again from scratch and repeat the process. It's worth noting I've only ever had this happen twice in my time preping Win7, and both times it was caused by installing onto a hard drive that eventually did die (hence why I moved to using a VM instead, where the issue has yet to occur).

Correct - this specific error, while not entirely helpful once it bubbles up to the user as a CD problem, is actually an indication that the media downloaded was bad. I've seen this quite a few times now, and 100% of the time the ISO download had failed in some way and a redownload (and CRC/hash check of the downloaded media to make sure it was valid) resolved the issue.

Unfortunately that means nothing - the dump says you have a hardware failure, so heed the warning very carefully and take the error very seriously.As to the data you posted, this dump unfortunately is useless. The minidump doesn't even contain the WHEA error record data, and as such I can't tell you anything more than an MCA bank reported an error. Either configure for a complete dump and compress/upload the next crash dump, or start testing the hardware. Something (or some things) inside this system are failing.

You would have to find a way to rewrite the computername field of the xml file BEFORE the setup routine runs (ala MDT or SCCM). Other than that, there's no way to do it other than using a script to change the computer name afterwards. Either way, this isn't a feature of Windows setup.

It would seem either your media is bad, or the initial install had errors. I've never seen that particular warning before, but it's saying that /generalize didn't work properly and the install is now invalid. It can't repair itself at that point, no matter what you do.

If you debug it further you'll find it's a SID/crypto error, and that sysprep didn't complete properly (hence the DRM information WMP has is for the user prior to sysprep, which is invalid, and thus the error because the user's keys and SID/user context are no longer matching and valid). I've run into it before, and the only fix is to redo the image. This is the main reason why my images are now all built in VMs with snapshot capabilities, so I can simply go back and try again when/if it fails (and it's rare, but yes, I've seen this one once or twice before and ultimately figured out the error).

No worries, and good luck. If you do actually nail it down, post back for others to see and reference in the future.

SCCM is huge, it does all of our software management, windows update management, and OS deployment, and it has WDS and WSUS "underneath". Take a look here for starters - it's a LOT to wrap your head around if you've never used SMS.

Well, netio.sys doesn't actually allocate anything, it's just the network input/output API driver (hence the name "netio.sys"). Meaning something on your machine is hammering the network and not releasing it's allocations via the network filter driver it has installed. At this point, it leaves only a few things (and without the .dmp and a debug kernel it's going to be impossible to tell): 1. Network drivers themselves - it looks like this is an nvidia chipset, and there aren't any known driver leaks in Vista SP2 or 7 with it, but you will want to make sure you've got the latest WHQL driver set anyway. 2. Firewall or antivirus software - most antivirus and all firewall software packages install filter drivers on the network stack (and hook the kernel as well) to trap I/O moving in and out of the system, and these packages can cause these sorts of problems too if they have a coding bug. I see you're running NOD32 for antivirus, but no special firewall software, but I also see you've got VMWare workstation installed. I'd consider making sure you've got the latest updates for both, and keep an eye out that one of these could be causing the problem. 3. uTorrent is running, and this particular torrent package does have some known issues with leakinkg memory, so it's always possible this is causing it. A quick check would be to disable and kill it and monitor to see if the memory leak behavior stops without this running.

Honestly at first glance I'm not sure - what happens if you run nslookup on the DC against the domain name itself, or try to ping it? I'm guessing it'll fail to resolve, but if it doesn't this may get interesting. The path error is most likely failing to find the domain sysvol and netlogon share (again, usually at \\domain.tld) and thus the error, so it's good to check that you have access to that befpre you run dcpromo. Also, consider using CoreConfigurator to run dcpromo to make sure it isn't the script that's failing (it looks ok, but it's also close to 1AM here so I may be missing something too). Just remember to run slmgr -rearm to give yourself more time - you should have a few months' time to eval before you need to install licenses, although if this is going to be something you do often (run a test environment) you might want to consider a Technet plus subscription.