So either it is a problem with a domain policy or there's something screwy
happening on my PC. But knowing that isn't all bad.
I did as you suggested and fired up Win 2003 in a VM. Installed the
application, started it, and uninstalled. I then clicked Ignore when the
relevant nag displayed. The uninstall finished, did not prompt for a
reboot, but *did* remove the files on a reboot (not the folders).
This is good because I can independently show that the installer does what
it is supposed to do despite what it is doing on my own PC, and close the
issue raised by the QA dept.
Thanks very much.
On 11/26/06, Bob Arnson <[EMAIL PROTECTED]> wrote:
John Lalande wrote:
> This is much different than the behavior of my own PC. Is it possible
> that there is a domain policy causing this? Our IT dept has just
> started using AD to push applications and maybe they have added a
> setting the the Group Policy that they don't completely understand.
I hope not.<g> Can you try on a 2003 Server VM that isn't joined to a
domain?
--
sig://boB
http://bobs.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
