Unsolved
This post is more than 5 years old
37 Posts
0
188403
August 7th, 2013 15:00
AppPortal fails to connect
I have a goofy issue.
Our setup
vWorkspace 8.0 running on Windows Server 2008 R2
Clients are Windows 7 (mixed at being 32bit, 64bit, Professional, and Enterprise)
Issue
Launch AppPortal with no Farm configuraton and it loads from the config.xml file automatically
Everything works fine at this point
Close out AppPortal
Re-Open it and get "Connection to [farm name] failed"
I can delete the Farm and it will go through the same circle - work and then fail
I have tried manually creating the the config; however, I get the same issue after that
It appears that after a first successful connection - the "Location" properties get removed - Location Name, Port, and broker
Any ideas?
Robert9111
34 Posts
0
August 8th, 2013 05:00
Are you using the latest build of connector for windows? I have an identical situation but for linux connector, it turns out that it was a connector version issue and the lates version thwn worked fine.
Maybe you could try with PromptForLocation=1 in config.xml, that stand for manual connect to farm
Robert
DELL-Andrew W1
378 Posts
1
August 8th, 2013 10:00
Hi Mike,
If you start AppPortal like this:
"C:\Program Files (x86)\Quest Software\vWorkspace Client\pnap32.exe" /autodelete
It will wipe out the Config automatically each time you close appportal.
Next time you open it, it will redownload the config.xml and carry on working.
To fix the actual problem, rather than avoid it, How did you generate the config.xml ?
Can you try manully setting up AppPortal and then clicking on "Export" to generate a new config.xml file ? Once you have this, try deploying the settings using this one instead and let us know if the issue goes away.
Thanks, Andrew.
hfmike1
37 Posts
0
August 8th, 2013 11:00
Robert, it is the latest build. I had this issue prior to a rebuild of our vWorkspace server also.
Andrew, That is actually how I created the config.xml. Manually set up the connection on my system and then exported to the server.
This is not happening to every system - it only happens to a majority of the systems in our China facility.
Everyone in US and the UK work perfectly. I think the systems that are affected are ones that were built using an image - using Windows Imaging - and I do not believe that the people that did these systems with the image created the image very well. I have tried to 'Sysprep' one of the systems and I come out with the same issue after a little bit. One system that did have this issue, had to be rebuilt and it was not done as an image - works perfectly now.
DELL-Andrew W1
378 Posts
0
August 8th, 2013 12:00
Hi Mike,
Take a look at
HKEY_CURRENT_USER\Software\Provision Networks\Provision-IT Client\Server Farms\Farm1
You'll notice the Subkeys "Location1" etc
What happens to these, does the whole content disappear or just some of it or does it appear to be set and valid still ?
Are they also trying to set the settings through an ADMX file ? We've had problems if you don't fill out all the options in the Group Policy and it ends up invalidating the settings.
Thanks, Andrew.
hfmike1
37 Posts
0
August 8th, 2013 13:00
No GPO involved
Yes, all of that info gets wiped in the HKCU settings.
For the time, I am going to go with the /autodelete parameter on the shortcut.