Mr B Jones added the comment:
All those logs came from one machine. SCCM is usually really good at detecting
the existence of an install by checking the package GUID in the windows
installed database, but getting the right GUID when dealing with a non-msi
install is sometimes hit and miss (with a pure MSI install, it just pulls
everything out of the MSI automagically). It can also check for the existence
of files/folders, and files with particular version numbers embedded in them
(though windows seems to display these version number differently than SCCM
sees them sometimes).
In this case I guess I got the wrong GUID, so it went on re-trying the install,
and all bets were then off. Usually the easiest way to get this right if it
isn't automatic from the MSI is install the package then look in the registry
for an uninstall or modify string which looks like "msiexec /x {GUID HERE}",
but if I remember correctly (and it has been a couple of weeks so I could be
thinking of the wrong package), the python installer doesn't do that.
When I'm back in work (from 9th), I can try it again SCCM.
Thanks for all your assistance.
Bryn
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29033>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
