This post is more than 5 years old
34 Posts
0
183502
Auto config of AppPortal
I know that it is possible to configure appportal with xml file via DNS record or registry key, but unfortunately non of those solutions are appropriates for us. So my question is, is it possible to deploy appportal to client through SCCM with pre-defined configuration. Maybe with some ini file. I was also thonkig about U3 version of AppPortal. Has anybody worked with it?
Thank's
Regards, Robert
DELL-David Y
228 Posts
0
January 31st, 2014 10:00
Hi Robert,
Thanks for the additional information.
We don't have a documented method for SCCM deployment but it may be possible to do this if it can be used to deploy using one of our existing methods.
One last option we havent mentioned so far is the ability to provide the config.xml as a file by email to the users, not the most automated method but it would be a simple approach.
Regards,
David
scott.knights
29 Posts
0
January 30th, 2014 23:00
Client configuration is stored in the registry under HKCU\Software\Provision Networks\Provision-IT Client\Server Farms. Each farm added is stored in a subkey called Farm1, Farm2, etc. You should be able to copy the values from a configured client and push these out to other users.
Scott.
DELL-David Y
228 Posts
0
January 31st, 2014 07:00
Hi Robert,
As Scott suggested you can export the registry keys from an already configured client, another option is to use our Group Policy template to configure the clients via GPO.
Will the users be launching a single full-desktop or is it a range of seamless applications?
If only a single application and the users will always be in the same location then you could look to deploy a pre-saved .pit file, this would contain all the connection information in a file and negate the need to configure AppPortal as it can be launched directly from the vWorkspace client.
If your users require anything more than a basic connection then U3 is not be recommended, if you are looking for the feature rich uer experience then it would have to be the full client.
Regards,
David
DELL-Andrew W1
378 Posts
0
January 31st, 2014 10:00
Hello,
Ok, you've stated that you can't update DNS but an easy option would be to push out a host file to the Client machines.
C:\Windows\System32\drivers\etc\hosts
This Contains a list of IP to hostname mappings.
Eg
10.10.122.4 vworkspace.fqdn
When AppPortal starts, it tries this http://vworkspace.fqdn as a generic address for downloading the xml file.
So, if you deploy the host file so that the address resolves to an IIS server hosting the config.xml, this group of machines will download their config.xml and it won't affect anyone other part of your domain.
Thanks, Andrew
Robert9111
34 Posts
0
January 31st, 2014 10:00
Hello David,
GPO is also not an option in our case, because we are just a small OU in worldwide AD forest, and is practicly impossible to implement a custom GPO for our OU. For DNS record we have a naming convencion which require that all records begin with site name and then server name..
At the moment maybe the best option is registry key import, because clients will use a range of seamless window apps, but here is a problem that a registry entry is now in HKCU, a few version ago it was in HKLM (There is still an error in admin guide for v8.0, saying the key is HKLM). So we should apply this registry every time user logs in. This is not what we like.
Is there any undocumentet trick to set a client config system wide, not user wide?
As I said, idea is to deploy and push AppPortal client together via SCCM.
/R
Robert9111
34 Posts
0
January 31st, 2014 11:00
Thank's David,
We've figure something out.
/R.