Hex Workshop 3.11 Deployment via MDT 2008
I'm trying to set up a silent installation for Hex Workshop 3.11 that also registers the software via a registry merge. I have managed to successfully do this on my own PC using both an unattended setup file, and through scripting with AutoIt 3.
The problem I'm running into right now is that neither of these methods work when I'm trying to deploy the software as an application on MDT. Once MDT reaches the point in the deployment where it attempts to install Hex Workshop, it just hangs until I wiggle the mouse a little bit, or move the deployment window around the screen.
I've attempted to duplicate this action using a script, hoping that by having the script move the cursor around a little bit, it would just continue the deployment as normal. This didn't work, unfortunately, but as soon as I put my hand on the mouse and moved it even slightly, the deployment continued normally.
I'm getting to the point where I may just run a batch file to copy/paste the completed installation folder and copy all the registry keys to the proper locations. I'd rather not do this because it just feels like a workaround rather than a solution though.
Has anyone ever run into an issue like this or does anyone have a suggestion on how to fix it?
The problem I'm running into right now is that neither of these methods work when I'm trying to deploy the software as an application on MDT. Once MDT reaches the point in the deployment where it attempts to install Hex Workshop, it just hangs until I wiggle the mouse a little bit, or move the deployment window around the screen.
I've attempted to duplicate this action using a script, hoping that by having the script move the cursor around a little bit, it would just continue the deployment as normal. This didn't work, unfortunately, but as soon as I put my hand on the mouse and moved it even slightly, the deployment continued normally.
I'm getting to the point where I may just run a batch file to copy/paste the completed installation folder and copy all the registry keys to the proper locations. I'd rather not do this because it just feels like a workaround rather than a solution though.
Has anyone ever run into an issue like this or does anyone have a suggestion on how to fix it?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Have you considered creating a proper package - re-packaging if necessary - instead of the current rather nasty lash-up you have now? Does HW come as an MSI? Does it, perhaps, extract an MSI (check %TEMP% and folders beneath %AppData%)? If so, you can create a transform for it which can include the .REG file's content.
If it's NOT an MSI and doesn't extract one, consider creating one using AppDeploy's Repackager tool.
If it's NOT an MSI and doesn't extract one, consider creating one using AppDeploy's Repackager tool.
Posted by:
gweatherall
14 years ago
Unfortunately it doesn't extract an MSI, and instead uses an InstallShield Setup.exe. I've managed to get it to silently install and add the .REG content using this method with an unattend file outside of MDT, but if I try to run it as part of a deployment, it hangs.
I'll try using the repackager tool, as I hadn't thought of that before. Thanks for the suggestion!
I'll try using the repackager tool, as I hadn't thought of that before. Thanks for the suggestion!
Posted by:
dunnpy
14 years ago
I've seen the MDT hang before, and so have other people on the net . There is a solution around an AutoIT script to move the mouse for you.
I could never pin it down to a particular app, so although Ian's (VBScab's) suggestion about packaging it may help it appears to be an MDT issue that's been around for a while.
Hope this helps,
Dunnpy
I could never pin it down to a particular app, so although Ian's (VBScab's) suggestion about packaging it may help it appears to be an MDT issue that's been around for a while.
Hope this helps,
Dunnpy
Posted by:
gweatherall
14 years ago
ORIGINAL: VBScab
Try using AppDeploy's Repackager!
This worked like a charm. I even managed to get the registry entries into the MSI without having to create a transform for it. The only issue I'm having now is that it doesn't create a start menu folder like the normal install does, but I'll keep playing around with it.
Thanks again!
Posted by:
anonymous_9363
14 years ago
Hint: Shortcut, Directory and CreateFolder tables, possibly the Component table as well, depending on how the repackager has built the MSI.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.