Well, this one's a doozy. I have three separate GPOs on Server 2003 R2 Standard, intended to perform an uninstall, clean, and installation of the new version of an application.
GPO 1 is the original policy that pushed out the application, which consists of several MSI files. To perform the uninstallation, I simply removed them from the policy and instructed it to uninstall from all applicable clients.
GPO 2 is a script to manually uninstall any other lingering versions of the application using "msiexec application.msi /uninstall", or whatever variant it is. There are numerous versions that may have been installed and may be in use throughout our organization, so I've gotta get rid of them too.
GPO 3 is similar to GPO 1 in that it uses the assigned applications section to push out some MSI files. Some are x86 and some are x64, so I selected the appropriate option so the x86 ones don't install on any x64 clients by accident.
So here's what happens... I'm intending for the policies to execute in the order I listed here. However, it seems that startup scripts execute at the very end of the boot process, before you get a logon prompt, but after everything else. So the old version gets successfully uninstalled, the new version gets installed, THEN my script runs, uninstalling the version that was just installed (I'm intending for the group policy to be authoritative and I'm trying to get rid of any "unauthorized" installs, which I want to do BEFORE GPO 3). I log on, everything is fine except for the fact that the application is uninstalled, so I disable GPO 2 and reboot, so GPO 3 will go into effect and reinstall itself (that's what it's supposed to do, right?). It says ""preparing network adapters" for a brief second, then BAM!!! Bluescreen.
Important points/notes:
-all of the MSI files are hosted on a UNC network share
-there are other applications that have been successfully installed via assigned applications. However, each of these policies only have one MSI each, and the problem only seems to be occuring with uninstalls
-I'm attempting a repair install on my workstation now. However, it's been hung at the "please wait" screen for a good 15 minutes now...
It seems like it might be due to some kind of corruption when doing uninstalls in a certain order. I've googled for an answer, but all I can find are vague references to paged pool memory, the SMB driver, and even CDROM drivers. What do you guys think could be causing this issue?
