- This topic is empty.
-
Posts
-
I have a RDS farm with two differents servers configurations (I have servers with office2003 and others with office2007)
All users can connect to the RDS farm with office2003 the connection is configured in the wnos.ini, but i have some users who needs to connect the RDS farm with office2007 (all users haven’t the permission to connect the office2007 farm)
How i can configure two groups of Thin Client who have differents wnos.ini configuration? (one with the connection informations for office2003 and the other for the office 2007)
Thanks
Don’t know why you have posted this in the WDM section but never mind.
How many client should have access to the 2007?CG
I post it here because there are no topic for configurations, and I think it’s maybe possible to make what I want with the WDM…
They are 90 clients to use the 2007. Actually this population connect to the farm with FatClient and .rdp
Thx
There are two easy ways to do this and one easy but expensive way:
– you create 70 machine based config files (mac.ini)
– you create two wnos.ini files, copy them on the same ftp server but in different folders, eg. /ftproot/wyse/2003/wnos/ and /ftproot/wyse/2007/wnos/
Now you assign the one or other wnos path to the appropriate clients.expensive way:
– you use WDM Enterprise and its Default Device Configuration (DDC) feature.CG
CSanta, did you get this working. I too am trying to deploy two different ini files. One for Xeniths and one for PC extender. I can get the Xeniths working fine but the PC Extenders will talk to WDM but not pull any config.
(Sorry Im new to all this)
I didn’t try the solution with mac ini file. I think it work but it’s too difficult to manage with all clients we have. I had already tried to make two folders with different config files but I was stuck on how to assign the correct path to the clients. How we can differentiate them in the WDM?
You will need WDM Enterprise for this. It has a feature called DDC (default device configuration).
CG
@ConfGen wrote:
There are two easy ways to do this and one easy but expensive way:
…
– you create two wnos.ini files, copy them on the same ftp server but in different folders, eg. /ftproot/wyse/2003/wnos/ and /ftproot/wyse/2007/wnos/
Now you assign the one or other wnos path to the appropriate clients.…
CG
Hi,
how assign to the path ?
if the wyse are in the same subnet, tag dhcp 161 and 162 are assign for one path no ?
- You must be logged in to reply to this topic.