cluberti

The only limitation, per se, is that it'll detect you're running SBS and limit you to port 80 (no SSL). If you've got a small number of seats that will hit the SBS server, it should be fine there. However, with 70+ clients (the upper end of SBS), it can create some disk I/O and CPU load via the SQL server when clients are requesting updates, or the server is checking for updates from Microsoft.

Actually, no - things stay enabled, but you have to use their associated icons or control panel entry points to configure them - security center is just the one-stop shop. I'll post the reg hacks here for disabling each component (I don't recommend it, but if you have a reason to do so, here's the poison): Windows Registry Editor Version 5.00 ;Disable Information Bar Prompt in Internet Explorer [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\InformationBar] "FirstTime"=dword:00000000 ;Disable Antivirus Monitoring [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "AntiVirusOverride"=dword:00000001 ;Disable Windows Firewall Monitoring [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "FirewallOverride"=dword:00000001 ;Disable Anti-virus Notifications [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "AntiVirusDisableNotify"=dword:00000001 ;Disable Firewall Notifications [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "FirewallDisableNotify"=dword:00000001 ;Disable Windows Firewall [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\WindowsFirewall\StandardProfile] "EnableFirewall"=dword:00000000 [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\WindowsFirewall\DomainProfile] "EnableFirewall"=dword:00000000 ;Disable Automatic Updates Notifications [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center] "UpdatesDisableNotify"=dword:00000001 ;Disable Automatic Updates [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU] "NoAutoUpdate"=dword:00000001 ;Disable Security Center Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc] "Start"=dword:00000004

Watch out for the first index build - it can take a very long time if you've got lots of data to index.

Since Vista technically RTMs tomorrow, expect driver updates for lots of hardware to release in the (very) near future.

That is correct, fax and scan is only on Business, Enterprise, and Ultimate. As far as a 3rd party fax app, I'm not sure any free ones exist yet, but there are some non-free ones out there that a quick google search turned up.

Can you telnet to port 21 from the other side of the router (testing the port 21 publishing rule)? Most ISPs block port 21 inbound so people don't run rogue FTP servers. You could also try configuring it on a different port to see if that works as well.

I've also seen this caused by startup programs - and autoruns (disabling all non-Microsoft items) resolved the issue. I forget which app caused it, but I do remember this on an AMD x64 chip back under XP Pro SP2, and I do remember playing the pin-the-tail-on-the-donkey game of re-enabling things a few at a time until I found the culprit. I haven't had the problem since, and I've since upgraded the box to Vista, which also doesn't have the problem.

Well, considering Windows sets the display based on the display driver's defaults, I'd say the display driver either a. did not get installed properly, or b. has a setting less than 800x600 as it's default - any time XP senses the display is less than 800x600 and the user didn't explicitly set it, you'll get that message.

It's a shot in the dark, but can you check this: http://blogs.technet.com/askperf/archive/2...at-startup.aspx

You could try to recover the old file data via a file restoration program like OnTrack's, but if the file itself is still on disk and not corrupt, I'm not sure what else can be done. Without a decent backup, you may be SOL (and might want to consider using an email provider that at least provides IMAP access).

Well, using Process Monitor should tell you if it's a reg key or file, and which one(s).

Well, using Process Monitor should tell you if it's a reg key or file, and which one(s).

While good info, this should be located in the "Networks and the Internet" portion of the boards.

1) yes - look up the DetachedProgram section of winnt.sif 2) it has to be scripted, but yes - you can use the "label.exe" command to do it.

What exactly are you looking for assistance on? Are you looking for help creating the xml, or something else?

No problem - what you want to do is a fairly common request, and that's the way I would suggest it be done (via WMI Win32_OperatingSystem).

Well, there's no winnt.sif switch to change it (only switch between Lego and Classic), and the switch is a BagMRU setting, so it'll change machine to machine. Your best bet is to create a user profile that is the way you want it, theme and all, and copy that ntuser.dat to $OEM$\$1\$DOCS\Default User\ on your CD so it becomes the default user profile.

I'd say yes .

That hex code means "access denied", so you might want to monitor with Process Monitor from sysinternals to see what you're getting "Access Denied" to.

Basically, yes, multiple policies in an OU for users - otherwise, you'll have to do loopback mode (and I certainly don't suggest that on DCs). Take a look at these technet articles (if you haven't already) on how it might work: http://technet2.microsoft.com/WindowsServe...8b31471033.mspx http://technet2.microsoft.com/WindowsServe...514b171033.mspx

Since the card's encryption capabilities are specified by the OS as to what the driver tells the kernel it's capable of, I'd say get a driver that supports it, or write your own. Otherwise, no, there's not.

I'm guessing all of the file accesses will be via searchindexer.exe or system accesses to the pagefile - the former means the index is likely too large to fit into available RAM (and gets swapped out - very bad for the indexer ), or system accesses to the pagefile means driver issue.

I second the registry change method, as I've seen this type of thing happen before. The OS is convinced it needs that space due to RAM constraints on boot, so it's likely you've got a startup application, service, or driver that is making an allocation request for a large amount of contiguous process space, and so right off of the bat Windows is "sure" that you'll need the pagefile if this app is going to use that process space. If you set it via the registry, it should take your changes on the next boot and stick with them.

You could do a mixture of security and WMI filtering (security to apply only to those users, and WMI filtering to only apply a specific GPO if the machine is running Server 2003, for instance). It'd require multiple GPOs per user that way, but it does work.

This is what I used to do in a previous life. Install NT4 on generic Intel Dell hardware, install SP6 and IE6 IEAK, any updates that were left, and then image it via ghost. Once the image was down on a new machine, ghostwalker was then run to change the SID and a script changed the machine name before booting into NT and scripting app installs.