Jump to content

Recommended Posts

Posted

So, I am revamping our deployment processing by using WIMs and PSADT. Sure it's a lot now, but should help easily update software down the line.

 

That said, I typically would use MECM's ability to supersede an app. For example Solidworks 2022 would have an uninstaller, and then when I create the 2023 app, it would reference the 2022 app. But this meant I had to keep 2022 going for a while, which just seems unnecessary now. Now I am in the process of uninstalling all previous versions of an app within the pre-installation section of PSADT.

 

For Solidworks, there is no all in one process of doing this. However, when building Solidworks with the admin image editor, there is an option to upgrade and/or uninstall a previous version, which means less work on my end. So, that's what I selected. So I ended up using that method so I can just call startswinstall and be done with it. When I do it manually and through the Software Center (when logged in), it works just fine. However, if a user never logged in and the app is required, it gets hung for some reason. Looking at the SummaryIMLog, it sets a registry key (which is just no feedback), and that's the last entry. Comparing that to a work install where it doesn't hang, it has the same line, but then a second later, the installer ends.

 

So, with ath being said, I was wondering was anyone else running into a similar issue? I could just monitor that registry key, and then kill the installer process, but it just seems crazy to me how this is happening.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...