Thanks for this Detlev,
The only thing that prevents us from doing this is the lack of updates from SUS. We don't like the idea of different versions of the Inventory/SLM SMACCs floating around. It sounds like there could be some harmful consequences if individual users are left to update their own tools. Over time the versions will diverge and that sounds bad to us.
Would there be any chance of allowing SUS style updates for this Remote Administration scenario?
Another thing to note that isn't mentioned in this document is that if you do want to run this from multiple systems or move the console to another system you'll need the configuration file. Unfortunately the connection/configuration file is stored under the logged in user's %APPDATA%.
So if you and another admin want to use the same configurations, you would need to keep these in sync somehow. So even if you are running this off of a file share, you'll run into an issue with the configuration file. You would also run into this issue if User A logs into the system and configures an additional setting, then User B logs in and would not have both systems. Currently we have to write a script to copy this configuration file for each user which logs into the system so the multiple connections exist for all uses. (currently we manage quite a number of systems by many administrators).
My vote would be if this configuration file was stored within the SMACC folder structure or was able to be configured/saved somewhere centrally so it wasn't dependant on the user.
Something worth adding is that Computer C needs to be 64-bit as the files you are copying have no 32-bit version.
I have automated the process with a powershell script, which makes it easier to install the SMACC and update it. I've posted it here on the community in case it helps.
Retrieving data ...