- This topic is empty.
11. August 2007 at 22:53 #549
I’m 4.5.1 enterprise. Trying for first time to use DDC for WTOS–though I’ve used regular FTP server for a while now. I’ve read/downloaded the various white papers. Everything looks good. Except the device does not pull its config. I see an error in event log that states “cannot access system profile”.
My package imported successfully and my rsp file and folder names match. I set the ddc successfully to a “department” in the view i have set up. I moved the device to the “department” in question and i can otherwise discover/reboot/ etc the device in WDM. In the network properties on device I can see it is seeing my wdm server and it has listed my wdmserver as the ftp source….
What the heck am I missing? So far wyse has just pointed me to the white papers I have already….i’m really hoping I’m missing some simple that somebody can point out to me……..
One other question–in the example RSP files in the DDC for WDM 4.4.1 white paper it lists an Imagesize of 63 for a S10 device–why does it not use 16mb?? I’ve tried both with no success.12. August 2007 at 15:26 #9981
a few things to check:
– when your unit is checking in, how much flash does it report to WDM? Use this value in your .rsp file.
– in WDM go to Configuration Manager-Preferences-Device Preferences and check whether DDC is enabled there. Also check if under Blazer Preferences the checkbox to send wnos is checked.
– again Configuration Manager-Preferences-Logging Preferences select Debug level and control the Systemlog in the systemtray when your unit is checking in. Do you see a complete check-in or just a date and time with an empty field?
For more help, please post your wnos.ini, te .rsp file and your folder structure inside ftproot.
ConfGen14. August 2007 at 15:43 #9989
this issue has been solved and I’m posting the info as this might help others.
Newer S10 devices check-in to WDM and show as such in the system setting that they have 0mb flash, whereas my older devices show as 32mb. My older devices work fine as long as the imagesize in your script specify 32. Newer devices require a parameter in your wnos.ini…S10WDMFLASH=32 where 32 is a variable you can specify…i chose 32 to match my older devices. This is a result of some new board the newer s10 devices use.
The problem with this is that you can no longer use option tag 186 because that will cause the device to instantly check in with WDM and DDC will fail. You must first manually point it to a FTP share where you have some minimal wnos.ini which can pass the above parameter to the device. Then you can point back to WDM server and reboot and it will check in correctly and DDC as needed. I’ve asked Wyse for any further info as to this problem….that using DDC is now not quite so simple as it used to be. I will post if I learn anything new…..14. August 2007 at 16:30 #9990
Instead of using a wnos.ini parameter you can also modify your .rsp file to reflect “Imagesize=0”. Register the new .rsp file and assign it to a new DDC.15. August 2007 at 0:00 #9993thinkthinMember
- Total Post: 1707
- Jacked into The Matrix
All you will need to do is create 2 packages, one with the imagesize=32 and one with image size=0.
You can absolutely use the 186 tag, when WDM discovers the device if there is no DDC package it will send the device to the default path set up in the Return FTP/ini preferance in WDM. By default this is inetpubftprootRapportWNOS.
So in this location you can put a “default” config if you like so if a device does not have a DDC configured it will get a base setup. Doing it this way means you do not need a 161 and 162 tag at all on the network,
-TT15. August 2007 at 15:23 #9998
i was thinking of this very same thing in the shower this morning…have not tried it yet but this sounds like the way to do it.19. August 2007 at 1:02 #10013
OK, now i’m stuck trying to set up more than one ddc for wnos. I have all the documents on this site for DDC and view setup.
WDM 4.5.1 enterprise. I have a 2 layer view setup by Department (more than a dozen depts) and then by WNOS config (just trying to do two so far). Granted my brain thinks in tree style from AD, but i do think i have setup my views/groups correctly. I get the “A ddc for this OS and media size already exist. only one is allowed” message and cannot figure out for the life of me how to get more than DDC setup. I select the view by dept > wnos setup, browse to the group to apply, it preselects blazer for OS and 32 for size and then i pick my 2nd config from the dropdown list…i get the error instead of being able to apply a 2nd ddc. I cannot seem to wrap my brain around a particular statement in the white paper for setting up views that says, “At this point you could also apply the DDC, remember you import all your OS images and create a single DDC for your devices with the same flash size. You then use the CTRL key to highlight the views folders you wish to apply the DDC to. For additional information see the Rapport DDC documentation. It is a common error to try and have many DDC configurations; you simply have one that is used to apply any number of differing images or configurations to you different views. This is where have the correct view structure can be so important as devices must be grouped together that need the same DDC configuration.” I don’t get this–the documentation shows you setting up different wnos.ini files for different usage (legacy and Desktop), but then how the heck do you apply more than based on the quoted statement above. Apologize for my naivete, but somebody please show me the light! I’ve imported 2 packages–one for a wnos that does a kiosk style setup (and this works just fine for the DDC i setup), but how the hell do i apply the second config i’ve imported to other devices?? I guess int he documentation it shows setting up the DDC but does not spell out clearly enough for me anyways how to give different views or groups a different config.
I have a bad feeling this will be too difficult to explain to me… 😥19. August 2007 at 10:37 #10015
OK, here is the trick.
Open the DDC config. Select the view you want to use. Let’s assume this view is called “Functions” and it shows 2 different functions (Kiosk and Admin).
In the view click on “Kiosk” and then select your imported package for the kiosk mode.
DO NOT CLICK FINISH NOW.
Instead of finishing now select the second function called “Admin” and again select your corresponding package.
Now you can click on finish.
This way all units that are members on the group Kiosk will get the kiosk package and the Admin member units will get the admin package.19. August 2007 at 12:19 #10016
thanks confgen that is indeed the step i was missing….i never picked up in the explanantions that you define additional setups all within the same ddc. Now I can go to work tomorrow and not waste half my day pulling my hair out. Thanks again!6. September 2007 at 18:18 #10160
Is anyone having trouble with V10L models checking in to WDM? We’ve been having an issue for awhile that’s sporadic to say the least. The V10Ls do not always check-in at reboot, and sometimes hang at contacting HSERVER. If that happens they eventually show the unable to locate profile message. Sometimes they just simply don’t check-in at all. All of this obviously makes using DDC dificult at best. When they do check-in though, the DDC configuration works just fine.
The S10 models work perfectly fine in the same environment. We are currently running WDM 4.5.1 and this is the second server we’ve tried. I’ve been told by WYSE that a fix for this should be released in 4.5.2, but was curious if anyone else has seen the same? Basically just looking to see if anyone has a successful implementation of DDC with V10L models currently?
Steve6. September 2007 at 22:32 #10161
I was never able to get DDC with WDM 4.5.1 and V10L up and running. I am waiting for 4.5.2 also.
ConfGen11. September 2007 at 17:39 #10185
Thanks! Glad to know we aren’t alone in this one at least. This is the first time I’ve had confirmation that anyone else has experienced the problem. Hopefully the next release does the trick though. For now we are configuring the devices manuall unfortunately.26. November 2007 at 18:19 #10871
Anyone heard anything regarding the 4.5.2 release of WDM? I checked with our saled engineer a bit ago, but haven’t heard back. Just wondering if anyone has heard anything about a release date?26. November 2007 at 23:57 #10872thinkthinMember
- Total Post: 1707
- Jacked into The Matrix
No, its been delayed as there is a major re-write going on to fix up some of the ongoing issues as I understand it,
-TT27. November 2007 at 8:00 #10874
As far as I’ve heard it should be available by end of this year/beginning next year. So, another 5-6 weeks to wait.
- You must be logged in to reply to this topic.