Hi Everyone
I'm rather stumped with SMS Software Deployment, basically I go through an application, package it accordingly to run silently remove EULA boxes change Registry Key settings. I do this with both MSI and EXE. Usually with EXE I use Inno Setup to place my registry keys and files, and than run the application with the silent switch within my Setup, with MSI I tend to create an MST or edit the Software Packages MSI directly. Ok with that all aside, I can run this software on my own machine from a commandline, (we use DFS Shares rather than Distribution Points, eg \\DFS_Root\Sharename\Package.exe)
Now I create a Package in SMS, Create my Program using the same Commandline as before, we are using a Managed Desktop environment (polite way of saying locked down environment) so I change the programs environment to Administrator, or if need the SMS Administrator for accessing network resources. I create a collection, Advertise it, Install the software, which works some of the time, But none of the HKEY_Current_User or userprofile settings are created. Now I understand that this is because the software is being installed as a System User, either Local Administrator or the SMS Administrator as I specified in the Programs Environment tab, so the HKEY_Current_User registry settings are being stored in HKEY_Users\.Default instead.
My question is how do you fix this? There is talk about using elevated privlages but means all the legacy exe will need to be converted to MSI. Problem is we have alot of legacy apps, + Microsoft doesn't recommend it.
The problem is driving me nuts, does anyone have any suggestions/solutions, best practice etc..
Cheers
I'm rather stumped with SMS Software Deployment, basically I go through an application, package it accordingly to run silently remove EULA boxes change Registry Key settings. I do this with both MSI and EXE. Usually with EXE I use Inno Setup to place my registry keys and files, and than run the application with the silent switch within my Setup, with MSI I tend to create an MST or edit the Software Packages MSI directly. Ok with that all aside, I can run this software on my own machine from a commandline, (we use DFS Shares rather than Distribution Points, eg \\DFS_Root\Sharename\Package.exe)
Now I create a Package in SMS, Create my Program using the same Commandline as before, we are using a Managed Desktop environment (polite way of saying locked down environment) so I change the programs environment to Administrator, or if need the SMS Administrator for accessing network resources. I create a collection, Advertise it, Install the software, which works some of the time, But none of the HKEY_Current_User or userprofile settings are created. Now I understand that this is because the software is being installed as a System User, either Local Administrator or the SMS Administrator as I specified in the Programs Environment tab, so the HKEY_Current_User registry settings are being stored in HKEY_Users\.Default instead.
My question is how do you fix this? There is talk about using elevated privlages but means all the legacy exe will need to be converted to MSI. Problem is we have alot of legacy apps, + Microsoft doesn't recommend it.
The problem is driving me nuts, does anyone have any suggestions/solutions, best practice etc..
Cheers