This content has been marked as final. Show 6 replies
And does updating to the most current Patch #4 help the problem?
Hope this helps.
We did end up trying a newer tumbleweed version. that seemed to fix the problem. I am also going to look into the latest patch as well.
the latest patch did not fix the issue. i guess i will have to go with updating the tumbleweed program instead. I'm not sure what is causing the issue. I don't know if TW and MTM are competing during startup and MTM wins out or that they are not compatible. It seems to be happening only on older machines imaged in 2004 or earlier.
Did you ever find a fix for this issue? We are having the same problem with some of our machines. Thanks
The only thing that immed springs to mind is that the basic install of VSE may have different policies to your epo policies.
So perhaps tumbleweed is blocked under the basic package but when they then update with the latest access protection policies from EPO it is allowed again.
just an idea
what does the access protection policy log say on the machines it work on?
I pushed out the newer version of tumbleweed via startup script. everything seems to be running smoothly.