Hi
I know this isn't specifically sccm related but it does happen via sccm.
I am upgrading some client software from an older version to the newest.
on a lot of machines I am seeing the following..
1. the application uninstalls the old software
2. somehow the process leaves behind the folder object.. by this I mean... the uninstaller actually removes the folder BUT somehow windows still thinks the folder is there.. all security settings etc. are wiped and there's no way to access the folder.. with
ANY account.
This means the new msi installation fails because it cannot access/create the same folder to install..
3. after a reboot the folder object is gone and the installation works perfectly..
Has anyone seen this kind of behaviour? and what can I do about it?
Kindest regards, Martin