cluberti

Like most Microsoft products, anyone can install it, but it takes some time to get used to using it. I'd suggest visiting isaserver.org and doing some research, and maybe even purchasing Tom's book (it's very good). ISA is easy to install, not so easy to master. However, on a side, slightly OT note, take the ISA 2004 test plus the designing AD security along with your cores, and you are an MCSE + Security .

You'll need to consider WinPE to deploy your images then, as WinPE 2005 includes WMI support. You can also use BartPE, as I believe there's a hack to get most WMI working there as well.

I have to second that one - you need a proxy server, and one that can understand AD, user accounts and groups, etc. The only one I am aware of is Microsoft's ISA Server.

You don't - you add a proxy server and force all internet traffic through it. This isn't something you can do per workstation without either 3rd party software or a proxy.

How much kernel paged pool and kernel nonpaged pool memory do you have available on your Exchange server when you see this error? Remember, Windows userland knows nothing about RAM, only virtual address space - if you're getting this error, you're likely out of virtual address space in the kernel nonpaged or kernel paged pool resource pools. You can get a rough idea by running perfmon and checking the memory counters Pool Nonpaged Bytes, Pool Paged Bytes, Free System Page Table Entries, and the Private and Virtual bytes counters for the store.exe process in the Process counters. Are you using the /3GB or /PAE options in your boot.ini file on the Exchange server? If so, why?

No, you can't "go back" - once you've got SP2 on an install, you can't go back to SP1. Also, since there is no "SP2" for 2003, I'm still confused as to how you could have 2003 SP2 on a CD - it doesn't exist...

Grab a utility called spacemonger, and you'll get a good look at what is using disk space, how much, and where.

... and you'd both be wrong . Memory mapped files are not processes, and yes, they have a 1GB limitation. There is not a public KB article on this, but I believe if you are an MS Partner there is an article describing this. Edit: I knew this existed. There is a technet article which backs me up on this, that is public: http://technet2.microsoft.com/WindowsServe...3.mspx?mfr=true The salient bits for those who don't want to read the whole article:

It doesn't - I can vouch for that .

I guess the next question is, what ATI hardware are we talking about, and what driver version are you using?

Why would you be installing 2003 SP1 on a WinXP SP2 install? Perhaps I misunderstood, but that's what it sounds like you are attempting, and it will not work.

Hm - ATI drivers are usually quite amenable to the flat file structure for RIS. You usually only need the actual subfolder that contains the driver files in your PNP drivers path. You could use a utility to change the resolution post-mortem, I guess .

I'd say your best option is #2, but make sure that you create these machines in their own OU when you first build them. This will make it easier to block policy inheritance with an empty GPO so they don't get policies applied while on the domain, and will also make purging the accounts much easier if they don't get removed properly when your script removes the machine from the domain (use the netdom.exe tool to remove from the domain, if you can).

You can download userdump from http://www.microsoft.com/downloads, and configure it to watch for all exceptions and then dump winmgmt.exe on process termination. That will allow you to get dumps of the process, even if it isn't currently running - something adplus is not able to do.

Yeah, it is a bit sad, but it is simply an architectural limitation of the 32bit platform.

What does the scr.bat file do, and does it need interactive access to the desktop? Remember that things run as startup or shutdown scripts run under the local system account, non-interactively. It would help to know what this file does and where it is located on your machine.

That error is ALWAYS caused by spyware or malware on your PC. Boot into safe mode, then start the cleanup with an antispyware program or three (like Windows Defender, Spybot, AdAware, etc), make sure you run an antivirus scan against the machine with current definitions from your antivirus vendor, and restart. IE will work fine afterwards once the machine is clean.

I'd still say that using filemon in this case is the best way to determine what process(es) seem to be actually writing or reading from disk, and then the determination can be made from there how to minimize or eliminate it (great suggestions all, by the way ).

Because there's a limitation on memory-mapped processes, drivers, and files in 32bit windows - any memory mapped process, driver, or file can only contain up to 1GB in space, no exceptions. Since the event logging .dll is running in the SharedProcess kernel address space (which is memory-mapped), the total size of all of the other things running in that SharedProcess space (services memory, desktop heap, POSIX/OS2 subsystem, etc) will add up to the other 500MB or so. By the way, the recommendation for ANY event log on the system is 100MB, especially security. Long post short - expected behavior.

Unless you're actually using WMI to gather data about the machine, or to perform functions like application installation and management (SMS), you do not need it running in a home-user environment.

Well, part of the reason is that the ultimate installation package inside this update is actually a Macromedia package, not a Microsoft package. Integrating this will likely be completely manual, as this file is a non-Microsoft package (just run the .exe with the "/t:<path> /c" switches, and check the resulting .exe's properties - it's a Macromedia package, signed by Macromedia themselves).

Have you run filemon on your system (from http://www.sysinternals.com) to see what is causing the activity? Usually this type of disk activity is caused by antivirus, for reference - for every one disk read or write, you get at least 4 or 5 passes on that I/O from the Antivirus (sometimes more, depending on the vendor). This might not seem like a lot, but fire up filemon sometime and just watch your A/V at work .

Hiding the contents of your script can be done once your vbscript is complete via the Microsoft Script Encoder: http://www.microsoft.com/downloads/details...&displaylang=en As to using runas in the script, the following simple 4 lines will work: set WshShell = CreateObject("WScript.Shell") WshShell.Run "runas /user:User ""C:\runsomething.cmd""" WScript.Sleep 100 WshShell.Sendkeys "password" It can be done much cleaner, but the above is an easy 4 lines, and it's a start.

You do need a license, virtual server or physical hardware, and you won't find any trial downloads from Microsoft for any 2000 OS. If you've got an MSDN subscription you can always use a version from that kit, if you've got a premier support contract with Microsoft you can always pop the question to your account manager, and if you're like most people without either you can grab a quick copy from most online vendors. My personal favorite is buycheapsoftware.com, but any vendor you trust will do: http://buycheapsoftware.com/ms_products~subcategory~19.asp And the only real differences between 2000 Standard and Advanced is the amount of memory they support, clustering capabilities, and network load balancing capabilities. If you don't need access to more than 4GB of RAM or an NLB or cluster, you don't need Advanced Server.

First, install the "Debugging Tools for Windows" from: http://www.microsoft.com/whdc/devtools/deb...installx86.mspx Once these tools are installed, do the following: 1. Create a directory called c:\adplus 2. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is "C:\Program Files\Debugging Tools for Windows" 3. Check the task manager and make sure that winmgmt.exe is running. 4. Type the following command in the command prompt: cscript adplus.vbs -crash -pn winmgmt.exe -o c:\adplus The next time winmgmt.exe crashes, you should get at least one (maybe many) *.dmp files in the C:\adplus folder. These can be debugged to tell you why winmgmt.exe is crashing.