cluberti

The error code 0x80004005 means access denied, so it obviously failed due to security permissions on those users account objects in AD. Were you using a domain admin account, and did you do a full forest and domain prep (domainprep for each domain tree in the forest too) when you first installed Exchange?

Hey, you said domain, not what kind - and as for NT4-functionality, yes, you lose the Group Policy aspect, but you can still use policies and logon scripts (oh, and Group Policy settings are almost all registry settings anyway). There's a price with a free solution, but hey, it's free .

I'm not aware of anything open-source that would run on Exchange to do this. GFI ME is a great product, but if you're already running Linux pretty heavily, I'd say stick some tools on a few of those and use them as antispam relays.

I prefer S3, but here's some info on what each does so you can decide which is best for your system: http://en.wikipedia.org/wiki/ACPI

Note that, in XP, removable drives do not support autorun at all. AutoPLAY works (that little menu you always see, asking you what to do), but autoRUN will not work - it's actually coded not to work, for a few different reasons (one being it's being emulated similar to a SCSI bus, and there are some security concerns there, etc). I'm not the developer, so I don't know all of the reasons why, but I do know for sure that this won't work from a removable device like that.

Do you mean you have to stop the DNS service and restart on the server, or is DNS resolution not working? Also, do any of your clients or servers have a DNS server or servers configured in their TCP properties that is outside of your domain?

The built-in Exchange 2003 IMF is not smart enough to be able to do this, but there are 3rd party utilities (and non-Exchange utilities) that can do this as well (and I'm speaking of things like a sendmail mail relay running spamassassin/mimedefang/antivirus to do this sort of thing, to keep the load off of your Exchange FE/BE or SMTP gateway servers).

I'm sure there are third party utilities that can do this, but you can also enable auditing in Group Policy to do this as well, logging into the event log.

No, workstation OSes lack the necessary components to handle domain traffic. However, you can emulate a Windows domain with Samba on *nix, so if you have a spare PC lying around, you could always give that a try (and although not as easy as a Windows OS as far as the learning curve will go, it's definitely cheaper ).

This tool is actually pretty easy to use without reading the destructions if you already understand NTFS permissions. It even allows you to do some things you can't do otherwise in the GUI of Windows (like pushing a permission down a tree or a set of folders in a tree, or removing a permission from a tree or a set of folders in a tree, without touching any other permissions at all - the main reason I purchased). Try the 30-day trial if you're seriously considering it, to see if it's something you'll find a regular use for.

You can run sysprep multiple times on the same image, with the following exceptions: You should not sysprep OEM media, you should only be running sysprep on volume or retail media. The activation period (for XP/2003) can only be reset three times by sysprep, after that the activation period cannot be reset. There have been times using Windows XP and Windows 2000 where after sysprep'ing an image 4 or 5 times the hardware detect portion of mini setup would start to fail, but I was never able to pinpoint the issue. After that, when I was still using sysprep, I would use a VM that allowed checkpoints and I'd always go back to the last checkpoint before running sysprep, and the issue never recurred.

I'd say it's a DNS problem, but can you provide the headers (sanitized, if necessary) of one of your failed messages? Also, check the DNS settings on your Exchange server, and make sure they're pointing to a working DNS resolver!

I personally use Security Explorer to backup/restore/change permissions, because (as you've found out) they don't survive a reinstall of the OS. http://www.scriptlogic.com/products/securityexplorer/

Yes. Check your PM for information on where to get my netboot .iso.

Do you have very current A/V on the system, not just antispyware? If not, you should read the following (hint: dcomcfg is a trojan, trying to hide as the legitimate dcomcnfg application): http://fileinfo.prevx.com/QQ875017050067-D...COMCFG.EXE.html

Fair enough. You do then run into the problem of either a ) using a linux boot disk or CD to boot the OS to get around the DOS network memory issue, or b ) work around the DOS networking memory considerations. You should be able to make b work (I've done this many times), but you also need to make sure that your IDE or SATA chipset drivers are integrated into the installation source, as you won't have any opportunities to use F6 to provide them. I think there are likely two issues here, and both are important and need to be addressed .

Any reason that you are not using RIS to do these network installs?

The problem is that, in a native mode 2000 or 2003 domain, NTLM v2 should not fail - so the problem isn't the 537's, necessarily, but they are the visible indications of a bigger machine or user account auth problem on the domain.

You're likely going to have to download and monitor your machine with process explorer (or install the debugging tools for Windows and get an adplus -hang dump of the svchost.exe PID that is causing the issue, when it's happening). Otherwise, we're all just doing educated guessing.

Apparently this is what the user wants. Not vice-versa.

I wouldn't think that you'd have profile corruption per se (temp files, favorites, desktop, etc), but, depending on where the user's files are located, file versioning issues such as saving a file in one location, then going back and saving a different copy from another location, etc. You could always create mandatory profiles (profile.man rather than profile.dat), which would help alleviate the profile versioning issues, but the file versioning issues will ultimately be up to the user.

Try this, then (if you're a good debugger) analyze the resulting .dmp file(s): 1. Install the "Debugging Tools for Windows" from http://www.microsoft.com/whdc/devtools/deb...installx86.mspx 2. Create a directory called c:\adplus 3. Open Internet Explorer, but do nothing else with it - no browsing, etc 4. 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" 5. Type the following command in the command prompt: cscript adplus.vbs -crash -pn iexplore.exe -o c:\adplus 6. Do not interfere with the debugger (cdb.exe) window that is opened, just let it run minimized 7. Recreate the crash, and when the crash occurs, you should get a .dmp file in C:\adplus. Either run windbg or cdb against the file to determine what happened, or PM me and I'll give you an FTP to upload the .dmp file to for analysis.

This is for RIS, but could be easily modified for CD or network-based installs. Since the directory exists, run it from something like cmdlines.txt or from SetupParams via a "UserExecute=" from Winnt.sif. ' // ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ' // Set variables for script ' // Set objShell = CreateObject("WSCript.shell") Const HKEY_LOCAL_MACHINE = &H80000002 strComputer = "." Set objReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _ strComputer & "\root\default:StdRegProv") strKeyPath = "SOFTWARE\Microsoft\Windows\CurrentVersion\Setup" objReg.CreateKey HKEY_LOCAL_MACHINE,strKeyPath Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colChassis = objWMIService.ExecQuery _ ("Select * from Win32_SystemEnclosure") ' // ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ' // Determine machine hardware and copy i386 for laptops ' // For Each objChassis in colChassis For Each strChassisType in objChassis.ChassisTypes Select Case strChassisType Case 1 strEntryName = "MACHINETYPE" strValue = "Other" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 2 strEntryName = "MACHINETYPE" strValue = "Unknown" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 3 strEntryName = "MACHINETYPE" strValue = "Desktop" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 4 strEntryName = "MACHINETYPE" strValue = "Low_Profile_Desktop" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 5 strEntryName = "MACHINETYPE" strValue = "Pizza_Box" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 6 strEntryName = "MACHINETYPE" strValue = "Mini_Tower" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 7 strEntryName = "MACHINETYPE" strValue = "Tower" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 8 strEntryName = "MACHINETYPE" strValue = "Portable" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 9 strEntryName = "MACHINETYPE" strValue = "Laptop" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 10 strEntryName = "MACHINETYPE" strValue = "Notebook" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 11 strEntryName = "MACHINETYPE" strValue = "Handheld" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 12 strEntryName = "MACHINETYPE" strValue = "Docking_Station" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 13 strEntryName = "MACHINETYPE" strValue = "All-in-One" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 14 strEntryName = "MACHINETYPE" strValue = "Sub-Notebook" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" Case 15 strEntryName = "MACHINETYPE" strValue = "Space_Saving" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 16 strEntryName = "MACHINETYPE" strValue = "Lunch_Box" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 17 strEntryName = "MACHINETYPE" strValue = "Main_System_Chassis" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 18 strEntryName = "MACHINETYPE" strValue = "Expansion_Chassis" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 19 strEntryName = "MACHINETYPE" strValue = "Sub-Chassis" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 20 strEntryName = "MACHINETYPE" strValue = "Bus_Expansion_Chassis" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 21 strEntryName = "MACHINETYPE" strValue = "Peripheral_Chassis" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 22 strEntryName = "MACHINETYPE" strValue = "Storage_Chassis" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 23 strEntryName = "MACHINETYPE" strValue = "Rack_Mount_Chassis" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case 24 strEntryName = "MACHINETYPE" strValue = "Sealed-Case_PC" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue Case Else strEntryName = "MACHINETYPE" strValue = "Unknown" objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strEntryName,strValue objShell.Run "robocopy \\RISserver\REMINST\full_source_xpsp2 %systemdrive%\i386 /E" End Select Next Next

Cool - never use a Symatec suite again - SAV is fine (within reason), but the rest of their products save Symantec Ghost are utter crap.

Since most antivirus packages (Symantec/Norton A/V included) use Explorer shell extensions, and since you're using Explorer to search, and because your A/V uninstall was botched, I'd say that the search and explorer issues are related to the A/V uninstall. You'll probably have to call Symantec to get it resolved (they usually have manual removal instructions for just such an occasion).