2xclient-x64.msi Transform

V

vito1

Member
I have made a 32 bit transform and it works fine.

Due to the fact i need a special 2xclient install for my outside web portal, i created and msi with the transform already applied.

Again, this works fine for 32 bit client
BUT,
I Can not get the transform to apply with the 2xclient-x64.msi



Tools used
Ocra
Directions from 2x blog
Made transform
Applied transform back to the original msi using msitrans
http://msdn.microsoft.com/en-us/library ... 85%29.aspx
Same steps, but the settings are not taking. I can even see the size of the msi grow.

32bit worked, 64 bit did not


(unless there is a better way to apply the transform from the web portal msi)

Thanks for the help
 
Hi there,

there are 64 bit version of the 2xClient and 2xWebPortal.

Anyway, you might open a ticket, so we can investigate this issue.


Kind regards,
 
vito said:
I have made a 32 bit transform and it works fine.

Due to the fact i need a special 2xclient install for my outside web portal, i created and msi with the transform already applied.

Again, this works fine for 32 bit client
BUT,
I Can not get the transform to apply with the 2xclient-x64.msi



Tools used
Ocra
Directions from 2x blog http://www.2x.com/blog/2010/11/products ... ransforms/
Made transform
Applied transform back to the original msi using msitrans
http://msdn.microsoft.com/en-us/library ... 85%29.aspx
Same steps, but the settings are not taking. I can even see the size of the msi grow.

32bit worked, 64 bit did not


(unless there is a better way to apply the transform from the web portal msi)

Thanks for the help
Click to expand...


Please check again with the latest version. The 64 bit installation was improved, however I recommend to use server side client policies when possible
 
After working with support, there was a problem with the 64bit client.

using client side options:
This does not help with remote home users.
IE: i setup a user for their desktop with specific options for the network. User goes home and connects with their home computer that needs a totally different option set. (like not to save creds)

How does this work?
from what i can tell, it does not work.

The Options should be able to query computer names in AD and also have different options for connections from different gateways.
 
Although I dont understand your query, please check the secondary connections.
You can set different connection gateways and different mode so that if you are from home, office, pub, or where ever you can preconfigure a connection mode that works for you
 
Zippo,

Thanks for the reply but i do not understand what you are stating in your post.
First, this one client is running v9 vds and cannot upgrade till the agent problem is resolved from a ticket submitted.
Basically this is needed....
The system needs to apply different setting for internal vs external connections. (Computers)
Why? Because internal computers are controlled by IT policy. Some or most remote computers are not.
External computers that connect into the farm may not be part of the IT policies. A good example is the redirection of extensions. Turning this feature off for remote connections is needed so a user’s home computer does not lose file associations to local apps causing more calls into the IT help desk. Another would be to not allow saving of credentials for remote users for security. (Just examples, other IT departments may have different needs)
In V10 I see the secondary policy, but I do not understand what you are recommending in your post. Can you explain more or point me to a document? Note: we are not using Deepnet or safe net
Furthermore,
The client connection option is great, but how does the application server determine what settings to apply and when?
Example: I create a policy for jdoe and add all the setting i need.
How does 2x determine if jdoe is connecting from an internal computer vs an external user to apply correct/different settings?
If I create a group call "remote2xSetting" , add users to the group you still would have the same problem of the 2x server not knowing where the user is connecting from and applying the defined settings.
If you create more than one group I still see the possibility for addition problems...
Let's take the remote2xsettings group and add another policy for AD group "internal2xSettings"
Add the user to both. Here the idea would be to apply settings per group. What policy will the user get since they are a member of two different groups?
One way to do this would be for the 2x server client setting to query groups for computers. Then, you could make a group of internal computers and use it in the LDAP look up. Currently, this does not seem to work.
With this, you can setup a default policy for internal computers. If a user connects to the 2x farm on a computer defined with in that internal group AD group, the internal settings would apply.
Let me even take this a bit further,
You can extend this to internal departments that need different settings.
Example: What if Jdoe connects during the day on 3 different computers in a domain and all the computers need different 2x settings? How does this happen?
If I am missing how to configure this, please let me know.
Thanks
 
You must log in or register to reply here.
Back
Top