Register Login 
 
 

Please use the links on the top right of the page to register and log onto SmartAccessCentral in order to post in the forums.

epa factory complete banner.gif

Subject: Troubles creating an Eindpoint Analysis Solution
Forums Search
You are not authorized to post a reply.
Author
  Messages Sort:
Jupiler

New Member
New Member
User Online: User is Offline
Posted:15/12/2005 1:45 PM
Dear Sir, Madam,
 
We are trying to make a custom Endpoint Analysis Solution, but we are having some difficulties in programming and configuring. We have installed Visual Studio .NET 2003 with C++ and we are trying to develop the Solution with Visual Basic Script.
 
The Solution needs to check if a service is running on the client machine. If so, de local drives must be shown in the citrix desktop environment. Therefore we would like to make a custom Endpoint Solution and configure this in a citrix configuration policy.
 
The project contains two scripts (Clientscript.vbs and Dispatcherscript.vbs). The scripts are both executed (we have added a meganism of writing a file to the c:\temp). In the SDK there is documentation and there are examples, but certain lines of code in the examples do not match the explanation in the SDK (see: env.setenquiry for VBS).
 
We have a couple of questions:
 
1. How are the scripts executed by the citrix endpoint environment?
2. How can we make the client response visible in debug information?
3. Where can we find more information on this topic?
4. How does the meganism around "env.setfinal" works? Is the function RequestScan executed more than once? How (with which command) is the final result given back to the Citrix environment?
5. Where can we find the lines written by the env.Trace procedure (Endpoint Analysis Service Diagnostic Facility)?
 
For complete information these are scripts we made:
 
Clientscript.vbs
 

Function DownloadableEntryPoint(theInput)

Dim theOutput

Set sh = CreateObject("Shell.Application")

theOutput = sh.IsServiceRunning("CSAGENT")

DownloadableEntryPoint = theOutput

End Function

 

DispatscherScript.vbs

 

Private Function Enquiry(env)

env.Trace "~~~ Creating expression ~~~"

Dim exp

Set exp = env.CreateExpression("http://145.70.20.44/EndpointAnalysisPackages/CSAAGENT.cab/1.0/downloadable/ClientScript.vbs", "DownloadableEntryPoint")

env.Trace "~~~ Setting enquiry ~~~"

exp.SetName("ClientValue")

env.SetNamedEnquiry(exp)

env.Trace "~~~ Done ~~~"

End Function

Private Function Evaluation(env)

env.Trace "~~~ Getting parameters ~~~"

env.value("result") = env.value("ClientValue")

env.Trace "~~~ Done Evaluation ~~~"

End Function

Function RequestScan(env, params)

env.Trace "~~~ RequestScan Entered ~~~"

Dim final

final = env.IsFinal()

env.Trace "~~~ IsFinal probed ~~~"

If Not final Then

env.Trace "~~~ Not final ~~~"

Enquiry env

env.Trace "~~~ SetFinal ~~~"

env.SetFinal

Else

env.Trace "~~~ Is final ~~~"

Evaluation env, params

End If

env.Trace "~~~ Bye bye for now from RequestScan ~~~"

End Function

 

Thank you in advance for your comment/information.

 

Best regards,

 

Roland Gardeniers & Luc Stegerman

Joslyn

SmartAccessCentral Moderator
SmartAccessCentral Moderator
User Online: User is Offline
Posted:18/12/2005 5:12 PM

Guys,

I have written a script based end point scan that checks for the service name that you pass it via a parameter set within the Access Suite Console.

The EPA is script based although we would not usually recommend using script based EPAs due to the fact that the code is cached on the client.

To view the tracing you need to obtain CDFTrace.exe (available from Citrix support)

Have a look at my code which I have based on your code and let me know if you have any questions.

Tim


Tim Joslyn

Tim@smartaccesscentral.com

www.SmartAccessCentral.com
Jupiler

New Member
New Member
User Online: User is Offline
Posted:19/12/2005 7:10 AM
Thanx.... Its works fine......
You are not authorized to post a reply.


ActiveForums 3.0
  Home|Forums|Editorials|EPA Packages|Snippets
Copyright (c) 2009 SmartAccessCentral Terms Of Use Privacy Statement