cluberti

It would probably be easier to create a profile, save the ntuser.dat, and copy this to your default user profile and the admin profile (and anywhere else you want it) than muck with this reg setting. I've never seen it work properly, but the profile .dat always works.

Come on, keep it on topic. If you want to debate Vista performance, do it in the Vista forum.

actually, if the EXTERNAL interface is wireless, but the INTERNAL interface is wired (the one we'll be using to connect to the LAN), ICS might work - I've never tried it, as I don't have a wireless device I want to mess with at the moment, but it just might work.

Sounds a lot like readyboost and superfetch in Vista to me...

Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch. Parameters The following parameters are displayed on the blue screen. Parameter Description 1 The exception code that was not handled 2 The address at which the exception occurred 3 The trap frame 4 Reserved Common exception codes include: 0xC0000005: STATUS_ACCESS_VIOLATION A memory access violation occurred. So a driver on your machine attempted to access memory that was invalid, or accessed memory that had been paged out while the driver was at DPC level or higher. Do you have any .dmp files in your Windows directory around the time of the last crash? That's about the only way to know for sure who/what caused this.

If you don't mind writing a bit of code, it can be done easily with C#. It's stored in the registry as a DigitalProductID value under HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Windows NT\CurrentVersion\, but it's not clear-text anymore, it's encrypted. You'll need to write some code, or use someone else's application code that's already written.

Well, if you were to gather a network trace from the wired machine trying to visit one of the 'slow" sites, and a network trace from the wireless machine going to the same site, do you see any obvious delays in traffic? Normally this is a DNS issue (make sure both machines have the same DNS servers configured), but to figure it out for certain I would suggest downloading and using wireshark or netmon to gather the network captures and view them.

What happens if you open a command prompt as administrator (start > programs > accessories, right-click "Command Prompt" and choose the "Run as Administrator" option), then type "C:\Program Files (x86)\Internet Explorer\iexplore.exe" to open IE as an administrator, then try the install?

Unless you have a way to segment the LAN in such a way that the clients using the router for DHCP do not have contact with the test DHCP server, you can only have one DHCP server on your LAN and expect this to work. I would instead suggest that you manually configure the IP address and DNS servers on your clients that are currently using the router (so they no longer need to use DHCP), and then stop that on the router.

That is correct, this should work just fine. You should contact Symantec on this if you cannot re-download it from the site. You can't just move an application (with only some very minor exceptions, and I am quite sure Norton 360 do not fall under these exceptions) from one machine to another. No, no need for that. In fact, that utility will likely try to wipe the drive, so don't use it. Just put the hard drive in the new machine as a slave to the master hard disk (have your friend over to help with that if you have trouble figuring out the jumpers) or on a cable that is unoccupied, and go from there.

If you download and run process monitor from sysinternals, and then monitor the registry while opening the drive (to give you this dialog box), what reg entries are "not found" or "access denied"? That would be what I would investigate and fix first.

you wouldn't happen to have a router on that LAN that is trying to do DHCP and DNS? Most home and SMB routers do this by default...

1. You should point the DNS entries at themselves first, using the other server as a secondary (same with WINS, if you're configuring that). 2. If IAS is installed on the virtual server DC, then you will need to install and configure on one of the new DCs and point your switches / servers / anything else using IAS to the new server. 3. You can use tools like replmon to view replication. Note though, that you will need to update the schema from an R2 cd on the virtual server DC before you can make a server running R2 a domain controller.

I'm moving this to a more appropriate forum, as this isn't W2K-specific, but more malware-related. Better assistance will likely be found there.

This is your third OWA post, and the third time I'm answering. Follow the previous SBS guides I mentioned, or, read this: http://www.msexchange.org/tutorials/Config...ote-Access.html Stop asking the same questions in different posts. Please.

If it really is the same system with just a new video card, contact Microsoft and get them to free up your key (or give you a new one), and that should be fine. If the system is markedly different from the last install (like a new motherboard, hard drive, etc), you'll probably not get a new key from Microsoft and will need to buy a new license. Again, if it's just a video card replacement, contact Microsoft and get it cleared up.

Merging all of these topics because it was posted 7 times in the Vista forum - not sure why, but the two responses are merged into the last post.

Unless you're trying to fix this as a learning exercise, I'm going to suggest backing your data up off of that machine and rebuilding - it'll be quicker, and you'll know for certain the install doesn't have a virus. If you're fixing this to learn how to fix it, however, and don't mind the downtime, then by all means don't let me stand in your way .

OEM disk and retail key do not work - you must have a retail CD to use a retail key, and an OEM key to install an OEM OS. I'd contact Microsoft asap to get media.

No, in fact trial versions won't accept retail or OEM product keys, at all. If you need media you can contact MS and fax them the COA, and they'll ship you a CD. Is that a retail key, or an OEM key?

LOL - good strategy

No, drivers for devices like disks and memory controllers, processor, etc load with the kernel right before the splash screen shows up. So, that would explain not being able to boot in safe mode, either. You could uninstall the drivers before moving motherboards, but that obviously isn't an option if the system dies.

If the DVD is the same version of the OS, then usually you can (some OEMs keys only work with the version that shipped and the architecture though, so be careful). However, home premium keys and business keys are different, so I don't think it'll matter in this scenario - if you want x64 business, you'll have to buy a license.

Yes - no version of Windows can perform magic and make one chipset driver that's installed work on another chipset. What you are asking is just not possible. If you want to replace a motherboard, replace it with the exact same one (or at least the same chipset and processor type). Otherwise, yes, you are "doomed". Drivers just don't work this way (it's not a Windows problem).

Data will likely be missing from your domain - not sure what, but esentutil is usually able to "fix" database corruption, but does so by discarding corrupted data in most cases. You could be missing user accounts, unable to start services, etc. Not only that, but once you have to resort to esentutil to "fix" a corrupted AD, it's no longer supported by Microsoft as it could be tainted (due to corruption) in any number of ways. Again, in the event esentutil allows you to boot normally, consider the installation "broken" from then on until you can bring up a new DC as a global catalog server, move the FSMO roles, replicate a few times, and dcpromo the old DC down. Once you've done that, go over your AD with a fine-toothed comb and make sure everything (and I do mean everything) works. This would also be the time to backup your GPOs with GPMC, make a backup of your AD, etc. http://www.petri.co.il/transferring_fsmo_roles.htm No, backing up the .dit file is unnecessary. Follow the backup strategies on technet instead: http://technet.microsoft.com/en-us/library/bb727048.aspx Usually file system corruption, or the writeback cache on the raid controller wasn't written to disk successfully, or your antivirus product scanned the file and corrupted it, etc. Too late for that - unless you've already backed them up with GPMC, you'll find they may or may not work on the new DC. You can try, but don't expect it to work - the GUIDs for everything in your new domain won't match the old, and it will likely simply ignore the old policies.