cluberti

The Symantec System Center console that ships with the 32bit version can talk to x64 versions, as far as I'm aware. You shouldn't have to modify that - only install the x64 version. What does Symantec say about this?

Saw similar post in NT/2000/2003 forum, so I'll post the same response here: A machine check error is an error in the processor that is detected by the OS and is correctable (if it wasn't, your machine would bugcheck/bluescreen). This usually signifies that your processor may need to be repaired/replaced (hopefully under warranty), as these are hardware errors happening in the processor. Since these only occur when running x64 versions of Windows, it would stand to reason that these errors are occurring in one of the additional registers addressable only by 64bit software. You can disable this error on Server 2003, but since it is a serious error, you should try to replace that hardware under warranty while you still can. 912310: How to disable the corrected machine check on a Microsoft Windows Server 2003-based computer http://support.microsoft.com/default.aspx?...kb;EN-US;912310

A machine check error is an error in the processor that is detected by the OS and is correctable (if it wasn't, your machine would bugcheck/bluescreen). This usually signifies that your processor may need to be repaired/replaced (hopefully under warranty), as these are hardware errors happening in the processor. Since these only occur when running x64 versions of Windows, it would stand to reason that these errors are occurring in one of the additional registers addressable only by 64bit software. You can disable this error on Server 2003, but since it is a serious error, you should try to replace that hardware under warranty while you still can. 912310: How to disable the corrected machine check on a Microsoft Windows Server 2003-based computer http://support.microsoft.com/default.aspx?...kb;EN-US;912310

No, there is no emulator - the problem is that x64 doesn't allow 32bit file system filter drivers. However, Symantec does have an x64 version of Symantec Antivirus 10.0. You'll need to get that from Symantec and install on x64 if you want Symantec Antivirus on your x64 machines.

Is this a domain or workgroup environment?

Are you setting DENY rights in NTFS, or just removing ALLOW permissions?

dcomcnfg is the Component manager. You can modify DCOM permissions there.

Windows Vista x64 and future client versions of the OS (Vista will more than likely be the last 32bit client OS released by Microsoft) will not have support for 16bit code at all. Note that this will not be new - Windows XP x64 does not support 16bit code either.

Microsoft doesn't make drivers. We include drivers for lots of common devices on the Windows CD, but only if the VENDOR supplies them. 1. The hardware vendor must supply drivers to Microsoft for inclusion on the Windows CD 2. The driver must meet WHQL certification to be put on the CD Since 3Com doesn't make 64bit drivers for the hardware, Microsoft cannot provide them on the CD. Unfortunately for you, you'll need to buy a NIC with a newer chipset to get x64 support. I strongly recommend Intel 10/100(/1000) PCI NICs.

Yes - you need to image the disk, not just the partition. If you only image a partition, you don't clone the MBR, and thus results in the problem you are seeing. If you can, boot to the Windows 2000 CD and open the recovery console. Run the fixboot and fixmbr commands and reboot. All should be fixed once you've done that.

Your post is so vague, we can't help you yet. Perhaps post the steps you took to produce the error, and a screenshot of the error itself?

Do you perchance have any APC PowerChute software installed?

Also, try downloading autoruns from www.sysinternals.com and you should be able to disable it (and any other application or service that starts with your PC).

Also, what applications are you trying to install - are they Windows installer packages that start after running setup.exe? If so, have you tried running "sfc /scannow" and then "msiexec /regserver" at the command prompt?

You're surprised that a chipset released 10 years ago doesn't have x64 drivers?

Are you seeing the Windows Update web site pop up, the Security Center GUI for enabling Windows Update, or the system tray icon letting you know that you need to configure Automatic Updates or that updates are available?

This data is incredibly hard for me to parse, and it's not what I was expecting. On one of the Windows 2000 Servers that is experiencing this issue, please do the following - do not modify these instructions. Failure to follow them properly will result in more data I can not help you with: 1. I need you to download the poolmon2vbs.zip file from the FTP site, and extract it to C:\POOLMON. - Double click C:\POOLMON\EnableRightCtrlScrollScroll.reg - Verify that "Write Debugging Information" is currently set for a "Complete Memory Dump", under Control Panel, System, System Properties, Advanced tab, Startup and Recovery. - Double click C:\POOLMON\EnablePoolTagging.cmd 2. I need you to configure the machine to gather a COMPLETE memory dump the next time the server hangs. - Right-Click My Computer and select Properties. Go to the Advanced TAB and click Performance Options. Click Change under Virtual Memory. Set the page file on the partition where the OS is installed to be equal to Physical RAM + 50 MB. - Create or modify the following registry value: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters Value: CrashOnCtrlScroll Type: REG_DWORD Data: 1 Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl Value: CrashDumpEnabled Type: REG_DWORD Data: 1 *** REBOOT *** 3. Start gathering the poolmon data: - Double click C:\POOLMON\LogPool.CMD, and press any key when prompted to start poolmon data gathering. - DO NOT CLOSE THE COMMAND PROMPT OR LOG OFF - THIS WILL STOP THE DATA GATHERING. 4. I then need you to download the perfwiz.exe file located here: http://www.microsoft.com/downloads/details...&displaylang=en - Double click on PerfWiz.exe and click "Next" - For "Monitoring Computer:" enter the machine name that you are monitoring from, and click "Next" - Select "Create New Log" and click "Next" - Choose the "Standard Perfmon log" radio button and click "Next" - For the "Target Computer" enter the machine name again - For the "Log Name:", please name it using the name of the computer being monitored. Set "Log file size" to 250MB, then click "Next" - Under "What is the average elapsed time for the issue to occur?" set the "Average Time to issue" to 1 hour and click "Next". - click "Start" button on the "Start, Stop or Delete Performance Log" window then click "Next", then "Finish". 5. The next time the server hangs, please hold down the right-hand CTRL key, then press the SCROLL LOCK key twice. This will cause the server to bugcheck and restart. 6. When the server reboots, please zip up the C:\POOLMON directory, the C:\PerfLogs directory, and the C:\WINNT\memory.dmp file. Upload all three .zip files to the FTP site, then let me know when this is complete. If you have any questions regarding these steps, please let me know.

http://www.microsoft.com/downloads/details...ang=en#filelist and http://technet2.microsoft.com/WindowsServe...b7c1341033.mspx

When it's frozen, can you ping the machine from another machine? Also, if you press the numlock key, does the numlock light go on and off?

What DC is your RUS configuration looking for? If it points to a DC it can't find or is offline, you will get this exact behavior.

Is this an install using an nLite'd CD, or is it a retail XP CD? Also, have you integrated any drivers, software, or patches into the installation sequence?

In general it's not good practice to make any changes to the top level domain policy, so you're smart in not doing so. I second (or is that third?) the suggestion of creating an OU (or multiple OUs) to contain computer objects, and apply Computer GPO settings to that OU or that set of OUs.

These events with that return value (87) indicate that they're coming from the SNMP service, and if this is a Compaq, it's a known issue with the management software in certain situations. If so, you will need to upgrade the management software to the latest supported version for your OS, or remove it altogether (if you choose this option, you need to remove and reinstall SNMP if you still need to use the SNMP service).

If all of the DC's are at one site, then you won't get any AD site-specific benefits, but you can still configure each site with a class C and set that class C up as a site in AD Sites and Services if it will make life easier for you. Your users will still be going back to the central office to log in, check security tokens, etc., but if it's management that's the issue there shouldn't be a problem setting up 40 sites in AD Sites and Services.

To configure the default option in the Windows XP shutdown dialog box to be "Shutdown", configure the following registry value: Key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer Value: Shutdown Setting Type: REG_DWORD Radix: Hex Data: 00000002 ---------- Possible values for Shutdown Setting: 00000001 = Log Off 00000002 = Shut Down 00000004 = Restart 00000010 = Stand By 00000020 = Stand By (with wakeup events disabled) 00000040 = Hibernate 00000080 = Disconnect (only available in Terminal Services sessions) You will need to apply this registry setting every time the user logs on. This is due to the fact that if the user changes this value to something other than Shutdown, Windows will continue to remember this changed value. This registry change will need to be applied every time the user logs on to make certain that "Shutdown" is the default value for each user.