nmX.Memnoch

You're lucky they did anything at all with only one dead pixel. Most LCD manufacturers only warranty the screen for six or more.

Unfortunately since it's a laptop reformatting is really your only option. Even if there was a folder you could put the driver in on the hard drive, the boot process would never get far enough in order to detect the hardware and load the drive. Your machine is actually blue screening with an error stating that it can't find a valid boot drive. You're not seeing this because WinXP is set to automatically reboot on BSOD by default. If you want to see the error press F8 while the system is booting and choose the "Disable restart on error" option from the menu.

If you're talking about for the DST changes then you'll have to install the patch on each workstation as well. The workstations do sync time with the domain controllers, but they use their local time zone settings.

It's hard to tell from the pictures but this one supposedly has the AUX connector: http://www.newegg.com/Product/Product.asp?...N82E16817159047 This is for the PII/PIII Xeon board right?

I'm not sure about the DHCP part, but Windows Clustering will work for AD Domain Controllers. The only caveat is that if one node in a cluster is a DC, then all nodes have to be DCs. If you're only doing a two-node cluster then you can use SCSI/SAS for the shared drives, but I would recommend just going with fiber channel. Dell has some nice entry-level SANs and iSCSI stuff that would work. Dell/EMC CX3-10c (4Gb/s Fiber Channel SAN/iSCSI, up to 4 nodes) http://www.dell.com/content/products/produ...;l=en&s=biz Dell PowerVault MD3000 (3Gb/s SAS, 2 nodes) http://www.dell.com/content/products/produ...;l=en&s=biz Edit: I forgot to mention the Dell/DMC AX150/AX150i. It's a lower cost fiber channel alternative than the CX3 series: http://www.dell.com/content/products/produ...;l=en&s=biz

I have to throw out a recommendation for SiteKiosk. We've had a public access machine setup at work for about 2 years now running SiteKiosk. There hasn't been one single issue, security or otherwise, with that machine.

From the other thread you have going: In other words, it may not even be possible. Again, my suggestion would be that either they set it before they leave, set it through OWA or not have it set at all. For starters, the application probably doesn't "require" admin privs to work properly. With a little work you can find the areas of the system that the application needs access to. Then give 'Users' the minimum level of access required for the application to work. There are an astonishing number of applications that claim to require admin privs to work when they simply need write access into a directory that 'Users' only have read access to by default. This is the application developer's fault, not Windows. Most times the access is only required for temp files (which should've been coded to write to %TEMP%) or for configuration files (which should've gone to %APPDATA%). We've had to do this with several of our applications. The Administrators group on all of our workstations is locked down through a GPO. What can one person do? Make yourself known. The security of the network is your job. If there's a security related incident, who do they come to or point fingers at? You. Take some time with those applications. Run FileMon, RegMon or just full on Process Mon. Use those utilities to find out where the application requires privileges. Make a few changes on a test workstation and then try running the application in the 'User' context instead of 'Admin' context. When you get it right, make a GPO that enforces the security permissions for the locations the application needs (that way you don't have to go to each workstation to make the change). Yes, it takes some extra work but you'll have a more secure environment. The users will initially be mad but they'll get used to it. And I guarantee that any problems you're having with them installing unauthorized applications (WebShots anyone?) will stop.

In your environment you have absolutely NO accountability. A user can just say "Well the admins know my password, they must've done it" and there's nothing you can say to refute that. Encryption is something to use on top of a properly secured network.

Admittedly I'm not an Exchange Server Admin...but it's not that hard to find documentation. http://technet.microsoft.com/en-us/library/aa997477.aspx

FrozenCPU used to carry them. Directron.com still carries some.

What's your motherboard model? Some older PII/PIII Xeon boards (particular dual PII/PIII Xeon boards) were limited in the amount of RAM they supported. Also, from the sounds of your post you have a bunch of different types/sizes of DIMMs installed right now...that can be bad too.

That's the correct answer. Your AD FQDN should never be the same as a valid DNS name on the internet. The Exchange "problem" is fixed by creating pointers in your internal DNS.

They're not my policies. I work for the US Air Force. Doing anything as another use is illegal. It's also unethical. Not to mention that it's about to become largely impossible since we are moving to SmartCard logon...no more passwords. You have to physically have the SmartCard and their PIN to logon as that user. The fact that you and your coworker have your users' passwords, memorized no less, is completely wrong. You're an admin...why do you need their password(s)? I assume that you're running Exchange for the email. Why can't you just use Exchange Admin to set the OOA for a given mailbox? For that matter...they can set it themselves if you have OWA running. Remember the SmartCards I mentioned? No need for PGP with those either...digital signature and encrypted email using a certificate on the card.

Also make sure that you have both WPA2 updates installed: http://www.microsoft.com/downloads/details...;DisplayLang=en http://www.microsoft.com/downloads/details...;DisplayLang=en 893357 adds WPA2 support to WinXP and 917021 updates WPA2 support.

You might want to rethink that bit as well since it's an older laptop.

I have a better idea... Train the users to remember to set their own away messages before they leave. We have a policy that we WILL NOT (and actually in our environment, legally can not) do this for a user.

The latest official Catalyst drivers on the ATI/AMD site are 6.2. http://ati.amd.com/support/drivers/2k/radeonx-2k.html

Except that it won't work if those services are disabled. I'm not sure about Remote Access Auto Connection Manager, but I know the other two have to be at least Manual/Started (that's the default for them).

Replacing a bad motherboard is not considered a "new PC". It may put Windows Activation "Out Of Tolerance" and require to you reactivate though.

Every laptop I looked at had a price increase going from a Core Duo to a Core 2 Duo of the same clock speed. Printers are having problems with Vista because the printer manufacturers are being lazy and/or greedy. What do I mean by greedy? Take a look at this HP page for the statement about drivers for a Photosmart 1000: http://h10025.www1.hp.com/ewfrf/wc/documen...872〈=en Pretty much ALL printer drivers need to be re-written. The reason is because Vista no longer allows kernel-mode drivers. This was changed for the stability of the system. A bad kernel-mode printer driver could take a system down in a heartbeat...not a good thing when you're running a large print server. So now Vista (and Longhorn Server) only allow user-mode drivers. Basically this means if it's a bad driver then that piece of hardware, and only that piece of hardware, will stop working instead of taking the entire operating system with it.

They're still making Core Duo's for laptops. Or at least you can still by laptops with them as a cheaper alternative.

Just keep in mind that if you go with an Intel solution and get a motherboard based in the P965 chipset that you'll only get one PATA port (two devices). And that one PATA port will be provided by a 3rd part solution. The southbridge (ICH8/ICH8R) for the P965 doesn't have PATA features built in anymore. Asus uses JMicron for that. It looks like Gigabyte is using their own solution. If you're going to stick with your PATA drive then it'd probably a good idea to get a PATA-to-SATA converter and save the PATA connection for your optical drive(s).

Have you tried it? It's not nearly as bad as people are making it out to be. Most of those same people said the same exact things when XP was released.Really, the only thing you need to make sure of is that drivers are available for all of your hardware. There may be a few software compatibility issues as well...but it's not nearly as bad as some people make it sound. Core Duo's are 32-bit only.

It's documented (here, here, here, and here). It will not work on a default install of any Windows version.

Yeah, that's basically overclocking the chipset. However, most OEM BIOS's don't offer any FSB or memory adjustment features. Those are reserved for enthusiast systems. A guy in the office next to mine put a P4 2.6/800 Northwood CPU in a system that only supported a 400MHz FSB...then came and asked me why the CPU was only running at 1.3GHz! It took me about a half second to realize that it was running at half speed because the FSB was running at half the CPUs rated speed (but full speed for the chipset).