As silly as this sounds, I would suggest using an IPSEC applied via Group Policy to enforce access/non-access based on port numbers and IP's. An lesser known function of the IPSEC rules is filtering. You'll want to keep in mind the policies are NOT stateful, so make sure to test your rules. Applying the IPSEC policy via Group Policy will ensure consistent re-application (in the event someone figure out how to un-apply the settings... and in that case, pull in HR/management).
Unplug the machine, hold the power button for about 10 seconds, plug it back in. You really don't want your machine bouncing on/off during power problems. Either that or go get a cheap UPS.
Macally offers the PHR-250CC with both USB 2.0 and a pair of Firewire 400 ports. Choose any 2.5" drive, can I suggest the Hitachi E7K100 or the E7K60, and you're set. The case is just a little thicker than a deck of cards. I've had a pair of these for the past year, alot of miles on them, and no problems to report.
They released SP2 to Pro users via Windows Update later to avoid the backlash from corporations that didn't have enough time to disable the automatic update. If they WERE power users, they would've downloaded the 250Mb file the day it was released to MSDN users anyway. A "power user" using Windows Update is NOT a power user, they're a luser...
Microsoft released SP2 in a staggered fashion. First to MSDN subscribers, OEM's, Enterprise customers, etc. Second, SP2 was unleashed to XP Home Edition via Windows Update. Today, they're finally allowing XP Pro users to get the patch. It was intended to allow corporate customers the ability to disable the update to their clients.
Take a look at the NSA security guides for Windows NT, 2000, XP, and 2003. Normal users on the machine will have no ability to modify the machine if the policy is applied (especially the policies that apply to the file system.)
I've used these policies for Windows 2000 lab machines, and have no known incidents with virii/trojans/stupid user tricks/etc...
Slashdot Mirror
As silly as this sounds, I would suggest using an IPSEC applied via Group Policy to enforce access/non-access based on port numbers and IP's. An lesser known function of the IPSEC rules is filtering. You'll want to keep in mind the policies are NOT stateful, so make sure to test your rules. Applying the IPSEC policy via Group Policy will ensure consistent re-application (in the event someone figure out how to un-apply the settings... and in that case, pull in HR/management).
Unplug the machine, hold the power button for about 10 seconds, plug it back in. You really don't want your machine bouncing on/off during power problems. Either that or go get a cheap UPS.
Macally offers the PHR-250CC with both USB 2.0 and a pair of Firewire 400 ports. Choose any 2.5" drive, can I suggest the Hitachi E7K100 or the E7K60, and you're set. The case is just a little thicker than a deck of cards. I've had a pair of these for the past year, alot of miles on them, and no problems to report.
They released SP2 to Pro users via Windows Update later to avoid the backlash from corporations that didn't have enough time to disable the automatic update. If they WERE power users, they would've downloaded the 250Mb file the day it was released to MSDN users anyway. A "power user" using Windows Update is NOT a power user, they're a luser...
Microsoft released SP2 in a staggered fashion. First to MSDN subscribers, OEM's, Enterprise customers, etc. Second, SP2 was unleashed to XP Home Edition via Windows Update. Today, they're finally allowing XP Pro users to get the patch. It was intended to allow corporate customers the ability to disable the update to their clients.
Take a look at the NSA security guides for Windows NT, 2000, XP, and 2003. Normal users on the machine will have no ability to modify the machine if the policy is applied (especially the policies that apply to the file system.)
I've used these policies for Windows 2000 lab machines, and have no known incidents with virii/trojans/stupid user tricks/etc...