- This topic is empty.
25. February 2009 at 16:16 #1910titansMember
- Total Post: 1
It’s my understanding i can create seperate wnos.ini senario’s through DDC.
Do I create an RSP > Package, then enforce it with DDC? If so how do i go about doing this. I’m not quite sure i know where to go. Anyone that’s done this that may have examples?
Thanks!3. April 2009 at 15:47 #15612
Sorry, for not coming back to you earlier. I must just have overseen your post.
If you not already managed to do it, you can find the needed packages and info on my website (look for “How to configure WTOS Default Device Configuration engl.” and in the Download section for the examples”
CG6. May 2010 at 6:27 #18289
Ive read the “How to configure WTOS with WDM 4.7.2 Default Device Configuration” document and applied what it says to my WDM installation.
But I am struggling to see how the seperate wnos.ini files are defined and utilised.
I dont see any mention at all about the wnos.ini file and how we define it per groupsthin clients.
Is it the way the ftp folder structure needs to be set out? If so can you please explain in a little bit more details.
At the moment all thin clients are picking up a default one I made in “C:Inetpubftprootwysewnoswnos.ini”.
Thanks in advanced.
Loris.6. May 2010 at 10:18 #18293
As described in detail in the mentioned document you have to use WDM Enterprise.
Then you import the needd package (some demo packages can be found on this website). Part of each package is a wnos.ini. You can modify this wnos.ini the way you like it and also put your firmware file in there if you want.
Now follow the steps in the doc on creating the DDC and assigning it to the clients.
CG6. May 2010 at 11:06 #18295
Ive done a search for some demo packages but there is only one on this site called gkey for WTOS.
This package does not have a wnos.ini file..6. May 2010 at 14:01 #182978. May 2010 at 13:26 #18326
Thanks for pointing me in the right direction, i got it to work now.
- You must be logged in to reply to this topic.