cluberti

Everybody calm down, you don't have to reinstall Windows just yet. Download autoruns (from www.sysinternals.com) and ShellExView (from www.nirsoft.net) - use autoruns to disable all non-Microsoft items, and use ShellExView to disable all non-Microsoft extensions and hooks to explorer.exe. Once you've done both, restart your machine and see if the problem occurs (if it was a software install/uninstall that caused it, you should be working properly at this point). You can either leave the system as-is, or re-enable things until the problem recurs to determine the culprit. If autoruns/shellexview don't work, I'd give that box a good scan with up-to-date antivirus and antispyware software in safe mode, and if that fails THEN I would suggest reinstallation of the OS.

Why give them elevated rights, when you could simply modify the permissions on the machine to the locations the application needs? Have you tried creating a shim via the Application Compatibility toolkit for this application as well? http://www.microsoft.com/technet/prodtechn...ty/default.mspx

Yeah, that'll break it for any domain.

It's been a long while for me as well, but if I remember correctly you go to Control Panel > Network > Identification tab > Change button. I remember Computer Description being a field in here. However, whether or not this will show up in Network Neighborhood depends on whether or not you're using a WINS server, and if the workstation can contact the PDC emulator.

I doubt that not having Crossfire in their driver set until RTM will "kill" them, and considering that ATI's FireGL product is going to run on Vista, I think it will be safe to expect OpenGL support for ATI products in Vista at launch.

Usually you get this error when the RIS server's BINLSVC is attempting to connect to the Active Directory via the DS service running on a domain controller. Were there any AD changes made around the time this started happening, is DNS misconfigured or working improperly on the RIS server, etc. ? Either the RIS server can no longer bind to a domain controller to get RIS information from the AD, or DNS isn't functioning properly on the RIS server (or the DC).

Run filemon (from sysinternals) while you are running the script, and it should tell you both where the access denied occurs on the disk, and what user was attempting the operation.

Actually, it'll be compressed - you'll have to use the "expand" command to expand it to the destination directory, as copying may - or may not - work.

I have not been able to verify that has happened as of yet, or if it ever will (you'd think I'd know these things??? - didn't know about the sysinternals thing until the morning it happened, so...). If it ever did happen, I'd bet soon would be Longhorn server at the earliest.

Since more than 90% of AD issues are directly cause by DNS misconfiguration/resolution issues, I'd have to second fizban's suggestion to check your DNS infrastructure on all machines and make sure everything is kosher before going any further in troubleshooting.

It appears that the Inspiron 1xxx series came with an integrated Intel 915 adapter - Dell lists the A08 version (6.14.10.4609) from July listed as available, is that the one you are using? Also, you could try to get a driver for the 915GM chipset directly from Intel to see if that behaves any better than the A08 version from Dell.

I'm using perfmon, windbg, and taking sporadic memory dumps of the machine in state

It's already on the installation media, in the i386 directory, as a compressed file (wmix.dl_). You should be able to expand it to the system32 directory (and optionally register it) without anything but an XP CD.

Personally I would recommend sticking with the Linux MX SpamAssassin/MimeDefang/ClamAV setup, as it is much faster than the Exchange IMF, but to answer your question, yes, the IMF will scan mail before it hits the store as long as it's SMTP mail inbound, rather than inter-Exchange mail. I've set up more than a few companies and an enterprise or three with Exchange in the back and Debian/Sendmail up front, but you do need to know a bit about Linux in general, and Sendmail, SpamAssassin, MimeDefang, and ClamAV before jumpting into something like that. Exchange 2007's IMF seems to behave much quicker than the 2003 IMF, but that's almost completely due to the fact that the 2007 servers are on beefier hardware, and they're 64bit .

Scriptlogic's Desktop Authority product does this as well, but again, is somewhat expensive per seat in a smaller organization. It does have other scripting and configuration benefits that most admins find to be a great time (and thus cost) saver, but it's still expensive.

A few things - have you checked the NTFRS logs on all of the domain controllers to make sure everything is replicating properly and the FRS isn't broken? From the errors you're getting, it sounds lke the 2003 server isn't getting updated information from the 2000 server(s) and is using stale sysvol data, which would indicate a replication problem. Also, make sure that the Windows Server 2003 machine does not have it's firewall enabled, and if you have any IPSEC policies in place or TCP filtering, that this is either working properly on all machines or is disabled entirely until the migration is complete.

Thanks - the Exchange blog is a must for everyone who deals with Exchange. They explain things very well, and they're not boring reads either .

You could always try running the applications in DOSbox as well, as that works very well for running DOS-based apps in Windows XP and Server 2003: http://dosbox.sourceforge.net/news.php?show_news=1

I'm actually getting some reports of this from elsewhere as well, and I'm not the first to have reported it either. It appears that this is indeed an issue in certain hardware scenarios, and it's being looked into. I've also been able to narrow it down to happening only when I'm doing some specific functions that invoke a UAC prompt, or visiting sites that load certain ActiveX controls in IE. Again, still trying to narrow it down to exactly when it happens and when I can repro it 100%, but I'm getting around 80% repro now, so I'm hopefully getting close. Glad to hear this isn't widespread though.

You might want to have a look at this article on the Exchange blog: http://msexchangeteam.com/archive/2004/06/21/161564.aspx

The next question is when did this start happening, and does it also occur when running in safe mode?

If you're in an AD domain, your Windows machines will sync to the time on your DCs, but as to the crackberries you'd have to get NTP sync software. Also, if you aren't in a domain, you can get a myriad of NTP sync software for Windows that should do what you need. Windows XP and Vista also include automatic sync options that can be found in the Date and Time settings, either in the control panel or by clicking on the clock in the taskbar.

That .dll is the Windows Media Indexer .dll, and should be on any system that has Windows Media Player installed from version 9 up. Not sure why it would come up unless Winamp is attempting to utilize a function in it for some reason.

To be honest, your best bet would be to call the vendor of the server or Microsoft, depending on from whom you purchased SBS. You get at least a few free incidents from Microsoft if you purchased that retail, and if you got it from the PC vendor you can contact them and they'll use their contract with Microsoft to get you support. If you're seeing the emails in the sync errors store, and Exchange is actually working, it could very well be a database corruption issue due to the faulty shutdown. Get someone on the phone who can dedicate time to you that knows how to resolve Exchange database issues - preferrably from Microsoft Exchange support . I'm glad you posted here in the hopes we could help (and we probably can, given enough time) - but you're obviously going to be in a hurry with a downed production email server, and this may not be the best place for that kind of timeframe.