Software Deployment

If you've lurked for a long time, you must surely be aware of the 'Package KB'? Wandering thither brought me to here, whereupon we can surmise that the set-up seems to pass arguments to MSIExec.EXE. So, try adding REBOOT=R ('R' means 'Really Suppress) to your command line.

Some of the other details in the KB may be of interest e.g. in the 'Notes' section, the suppression of the 'AutoDesk Customer Involvement Program' dialog.

Thanks for the reply

ORIGINAL: VBScab

If you've lurked for a long time, you must surely be aware of the 'Package KB'? Wandering thither brought me to here, whereupon we can surmise that the set-up seems to pass arguments to MSIExec.EXE. So, try adding REBOOT=R ('R' means 'Really Suppress) to your command line.

TBH I when I searched I clicked on here, I read the info as alternative installation method using the MSI file rather than setup.exe passing the information onto msiexec. I'll give it a whirl tomorrow when I'm back in the office.

Some of the other details in the KB may be of interest e.g. in the 'Notes' section, the suppression of the 'AutoDesk Customer Involvement Program' dialog.
here

Unfortunately due to office politics and organisational structure, other than modifying a few command lines here and there I'm not actually allowed to modify or interfere with the deployments themselves.

Thank you for the info though. And thank you for your help!

I wasn't suggesting that you changed the deployment but pointing out that the EXE seems to take standard WI arguments. Thus your command line could include the REBOOT=R property/value pair.

I know that, When I mentioned modifying the deployment, I was referring to the suppression of the 'AutoDesk Customer Involvement Program', I'm not sure why that wasn't quoted in my original reply to your post.

Also apologies for cross posting, my browser crashed out and I had enough time to hit back and copy my post to my clipboard, and then navigate my way back into the forums. It was completely unintentional, I must've either been navigated my way back into the wrong forum or looking at what had been cached, so apologies (It was about 6pm in my local timezone when I did so, it'd been a long day).