allen2

As a side note, Microsoft never released a Windows 2007.

Does the other drives show the same behavior ? I had this behavior some years ago and in the end it was computer memory that was faulty. So should do crossed tests, test the crc of the file of this hard drive from another computer and test crc of other files from another hard drive on the original computer.

The shutdown command used from another computer has requirements: - Server service should be started on the target and not filtered. - You need to have the shutdown right on the target computer. In PE the server service might not be even installed. And for the credentials, you're way off as each PE is running with the system account and without other account (by default). You should first check if you are able to connect to the remote PE with a command line "net use". Another way of doing things properly would be creating a service on the PE and send it the custom command when you want or you might want to do this the other way around (a service on the PE could check regularly a network location to know if it need to shutdown).

As Ibm hardrive became Hitachi, i think the tools for ibm drives should work. Try disk manager 2000 (it should be able to install a dynamic drive overlay on your hitachi drive): the file you need is there. If it doesn't work you can still try HFT (Hitachi feature tool) to reduce the size of the drive.

You could use a drive overlay (most hard drive makers did their own) and you may also need to create a small first partition. What is the make of the new hard drive ?

Ok, i've gotten 7.1GB of MS KB articles (131700) and there is till a long way to finish. But i would like to be ready when the extracting will be done. So does someone know a good tool that can analyze html and store in database the useful information (the reverse of for example php/mysql that recreate web pages using template) ?

Most likely you didn't use the right ahci drivers when you integrated them (you need the x64 one). There a lot of posts around about changing to ahci after install (use search).

You need to see all the files as ntuser.dat is hidden. You can do it from the server or any computer as long as the user isn't logged on.

The only reason, i see for it to be in dmz, is so it can handle the smtp function without another device or redirection (which is a very stupid idea). As Tripedacus said, it is very dangerous having a DC in DMZ. You might think about buying more hardware like two more servers and use them to create VMs for handling each function (one for each). You'll need also to setup a smtp relay with filtering capability in both ways. The problem you encounter might be a "simple" reverse spam attack (with non delivery reports).

Sorry to intrude on this thread, but instead of calculating a md5 of something this small, i would compress it with 7zip (for example): - You might be interested in looking at it after and you can't get it from its md5. - You 'll have a limited number of md5 of bootstrap. - Someone might have created a new bootstrap and then you'll need to update your md5 reference. - How are you going to handle the unknown md5 ? If your entire bootstrap is stored, you can find the closest one (with a binary comparison for example) but you can't do this with md5. - As you said 2 md5 might be identical and the probability for such thing on such a low number of bytes should be extremely low but even then you might want to be sure that they're different or not. Sorry again if i am totally of topic there.

It might be referenced in the user registry (i.e.: in his roaming profile folder\ntuser.dat). You might check it when the user isn't connected by loading its hive with regedit.

The way i see things: - list all used printer drivers from the x86 existing server. - find the MS certified x64 drivers for the new x64 2008R2 servers. If the drivers aren't certified, you'll need to test them extensively. Also some drivers might be incompatible with others. - Install the drivers properly on one of the 2008R2 servers. - create a printer queue for each driver and share it. - map the printers queues (created at previous step) on the others 2008R2 servers using a script (vbs can easily handle this) then remove the printer queues still using a script. This way only the drivers will be installed on the new servers. As a side thing, if you feel like using printmig, don't !!! It won't handle new printer drivers. You also relay on printbrm if you don't like the script thing.

I'd check if it happen only with this system as MS KB list about 10 articles and most comes with post sp1 hotfix for those crash (none network related) then you'll know if it's really hardware related. I don't have another system you could the hotfixes but sometimes it only make things worse they're only lightly tested. Also ndis.sys crash debug might be the effect and not the cause => sometime poorly made network drivers come with memory leaks or there was an error and it was ndis.sys this time but might affect another driver next time. I'll also try setting bios settings to default if possible and at least those memory related.

Most scsi/sas controller makers provide tools to monitor the drives (including smart) but those doesn't display smart values if that's what you're looking for.

You need : - to comment the line RunMeWithCScript() - to comment all lines with wscript.echo (unless you want popup for each line). - to launch the script with wscript.exe instead of cscript if you're launching it from another script.

And i am pretty sure that most of us here never even tried to manually download more than 50 Microsoft patchs as there are now a lot of ways to get them downloaded by scripts or apps.

Most of those aren't usually in a service pack so the name "Unofficial XP SP4" might not be the right choice. Also i totally agree with Yzöwl : i wouldn't install an official SP if i don't have all the source to create it (you could create a script or an app which would download then integrate on a source XP or install on live XP) and for each step the possibility to oversee what the script or app is doing and have the KB links for each downloaded patch.

Are you trying to boot from san or ethernet (so iscsi) ?

You could try vga mode to see if it's really video related.

(ECHO ThisServicePackBuild = 1)>> update.txt or (ECHO ThisServicePackBuild = 1)1>> update.txt will work.

In this case, it might be an overheating component (like southbridge and northbridge) on the mainboard.

Might be memory or video card issue.

Also WIN386.SWP is the swap file for win9x and has nothing to do in XP.

If the loopback interface stil work, you'll know that the tcp/ip stack is working.

I would format anyway as you can't know for sure if you didn't missed something else when there are many virus/trojans. Did you checked if the loopback was still working (ping 127.0.0.1) ? Also, the error message you get is usually related to .net framework so may be removing it or reinstalling it might solve the problem.